RE: Proposal for updated ATAG 2.0 Exit Criteria
Tom Babinszki <[email protected]> Wed, 15 Apr 2015 20:38:49 -0400
| Newsgroups | gmane.org.w3c.accessibility.tools |
|---|---|
| Message-ID | <OFB902A573.BAD4E6BF-ON85257E29.00038965-85257E29.00038F2D@us.ibm.com> |
This is a multipart message in MIME format. --=_alternative 00038F2D85257E29_= Content-Type: text/plain; charset="US-ASCII" I agree. Tom Tom Babinszki IBM Human Ability and Accessibility Center E-mail: [email protected] Phone: (847) 917-2990 From: "Richards, Jan" <[email protected]> To: "[email protected]" <[email protected]> Date: 04/15/2015 10:14 AM Subject: RE: Proposal for updated ATAG 2.0 Exit Criteria Just a reminder to all AUWG members: Please help ATAG 2.0 to move through CR by sending a message signalling whether or not you agree with the Exit Criteria proposal below. Thanks Tim and Alastair for responding already. PROPOSAL: Updated proposal to replace the current ATAG 2.0 Exit Criteria ( http://www.w3.org/TR/ATAG20/#exit). Notes: - The wording borrows from HTML5 ( http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html ) - The section: "Success criteria referencing WCAG 2.0 for priorities" is taken from existing approved Exit Criteria. ---------------------- For this specification to be advanced to Proposed Recommendation, there must be at least two independent implementations of features that meet each success criterion. Each of these features may be implemented by a different set of products and there is no requirement that all features be implemented by a single product. *Independent authoring tools* are tools by different developers that do not share (or derive from) the same source code for the relevant feature(s). Sections of code that have no bearing on the implementation of this standard are exempt from this requirement. The authoring tools must be a shipping product or other publicly available version. Experimental implementations, specifically designed to pass the test suite and not intended for normal usage, are not permitted. *Implemented* refers to situations in which a success criterion is applicable to a given authoring tool and the authoring tool meets the success criterion. This is in contrast to situations in which a success criterion is not applicable. *Success criteria referencing WCAG 2.0 for priorities* <THIS SECTION COPIED FROM EXISTING APPROVED EXIT CRITERIA> For the thirteen ATAG 2.0 success criteria that are dependent on WCAG 2.0 [3] for their levels, each ATAG 2.0 success criterion must be implemented for two WCAG 2.0 success criteria at each level: A, AA, and AAA. These six WCAG 2.0 success criteria are a sampling of the requirements of WCAG (e.g. text alternatives for non-text content, keyboard accessibility, sufficient contrast). ----------------------- Cheers, Jan (MR) JAN RICHARDS PROJECT MANAGER INCLUSIVE DESIGN RESEARCH CENTRE (IDRC) OCAD UNIVERSITY T 416 977 6000 x3957 F 416 977 9844 E [email protected] --=_alternative 00038F2D85257E29_= Content-Type: text/html; charset="US-ASCII" <font size=2 face="sans-serif">I agree.</font> <br><font size=2 face="sans-serif">Tom</font> <br> <br><font size=2 face="sans-serif">Tom Babinszki<br> IBM Human Ability and Accessibility Center<br> E-mail: [email protected]<br> Phone: (847) 917-2990<br> </font> <br> <br> <br> <br><font size=1 color=#5f5f5f face="sans-serif">From: </font><font size=1 face="sans-serif">"Richards, Jan" <[email protected]></font> <br><font size=1 color=#5f5f5f face="sans-serif">To: </font><font size=1 face="sans-serif">"[email protected]" <[email protected]></font> <br><font size=1 color=#5f5f5f face="sans-serif">Date: </font><font size=1 face="sans-serif">04/15/2015 10:14 AM</font> <br><font size=1 color=#5f5f5f face="sans-serif">Subject: </font><font size=1 face="sans-serif">RE: Proposal for updated ATAG 2.0 Exit Criteria</font> <br> <hr noshade> <br> <br> <br><tt><font size=2>Just a reminder to all AUWG members: Please help ATAG 2.0 to move through CR by sending a message signalling whether or not you agree with the Exit Criteria proposal below.<br> <br> Thanks Tim and Alastair for responding already.<br> <br> PROPOSAL:<br> <br> Updated proposal to replace the current ATAG 2.0 Exit Criteria (</font></tt><a href=http://www.w3.org/TR/ATAG20/#exit><tt><font size=2>http://www.w3.org/TR/ATAG20/#exit</font></tt></a><tt><font size=2>).<br> <br> Notes:<br> - The wording borrows from HTML5 (</font></tt><a href="http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html"><tt><font size=2>http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html</font></tt></a><tt><font size=2>)<br> - The section: "Success criteria referencing WCAG 2.0 for priorities" is taken from existing approved Exit Criteria.<br> <br> ----------------------<br> For this specification to be advanced to Proposed Recommendation, there must be at least two independent implementations of features that meet each success criterion. Each of these features may be implemented by a different set of products and there is no requirement that all features be implemented by a single product.<br> <br> *Independent authoring tools*<br> are tools by different developers that do not share (or derive from) the same source code for the relevant feature(s). Sections of code that have no bearing on the implementation of this standard are exempt from this requirement. The authoring tools must be a shipping product or other publicly available version. Experimental implementations, specifically designed to pass the test suite and not intended for normal usage, are not permitted.<br> <br> *Implemented*<br> refers to situations in which a success criterion is applicable to a given authoring tool and the authoring tool meets the success criterion. This is in contrast to situations in which a success criterion is not applicable.<br> <br> *Success criteria referencing WCAG 2.0 for priorities*<br> <THIS SECTION COPIED FROM EXISTING APPROVED EXIT CRITERIA><br> For the thirteen ATAG 2.0 success criteria that are dependent on WCAG 2.0 [3] for their levels, each ATAG 2.0 success criterion must be implemented for two WCAG 2.0 success criteria at each level: A, AA, and AAA. These six WCAG 2.0 success criteria are a sampling of the requirements of WCAG (e.g. text alternatives for non-text content, keyboard accessibility, sufficient contrast).<br> -----------------------<br> <br> Cheers,<br> Jan<br> <br> <br> (MR) JAN RICHARDS<br> PROJECT MANAGER<br> INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)<br> OCAD UNIVERSITY<br> <br> T 416 977 6000 x3957<br> F 416 977 9844<br> E [email protected]<br> <br> </font></tt> <br> --=_alternative 00038F2D85257E29_=--