Y'a-t-il eu réponse sur la question d'Aurélien ? 2015-12-16 12:07 GMT+01:00 Aurélien Levy <[email protected]>:
> Bonjour Dominique, > > Merci de cette information, je profite de l'occasion pour t'interroger > concernant la mise à jour d'Accessiweb vers le RGAA 3.0 ou vers une > version nettoyée de html5/aria (le RGAA 3.0 ayant également une série de > bugs connus). > > Il me semble que ce point n'as pas été évoqué lors du dernier séminaire. > Il est étrange à l'heure actuelle de continuer de garder cette différence > sachant que c'était un des principaux arguments justifiant le passage à > Accessiweb. Il me semble également important de savoir si Accessiweb va > continuer à vivre en parallèle du RGAA. > > Merci d'informer le GTA quand à la position et à l'agenda que compte avoir > Braillenet vis à vis de ce sujet qui nous impacte tous. > > A Bientôt > > Aurélien > > Bonjour à tous, > Pour votre information je vous fais suivre ci dessous le message de Jeanne > Spellman, UAWG W3C. > Cordialement, > Dominique Burger > Présidnet de BrailleNet > > The User Agent Accessibility Guidelines Working Group (UAWG) has published > User Agent Accessibility Guidelines (UAAG 2.0) and UAAG 2.0 Reference as > W3C Working Group Notes. > http://www.w3.org/TR/UAAG20/ > http://www.w3.org/TR/UAAG20-Reference/ > > UAAG 2.0 is complete. It provides specific guidance for browsers and other > user agents, and reference information for accessibility professionals. > > The UAWG has identified implementations of the features ("success > criteria") of UAAG 2.0, demonstrating that it is possible to implement the > UAAG 2.0 success criteria. The threshold for a specification becoming a > formal W3C Recommendation ordinarily involves extensive formal testing of > implementations of each success criteria across multiple user agents -- > which in the case of UAAG 2.0 would have required manual testing of many > browser user interfaces. Sufficient testing resources were not available > for this level of testing. W3C does not currently plan to advance UAAG 2.0 > to Recommendation status. W3C plans to include user agent accessibility > considerations in future accessibility guidelines work. > > UAAG 2.0 is still needed and relevant, and may be increasingly relevant in > the future. The work of the current task forces for Mobile Accessibility > and Low Vision Accessibility show the importance of combined consideration > of content, user interface, extensions, applications and user agents. While > many of the UAAG 2.0 features are supported in individual browsers, there > is a need for more consistent and reliable support for accessibility > features across all browsers and user agents. UAAG 2.0 provides specific > accessibility guidance for user agent developers who want to build a better > user experience for all. > > Comments: > Comments on the Notes can be sent to [email protected] (Public > Archive). Although the UAAG working group is closing and will not respond, > comments can provide useful input for future work in this area. > > Background: > > UAAG 2.0 defines how browsers, browser extensions, media players, readers, > and other "user agents" should support accessibility for people with > disabilities and work with assistive technologies. UAAG 2.0 Reference > provides additional information about the guidelines and success criteria, > including intent, examples, and resources. For more information on UAAG and > other standards from the W3C Web Accessibility Initiative (WAI), see: > > * UAAG Overview <http://www.w3.org/WAI/intro/uaag.php> > <http://www.w3.org/WAI/intro/uaag.php> > * WAI Guidelines and Techniques <http://www.w3.org/WAI/guid-tech.html> > <http://www.w3.org/WAI/guid-tech.html> > * User Agent Accessibility Guidelines Working Group (UAWG) > <http://www.w3.org/WAI/UA/> <http://www.w3.org/WAI/UA/> > > URI: > The first URI above goes to the latest version of the document. The > "dated" version of this draft is: > <http://www.w3.org/TR/2015/NOTE-UAAG20-20151215/> > <http://www.w3.org/TR/2015/NOTE-UAAG20-20151215/> The difference between > these URIs are explained in Referencing and Linking to WAI Guidelines and > Technical Documents at: <http://www.w3.org/WAI/intro/linking.html> > <http://www.w3.org/WAI/intro/linking.html> > > 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, > > Jim Allan, UAWG Chair > Jeanne Spellman, UAWG W3C Staff Contact > Judy Brewer, WAI Director > > > > _______________________________________________ > liste_gta mailing > [email protected]http://list.accessiweb.org/mailman/listinfo/liste_gta_list.accessiweb.org > > > > -- > Aurélien Levy > ---- > Temesis > > > _______________________________________________ > liste_gta mailing list > [email protected] > http://list.accessiweb.org/mailman/listinfo/liste_gta_list.accessiweb.org > > -- *Ariane Andurand* *Experte CMS Joomla! depuis 2008* *Membre du GTA depuis 2011* @ArianeWedesign
_______________________________________________ liste_gta mailing list [email protected] http://list.accessiweb.org/mailman/listinfo/liste_gta_list.accessiweb.org
