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

FW: Readability of "Reflected web content accessibility problems"

From: Richards, Jan <jrichards@ocad.ca>
Date: Thu, 2 Sep 2010 16:40:16 -0400
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <F2C77FB59A1A4840A01EF5F59B1826E2090950A45A@ocadmail.ocad.ca>
Hi all,

I like the suggested clarification.


-----Original Message-----
From: public-atag2-comments-request@w3.org [mailto:public-atag2-comments-request@w3.org] On Behalf Of Alan Chuter
Sent: September 2, 2010 7:10 AM
To: public-atag2-comments@w3.org
Subject: Readability of "Reflected web content accessibility problems"

I found this phrase "Reflected web content accessibility problems" 
difficult to understand even after reading the following paragraph. The 
explanation seems very verbose, perhaps because it contains complete 
text from the glossary entries ("an authoring tool user interface 
accessibility problem is caused directly by a web content accessibility 
problem in the content being edited").

It could be written more concisely, like this: "However, where an 
accessibility problem is caused directly by the content being edited 
(e.g., if an image in the content lacks a label), then this would not be 
considered a deficiency in the accessibility of the user interface."

Alan Chuter,
Accessibility and User Experience Department,
Technosite - Fundosa group (ONCE Foundation),
Tel: 91 121 03 30
E-mail: achuter@technosite.es

Received on Thursday, 2 September 2010 20:40:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:39:59 UTC