A A A A A

(Inactive) Web Best Practices: Teleconference Details

Teleconference details

Agenda

1.0 Call Next Week
  • Anyone will to chair the call

2.0 Review updated conceptual model of web accessibility evaluation

3.0 Web Accessibility Coding Practices
  • http://trac.web-accessibility-best-practices.org/wiki/design/features
  • Purpose of Resource
    • Support resource for OAA web accessibility tools (Primary)
    • Support features and terminology of the conceptual model for web accessibility evaluation (Primary)
    • Complying with WCAG 2.0 (Primary)
    • Using HTML4/HTML5 web standards (Primary)
    • Optimizing usability by people with disabilities (Primary)
    • Supporting “Responsive” web design to adapt content to the capabilities of different devices, including assistive technologies (Secondary)
  • User Scenarios
    • Web application developers (HTML/CSS/Javascript)
    • Web developers (HTML/CSS)
    • User interface designers
    • Content providers
    • People with disabilities
    • Administrators

Minutes

1.0 Call Next Week
  • JG: Anyone interested in chairing call (none)
  • No call next week (June 6th), next call will be June 13th
  • Introductions

2.0 Review updated conceptual model of web accessibility evaluation
  • NH: Over view of the conceptual model for web accessibility evaluation
  • TW: I have been trying to get my head in the game
  • TW: Is a node result for a specific element and page results are for a whole page
  • NH: A page result can have node results, one example is the main landmark rule, you have to look at all elements until you find role=“main”, if it doesn’t pass there are no node results, if does you can pass
  • TW: That is really helpful
  • TB: Can a page have a conflict with a page result and element result
  • JG: Every rule stands on its own
  • JG: Any other questions or comments?

3.0 Web Accessibility Coding Practices
  • JG: Can people go to the link
  • JG: Review of purpose
  • HR: We need to include real developers
  • JG: How do you propose to do that?
  • HR: People can bring developers on board
  • TW: I agree with you, we have a significant number of developers, how to bring them
  • MB: How do we organize the practices, I have something prepared, but I have some assumptions
  • MB: For a we developer has landed at these practices, what is there biggest need?
  • MB: Can we go around the room..
  • TW: 1. Concrete development procedures, coding examples
  • TW: 2. These practices have a return on investment, other than good will
  • TW: 3. They want good tools that help them understand accessibility in their work flow
  • Ranti: MSU has similar concerns, we do not have checklist, we just say follow WCAG 2.0
  • Ranti: How do make sure we are making progress and that it is working
  • MB: Similar things, a list of steps, hopefully numbered
  • MB: Most people coming to the site want to know where to start, a priority
  • MB: We should have categories (Rule Categories)
  • MB: Practices need to mirror the categories used by the tools
  • MB: In order of PSU importance:

  1. Image Descriptions
  2. Form Controls
  3. Headings
  4. Link Text
  5. Data Tables
  6. Colors & Fonts
  7. Abbreviations and Language
  8. Reading Order
  9. Keyboard Operability
  10. Audio Transcripts
  11. Video Captions
  12. Web Animation (i.e. Flash)
  13. Error Prevention & Correction
  14. Flashing-free Content

Participants