Warning: include(top.html): failed to open stream: No such file or directory in /data/www/world/accessit/print.html on line 3

Warning: include(): Failed opening 'top.html' for inclusion (include_path='.:/wwwudev/world/doit/Kb/Incs:/www/world/doit/Kb/Incs') in /data/www/world/accessit/print.html on line 3
Are there accessibility guidelines for web browsers?

Are there accessibility guidelines for web browsers?

DO-IT Factsheet #1154
/articles?1154

Web browsers fall under the category user agent, which the World Wide Web Consortium (W3C) has defined as follows:

Any software that retrieves and renders web content for users. This may include web browsers, media players, plug-ins, and other programs—including assistive technologies—that help in retrieving and rendering web content.

In order for web content to be accessible, web content designers must design accessible content, and user agents must be able to deliver that content in an accessible way. The W3C, through its Web Accessibility Initiative (WAI™), has developed guidelines for both parties. Guidelines for designers include the Web Content Accessibility Guidelines [1] and XML Accessibility Guidelines [2]. Guidelines for user agents are the User Agent Accessibility Guidelines [3] (UAAG). A user agent that conforms to these guidelines will promote accessibility through its own user interface and through other internal facilities, including its ability to communicate with other technologies (especially assistive technologies). Furthermore, all users, not just users with disabilities, are expected to find conforming user agents to be more usable. Below are the twelve guidelines contained within UAAG 1.0:

  1. Support input and output device-independence
  2. Ensure user access to all content
  3. Allow configuration not to render some content that may reduce accessibility
  4. Ensure user control of rendering
  5. Ensure user control of user interface behavior
  6. Implement interoperable application programming interfaces
  7. Observe operating environment conventions
  8. Implement specifications that benefit accessibility
  9. Provide navigation mechanisms
  10. Orient the user
  11. Allow configuration and customization
  12. Provide accessible user agent documentation and help

The following AccessIT Knowledge Base articles may also be of interest:

References