Does this page look plain and unstyled?

Tools, wizards, articles and tutorials on Web Accessibility for the conscientious web developer

Subscribe to Accessify's RSS Feed   

Mike Davies’ thoughts on the state of accessibility (BarCamp London 2)

A thought-provoking piece by Mike Davies:

Creating an accessible web experience involves the co-ordination number of independent groups. The website builders have an important role, but they cannot cover the entire spectrum of accessibility issues. The user-agent vendors (typically browsers, but not limited to that) play an equally important role, taking accessible content and rendering it in an accessible way. They are also tasked with the responsibility of easing visitor access to content by features such as font-resizing, alternate stylesheets, colour filters, print functionality. The assistive technology provider also plays an important role, making sure that content is conveyed to the user in a way they can perceive and operate…

To that, I’d add a question: what about the responsibility of the end users? The onus also needs to be on them to know which tools are available to them and how to use them properly?

GAWDS has failed. Accessifyforum has failed. Accessites is fundamentally flawed. WCAG 2.0 is in trouble. Joe Clark’s WCAG Samurai remains as a glimmer of hope, so to is WaSP’s Accessibility Task Force. We need something that doesn’t repeat the same mistakes as GAWDS and Accessifyforum, but at the same time be open to involvement by the community, for the community

BarCamp London 2: Accessibility Panel Thoughts.

Comments (7) left to “Mike Davies’ thoughts on the state of accessibility (BarCamp London 2)”

  1. Robin wrote:

    I’m interested in what Accessifyforum’s original “mission” was. Surely it can’t have failed unless it’s not lived up to an original manifesto.

  2. Ian Lloyd wrote:

    Accessifyforum has failed? First I knew of it.

    For those who don’t know, I don’t run/own accessifyforum - I basically let Nigel Peck partner the site with accessify.com, and to be honest, it’s massively more active than this site - they server very different purposes. But to say it’s failed, well … like the previous commenter said, how can it fail if it didn’t have a mission?

    As I see it, it has enabled *many* people to engage in some really useful conversation, and I’m sure that the end result of that is a whole lot more people creating more accessible sites through their learning. How is that a bad thing?

  3. Patrick H. Lauke wrote:

    as a forum to discuss (mainly) html/css, accessifyforum has certainly been valuable . however, it has not grown into a place where accessibility is discussed, regardless of technology…a place where dialog is fostered among the many different stakeholders (content developers, user agent developers, users with disabilities) and where solutions are explored that go beyond html/css/flash/etc, beyond WCAG 1.0 or even WCAG 2.0. this makes me think of the ideas behind the tangram model http://www.ukoln.ac.uk/qa-focus/documents/briefings/briefing-101/html/
    we need to move beyond WCAG and beyond the ideal of “universal accessibility” - laudable in principle, but a pipe dream (until we get some hardcore solutions like servers with content stored in all sorts of formats and CC/PP negotiation between browser and server). i’m not talking ghetto-isation, or the old “text only version for blind users” misconceptions…but an aknowledgment that, in certain situations, it’s just not possible to provide one solution that works equally well for all audiences, even with adaptation.

    anyway, that’s what i *think* mike is getting at :)

  4. Beast-Blog.com - Failed? Fundamentally Flawed? wrote:

    […] In a news item that I first saw at Accessify.com there is a quote taken from the original “BarCamp London 2: Accessibility Panel Thoughts” post at Mike Davies’ Isolani site. It’s a quote I don’t necessarily agree with. Before I provide it here I want to say I’m not trying to stir anything up or cause trouble, and I’m not commenting on the rest of the article (which, aside from the alleged damage caused by “universalists,” I mostly agree with), but I do want to say remarks like this bother me a bit. First I’ll provide the quotation, then I’ll explain what it is I don’t agree with and why. GAWDS has failed. Accessifyforum has failed. Accessites is fundamentally flawed. — Mike Davies […]

  5. Mike Cherim wrote:

    And I simply must add my two cents.

  6. Isofarro wrote:

    Patrick, yep you’ve gotten right to the crux of the problem. Thanks, your explanation is far more lucid! (Thanks for the link to the Tangram model. Interesting)

    Mike

  7. Kelvin wrote:

    I posted my thoughts on this subject here:

    http://kelv.in/side/accessibility-and-usability/

Post a Comment

(Never published)
 

Site Navigation

Outside reading

Jeremy Keith does an excellent write-up of the Accessibility 2.0 conference (which I was unable to attend)
Sharepoint and Web Accessibility
Bruce Lawson describes the disparity between Sharepoint/MOSS developed web sites and the level of accessiblity that the tool offers to users (summary - it really is not good!)
How does a screen reader user really hear your web site?
Interesting post on Beast Blog about how a screen reader user - a real one! Not one of those fake web developer tester types! - uses the tool to read a web page. A few surprises were waiting in store for author Mike Cherim.
Web Accessibility Toolbar now available in simplified Chinese
The Web Accessibility Tools Consortium (WAT-C) release a simplified Chinese version of the Web Accessibility Toolbar.
Web 2.0 vs Web Accessibility
1-day seminar in London, 25th April, brings together experts in the field to discuss/demonstrate the accessibility issues faced by web 2.0.
Leading accessibility technologists form new alliance to fix problems
The Accessibility Interoperability Alliance (AIA), comprising (among others) Adobe, HP, Microsoft, Novell, and from the assistive tech industry Dolphin, GW Micro and HiSoftware forms to work together "to create and harmonize standards for accessible techn
Fieldsets, legends and screen readers
An excellent run-down of how fieldsets and legends can improve accessibility and how the various screen readers cope with this useful markup.
CAPTCHAs explained - WacBlog
Another really good post on the RNIB\'s Web Access Centre blog explaining captchas, why they\'re bad for accessibility and what the alternatives may be.
Making WCAG easier to read
Derek Featherstone has created some fancy style sheets to make reading WCAG documents a little easier on the eye.
Top Tips for the title attribute
Ann McMeekin provides a set of simple tips regarding when - or rather when not to - use the title attribute. \'Cos sometimes you can try *too much* to be helpful
California court tilts towards mandating web accessibility
Outlaw.com reports (on behalf of The Register) on the Target California class action lawsuit, digging a little deeper into what Target have been doing of late to address matters.
Screen Readers and display:none
Juicy Studio, aka Gez Lemon, investigate some quirks whereby screen readers announce content that they should not be. Perhaps this could be used for good rather than evil?
Google Developer Podcast: The status of accessibility on the Web
An interview with Google research scientist TV Rahman (and Hubbell, his seeing-eye dog!). Lots of talk about CAPTCHAs and accessibility, but no sign of a transcript for this interview as yet.
Transcript of Shawn Henry's talk from Jun 5th 2007 in London on RNIB's Web Access Centre Blog
Virtual worlds open up to blind
"Online virtual worlds could soon be accessible to blind people thanks to research by students at IBM in Ireland" states BBC News

View all Accessify bookmarks on del.icio.us



This page is styled using Cascading Style Sheets (CSS). If you can read this message, the chances are that your browser does not properly support CSS or you have disabled this yourself. The content on this site is perfectly readable without style sheets, though; it just doesn't look quite so fancy.

site statistics

This site is partnered with MIS Web Design and Top4Office for Copiers and Digipro for Photocopiers. Web design by Swindon Internet & PR Services.

How you can help support this site: Learn web design from the creator of this site, or help him by requesting some PR Photography