The UK and other countries in and outside of Europe are making progress towards more web accessibility. Most recently, the 25 European Commission member states and nine accession countries announced a plan that could make accessibility in e-procurement mandatory. Hoorah! Let’s hope it goes into action, and the U.S. takes similar action sometime soon.
Author: Dennis
Why the Title tag is so important for Accessibility as well as SEO and usability.
- screenreader/text browsers
- visual anchor
- bookmarking
- printing
- SEO
- search results
- tip: use character encoding for special chars
- tip: use “>” or “:” to separate sections
Download Web Axe Episode 21 (Title Tag)
Related links:
- Constructing meaningful page titles
- The Usable Page Title
- W3C Quality Assurance
- Building the Perfect Page
- 7.4.2 The TITLE element
WebAIM Site Redesign
One of my favorite resources, WebAIM, has recently re-launched its web site! WebAIM has provided an excellent article documenting the redesign which explains the goals, processes and decisions made during the 9-month project. The relaunch is an excellent example of a well-coded, usable, and accessible web site. Good job WebAIM!
PS:
The new site features a blog where I left a comment on the blog entry about the redesign. Apparently there’s also an “email discussion list” about it on the site relaunch with more entries.
W3C’s WAI WCAG 2.0
What the hell does that title mean? To translate, it means that (warning: read slowly if this is all new to you!):
The The World Wide Web Consortium (W3C) is on the verge of releasing the first major update (since 1999) to their Web Content Accessibility Guidelines (WCAG) under their movement called the Web Accessibility Initiative (WAI).
The nearly complete revision of the “official” guidelines on web accessibility has taken a big hit from Joe Clark, a well-know accessibility and standards guru. I find the guidelines pretty technical, quite extensive, and organized from a different perspective. But at least the Checklist is still quite usable.
I’m not defending the W3C, but I suppose the lengthy time it took and the wordy, complex language is a product of the massive, highly corporate authoring process. Sad, but true.