Re: RGAA (was RE: @summary in the wild)

summary attribut is requiered only for data table and we expect to change the guidelines to limit its use only on complex data table.

RGAA will be frequently updated specialy when ARIA will become official recommandation, it's a suite of unit test to verify conformity to wcag 2.0 (specially needed by the public services to verify that the webagency is really doing her job correctly when the tender target a wcag compliant website)

Aurélien
----- Mail Original -----
De: "stephane deschamps" <stephane.deschamps@orange-ftgroup.com>
À: "Patrick H. Lauke" <redux@splintered.co.uk>
Cc: "John Foliot" <jfoliot@stanford.edu>, "HTML Accessibility Task Force" <public-html-a11y@w3.org>, "W3C WAI-XTECH" <wai-xtech@w3.org>
Envoyé: Jeudi 10 Décembre 2009 17h54:16 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: RGAA (was RE: @summary in the wild)

RGAA V2 does two things:

1. Since it is targeted at public services, it assumes most of them will
mostly use HTML. So a lot of checkpoints deal with HTML/CSS/JS. It does deal
with all these in an accessibility-supported logic rather than a WCAG1
outlook.

2. It also integrates multimedia but to a lesser extent than HTML/CSS/JS.

I'm sure Aurélien (who helped in writing the RGAA) can be more specific when
he gets back to reading the list.
 
-- 
Kind regards,
Stéphane Deschamps
Orange-France Telecom Group / IT Accessibility



-----Message d'origine-----
De : Patrick H. Lauke [mailto:redux@splintered.co.uk] 
Envoyé : mercredi 9 décembre 2009 19:11
À : stephane.deschamps@orange-ftgroup.com
Cc : 'John Foliot'; 'HTML Accessibility Task Force'; 'W3C WAI-XTECH'
Objet : Re: @summary in the wild (was FW: [WebAIM] Jaws 11 and table
summary)

On 09/12/2009 17:03, stephane.deschamps@orange-ftgroup.com wrote:

> For what it's worth, @summary is a required attribute of the RGAA 2, the
> French adaptation of WCAG2 destined to all public service web sites.

Just wondering: the spirit of WCAG2 is that it's tech agnostic, and none 
of the techniques for, say, HTML are actually normative. Is RGAA 2 
actually grabbing a subset of the techniques and making them normative? 
Wouldn't this risk making it obsolete very quickly, not adaptable to new 
better techniques/technologies, etc...just like it happened with WCAG 1?

P
-- 
Patrick H. Lauke
______________________________________________________________
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]

www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com | http://flickr.com/photos/redux/
______________________________________________________________
Co-lead, Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
______________________________________________________________



*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************

Received on Thursday, 10 December 2009 23:47:36 UTC