Second Draft of UAAG Exit Criteria

I received some feedback on the first draft of the UAAG 2.0 exit 
criteria, which I am incorporating into the following proposal:

Exit Criteria
The User Agent Accessibility Guidelines Working Group intends to submit
this document for consideration as a W3C Proposed Recommendation as soon
as the following conditions are met. We expect to complete testing and
show evidence of meeting all exit criteria, and change or remove the
at-risk items as needed, no earlier than @@[date]@@.

1. Define test cases: Complete a set of tests needed to cover all UAAG
normative success criteria.

2. Test Implementations: Perform these tests and verify independent 
results on user agents, and to the extent needed, combinations of users 
agents and extensions.

Note on Independent Implementations:
a) Success criteria that rely solely on the rendering engine of
the user agent (e.g. x.x.x) will need implementations of two different 
rendering engines.

b) Success criteria that rely solely with the user agent user interface 
(e.g. x.x.x) may have implementations using the same rendering engine.

c) Success criteria that can be met with an extension to the user agent
may be met with two different extensions on the same base user agent.

d) Implementations (plugins, extensions or user agents) must be from 
different code bases in order to be considered independent.





On 2/6/2015 6:43 PM, Jeanne Spellman wrote:
> UAWG WG,
>
> Since getting Exit Criteria approved is a long process, I'm getting it
> started.
>
> Exit Criteria are used by the W3C Director (or designate) to show that
> the spec deserves to advance to the next stage of the W3C process. It is
> used to show that the spec works in the real world by showing that each
> feature is implemented in 2 independent products. Good exit criteria
> tell a convincing story that the spec is mature, complete and widely
> implemented.
>
> I expect that a tricky issue for us will be determining what are
> independent products when many products share the same rendering engine.
>
> Here are some sample Exit Criteria:
>
> ATAG: http://www.w3.org/TR/2013/CR-ATAG20-20131107/#exit
> WCAG: http://www.w3.org/TR/2008/CR-WCAG20-20080430/#status_exit
> ARIA: http://www.w3.org/TR/2011/CR-wai-aria-20110118/#sotd_exit
>
> Note that all of these include Features At Risk, so we need to finish up
> identifying all the implementations we have of each success criteria.
>
> Here's a proposal for a first draft of the Exit Criteria for UAAG 2.0:
>
> ----------------------------------------
> Exit Criteria
> The User Agent Accessibility Guidelines Working Group intends to submit
> this document for consideration as a W3C Proposed Recommendation as soon
> as the following conditions are met. We expect to complete testing and
> show evidence of meeting all exit criteria, and change or remove the
> at-risk items as needed, no earlier than @@[date]@@.
>
> 1. Define test cases: Identify a set of tests needed to cover all UAAG
> normative success criteria.
>
> 2. Test Implementations: Perform these tests on multiple separate
> combinations of users agents and/or user agents and extensions.
>
> 3. Verify interoperable results: Find at least two independent
> implementations of each normative success criterion.
>
> Note on Independent Implementations:
> 1) Success criteria that can only be met using the rendering engine of
> the user agent will need implementations of two different rendering
> engines.
>
> 2) Success criteria that can only be met with the user agent user
> interface may have implementations using the same rendering engine.
>
> 2) Success criteria that can be met with an extension to the user agent
> may be met with two different extensions on the same base user agent.
>
> 3) Implementations (plugins, extensions or user agents) must be from
> different code bases in order to be considered independent.
>
>

-- 
_______________________________
Jeanne Spellman
W3C Web Accessibility Initiative
jeanne@w3.org

Received on Thursday, 19 February 2015 17:54:49 UTC