Proposal for updated ATAG 2.0 Exit Criteria

Hi all,

Since it seems like we will be able to amend the ATAG 2.0 exit criteria, here's an idea for how to start:

(borrowing heavily from HTML5 and CSS exit criteria (which are virtually the same - http://www.w3.org/TR/css3-fonts/#cr-exit-criteria)

-------------
For this specification to be advanced to Proposed Recommendation, there must be at least two independent implementations of each feature. Each feature may be implemented by a different set of products and there is no requirement that all features be implemented by a single product.

Notes:

Note 1: "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.

Note 2: "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.

Note 3: Thirteen ATAG 2.0 success criteria are dependent on WCAG 2.0 for their levels (i.e. A.1.1.1 Web-Based Accessible (WCAG), B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG), etc.). These will be tested at WCAG 2.0 Level A.
-------------


Cheers,
Jan

(MR) JAN RICHARDS
PROJECT MANAGER
INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
OCAD UNIVERSITY

T 416 977 6000 x3957
F 416 977 9844
E jrichards@ocadu.ca

Received on Monday, 30 March 2015 16:57:08 UTC