W3C

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

Quick access to

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

1-20 21-33

question comments

Comment LC-2725: WCAG Compliance
Commenter: Robert Owoo <afrinique@gmail.com> (archived message)
Context: Document as a whole
I just wanted to enquire about the WCAG standard.
I am looking to design a website and wanted to how much it would cost us to
implement these standards?
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-2762: minimum contrast
Commenter: David Torres Leal <dtorres@technosite.es> (archived message)
Context: WCAG 2.0 Layers of Guidance
Not assigned
Resolution status:

Hi everybody!!

I have checked out a lot of information about the Success "Criteria 1.4.3 Contrast (Minimum)" and in all cases it just refers to text and images of text. What happens to essential images such as icons, pictograms which do not contain text? Do not they have a minimum contrast ratio?

All of us know that some images should have a minimum contrast ratio in order to be noticed by eyesight people.

Best Regards and thanks in advance,
David Torres Leal
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-2942: Captions for video in foreign language
Commenter: Makoto Ueki <makoto.ueki@gmail.com> (archived message)
Context: 1.2.2 Captions (Prerecorded): Captions are provided for al...
assigned to Andrew Kirkpatrick
Resolution status:

Name: Makoto Ueki
Email: makoto.ueki@gmail.com
Affiliation:
Document: W2
Item Number: Success Criterion 1.2.2
Part of Item:
Comment Type: question
Summary of Issue: Caption for video in foreign language
Comment (Including rationale for any proposed change):
When a video is presented in foreign language, which language should be used for caption?

For example, a video is embeded in a Japanese web page. In the video, a person speaks English. But the video is intended for Japanese users. Which language should the author use for adding caption to the video in order to meet SC 1.2.2, Japanese or English?

Proposed Change:
Just want to clarify. Thank you very much in advance for your time.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-2922: Are ARIA landmarks required?
Commenter: Glenda Sims <Glenda Sims <glenda.sims@deque.com>> (archived message)
Context: 1.3.1 Info and Relationships: Information, structure, and...
assigned to Joshue O Connor
Resolution status:

I need clarification on *2.3.1 Info & Relationships*. Can you tell me if
my interpretation is correct:

I think it is possible to pass WCAG 2.0 SC 1.3.1 without using ARIA
landmarks. As much as I love ARIA landmarks...I do not think they are
required in WCAG 2.0.

I always recommend them, but I don't currently have my team call a WCAG 2.0
violation on SC 1.3.1 if ARIA landmarks are missing.

Thanks in advance for your insight (as you might guess, the Deque
Accessibility Experts are not in agreement in how to interpret this).
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-2964: 1.3.2. Violation?
Commenter: CB Averitt (archived message)
Context: 1.3.2 Meaningful Sequence: When the sequence in which cont...
Resolution status:

Does the W3C find any Meaningful Sequence violations in the examples given?
Comment (Including rationale for any proposed change):
The first example located here,
http://sites.averittweb.com/MyWeb/test/MeaningfulSequencePage/example1/
is an html page. Some functionality, used for reference only, has been replaced with static images. The primary focus is the reading order of the three paragraphs. Is meaningful sequence violated?
The second example located here,
http://sites.averittweb.com/MyWeb/test/MeaningfulSequencePage/example2/
is a static image but is coded very similar to our first example. “Tip" is located near the bottom and is a pop-up modal. Other buttons could be present in the same area as “Tips”. Buttons such as, “keywords”, “hints”, and others. The primary focus is the reading order of where the “Tip” button is located. Is meaningful sequence violated?
This is related to a real life situation and the Deque Experts are not in agreement as to whether or not this is a violation of 1.3.2. We really value your interpretation of this so we can confirm that we are accurately applying WCAG 1.3.2 to this assessment.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-2766: multiple search buttons
Commenter: <noreply@w3.org> (archived message)
Context: 1.3.2 Meaningful Sequence: When the sequence in which cont...
Not assigned
Resolution status:

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)

Comment LC-2767: Search button followed by search options
Commenter: <noreply@w3.org> (archived message)
Context: 1.3.2 Meaningful Sequence: When the sequence in which cont...
Not assigned
Resolution status:

Name: Makoto Ueki
Email: makoto.ueki@gmail.com
Affiliation: WAIC(Web Accessibility Infrastructure Committee in Japan)
Document: W2
Item Number: Success Criterion 1.3.2
Part of Item:
Comment Type: question
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-2768: Text field followed by instructions
Commenter: <noreply@w3.org> (archived message)
Context: 1.3.2 Meaningful Sequence: When the sequence in which cont...
Not assigned
Resolution status:

Name: Makoto Ueki
Email: makoto.ueki@gmail.com
Affiliation: WAIC(Web Accessibility Infrastructure Committee in Japan)
Document: W2
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-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-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)

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-2941: Social Media Buttons
Commenter: makoto.ueki@gmail.com (archived message)
Context: Statement of Partial Conformance - Third Party Content
assigned to Andrew Kirkpatrick
Resolution status:

Name: Makoto Ueki
Email: makoto.ueki@gmail.com
Affiliation:
Document: W2
Item Number: Statement of partial conformance - third party content
Part of Item:
Comment Type: question
Summary of Issue: Social Media Buttons
Comment (Including rationale for any proposed change):
Can "Statement of Partial Conformance - Third Party Content" be applied to social media buttons such as "Like!" button and "tweet" button?

In general, scripts and HTML codes are generated and provided by the social media. It is not content that is under the author's control as described in "Statement of Partial Conformance - Third Party Content". When putting these kind of buttons on a web page, authors can't change the scripts and codes.

For example, generated code for "Like!" button of Facebook is:

<button type="submit">
<i class="pluginButtonIcon img sp_plugin-button sx_plugin-button_favblue"></i>
</button>

This would fail under SC 4.1.2 as the name for the button can't be programmatically determined.

There is a social media button which uses CSS background image for the button and it fails under SC 1.1.1 as well. However authors can't change it.

This means any web pages which have these social media buttons can't conform to Level A.

I'm wondering if "Statement of Partial Conformance - Third Party Content" can be applied to these cases.

Proposed Change:
If "Statement of Partial Conformance - Third Party Content" can be applied, please add the information to Understanding document.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

general comment comments

Comment LC-2727: Trying to locate information on the W3C site
Commenter: Alan Gelder <alan.gelder@dpi.vic.gov.au > (archived message)
Context: Document as a whole
As a matter of finding info on the W3C site, I am finding it very difficult.

Navigation on the pages I have looked at are drastically different:

http://www.w3.org/WAI/intro/people-use-web/principles
this one has tabs

http://www.w3.org/standards/webdesign/accessibility#examples
this one a completely different design

http://www.w3.org/WAI/intro/wcag.php
this one has quick links and page contents in one form of anchored links

http://www.w3.org/TR/WCAG-TECHS/SCR28.html#SCR28-description
here the anchored links are presented differently

http://www.w3.org/TR/WCAG-TECHS/
this one the menu has disappeared, fair enough it's a note/report thing.

http://www.w3.org/WAI/WCAG20/quickref/
this one has a menu where I can choose what I see on the page, though it is not entirely clear. But it's an interesting approach - accessible compiant?

Ok, these are different parts of what the W3C do, but it is confusing to get around these pages because nothing appears consistent in the design.

Anyway, my problem is that I am just trying to find the wcag advice re mega menus, anchored links, and scrolling/marquee images. I have tried Googling without much success, including the top level w3c google search option.

If you have any tips re where this info sits or how to find it easily, that would be terrific!
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

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)

Comment LC-2685: Web page colours
Commenter: Les Delaney <lesdelaney@oneseniors.com.au> (archived message)
Context: 1.4.3 Contrast (Minimum): The visual presentation of text...
Not assigned
Resolution status:

P L E A S E make the suggestion to webpage designers to be carefull of their colour choices!

Light grey - light blue and other pale colours on pale and white bacgrounds ARE JUST IMPOSSIBLE TO READ for people with dyslexia and poor eyesight. WHY do they persist in making life a misery for these people? PLEASE have the designers make better choices!!!!
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-2571: Touchscreen Accessibility
Commenter: Makoto Ueki <makoto.ueki@gmail.com> on behalf of JIS (archived message)
Context: 2.1.1 Keyboard: All functionality of the content is operab...
assigned to Gregg Vanderheiden
Resolution status:

Touchscreen issues are covered by WCAG 2?

SC 2.1.1 requires the keyboard accessibility. What about a touchscreen interface?

For example, 'onmouseover' and 'onkeypress' don't work on the touchscreens such as iPhone and iPad.

Does WCAG 2 require the touchscreen users to buy and use a keyboard for such devices?

Proposed Change:
Just to make sure if WCAG 2 covers touchscreen issues or not. WAIC need an answer from WCAG WG in order for JIS X 8341-3:2010(our standards) to harmonize with WCAG 2. Thank you very much.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

typo comments

Comment LC-2716: errata: close of hypertext anchor </a> is misplaced
Commenter: Bruce Bailey <bailey@access-board.gov>
Context: 3.3.4 Error Prevention (Legal, Financial, Data): For Web p...
In SC 3.3.4, there is a defined term, "user-controllable" (followed by the word "data"). From the linked term in the glossary, it is clear that the term being defined is "user-controllable data" (and *not* just "user-controllable").
http://www.w3.org/TR/WCAG20/#user-controllabledef

Proposed Change:
Move the word "data" inside the hyperlink or update and/or update the errata document.
http://www.w3.org/WAI/WCAG20/errata/
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-2588: Missing period at end of numbered list.
Commenter: Bruce Bailey <bailey@access-board.gov> (archived message)
Context: 4. Only Accessibility-Supported Ways of Using Technologies:...
Most list items end with a comma or period with the last item in the list ending with a period.

Proposed Change:
3.when any technology that is not relied upon is not supported by a user agent

->

3.when any technology that is not relied upon is not supported by a user agent.
(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)

Comment LC-2759
Commenter: Devarshi Pant <devarshipant@gmail.com>> (archived message)
Context: in
Resolution status:

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)

1-20 21-33

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