RE: Proposal for updated ATAG 2.0 Exit Criteria
"Alex Li (LCA)" <[email protected]> Wed, 15 Apr 2015 14:41:14 +0000
| Newsgroups | gmane.org.w3c.accessibility.tools |
|---|---|
| Message-ID | <BN3PR0301MB1203E9C58531805E6D4CADE7C9E50@BN3PR0301MB1203.namprd03.prod.outlook.com> |
--_000_BN3PR0301MB1203E9C58531805E6D4CADE7C9E50BN3PR0301MB1203_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I have a clarifying question. I think I understand everything until I read=
the following.
"These six WCAG 2.0 success criteria are a sampling of the requiremen=
ts of WCAG (e.g. text alternatives for non-text content, keyboard accessibi=
lity, sufficient contrast)."
Can somebody explain to me what the sentence is for?
-----Original Message-----
From: Richards, Jan [mailto:[email protected]]
Sent: Wednesday, April 15, 2015 7:08 AM
To: [email protected]
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 C=
riteria 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/p=
ublic-permissive-exit-criteria.html)
- The section: "Success criteria referencing WCAG 2.0 for priorities" is ta=
ken from existing approved Exit Criteria.
----------------------
For this specification to be advanced to Proposed Recommendation, there mus=
t be at least two independent implementations of features that meet each su=
ccess criterion. Each of these features may be implemented by a different s=
et 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 sa=
me source code for the relevant feature(s). Sections of code that have no b=
earing on the implementation of this standard are exempt from this requirem=
ent. The authoring tools must be a shipping product or other publicly avail=
able version. Experimental implementations, specifically designed to pass t=
he 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 cr=
iteria that are dependent on WCAG 2.0 [3] for their levels, each ATAG 2.0 s=
uccess criterion must be implemented for two WCAG 2.0 success criteria at e=
ach level: A, AA, and AAA. These six WCAG 2.0 success criteria are a sampli=
ng 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]<mailto:[email protected]>
--_000_BN3PR0301MB1203E9C58531805E6D4CADE7C9E50BN3PR0301MB1203_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
#800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt;">
<div>I have a clarifying question. I think I understand everything un=
til I read the following. </div>
<div> </div>
<div style=3D"padding-left:36pt;">"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)."</div>
<div> </div>
<div>Can somebody explain to me what the sentence is for?</div>
<div> </div>
<div>-----Original Message-----<br>
From: Richards, Jan [<a href=3D"mailto:[email protected]">mailto:jrichards=
@ocadu.ca</a>]
<br>
Sent: Wednesday, April 15, 2015 7:08 AM<br>
To: [email protected]<br>
Subject: RE: Proposal for updated ATAG 2.0 Exit Criteria</div>
<div> </div>
<div>Just a reminder to all AUWG members: Please help ATAG 2.0 to mov=
e through CR by sending a message signalling whether or not you agree with =
the Exit Criteria proposal below.</div>
<div> </div>
<div>Thanks Tim and Alastair for responding already.</div>
<div> </div>
<div>PROPOSAL:</div>
<div> </div>
<div>Updated proposal to replace the current ATAG 2.0 Exit Criteria (<a hre=
f=3D"http://www.w3.org/TR/ATAG20/#exit">http://www.w3.org/TR/ATAG20/#exit</=
a>).</div>
<div> </div>
<div>Notes:</div>
<div>- The wording borrows from HTML5 (<a href=3D"http://dev.w3.org/html5/d=
ecision-policy/public-permissive-exit-criteria.html">http://dev.w3.org/html=
5/decision-policy/public-permissive-exit-criteria.html</a>)</div>
<div>- The section: "Success criteria referencing WCAG 2.0 for priorit=
ies" is taken from existing approved Exit Criteria.</div>
<div> </div>
<div>----------------------</div>
<div>For this specification to be advanced to Proposed Recommendation, ther=
e must be at least two independent implementations of features that meet ea=
ch success criterion. Each of these features may be implemented by a differ=
ent set of products and there is
no requirement that all features be implemented by a single product.</div>
<div> </div>
<div>*Independent authoring tools*</div>
<div>are tools by different developers that do not share (or derive from) t=
he 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 req=
uirement. The authoring tools must
be a shipping product or other publicly available version. Experimental imp=
lementations, specifically designed to pass the test suite and not intended=
for normal usage, are not permitted.</div>
<div> </div>
<div>*Implemented*</div>
<div>refers to situations in which a success criterion is applicable to a g=
iven authoring tool and the authoring tool meets the success criterion. Thi=
s is in contrast to situations in which a success criterion is not applicab=
le.</div>
<div> </div>
<div>*Success criteria referencing WCAG 2.0 for priorities* <THIS SECTIO=
N 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).</div>
<div>-----------------------</div>
<div> </div>
<div>Cheers,</div>
<div>Jan</div>
<div> </div>
<div> </div>
<div>(MR) JAN RICHARDS</div>
<div>PROJECT MANAGER</div>
<div>INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)</div>
<div>OCAD UNIVERSITY</div>
<div> </div>
<div>T 416 977 6000 x3957</div>
<div>F 416 977 9844</div>
<div>E <a href=3D"mailto:[email protected]">[email protected]</a></div>
<div> </div>
<div> </div>
</span></font>
</body>
</html>
--_000_BN3PR0301MB1203E9C58531805E6D4CADE7C9E50BN3PR0301MB1203_--