Our web applications can suffer from inaccessibility problems due to inherent markup limitations. Martin Kliehm helps us sort through the WAI specs for Accessible Rich Internet Applications (ARIA) to increase usability.
Space constraints can put the squeeze on accessibility and usability. Mike Brittain shares his method for making itty-bitty forms more accessible and easier to use.
Could accessibility guidelines and practices be improved by greater emphasis on user research? Maurizio Boscarol thinks the answer is probably “yes.”
Forms are a pain. You can make them pretty, make them accessible, or go a little crazy trying to achieve both. Nick Rigby offers a happy solution.
Molly Holzschlag explains how the practices you already use to create standards-based, accessible websites can serve you in the growing field of internationalization.
The W3C’s Web Content Accessibility Guidelines (WCAG) are about to be updated for the first time since 1999. Joe Clark takes a close look at WCAG 2 and reports back.
Nifty web maps powered by Google and Yahoo! APIs are all the rage. And rage is what a visually impaired user may feel when trying to use them. Is there a way to make beautiful web maps accessible? In a word, yes.
acronym element is missing in XHTML 2.0. Internet Explorer 6 ignores the
abbr element. JAWS doesn’t like
dfn. AAA-level compliance requires you to find a solution. Make it work.
It’s no coincidence that search engines love highly accessible websites; in fact, by designing for accessibility, you’re already using effective search-engine optimization techniques. Andy Hagans explains yet another reason to pay attention to accessibility.
PDF accessibility is not as straightforward as HTML accessibility. But it can be done, if you put the same care into marking up your PDFs that you put into marking up websites.