W3C

List of comments on “Web Content Accessibility Guidelines (WCAG) 2.0” (dated 11 December 2008)

Quick access to

There are 6 open comments (sorted by their types, and the section they are about).

question comments

Comment LC-2778
Commenter: Makoto Ueki <makoto.ueki@gmail.com> on behalf of WAIC(Web Accessibility Infrastructure Committee in Japan) (archived message)
Context: 1.3.2 Meaningful Sequence: When the sequence in which cont...
Item Number: Success Criterion 1.3.2
Part of Item:
Comment Type: question
Summary of Issue: Text field followed by instructions
Comment (Including rationale for any proposed change):
We'd like to make sure if the following example "affects its meaning" or not.

ex1. Instructions
<label for="account">Credit card account number</label>
<input type="text" id="account">
<p>15 - 16 digits, no dashes or spaces</p>

There is a text field which is followed by restrictions on the format of data that users must enter. Screen reader users might not be able to perceive that there is the instructions for this text field. Or they could perceive it after they input data to the text field.
Does this text field meet SC 1.3.2?

Proposed Change:
WAIC would like to have the answer from WCAG working group in order to harmonize JIS(Japanese Industrial Standards) with WCAG.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-2779
Commenter: Makoto Ueki <makoto.ueki@gmail.com> on behalf of WAIC(Web Accessibility Infrastructure Committee in Japan) (archived message)
Context: 1.3.2 Meaningful Sequence: When the sequence in which cont...
Summary of Issue: Search button followed by search options
Comment (Including rationale for any proposed change):
We'd like to make sure if the reading order of the following example "affects its meaning" and the focus order "preserves meaning and operability.".

ex2. Search Options
<input type="text" title="keyword">
<input type="submit" value="Search">
<input type="radio" name="optionsRadios" id="optionsRadios1"
value="option1" checked>
<label for="optionsRadios1">Search example.com</label>
<input type="radio" name="optionsRadios" id="optionsRadios2" value="option2">
<label for="optionsRadios2">Search the web</label>

There is a text field for search which is followed by radio buttons providing search options. Screen reader users might not be able to perceive that there are the radio buttons before pressing the search button.
Does this text field meet SC 1.3.2 and/or SC 2.4.3?

Proposed Change:
WAIC would like to have the answer from WCAG working group to confirm the intent of both SC in order to harmonize JIS(Japanese Industrial Standards) with WCAG.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-2780
Commenter: Makoto Ueki <makoto.ueki@gmail.com> (archived message)
Context: 1.3.2 Meaningful Sequence: When the sequence in which cont...
ex3. Optional button
https://www.google.com/
The reading and focus order would be:
- text field
- "Google search" button
- "I'm Feeling Lucky" button

There is a text field for search and a search button which is followed by an optional button "I'm feeling Lucky". Screen reader users might not be able to perceive that there is the optional button before they press the search button. Does this text field meet SC 1.3.2 and/or 2.4.3?

Proposed Change:
WAIC would like to have the answer from WCAG working group to confirm the intent of both SC in order to harmonize JIS(Japanese Industrial Standards) with WCAG.

Thanks so much in advance for your time and trouble.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

general comment comments

Comment LC-2760
Commenter: Devarshi Pant <devarshipant@gmail.com>> (archived message)
Context: WCAG 2.0 Supporting Documents
Refer URL: http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/ARIA1
Note the statement made under 'User Agent and Assistive Technology Support
Notes' which states that IE 8 does not support aria-describedby at all. I
tested the aria-describedby property using JAWS 13 and IE 8 and it did work
barring minor issues. Therefore, I question the credibility of this
statement. Note that in IE 8, the aria-describedby property on the text
programmatically tied to the control is spoken twice (which could be due to
the use of landmark roles).

Proposed Change: Change the latter part of the sentence to read, "IE 8
partially supports aria-describedby ..."
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

substantive comments

Comment LC-2758
Commenter: Devarshi Pant <devarshipant@gmail.com> (archived message)
Context: in
Refer URL
http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-identified.html
Second para, second sentence, under 'Intent of this Success Criterion'
reads "For example, certain technologies can specify that the user's input
must not fall outside a specific range, or that a form field is required.
Currently, few technologies support this kind of programmatic information,
but the Success Criterion does not require, nor prevent it."
I think there are the issues with the statement quoted above.
1. "Certain technologies" is not clear. Does it mean ARIA, title
attributes, etc.?
2. "Few technologies" is not clear either.
3. "but the Success Criterion does not require, nor prevent it" does not
sound correct grammatically and would be better served using neither / nor.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

editorial comments

Comment LC-2769: Understanding Levels of Conformance unclear
Commenter: <noreply@w3.org> (archived message)
Context: Conformance
Name: Shawn Henry
Email: shawn@w3.org
Affiliation: W3C WAI / MIT
Document: UW
Item Number: Understanding Conformance
Part of Item: Intent
Comment Type: editorial
Summary of Issue: Understanding Levels of Conformance unclear
Comment (Including rationale for any proposed change):
Several places (such as the How to Meet / quick ref) link the word "level(s)" to http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance#uc-levels-head

This section is missing the basic description of what the levels are and how people might use them.

(Also, there are three paragraphs before you even get to mention of the three levels; the first use of the word level is unrelated "a high level of confidence"; and A, AA, and AAA" is no where in the section.)

Proposed Change:
Edit that explanation of levels to be more clear and address readers who come at it from different places and perspectives, particularly those looking for a basic idea of what the levels are in general. (I understand you don't have a definition of each level like in WCAG 1.) (I think Judy Brewer worked on explanations of the levels a few years ago and might have some input.)

A quick & easy thing that would help a bit is to include "levels A, AA, and AAA" at the top of the section so people at least have some grounding.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Add a comment.


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: Overview.php,v 1.46 2013-10-04 08:11:33 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org