W3C home > Mailing lists > Public > public-wcag2ict-tf@w3.org > August 2012

ACTION-29 Analysis of 2.2.1, 3.2.1, 3.2.2, 3.3.4, 4.1.2 coverage of documents that have no interactivity beyond simply hyperlinks

From: Andi Snow-Weaver <andisnow@us.ibm.com>
Date: Thu, 2 Aug 2012 13:22:16 -0500
To: public-wcag2ict-tf@w3.org
Message-ID: <OFFC756401.C72825B9-ON86257A4E.00612ACC-86257A4E.0064EA71@us.ibm.com>


This action item is a follow-up item. We agreed, per the WCAG WG request,
to remove statements from our guidance that said that documents that are
not interactive beyond simple hyperlinks would automatically apply. The
follow up was to check to make sure documents are still covered and we
didn't lose anything by removing that statement.

2.2.1 Timing Adjustable: Our guidance says this applies directly replacing
"content" with electronic documents and software". Seems clear that
documents are covered.

3.2.1 On Focus: Our guidance says this applies directly. The first sentence
of INTENT makes it clear that this applies to navigation within a document.
In a document with no interactivity beyond simple hyperlinks, nothing gets
focus except hyperlinks which don't change context on receiving focus. So
this one seems clear.

3.2.2 On Input: Our guidance says this applies directly. There is a note in
intent that contains this sentence: Clicking on links or tabs in a tab
control is activating the control, not changing the setting of that
control. So it seems clear that hyperlinks in a document may change the
context.

3.3.4 Error Prevention (Legal, Financial, Data): Our guidance says this
applies directly. Seems like it would be obvious to document authors that
their documents don't cause execute transactions and would therefore meet
this.

4.1.2 Name, Role, Value: Our guidance says this applies directly but it's
not so obvious whether document authors need to do anything to meet this
one and "links" are included in the examples in the SC itself. The intent
includes a note that states "This success criterion is primarily for Web
authors who develop or script their own user interface components. For
example, standard HTML controls already meet this success criterion when
used according to specification. " We might need to add a more general
version of this statement to our guidance. Something like "Standard
controls in many document formats already meet this success criterion when
used according to specification. Consult accessibility guidelines for the
document format for guidance."

Andi
Received on Thursday, 2 August 2012 18:22:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 2 August 2012 18:22:54 GMT