I found a great article from Digital Web on the frustrations of getting the client to understand the need for web accessibility.
10 Reasons Clients Don’t Care About Accessibility
What are your thoughts?
Techniques and discussion on setting the tabbing sequence and creating access keys for elements on your HTML page.
- W3C Checkpoint 9.4 (Priority 3)
- W3C Accesskey Attribute
- W3C Tab Index Attribute
- WebAim on Keyboard Accessibility Enhancement
Sample Code:
So, you’ve done all you can to make your site fully accessible. And now you have to test it! There are many different methods and opinions of what the best way is, as Dennis explains, and auto-checker applications are only a small piece of the pie.
Great tools for testing web accessibility:
- Cythia Says
- A-Prompt
- Watchfire WebXACT
Firefox Web Developer ToolbarAccessibility Toolbar (IE 5+)- Testing with Screenreaders from WebAim
- WAVE from WebAim
- ATRC Web Accessibility Checker
- Opera 8
UDPATE AUG 2009!
Categories
Terminology Explained
Clearing up a few strange terms related to accessibility.
- A user agent is the client application used with a particular network protocol.
- Device independent means a user can perceive and interact with the Web through any type of apparatus (mobile phones, PDAs, interactive television systems, etc.). Device independent on Wikipedia
- Assistive Technology (AT) is a generic term that includes assistive, adaptive, and rehabilitative devices and the process used in selecting, locating, and using them.
- A deprecated element or attribute is one that has been outdated by newer constructs.
Categories
Skip-Nav Technique
The “skip-nav” technique is a method for the online cursor to jump over a group of navigation links, usually a site’s main menu.
Download Web Axe Episode 6
Links:
Sample code:
Skip navigation
...[header and navigation links]...
Heading
This is the first paragraph