R: Readability of "Reflected web content accessibility problems"

Me too.

---
Roberto Scano (rscano@iwa.it)
IWA/HWG International Project Manager and EMEA Coordinator 
International Webmasters Association / HTML Writers Guild 
W3C Advisory Commitee Representative for IWA/HWG W3C 
WCAG Working Group Member - W3C ATAG Working Group Member 
Expert of ISO TC 159/SC 4 'Ergonomics of human-system interaction'
Expert of ISO JTC 1/SC 35 'User Interfaces'
http://www.iwanet.org - http://www.hwg.org
E-Mail: emea@iwanet.org - w3c-rep@iwanet.org

-----Messaggio originale-----
Da: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] Per conto di Richards, Jan
Inviato: giovedì 2 settembre 2010 22:40
A: w3c-wai-au@w3.org
Oggetto: FW: Readability of "Reflected web content accessibility problems"

Hi all,

I like the suggested clarification.

Cheers,
Jan

-----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,
Consultant,
Accessibility and User Experience Department,
Technosite - Fundosa group (ONCE Foundation),
Tel: 91 121 03 30
E-mail: achuter@technosite.es
www.technosite.es

Received on Friday, 3 September 2010 05:17:51 UTC