The moving cursor writes, and having written, blinks on.
You are currently browsing the yearly archives for 2007
“CAPTCHA” is an acronym for “Completely Automated Public Turing test to tell Computers and Humans Apart”and is a test for determining whether a given user is a human being or another automated system. The tests are based upon the concept that a computer will not be able to respond correctly to certain kinds of questions. If the correct solution is entered, the presumption is that the respondent is human. On this basis, CAPTCHAs may be considered when you want to prevent automated systems from gaining access to specific web services such as using an online contact form, registering for an online account or posting on a forum.
What is the best way to construct a “Read more” link?
Site news, blogs, article archives. These are all examples of situations in which it is common to publish a small text extract (or “teaser”) from a piece of content followed by a link to the full, uncut, version. The problem we have, from an accessibility point of view, is that we need to avoid repetive link text. The common solution, as suggested by WCAG 1.0, is to use the title attribute to distinguish the links.
I’ve just been reading Gian Sampson-Wild‘s article Testability Costs Too Much on A List Apart,=. she has raised an issue regarding the impact of testability upon the decision to include, or omit, some success criteria. It certainly makes for slightly disturbing reading.
I’ve had some vague feelings on unease about WCAG2.0 for a while now. Whilst I was able to highlight some issues in the earlier draft and there are signs of an improvement in the current draft, I’ve still been unsure about the overall approach for reasons I couldn’t specify. Having read what Gian has to say, I think she’s hit the proverbial nail.
Victor Tsaran is an accessibility engineer at Yahoo! who focuses on developing best practices for the creation of websites that work well with screen readers. In this video, he provides an introduction to some of the things that work well in the world of screen readers and others that fare more poorly.
If you haven’t seen a screen reader being used, I strongly recommend that you take the time out to watch this video (duration: 27:23). It will help explain why issues such as list markup and correct use of header elements is so important when developing an accessible web site.
Further to my previous post, I’m continuing to read through Gian Sampson-Wild‘s technical review of the WCAG Samurai Errata. This time, I thought I’d look at the issues facing users with cognitive disabilities.
Like Gian, I’m also a little disappointed that WCAG Samurai didn’t seize this opportunity to correct some of the oustanding problems with WCAG 1.0 as it relates (or doesn’t) to users with cognitive disabilities. That said, I acknowledge that a bit of short-term tinkering is woefully inadequate if we want to address the needs of these, largely overlooked, users properly. But I think we can make a start now if we then follow it up with a full scale investigation later on. One potential benefit would be raising the profile of these users sooner rather than later. If we can get designers to start thinking about users’ needs, so much the better.
I’ve been reading through Gian Sampson-Wild‘s technical review of the WCAG Samurai Errata and she seems to have picked up on most of the points that I noticed but is perhaps over-critical in other areas. In this post, I’ll confine myself to looking Gian’s comments under Accessible Technologies.