Re: Authoring tools and WCAG 2.0's "Accessibility Supported"

I think that for accessibility supported in ATAG shall means the same inside 
WCAG: a developer can use technologies like XHTML, CSS, JS (for Web based 
user interfaces) and use them in a manner that are accessible by assistive 
tecnologies. A solution for script-based interfaces and for RIA will be to 
require, in baseline, to refer to WAI-ARIA.
Btw, referring to WCAG 2 for User interface accessibility requirements refer 
indirectly also to WAI-ARIA (if i remember well, is guideline 4.1, success 
criteria 4.1.2).

----- Original Message ----- 
From: "Jan Richards" <jan.richards@utoronto.ca>
To: "WAI-AUWG List" <w3c-wai-au@w3.org>
Sent: Wednesday, May 14, 2008 10:44 PM
Subject: Authoring tools and WCAG 2.0's "Accessibility Supported"


>
> Just a thought...
>
> Looking at WCAG 2.0's concept of "Accessibility Supported"
> (http://www.w3.org/TR/WCAG20/#accessibility-supporteddef) I started
> wondering about support that authoring tools might provide.
>
> Checkers aren't likely advanced enough yet but I can imagine
> multi-format checkers that would have settings re: which technologies
> the user believed to be accessibility supported. (or similarly at the
> stage of choosing formats)
>
> Any other thoughts?
>
> Cheers,
> Jan
>
>


--------------------------------------------------------------------------------



No virus found in this incoming message.
Checked by AVG.
Version: 8.0.100 / Virus Database: 269.23.16/1446 - Release Date: 16/05/2008 
7.42