Fwd: EOWG comments on UAAG 2.0 Working Draft 17 June 2010

Dear UAAG WG,

 From a quick skim, it looks like some of our previous comments at <http://lists.w3.org/Archives/Public/public-uaag2-comments/2010Jul/0000.html> were not addressed. Some of these are below.

Regards,
~Shawn for EOWG


-------- Original Message --------
Subject: EOWG comments on UAAG 2.0 Working Draft 17 June 2010
Date: Fri, 30 Jul 2010 17:25:51 -0500
From: Shawn Henry <shawn@w3.org>
To: public-uaag2-comments@w3.org
CC: EOWG (E-mail) <w3c-wai-eo@w3.org>

Dear UAAG Working Group,

Thank you for the opportunity to review User Agent Accessibility Guidelines (UAAG) 2.0 W3C Working Draft 17 June 2010
<http://www.w3.org/TR/2010/WD-UAAG20-20100617/>

EOWG has several suggestions from an education and outreach perspective, below.

1. "Handles" for Principles, and probably also Guidelines.

We applaud the use of "handles" for each success criteria (for example, "Global Volume" in "3.7.1 Global Volume: The user can globally set volume"). We strongly suggest providing such handles for each of the principles. Please also consider providing handles for the guidelines as well.

[update Sept 2013:]
It looks like you have handles in the Table of Contents, but these are not used throughout the document.
]]

...

6. Link to Overview.

Please add a link in the Abstract and in the introduction to the UAAG Overview http://www.w3.org/WAI/intro/uaag.php
(For example, see WCAG http://www.w3.org/TR/WCAG/#abstract & http://www.w3.org/TR/WCAG/#intro )

...

8. Glossary.

Consider ways to improve usability of the glossary, especially for screen reader users and non-keyboard users. For example, consider "[top of glossary]" links, and maybe headings for each letter.

...

Under glossary terms where there are lists, we recommend getting rid of the space between the sentences and the lists. (This improves proximity.) For example, instead of:
"
*assistive technology*
An assistive technology:

1. relies on services...
2. provides services beyond...

Examples of assistive technologies that are important in the context of this document include the following:

- screen magnifiers,...
- screen readers,...
"

close up the spacing like this:
"
*assistive technology*
An assistive technology:
1. relies on services...
2. provides services beyond...
Examples of assistive technologies that are important in the context of this document include the following:
- screen magnifiers,...
- screen readers,...
"

9. Appendix B.

For "Appendix B: How to refer to UAAG 2.0 from other documents" please consider not duplicating content that is elsewhere, and instead pointing to "Referencing and Linking to WAI Guidelines and Technical Documents" at <http://www.w3.org/WAI/intro/linking.html>. We are happy to consider edit suggestions for that page.

...

12. Consistency, typos, copyediting.

Most of the guidelines are consistent in tone (e.g., "Provide xyz..."), except: "The user agent must behave in a predictable fashion." (Note WCAG's similar guidelines is worded: "Make Web pages appear and operate in predictable ways.")

...

Consider avoiding "e.g.," and always writing out "for example".

[update Sept 2013:]
In either case, it should be followed by a comma:
	... other accessibility specifications (for example, WCAG) ...
	... other accessibility specifications (e.g., WCAG) ...
]]

...

Consider getting a skilled technical editor to suggest specific ways to simplify the language, for example:
* "Three of the principles are congruent to..." -> "Three of the principles are the same as..." or "Three of the principles are similar to..."
* "The user agent must behave in a predictable fashion." -> "Make the user agent behave in predictable ways." (note earlier comment about consistent tone)

[update Sept 2013:]
Unnecessarily complex wording still there.
UAAG draft has "Guideline 3.4 - The user agent must behave in a predictable fashion."
Note similar WCAG wording: "Make Web pages appear and operate in predictable ways."
]

...

###

Received on Wednesday, 11 September 2013 18:48:00 UTC