64 items tagged “accessibility”
2007
Ignorance and inspiration. I’m pretty gobsmacked at the levels of ignorance about web accessibility out there—it’s not that hard people! I’m obviously more out of touch with mainstream developers than I thought; I was under the impression that people had generally got the message.
Google Maps, HTML version. Google’s mostly undocumented accessible version of Google Maps. Robin Christopherson demonstrated this yesterday at FOWA.
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
Conversations with Joe Clark
Jonathan Delacour is three days in to his Conversation with Joe Clark series (see also parts one and two and the introductory book review). I thoroughly recommend reading the whole series, but here are a few points that stood out for me:
[... 786 words]Joe Clark interviews
On Monday, Slashdot posted an excellent in depth interview with Joe Clark, author of Building Accessible Websites. In a fantastic display of cluelessness they pasted the XHTML document which Joe sent them straight in to the Slashdot template, <html> tags and all. The good news is that there’s more Joe Clark related goodness to come, courtesy of Jonathan Delacour:
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.
Accessible headers
Mark’s latest accessibility tip concerns header tags (<h1> through <h6>). Mark explains that using headers in the right order helps screen readers to interpret the structure of your pages, and shows how to use CSS to effectively style headers. Mark once again demonstrates the comment hack as a way of bringing Netscape 4 in line with other browsers, a technique that has been criticised by the More Like This Weblog as unnecessary encouragement for NS4 users. Incidentally, Johannes Koch has an excellent summary of CSS hiding techniques.
Accessible fonts
Mark has out-done himself today with his long awaited coverage of relative font sizes. This is a notoriously tough topic (thanks to a whole bunch of strange CSS bugs and browser differences) but Mark carefully and comprehensively explains the various work arounds and CSS hacks needed to get the right effect with maximum accessibility.
Jonathan on longdesc
Jonathan has insider knowledge that Mark will not be covering the longdesc attribute in his accessibility series. This it not because longdesc is not a useful accessibility tool, but simply because it does not fit the “fire and forget” nature of Mark’s series. Jonathan’s post discusses longdesc and the difficulties involved in adequately describing an image.
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.
Final table tip
A final table tip from Mark: Providing a summary for tables. Mark explains the summary attribute which should be attached to every <table> tag to summarise the purpose of the table. Tables used for layout should include an empty summary attribute to show they are layout tables (in a similar way to empty alt tags for layout images). The summary attribute is only used by text to speech browsers, so I’m slightly confused as to why it should be included for layout tables—surely if the attribute is empty a speech browser will skip tstraight over it as if it wasn’t there?
Accessible tables
Mark has been educating us on the accessible way of marking up tables, with particular reference to calendar tables on blogs. My blog doesn’t have a calendar (yet, I’m considering adding one) but Mark’s articles have brought up some interesting things that I was previously unaware of. Giving your calendar a real caption explains the <caption> tag, which can provide a useful (and easily styled) caption for any table. Using real table headers explains how <th> tags are interpreted by speech browsers and shows how they can be used in conjunction with the abbr attribute to create more accessible table columns.
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.
Additional navigational links
Today’s accessibility tip: Providing additional navigation aids. Mark explains the concept of “relative” links using the <link> tag, which can be used to provide shortcuts to the next and previous page in a sequence as well as links to a site’s homepage. He also provides instructions for implementing them in Moveable Type, and asks for suggestions as to how it could be done in Radio. These links are not rendered in the actual body of a page but can be used by many browsers to provide additional navigation aids. My blog has these already but only as shortcuts to my categories and a link back to the home page—I haven’t yet implemented them for next/previous buttons while browsing the archives (which is arguably their most useful ability). Time to get hacking...
Day 8: page titles
Day 8: Constructing meaningful page titles—the accessibility tips are flying thick and fast now. I’ve always been conscientious of my page titles (after all, they’re all you get when when you use your browser’s history feature) but it seems I was not quite conscientious enough. My titles now all carry a reference to the name of the blog in addition to a description of the page.
Mark replies
Mark mailed me in response to my query about limiting his accessibility series to weblogs rather than expanding it to cover general sites:
[... 176 words]