[wbs] response to 'EOWG Call for Review: Why Standards Harmonization is Essential to Web Accessibility, 2006 March'

Here are the answers submitted to 'EOWG Call for Review: Why Standards
Harmonization is Essential to Web Accessibility, 2006 March' (Education
and Outreach Working Group) for Shawn Henry.



---------------------------------
Why Standards Harmonization is Essential to Web Accessibility
----




 * ( ) I accept this version of the document as is
 * ( ) I accept this version of the document, and suggest changes below
 * ( ) I accept this version of the document only with the changes below
 * ( ) I do not accept this version of the document because of the
comments below
 * ( ) I abstain (not vote)





---------------------------------
Comments
----
Comments on the document, formatted as described above.

Comments (or a URI pointing to your comments): 
priority: [editor's discretion]
location: Overview or other
suggested revision: define "Web content" (or link to definition)
(at /WAI/CVS/WWW/WAI/intro/accessibility.php#content we have "Web
"content" generally refers to the information in a Web page or Web
application, including text, images, forms, sounds, and such. More
specific definitions are available in the WCAG documents, which are linked
from the Web Content Accessibility Guidelines (WCAG) Overview.")
rationale: jargon

priority: [editor's discretion]
location: Abstract
suggested revision: include accessibility of authoring tools

priority: [editor's discretion]
location: Overview
current wording: browsers and media players
suggested revision: browsers, media players, and other "user agents"

priority: [editor's discretion]
location: Overview
current wording: "While W3C's Web Content Accessibility Guidelines 1.0..."
suggested revision: spell out W3C on first reference

priority: [editor's discretion]
location: 
- "Harmonization of Web accessibility standards is key to making an
accessible Web, because it creates a unified market for authoring tools
which produce conformant content."
- "Together these three WAI guidelines provide mutually reinforcing
solutions which result in more comprehensive and effective accessibility."
- "This can make it more difficult for developers of authoring tools and
evaluation tools (which are used to evaluate..."
- [@@others?]
suggested revision: which>that
rationale: "which" is to introduce nonrestrictive clauses, and "that" is
to introduce restrictive clauses
location:
- "Web Content Accessibility Guidelines 1.0 (WCAG 1.0), which describe..."
"Authoring Tool Accessibility Guidelines 1.0 (ATAG 1.0), which
describe..."
"User Agent Accessibility Guidelines 1.0 (UAAG 1.0), which describe.."
suggested revision: delete ", which" or change to "that"

priority: [editor's discretion]
location: Overview
current wording: "...minimally aware of the rationale for Web
accessibility, or disinclined to learn guidelines and techniques for
accessibility."
suggested revision: change "disinclined"
rationale: uncommon word for English speakers, also may be difficult to
translate

priority: [editor's discretion]
location: Overview
current wording: 
"- the Web Content..."
"- the Authoring Tool..."
"- the User Agent ..."
suggested revision: delete "the"
rationale: much stronger & easier to skim

priority: [editor's discretion]
location: Overview
current wording: "
Web Content Accessibility Guidelines 1.0 (WCAG 1.0), which describe...
Authoring Tool Accessibility Guidelines 1.0 (ATAG 1.0), which describe...
User Agent Accessibility Guidelines 1.0 (UAAG 1.0), which describe.."
suggested revision: link to Overview pages 
- http://www.w3.org/WAI/intro/wcag.php
- http://www.w3.org/WAI/intro/atag.php
- http://www.w3.org/WAI/intro/uaag.php

priority: [editor's discretion]
location: Overview
current wording: "describe how to make browsers and media players
accessible, and how to ensure their interoperability with assistive
technologies."
suggested revision: "...and how to ensure they are interoperable with
assistive technologies."

priority: [editor's discretion]
location: Overview
current wording: W3C/WAI
suggested revision: W3C WAI

priority: [editor's discretion]
location: Overview
current wording: "Together these three WAI guidelines provide mutually
reinforcing solutions..."
suggested revision: hypenate mutually-reinforcing: "Together these three
WAI guidelines provide mutually-reinforcing solutions..."
rationale: not sure about gramatically correct

priority: [editor's discretion]
location: Current situation
current wording: "...as they will then need to support potentially
conflicting sets of implementation and evaluation techniques."
suggested revision: add multiple: "...as they will then need to support
multiple, potentially conflicting sets of implementation and evaluation
techniques."

priority: [editor's discretion]
location: Current situation
current wording: "For each such factor, or "fragmentation driver,"
however, there is also a good reason to promote harmonization of
standards:
suggested revision: something more like "However, these factors, or
"fragmentation drivers", are myths and there is also a good reason to
promote harmonization of standards:" [still needs work]

priority: [editor's discretion]
location: Current situation
current wording: "[NOTE: a linearized version of the following table is
available.]"
suggested revision: delete linearized version.
rationale: unnecessary complexity

priority: [editor's discretion]
location: Current situation
current wording: "[NOTE: a linearized version of the following table is
available.]"
suggested revision: change "linearized"
rationale: jargon

priority: [editor's discretion]
location: table
suggested revision: set CSS top
rationale: better spacing within cell for readability & visual astetics

more coming tomorrow...



These answers were last modified on 16 March 2006 at 06:03:47 U.T.C.
by Shawn Henry

Answers to this questionnaire can be set and changed at
http://www.w3.org/2002/09/wbs/35532/harmon/ until 2006-03-18.

 Regards,

 The Automatic WBS Mailer

Received on Thursday, 16 March 2006 06:10:05 UTC