RE: Wrapping up the ATAG-WG

To kick off the discussion of future of accessible authoring tool guidance.=
..=0A=
=0A=
Some thoughts on where ATAG's requirements might go from here:=0A=
=0A=
1. By this point, WCAG is quite well known by accessibility folks and devel=
opers, but ATAG ... not so much (it doesn't help that ATAG is [1] a major a=
ir transport industry group, [2] a dutch appliance maker and [3] a Facebook=
-related slang word [3]).=0A=
=0A=
2. Nevertheless, in the short- to medium-term, ATAG 2.0 should remain the s=
table W3C reference. Anything else, would unnecessarily undermine all of th=
e group's many years of work.=0A=
=0A=
3. It's important to remember that there is a lot of nuance in ATAG. It's n=
ot just about one type of tool producing one type of content. It was design=
ed to apply any time people are creating or modifying web content for use b=
y other people. This can include social media, content management systems, =
integrated development environments, as well as more conventional web autho=
ring tools.=0A=
=0A=
4. WCAG 2.0 is currently locked down with just a small mention of ATAG in i=
ts introduction (http://www.w3.org/TR/WCAG20/#intro), but the WCAG 2.0 supp=
ort documentsare still open and could be updated to include links to ATAG 2=
.0 along with the explanation that when web content is used to create a web=
 authoring interface, ATAG 2.0 applies.=0A=
=0A=
5. If a minor update to WCAG is published (e.g. a WCAG 2.1), then the exist=
ing (very concise) ATAG reference might be expanded. ALSO, in WCAG's confor=
mance section it might be pointed out that it is not enough for web-based a=
uthoring tools to just conform to WCAG, when ATAG also applies.=0A=
=0A=
6. In the longer-term, if a major WCAG update is published (e.g. WCAG 3.0),=
 Part A of ATAG 2.0 would be a candidate for rolling into WCAG.=0A=
- Some success criteria in Part A restate WCAG success criteria for the ben=
efit of non-web based tools (to which ATAG also applies) =0A=
- There are a few things that could be applied more generally than authorin=
g tools (e.g. A.3.1.6 Present Keyboard Commands; A.3.2.3 Static Input Compo=
nents)=0A=
- There are also some special cases (e.g. Preview (A.3.7), Independence of =
display (A.3.6.1), etc.) that perhaps could become something like a "WCAG -=
 Authoring Tool User Interface Extension".=0A=
- Maybe ATAG could take advantage of WCAG's name recognition with a re-bran=
ding such as a "WCAG - Authoring Tool Support Extension"=0A=
=0A=
7. If WAI ever embarks on a standard for general-purpose application access=
ibility (e.g. applying to non-web-based desktop apps, mobile apps, web apps=
, etc.), much of Part A could be rolled in and of course much of Part B wou=
ld apply to applications that are also authoring tools.=0A=
=0A=
[1] http://www.atag.org/about-us/who-we-are.html=0A=
[2] http://www.atagnederland.com/=0A=
[3] http://www.urbandictionary.com/define.php?term=3DAtag=0A=
=0A=
Cheers,=0A=
Jan=0A=
=0A=
(MR) JAN RICHARDS=0A=
PROJECT MANAGER=0A=
INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)=0A=
OCAD UNIVERSITY=0A=
=0A=
T 416 977 6000 x3957=0A=
F 416 977 9844=0A=
E [email protected]=0A=
=0A=
________________________________________=0A=
From: Richards, Jan [[email protected]]=0A=
Sent: October-26-15 10:48 AM=0A=
To: [email protected]=0A=
Subject: Wrapping up the ATAG-WG=0A=
=0A=
Hi all,=0A=
=0A=
Today's ATAG-WG call is CANCELLED. And, sinces Jutta will be traveling next=
 week, the call next Monday (Nov 2) is also CANCELLED.=0A=
=0A=
That leaves us with no further calls before the working group is scheduled =
to wrap up on Nov 5 (http://www.w3.org/WAI/AU/2010/auwg_charter).=0A=
=0A=
So, instead we'd like to invite you to do two things:=0A=
=0A=
(1) Think about the future of accessible authoring tool guidance (e.g. how =
to promote ATAG 2.0, which W3C groups could take up the effort, is anything=
 missing, etc.). Send any thoughts to the mailing list, where they can be a=
rchived.=0A=
=0A=
(2) Join us for an informal call (on a date TBD in November) for past and p=
resent ATAG-WG members to celebrate ATAG 2.0 and discuss the future of acce=
ssible authoring tool guidance. Hopefully, we can find a time that works fo=
r most people. Please let us know if you'd be interested in joining us.=0A=
=0A=
Cheers,=0A=
Jan=0A=
=0A=
=0A=
(MR) JAN RICHARDS=0A=
PROJECT MANAGER=0A=
INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)=0A=
OCAD UNIVERSITY=0A=
=0A=
T 416 977 6000 x3957=0A=
F 416 977 9844=0A=
E [email protected]=0A=
=0A=