- From: Tim Boland <frederick.boland@nist.gov>
- Date: Fri, 04 Nov 2005 09:05:00 -0500
- To: w3c-wai-au@w3.org
Thanks for updating the techniques! I find the information in the notes at the beginning of the updated techniques document somewhat confusing. Why is the AUWG publishing the techniques along with the Guidelines if not to consider some ways (although not the only ways) of demonstrable sufficiency in meeting the ATAG2.0 success criteria, as an aid to those seeking to comply with ATAG2.0? (NOTE: the WCAG WG is developing informative Guide Documents to augment the normative WCAG2.0 success criteria in WCAG2.0; in these Guide Documents are listed, for each WCAG2.0 success criterion, at least one technique deemed by the WCAG WG to be "sufficient" for meeting the referenced success criterion, in that successful accomplishment of that technique would, in the WCAG WG's opinion, satisfy the stated success criterion. However, there may be other ways to meet the WCAG2.0 success criterion besides use of those techniques, and there are additional "advisory" techniques given to benefit accessibility, although these are not deemed "sufficient" in the sense mentioned previously.) Perhaps the AUWG could take a similar approach if appropriate? For example, the "strongly suggested" techniques referenced could be considered "sufficient" in the same sense as WCAG WG uses the word "sufficient"? I think that authoring tool accessibility may be demonstrable when implemented in technological components/interfaces, and the AUWG might want to give some more specific suggestions on testable techniques - ways- (although not the only techniques -ways-) that those seeking to satisfy the Authoring Tools success criteria might do so; otherwise, those wanting to claim conformance to ATAG2.0 might not have enough information to know where to start.. Thanks and best wishes Tim Boland NIST At 04:46 PM 11/2/2005 -0500, you wrote: >Hi everyone, > >The first installment of the new ATAG 2.0 techniques (A.2.1 - A.2.5) has >been updated in place at: > >http://www.w3.org/WAI/AU/2005/11/tech1.html > >Please comment or sign-up on the list. > >=================================================== > >Techniques for Checkpoint A.1.1 >Techniques for Checkpoint A.1.2 >Techniques for Checkpoint A.1.3 >Techniques for Checkpoint A.1.4 >Techniques for Checkpoint A.1.? >Techniques for Checkpoint A.2.1 - JR - ok >Techniques for Checkpoint A.2.2 - JR - ok >Techniques for Checkpoint A.2.3 - JR - ok >Techniques for Checkpoint A.2.4 - JR - ok >Techniques for Checkpoint A.2.5 - JR - ok >Techniques for Checkpoint A.2.6 >Techniques for Checkpoint A.2.7 >Techniques for Checkpoint A.2.8 >Techniques for Checkpoint A.2.9 >Techniques for Checkpoint A.3.1 >Techniques for Checkpoint A.3.2 >Techniques for Checkpoint A.3.3 >Techniques for Checkpoint A.4.1 >Techniques for Checkpoint B.1.1 >Techniques for Checkpoint B.1.2 >Techniques for Checkpoint B.1.3 >Techniques for Checkpoint B.1.4 >Techniques for Checkpoint B.2.1 - JR >Techniques for Checkpoint B.2.2 - JR >Techniques for Checkpoint B.2.3 - JR >Techniques for Checkpoint B.2.4 >Techniques for Checkpoint B.2.5 >Techniques for Checkpoint B.2.6 >Techniques for Checkpoint B.2.7 >Techniques for Checkpoint B.2.8 >Techniques for Checkpoint B.2.9 >Techniques for Checkpoint B.3.1 >Techniques for Checkpoint B.3.2 >Techniques for Checkpoint B.3.3 >Techniques for Checkpoint B.3.4 > >=================================================== > >Cheers, >Jan > >-- >Jan Richards, M.Sc. >User Interface Design Specialist >Adaptive Technology Resource Centre (ATRC) >Faculty of Information Studies >University of Toronto > > Email: jan.richards@utoronto.ca > Web: http://jan.atrc.utoronto.ca > Phone: 416-946-7060 > Fax: 416-971-2896 > > > > >-- >Jan Richards, M.Sc. >User Interface Design Specialist >Adaptive Technology Resource Centre (ATRC) >Faculty of Information Studies >University of Toronto > > Email: jan.richards@utoronto.ca > Web: http://jan.atrc.utoronto.ca > Phone: 416-946-7060 > Fax: 416-971-2896 > > >
Received on Friday, 4 November 2005 14:05:51 UTC