Bonjour,

Appel à commentaire très interessant.
Pour ce qui concerne ARIA 10 (ariadescribedby sans alt) cela ne devrait pas 
passer AccessiWeb HTML5/ARIA 1.1 car le support annoncé n'inclut pas Voice Over 
qui fait partie de la base de référence.
D'ailleurs si quelqu'un peut faire un petit test rapide (je n'ai pas de mac 
sous la main) ce serait bienvenu.
En revanche si il y à support de VO cela pourra faire partie d'une MAJ une fois 
les techniques publiées.


Je n'ai pas encore tout vérifié mais les techniques que j'ai pu vérifié sont 
déjà prise en charge par AW HTML5/ARIA à l'exception de :
- ARIA 7 et ARIA 8 (label et labelledby) dont le support annoncé semble 
insuffisant.
 
________________________________
Jean-Pierre Villain - Qelios - 06 98 08 50 49



________________________________
 De : Sylvie Duchateau <sylvie.duchat...@snv.jussieu.fr>
À : GTA <liste_gta@list.accessiweb.org> 
Envoyé le : Vendredi 17 janvier 2014 10h57
Objet : [Liste GTA] Appel à commentaires W3C sur Understanding et techniques 
pour WCAG 2.0
 

Bonjour à toutes et tous,
Le W3C a publié hier une nouvelle ébauche des documents d'accompagnement 
pour les WCAG 2.0: Understanding WCAG 2.0 et techniques for WCAG 2.0.
Le groupe de travail souhaite en particulier les commentaires de la 
communauté d'ici au 14 février prochain à propos des nouvelles 
techniques ARIA et en particulier la technique ARIA10 qui permettrait 
d'utiliser ariadescribedby pour donner une alternative à un élément 
graphique et se passer de l'attribut alt. La question est de savoir si 
cela est concevable.
Vous trouverez ci-dessous le message original publié sur la liste WAI-IG 
du W3C avec tous les liens et les modalités.
Bonne réception et bonne journée
Amicalement
Sylvie

-------- Message original --------
Sujet:     Call for Review: WCAG 2.0 Techniques Draft Updates

    Thu, 16 Jan 2014 20:17:32 +0000

    
Date :     Thu, 16 Jan 2014 14:17:19 -0600
De :     Shawn Henry <sh...@w3.org>

    

    


Dear WAI Interest Group Participants,

The W3C WAI announces a Call for Review of updates to two supporting documents 
for Web Content Accessibility Guideline (WCAG) 2.0. *This is not an update to 
WCAG 2.0, which is a stable document*.

The supporting documents (W3C Working Group Notes) are updated periodically to 
reflect current practices and technologies. Previously they were updated about 
once a year. The WCAG Working Group plans to update them more frequently.

The existing Techniques and Understanding documents remain in place as W3C 
Notes while these separate draft updates are under review and the WCAG Working 
Group addresses comments.

The following draft updates are available for review as Editors' Drafts:
- Techniques for WCAG 2.0 Editors' Draft
http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/
- Understanding WCAG 2.0 Editors' Draft
http://www.w3.org/WAI/GL/2014/WD-UNDERSTANDING-WCAG20-20140107/

The changes are highlighted in diff-marked versions at:
- http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/complete-diff.html
- 
http://www.w3.org/WAI/GL/2014/WD-UNDERSTANDING-WCAG20-20140107/complete-diff.html

Changes that apply to "How to Meet WCAG 2.0: A customizable quick reference..." 
are available in a draft at:<http://www.w3.org/WAI/WCAG20/quickref/20140107/>

Updates for review:
Most of the updates in this draft are new WAI-ARIA Techniques. The WCAG Working 
Group is still discussing appropriate ways to provide text alternatives for 
images -- specifically, is it OK to not provide an alt attribute and instead 
use ARIA attributes? We particularly request feedback on this issue and related 
techniques such as F65[1]. See the examples and details at:
- ARIA10: Using aria-labelledby to provide a text alternative for non-text 
content<http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/ARIA10>

Please send any comments on these Editors' Drafts by *14 February 2014*. 
Comments and contributions for additional WCAG 2.0 techniques can be sent via 
web form or e-mail, per:
- Instructions for Commenting on WCAG 2.0 Documents
http://www.w3.org/WAI/WCAG20/comments/

*Important notes about techniques*:
- The basis for determining conformance to WCAG 2.0 is the success criteria 
from the WCAG 2.0 standard -- not the techniques. W3C’s techniques are 
informative and are not intended to be required. Learn more from "Understanding 
Techniques for WCAG Success Criteria" 
at<http://www.w3.org/TR/UNDERSTANDING-WCAG20/understanding-techniques.html>
- Publication of techniques for a specific technology does not imply that the 
technology can be used in all cases to create accessible content that meets 
WCAG 2.0. Developers need to be aware of the limitations of specific 
technologies and ensure that they provide content in a way that is accessible 
to all their potential users.

If you are interested in actively contributing to the development of additional 
WCAG 2.0 techniques and support material through the WCAG Working Group, please 
see:
- Participating in WAI<  http://www.w3.org/WAI/participation>  and contact 
Michael Cooper

For an introduction to the WCAG documents, see:
- WCAG Overview
http://www.w3.org/WAI/intro/wcag.php

Please let us know if you have any questions. Thank you in advance for your 
comments.
Feel free to circulate this message to other lists; please avoid cross-postings 
where possible.

Regards,
Shawn Henry, W3C, WAI Outreach
Andrew Kirkpatrick, Adobe Systems Inc., WCAG WG Co-Chair
Joshue O Connor, WCAG WG Co-Chair
Michael Cooper, W3C, WCAG WG Staff Contact

---
[1] F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute 
on img elements, area elements, and input elements of type 
"image"<http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/F65>




-----
Shawn Lawton Henry
W3C Web Accessibility Initiative (WAI)
Massachusetts Institute of Technology (MIT)
e-mail: sh...@w3.org
phone: +1.617.395.7664
about: http://www.w3.org/People/Shawn/




_______________________________________________
liste_gta mailing list
liste_gta@list.accessiweb.org
http://list.accessiweb.org/mailman/listinfo/liste_gta_list.accessiweb.org
_______________________________________________
liste_gta mailing list
liste_gta@list.accessiweb.org
http://list.accessiweb.org/mailman/listinfo/liste_gta_list.accessiweb.org

Reply via email to