Too much accessibility

Post details

By bim
Before being accused of blasphemy, let me explain. It's my view that some HTML attributes, or techniques designed to improve accessibility, are often over-used or over-helpfully chosen, resulting in content that is less, rather than more, accessible. Perhaps this over-egging of the pudding stems from web authors being unaware of how disabled users interact with their web sites. Or perhaps they don't fully understand what the techniques achieve and how they function. Either way, it's an awful waste to have such good intentions so badly misdirected.

As a user of two different screen readers as well as screen magnification, and being a regular user of keyboard commands for navigation, I've a vested interest in casting light on this knotty subject. So let's point a glaring spotlight on some of the ways that functional inaccessibility can result from misuse of, what should be, accessibility-enhancing techniques. Each of the culprit techniques or attributes will get it's own blog article.

If you've got a favourite, or least favourite, technique that needs a little light shed on it, get your torch out and add it to the list. To originate an article, just e-mail it to: bim.egan@rnib.org.uk with "too much accessibility article" as the subject line, and I'll post it with a link back to you.


Comments (7)

Tag: Too much accessibility

Posted at: 6/09/2006 4:13 PM by Sarah Raisanen

my (least) favourite

patrick h. lauke said
completely redundant title attributes on links that just reiterate link text, and even worse put "click here" or "link to" in there

table summaries that explain how many rows/columns are in the table...this is the job of the AT to expose to the user, i'd say

well meant, but useless, ALT attributes on those pesky stock photography type images that are nothing but visual fluff; yes, they visually convey a certain mood or whatever...but i'd argue that this mood should also come through in the written copy of a site, thus not seeing the image doesn't mean that the character (quirky? serious?) is lost

tabindex where natural control of flow through markup order is far more appropriate

overuse of fieldset and legend to put around a single form element, rather than a set of checkboxes etc

Posted at: 3/8/2010 3:23 PM by Sarah Raisanen

Text only pages and more...

JackP said:
I'm surprised no-one's yet mentioned that old favourite:
Text only pages

target="_blank" (in general)

Advising that clicking on an email address may launch an email application 'in a new window'

non-link | characters | between | links | when | you | could | just | mark | them | up | as | an | inline | list

Then we've got

Alt attributes that begin "a picture of..."

Including accesskeys but using display:none so they don't get in the way
summary="layout table"

not knowing what the difference is between a server and client side image map, and producing redundant
text links for virtually everything

And the last two are more attitudes than features, but nonetheless...
people who don't realise that certain "until user agents..." clauses have now been met

anyone that tells me to "upgrade to a new browser" simply because I've switched javascript or css off

Posted at: 3/8/2010 3:26 PM by Sarah Raisanen

JAWS

bruce said:
Can we have a parallel series called "not enough accessibility" which looks at how JAWS and its rivals fail with useful bits of html?

Posted at: 3/8/2010 3:28 PM by Sarah Raisanen

Many thanks

Bim said:
Many thanks to all for useful and valid comments, some of the points raised by Patrick and Jack are already in the plan for the series, including:
* Unnecessary summaries and captions in layout tables
* How TABINDEX can make nonsense of the tab order,
* The craziness that too often results from using TITLE attributes.

The other issues raised can be added to the "to do" list, but if you want to originate an article, just e-mail it to
bim.egan@rnib.org.uk
use "too much accessibility article" as the subject line and I'll post it with a link back to you.

Bruce's comment's could spark another illuminating series, got any examples to start it off please Bruce?

Posted at: 3/8/2010 3:31 PM by Sarah Raisanen

dl, ins and del

bruce said:

I'm told that dl gives "too much information"; and ins and del don't seem terribly well supported by screenreaders …

Posted at: 3/8/2010 3:34 PM by Sarah Raisanen

TITLE attribute

Bim said:
Yes, it's true that DL often gives information overload, not sure about support for INS and DEL, but will check it out. In fact as support for the TITLE attribute is so variable across different browsers and assistive software, it might apply to both "too much" and "too little".

You're right, it really would make a good series. It's on the list. Thanks.

Posted at: 3/8/2010 3:37 PM by Sarah Raisanen

More favourites

Seb Crump said:
I agree with all thosse suggested above. I'd add:
* Overuse of Accronym/Abbreviation tags - not every instance of an accronym needs to be marked up, but it's common to see the same accronym marked up several times in consecutive (or even within a single) sentence(s), just adding to clutter.
* 'Accessibility features' that are provided in an inaccessible way, e.g. text resize that relies on JavaScript.

Posted at: 3/8/2010 3:39 PM by Sarah Raisanen

Add a comment

If you would like to add a comment, you need to login first.