RE: Applying ATAG to status updates

Hi Alastair,

I think this was a very useful exercise. I've added my comments in the next column.

Cheers,
Jan



-- 
(Mr) Jan Richards, M.Sc.
jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
Inclusive Design Research Centre (IDRC) | http://inclusivedesign.ca/
Faculty of Design | OCAD University


> -----Original Message-----
> From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On Behalf
> Of Alastair Campbell
> Sent: November 29, 2010 2:20 PM
> To: w3c-wai-au@w3.org
> Subject: Applying ATAG to status updates
> 
> 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
>