Writing accessible HTML has moved from being a pain to something that most companies recognize as important, if difficult. One of the biggest problems with accessibility is that there are so many ways you can affect the accessibility of a Web page. Unlike HTML validators a lot of accessibility is subjective. In other words, an accessibility validator can tell if there is missing alt text on an image. But it can't tell if that alt text actually describes the image or if it's just gobbledegook. You might create color blind friendly Web pages, but the text inside is so obscure that it can't be accessed even by the person who wrote it.
That's where the Accessibility Wizard comes in. You tell it what your role is in creating the Web page, and what level of accessibility you want the page to function at, and this wizard will tell you what you need to pay attention to. For example, if you're an Information Architect creating dynamic features on a AA-conformance site, you need to remember not to create auto-refreshing pages, use W3C standards, and avoid deprecated features. And the wizard will go into as much detail as you need to help you fulfill your role.
- Find out your part in accessibility with the Accessibility Wizard
- Validating for Accessibility
- What do the Accessibility Guidelines Mean to Me?
- Low Vision Web Page Layouts
- Does the Accesskey Attribute Improve Accessibility?
- See previous software picks of the week
Comments
No comments yet. Leave a Comment