Comments on: Too much accessibility

By: Web Access Centre Blog :: Hidden barriers to accessibility

Web Access Centre Blog :: Hidden barriers to accessibility — Mon, 30 Jul 2007 07:27:07 +0000

[…] Rather like “Too much accessibility“, this series will grow with time, and your suggestions for additional topics is welcome. […]

By: Seb Crump

Seb Crump — Tue, 19 Sep 2006 11:59:42 +0000

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.

By: Bim

Bim — Fri, 15 Sep 2006 10:41:43 +0000

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.

By: bruce

bruce — Fri, 15 Sep 2006 10:05:44 +0000

Ooops - it ate my code examples: I’m told that dl gives “too much information”; and ins and del don’t seem terribly well supported by screenreaders …

By: bruce

bruce — Fri, 15 Sep 2006 10:04:34 +0000

I’m told that the gives “too much information”; and don’t seem terribly well supported by screenreaders …

By: Bim

Bim — Fri, 15 Sep 2006 08:52:39 +0000

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?

By: bruce

bruce — Thu, 14 Sep 2006 14:44:25 +0000

Can we have a parallel series called “not enough accessibility” which looks at how JAWs and its rivals fail with useful bits of html?

By: JackP

JackP — Thu, 14 Sep 2006 08:55:18 +0000

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

By: patrick h. lauke

patrick h. lauke — Wed, 13 Sep 2006 21:38:40 +0000

* 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

completely unrelated, but: as with every darned wordpress install, the tab order of your comment form here is quirky…”message” should come after “website”, but doesn’t…