W3C home > Mailing lists > Public > w3c-wai-au@w3.org > October to December 2010

Applying ATAG to status updates

From: Alastair Campbell <acampbell@nomensa.com>
Date: Mon, 29 Nov 2010 19:19:30 +0000
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <D4219A0ECCAE794C9ED7DC6F5A4C0CD537B3017429@jupiter.intranet.nomensa.com>
Hi everyone,

During this little meeting hiatus I've tried applying ATAG to Facebook status updates (the simple end of the range!).

Most of it was fairly straightforward, and most of the time was taken doing a WCAG 2 audit (A.1.1.1). Running through the rest of ATAG was fairly quick in this case.

Before I write it up into an article, it would be good if someone can check I'm on the right track?

The easiest way to show the results seems to be a spreadsheet (attached), with item, result and notes. I used the last draft as the basis.
(http://www.w3.org/WAI/AU/2010/ED-ATAG20-20101108/)

A few of them I've put a question mark next to the result where I'm not sure, so if you aren't sure you have time to look, just filter it down to those few.

Comments that have "NB:" are notes towards improving the guidelines. For example, "B.2.4.4 Suggest Previous Author Entries" implies that an interface *must* provide the option, which doesn't make sense relating to a Facebook status update.

Overall, I was quite impressed with Facebook's general accessibility, people with modern ATs shouldn't have any trouble using the interface. Just a shame that adding alt text to images is impossible, and it sticks the whole content of the post into a heading 6...

Kind regards,

-Alastair

-- 
Alastair Campbell         |  Director of User Experience

Nomensa Email Disclaimer:
http://www.nomensa.com/email-disclaimer




Received on Monday, 29 November 2010 19:20:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 29 November 2010 19:20:24 GMT