W3C home > Mailing lists > Public > wai-eo-editors@w3.org > September 2010

Comments on How People with Disabilities Use the Web: Accessibility Requirements

From: Jennifer Sutton <jsuttondc@gmail.com>
Date: Fri, 17 Sep 2010 04:37:46 -0700
Message-Id: <7.0.1.0.2.20100917043523.02768a88@earthlink.net>
To: wai-eo-editors@w3.org
EOWG-Editors:

Here are comments on:
How People with Disabilities Use the Web: Accessibility Requirements:

http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/provisions
Editors Draft: $Date: 2010/09/05 13:13:23 $ [


These comments are mostly for editor's discretion, and they relate to 
the email Shawn sent to the main EOWG list on:
Date: Tue, 14 Sep 2010 07:57:43 -0500


The only item that isn't editorial is MY Item 4, below. I will bring 
it up on today's call, as appropriate.
:Jennifer


Note: for these comments, I didn't focus on the Expanding/Collapsing 
implementation.  I read the document via expanding all.

1. mobile phones browsers,

JS: Maybe this should be "browsers on mobile phones"
or
"mobile phones' browsers,"

or

"mobile phone browsers,"

2. Text alternatives are equivalents for non-text content. This includes:

Is it clear what "This" refers to?

Maybe "Examples include:"

3.  "Text alternatives convey the purpose of an image or function[JS: 
delete,] to provide an equivalent
user experience.

4.  In this part, should there be a reference for developing audio 
descriptions?

Web browsing methods:
[@@ to be developed]
[@@
Captions and transcripts
]
[@@
Sign language
]
  5. For me, the references to "It" are a little confusing here:

"It also allows other forms of adaptation, including automatic 
generation of page
outlines and summaries to help users get an overview and to focus on 
particular parts more easily."

In the previous sentence, I believe I understood that "It" meant 
content. But I'm not sure, here.

JS: Maybe something like:

"The ability to change browser settings also allows other forms of 
adaptation, including automatic generation of page
outlines and summaries to help users get an overview and to focus on 
particular parts more easily."


6.  Generally, is there a maintenance strategy for keeping this 
updated i.e. when ATAG and UAG move to their next versions, will 
these references need to be changed?

7. I'm not quite clear about this:
"This includes considerations for people who do
not use assistive technologies, and for people using assistive 
technologies and observe
interference from prominent background."

JS: Maybe something like:
This includes considerations for people who do
not use assistive technologies[JS: delete ,] and for people using 
assistive technologies and who experience
interference from prominent audio or visual content in the background."

And yes, I agree that this proposal is a bit too wordy.


8. I don't think this is a complete sentence:
"For instance, to read it aloud, generate page summaries, and to 
provide definitions
for unusual words such as technical jargon."

JS: Maybe something like:

"For instance, providing clear and understandable language helps when 
someone needs to have the page read aloud, generate page summaries, 
and to provide definitions
for unusual words such as technical jargon."

JS: But I'm not sure my proposal conveys the precise meaning intended.

9.  In particular[JS: add comma] it helps

10. they frequently use[JS: del ,] to enhance"

JS: Maybe:
they frequently use. When they do, they can  enhance . . ."


11. Forms and other interaction can be confusing or difficult to use 
for many people,
so that they are more likely to make mistakes.

JS: Maybe:
"Forms and other interaction can be confusing or difficult to use for 
many people, and, as a result, they may be more likely to make mistakes."

12. Meeting this requirement[JS: del s] helps people who do not see 
or hear the content, and may . . .
Received on Friday, 17 September 2010 11:38:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 17 September 2010 11:38:51 GMT