Re: Proposal for updated ATAG 2.0 Exit Criteria
Alastair Campbell <[email protected]> Fri, 17 Apr 2015 10:06:34 +0100
| Newsgroups | gmane.org.w3c.accessibility.tools |
|---|---|
| Message-ID | <D1568184.2384E%[email protected]> |
--_000_D15681842384Eacampbellnomensacom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Hi Alex
You wrote:
"WCAG 2.0 has already been tested for implementability. But that was only =
for web pages not authoring tools."
I=92m trying to think where that would apply differently. The WCAG SC in AT=
AG apply to web based interfaces and web output.
Just thinking through a few examples:
- A.1.1.1 is basically a WCAG check of the authoring interface, that should=
apply to any web page/app and isn=92t unique to authoring tools.
- B.1.1.1 Content auto-generation after authoring session: it is easy not t=
o generate different (inaccessible) content after the authoring session.
- B.1.2.1 Restructuring and Recoding Transformations: Is a WCAG check of co=
ntent output.
- B.2.3.1 Alternative Content is Editable: Is non-text content only, so isn=
=92t that many SC from WCAG. But even so it is a straightforward WCAG check=
that isn=92t particular to authoring tools.
- B.2.4.1 Accessible Template Options: Nothing unique to authoring tools he=
re=85
For a web-based authoring tool (like Defacto/Drupal) the distinction isn=92=
t very meaningful, the interface and the output are synonymous.
Can you think of any examples where the authoring tools aspect makes it uni=
que or harder for authoring tools?
Kind regards,
Alastair
--_000_D15681842384Eacampbellnomensacom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space;=
-webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14p=
x; font-family: Calibri, sans-serif;"><div><span style=3D"font-family: Cali=
bri; font-size: 11pt;">Hi Alex</span></div><div><span style=3D"font-family:=
Calibri; font-size: 11pt;"><br></span></div><div><span style=3D"font-famil=
y: Calibri; font-size: 11pt;">You wrote:</span></div><span id=3D"OLK_SRC_BO=
DY_SECTION"><div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:s=
chemas-microsoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:of=
fice:word" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xml=
ns=3D"http://www.w3.org/TR/REC-html40"><div lang=3D"EN-US" link=3D"blue" vl=
ink=3D"purple"><div class=3D"WordSection1"><p class=3D"MsoNormal"><span sty=
le=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73,=
125);">"<i>WCAG 2.0 has already been tested for implementability.&nbs=
p; But that was only for web pages not authoring tools.</i>"</span></p=
></div></div></div></span><div><br></div><div>I=92m trying to think where t=
hat would apply differently. The WCAG SC in ATAG apply to web based interfa=
ces and web output.</div><div><br></div><div>Just thinking through a few ex=
amples:</div><div>- A.1.1.1 is basically a WCAG check of the authoring inte=
rface, that should apply to any web page/app and isn=92t unique to authorin=
g tools.</div><div>- B.1.1.1 Content auto-generation after authoring sessio=
n: it is easy not to generate different (inaccessible) content after the au=
thoring session.</div><div>- B.1.2.1 Restructuring and Recoding Transformat=
ions: Is a WCAG check of content output.</div><div>- B.2.3.1 Alternati=
ve Content is Editable: Is non-text content only, so isn=92t that many SC f=
rom WCAG. But even so it is a straightforward WCAG check that isn=92t parti=
cular to authoring tools.</div><div>- B.2.4.1 Accessible Template Opti=
ons: Nothing unique to authoring tools here=85</div><div><br></div><div><di=
v>For a web-based authoring tool (like Defacto/Drupal) the distinction isn=
=92t very meaningful, the interface and the output are synonymous.</div></d=
iv><div><br></div><div>Can you think of any examples where the authoring to=
ols aspect makes it unique or harder for authoring tools?</div><div><br></d=
iv><div>Kind regards,</div><div><br></div><div>Alastair</div><span id=3D"OL=
K_SRC_BODY_SECTION"><div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=
=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schemas-microso=
ft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/=
omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><div lang=3D"EN-US" link=3D=
"blue" vlink=3D"purple"><div class=3D"WordSection1"><p class=3D"MsoNormal">=
<span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rg=
b(31, 73, 125);"><o:p></o:p></span></p><p class=3D"MsoNormal"><span style=
=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 1=
25);"><o:p> </o:p></span></p></div></div></div></span><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></body></html>
--_000_D15681842384Eacampbellnomensacom_--