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

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

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Fri, 17 Sep 2010 14:10:12 +0200
Message-ID: <4C935AA4.6010003@w3.org>
To: Jennifer Sutton <jsuttondc@gmail.com>
CC: wai-eo-editors@w3.org
Hi Jennifer,

Thank you for your comments. They will all be addressed in upcoming 
iterations, I don't think we need to discuss them on *this* call.

Note that comment #4 relates to references to an incomplete page. We 
will revisit these cross-references when all pages are completed.

For your reference, please find below how they will be addressed:


On 17.09.2010 13:37, Jennifer Sutton wrote:
> 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,"

Agree, will be fixed in the next iteration.


> 2. Text alternatives are equivalents for non-text content. This includes:
>
> Is it clear what "This" refers to?
>
> Maybe "Examples include:"

Agree, will be fixed in the next iteration.


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

Agree, will be fixed in the next iteration.


> 4. In this part, should there be a reference for developing audio
> descriptions?
>
> Web browsing methods:
> [@@ to be developed]
> [@@
> Captions and transcripts
> ]
> [@@
> Sign language
> ]

Will be revisited when "web browsing methods" page is completed.


> 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."

Agree, will be fixed in the next iteration.


> 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?

Unfortunately yes.


> 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."

Agree, will be fixed in the next iteration.


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

It looks fine to me ;)


> 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."

Agree, will be fixed in the next iteration.


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

It absolutely does.


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

Agree, will be fixed in the next iteration.


> 10. they frequently use[JS: del ,] to enhance"
>
> JS: Maybe:
> they frequently use. When they do, they can enhance . . ."

Agree, will be fixed in the next iteration.


> 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."

Agree, will be fixed in the next iteration.


> 12. Meeting this requirement[JS: del s] helps people who do not see or
> hear the content, and may . . .

Agree, will be fixed in the next iteration.


Thanks a lot.

Best,
   Shadi

-- 
Shadi Abou-Zahra - http://www.w3.org/People/shadi/ |
   WAI International Program Office Activity Lead   |
  W3C Evaluation & Repair Tools Working Group Chair |
Received on Friday, 17 September 2010 12:10:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 17 September 2010 12:10:41 GMT