W3C home > Mailing lists > Public > w3c-wai-au@w3.org > July to September 2011

RE: more atag comments

From: Richards, Jan <jrichards@ocad.ca>
Date: Tue, 26 Jul 2011 19:46:54 +0000
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <0B1EB1C972BCB740B522ACBCD5F48DEB036563B2@ocadmail-maildb.ocad.ca>
Hi Tim,

Comments marked JR...

--
(Mr) Jan Richards, M.Sc.
jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
Inclusive Design Research Centre (IDRC) | http://idrc.ocad.ca/
Faculty of Design | OCAD University

From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On Behalf Of Boland Jr, Frederick E.
Sent: July 25, 2011 10:34 AM
To: w3c-wai-au@w3.org
Subject: FW: more atag comments

Fyi Best Tim Boland NIST

From: Boland Jr, Frederick E.
Sent: Thursday, July 21, 2011 3:07 PM
To: Boland Jr, Frederick E.
Subject: more atag comments

A.3.2.1
Does this cover the case where an author makes a change (maybe forgets about the
change made), and the authoring tool closes the session but "remembers" the edit later
(maybe when the author exits the authoring tool)?  Is such a scenario possible with
at least some authoring tools (if not then your response is fine..)

JR: I think when the authoring tool "remembers the edit" as you say, it is essentially saving it.

A.3.2.2
Is there a reason to break the consistency with WCAG2 for testability (maybe make "tighter"
or less arbitrary?)..  if keeping consistency is more important then I understand..

JR: I think the WCAG2 formulation is fairly testable, it's just arbitrary. Why 20 hours and not 19? If we change it, however, we then need to explain two things. Our new arbitrary value AND why we changed WCAG's.

A.3.2.3
"pointer input - input from mouse or other pointer" - circular definition?  - what specifically
can or can not be classified as a "pointer"?
"moving around" relative to "what" reference (for example, screen, enclosing window, what)?  Is
this only for visual media or for other kinds (audio, tactile, etc.)?

JR: We could say "Pointing device input" instead. "Pointing Device" is used without a definition in CSS3. http://dev.w3.org/csswg/css3-ui/#pointing-devices-and-keyboards

JR: WCAG2 says "moving" in "2.2.2 Pause, Stop, Hide: For moving, blinking<http://www.w3.org/TR/WCAG20/#blinksdef>, scrolling, or auto-updating information, all of the following are true: (Level A)" without definition.
Received on Tuesday, 26 July 2011 19:47:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 26 July 2011 19:47:19 GMT