W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > October 2014

Re: Your comments on Techniques for WCAG 2.0 ( LC-2961)

From: <joshue.oconnor@cfit.ie>
Date: Tue, 21 Oct 2014 16:41:52 +0000
Message-Id: <E1XgcVM-0005BL-UU@jessica.w3.org>
To:
Cc: public-comments-wcag20@w3.org
 Dear ,

The Web Content Accessibility Guidelines Working Group has reviewed the
comments you sent [1] on the Last Call Working Draft [2] of the Techniques
for WCAG 2.0 published on 6 Mar 2014. Thank you for having taken the time
to review the document and to send us comments!

The Working Group's response to your comment is included below.

Please review it carefully and let us know by email at
public-comments-wcag20@w3.org if you agree with it or not before 28th Oct
2014. In case of disagreement, you are requested to provide a specific
solution for or a path to a consensus with the Working Group. If such a
consensus cannot be achieved, you will be given the opportunity to raise a
formal objection which will then be reviewed by the Director during the
transition of this document to the next stage in the W3C Recommendation
Track.

Thanks,

For the Web Content Accessibility Guidelines Working Group,
Michael Cooper
W3C Staff Contact

 1. (reference not available)
 2. http://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140306/


=====

Your comment on ARIA7: Using aria-labelledby for link purpose:
> https://github.com/w3c/wcag/pull/33
> 
> Changing accessible name from rendered/visible text generally causes
> accessibility issues. Especially, changing accessible name completely
> different one from rendered/visible text causes serious accessibility
> issues.
> 
> ARIA 1.0 Recommendation provides some examples of similar issues. In a
> note of |aria-hidden| 
>
http://www.w3.org/TR/2014/REC-wai-aria-20140320/states_and_properties#aria-hidden
> 
> Note: Authors are advised to use extreme caution and consider a wide
> range of disabilities when hiding visibly rendered content from
> assistive technologies. For example, a sighted, dexterity-impaired
> individual may use voice-controlled assistive technologies to access a
> visual interface. If an author hides visible link text "Go to checkout"
> and exposes similar, yet non-identical link text "Check out now" to the
> accessibility API, the user may be unable to access the interface they
> perceive using voice control. Similar problems may also arise for screen
> reader users. For example, a sighted telephone support technician may
> attempt to have the blind screen reader user click the "Go to checkout"
> link, which they may be unable to find using a type-ahead item search
> ("Go to…").
> As Example 1 of ARIA7 changes accessible name from "Read more..." to
> "Storms hit east coast", people who use voice control or who are blind
> and communicating with sighted person may face issues.
> 
> Thus we should get rid of Example 1 of ARIA7.
>  takenspc	ARIA7 Remove Example 1


Working Group Resolution (LC-2961):
Thank you for your comment.  The working group has reviewed the comment and
agrees that the example could cause accessibility issues for some users
with disabilities and should be removed from this technique.  

The group also agreed to update example 1 as follows by adding a redundant
referenence to the "Read more text".

Example 1: Providing additional information for links

This example will mean that the link text as shown on screen is then used
as the start of the accessible name for the link. Popular screen readers
like JAWS and NVDA will announce this as:

"Read more ...Storms hit east coast" and will display that same text in the
links list which is very useful for screen reader users who may browse by
links. 

<h2 id="headline">Storms hit east coast</h2>

<p>Torrential rain and gale force winds have struck the east coast, causing
flooding in many coastal towns.
<a id="p123" href="news.html" aria-labelledby="p123 headline">Read
more...</a></p>

NOTE: Technique ARIA 8 addresses the use of aria-label when link text may
not be available and thus also provides a solution for that particular
scenario.

We hope this addresses your concerns.

----
Received on Tuesday, 21 October 2014 16:41:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:18 UTC