47 items tagged “accessibility”
2007
The longdesc lottery. Mark Pilgrim is now writing for the WHATWG blog. Here he makes the case for replacing the longdesc attribute with a better solution, based on ten years of developer ignorance and misuse. As always with that site, check the comments for a microcosm of the larger debate.
html4all. New mailing list / advocacy group focusing on accessibility issues relevant to HTML 5. This is something that the core HTML 5 group have taken a lot of criticism for, although it’s unfair to say that they don’t care about accessibility (they are however challenging a lot of sacred cows).
I've actually been using the latest version of JAWS recently, as part of my work on HTML5. From a usability point of view it is possibly the worst software I have ever used. I'm still horrified at how bad the accessibility situation is. All this time I've been hearing people worried about whether or not Web pages have longdesc attributes specified or whatnot, when in fact the biggest problems facing blind users are so much more fundamental as to make image-related issues seem almost trivial in comparison.
Why the Alt Attribute May Be Omitted. “The benefit of requiring the alt attribute to be omitted, rather than simply requiring the empty value, is that it makes a clear distinction between an image that has no alternate text (such as an iconic or graphical representation of the surrounding text) and an image that is a critical part of the content, but for which not alt text is available.”
WCAG Samurai. Anonymous Samurai, headed up by Joe Clark, publish their errata for WCAG 1.0 (with two independent peer reviews). Recommended as a better alternative to WGAC 2.0.
hAccessibility. The use of the abbr element in hCalendar causes screen readers to read out an incomprehensible number instead of a date.
New Dutch accessibility law. Sounds extremely forward thinking, designed by people who really understand the field. Just one problem: the guidelines are only available in Dutch!
2005
Greasemonkey for personalized accessibility. Why Greasemonkey is the perfect tool for client-side accessibility enhancements.
Gecko Info for Windows Accessibility Vendors (via) “This FAQ explains how makers of Windows screen readers, voice dictation packages and magnification software can support Gecko-based software”
2003
Accessible Python
A post on Bryan Richard’s blog about Safari leads to a query about whether or not Py (a Python print magazine) should move to PDF, which in turn leads to a fascinating discussion about the accessibility of both websites and Python source code itself. Well worth taking the time to read.
Better DHTML navigation
Adrian Holovaty demonstrates how standards compliant code and effectively written javascript can decimate the size of a clunky navigation interface, and make it more usable and accessible to boot: Web standards improve 2theadvocate.com navigation.
Using page titles properly
Adrian Holovaty eloquently demonstrates why real page titles (as opposed to titles stuffed with meaningless marketing keywords) are so important, using local entertainment listings as his example. One site that would do well to take his advice (despite not being in the entertainments listings business) is The Register, which has been failing to provide story headlines in page titles for as long as I have been visiting it. This is almost certainly a flaw in their content management system, but in 2003 it is an inexcusable error to make.
2002
Pull quotes and page titles
Adrian Holovaty has followed up his discussion of page titles on news article pages with a look at the oft-abused pull-quote. Adrian points out how pull quotes can lead to poor accessibility for text browsers and screen readers, and suggests that providing a “skip quote” link could help improve things. Adrian’s comments section attracts a number of professional web deverlopers working on all kinds of news sites so the discussion is likely to be well worth watching over the next few days.
Newspaper sites and the link element
Adrian Holovaty advocates the usage of next/previous link elements on newspaper sites to add optional linear navigation. His comments include some interesting discussions on whether or not this feature would really be of use on that kind of site.
IBM accessibility center
IBM’s Accessibility Center has a plethora of useful information and resources, including a free 30 day trial of their Home Page Reader text-to-speech browser software.
Alt all the way
Mark says that today is the most important day of his whole accessibility series, and who are we to argue? The topic is the alt attribute for images, and the message is simple: Every image should have one, even if the image is there purely as layout decoration (in which case an empty attribute should be used). Surprisingly Mark does not give advice on chosing text for the attribute but he does provide an excellent further reading list, which includes Hixie’s superb Mini FAQ About The Alternate Text Of Images.
More tips from Mark
Time to catch up on Mark Pilgrim’s accessibility tips. Four have been added since I last checked, so I’ll go through them in turn.