[Fwd: Re: New ATAG 2.0 Editor's Draft]

Forwarded from: Barry Feigenbaum





comments on new draft

general comment:s

use of only single word criterial titles (ex A.3.3.3 Blinking) seems a
little abrupt. should at least be a phrase.

this could be out of scope but we never mention language use; content in
the wrong language is inherently inaccessible (as its meaning cannot be
comprehended if one is disabled by not knowing the language).  so
localization is a form of providing an accessible alternative, closely
related is low "reading level".

A.2.3.5 does "contrast ratio" need to be a defined term. think so,
including how to compute it.  is this text to background ratio only;
  what about when using different colors for text parts, etc.

A.2.3.9 is the more of a "level AAA"

A.2.3.11 think you need to exclude certain prerecorded stuff, like a
movie or TV show you did not produce yourself,  where there is no way to
control the fg/bg noise ratio.

A.3.1 "hand eye" -> "hand-eye"

A.3.1.3 why not also "content display"?

A.3.1.6 ... using conventions of the platform (e.g. via "tab", ....)

A.3.3.1 may not be possible in a web-based tool.  info in forms, etc not
sent to server could get lost on server session time-outs.

A.3.3.3 title not broad enough,  what about use of arrow keys that cause
the display to scroll to follow a caret, surely this is desired
behavior.  I don't know of any GUI component that can turn this behavior
off.

does not fit in A.3.3 time limits, closer to A.3.4 (blink is a form of
flash)

A.3.3.4 vs A.3..3.2 this is a gimme AA criteria (10 vs 5 no diff in effort)

suggest A.3.6.1 become AAA and a pure text search be AA. example,
browsers don't typically offer a find that looks at non displayed (such
as tag attr text) text; only the text as rendered is scanned

A.4.1.2 should also cover acronyms

A.4.1.x should add "easy to access mechanism" (ex by keyboard, tool
button, etc)

A.4.2.1 define ":change of context"

suggest adding  A.4.3.2 Undo (chrome) Author actions that modify
authoring tool settings must either be reversible by an "undo" or
"cancel" function or ... warning to  the author ...

A.4.4.1 plain text may not be accessible, consider ASCII graphics.
should we add more description

B.223.2 or if no content type in the choice set has an A benchmark, the
author is warned that adding content in these content types will make
the resulting content inaccessible..

B.2.4.2 "image database" -> "object database"

B.2.4.3 references may not need to be valid URIs, ex a simple file name
is not "universal"

B.2.5  rationale "is often" -> "are often"

Barry A. Feigenbaum, Ph. D.
Tool Architect
Human Ability and Accessibility Center - IBM Research
www.ibm.com/able, w3.ibm.com/able
voice 512-838-4763/tl678-4763
fax 512-838-9367/0330
cell 512-799-9182
feigenba@us.ibm.com
Mailstop 904/5F-021
11400 Burnet Rd., Austin TX 78758

Accessibility ARB Representative on SWG ARB
W3C AUWG Representative
Austin IBM Club BoD
Interface Technologies IDT Member
QSE Development TopGun

Sun Certified Java Programmer, Developer & Architect
IBM Certified XML Developer; OOAD w/UML

This message sent with 100% recycled electrons

Received on Monday, 4 June 2007 20:16:13 UTC