W3C home > Mailing lists > Public > w3c-wai-au@w3.org > October to December 2010

ATAG2: Proposal on "prior to publishing" plus auto-generation

From: Richards, Jan <jrichards@ocad.ca>
Date: Thu, 11 Nov 2010 12:18:30 -0500
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <F2C77FB59A1A4840A01EF5F59B1826E20A283A907E@ocadmail.ocad.ca>
ISSUE: The "prior to publishing" comments open a big can of worms because of the many permutations:
- wikis workflow: frequent short "authoring sessions"+"publishing" events as the author works
- but "authoring session" is hard to use because authors can always exit
- automatic processes may be interspersed with the author workflow in many ways (e.g., before, during, after the author)

MULTI-PART PROPOSAL:

(1) Split Auto-Generate SC (Bonus: I think this will let us remove this Part B applicability note: "Applicability after the end of an authoring session:")

(was B.1.3.1) Auto-Generate Accessible Content for Publishing (WCAG): *Authors* have the default option that when *web content* is *automatically-generated* for *publishing* after the *end of an authoring session*, the content meets the WCAG 2.0 success criteria.
NOTE: This applies only to automatic processes specified by the authoring tool developer. This does not apply when *author actions prevent generation of accessible web content*.
- 3 WCAG levels

NEW DEFN: author actions prevent generation of accessible web content (there are so many I thought this deserved its own defn):
When the actions of authors prevents authoring tools from generating accessible web content (WCAG). Examples include:
- turning off accessibility options
- ignoring prompts for accessibility information (WCAG)
- providing faulty accessibility information (WCAG) at prompts
- modifying the authoring tool (e.g., via scripting, macros, etc.)
- installing plug-ins
- etc.

Ed. This SC now handles ONLY tools like W3C's email archiver, Facebook, etc. where some auto-content generation occurs just before end-user consumption.


(NEW SC) Auto-Generate Accessible Content for Authoring (WCAG): *Authors* have the default option that when *web content* is *automatically-generated* for an *authoring session* then one of the following is true:
(a) Accessible: the content meets the WCAG 2.0 success criteria without author input; or
(b) Prompting: during the automatic generation process, authors are prompted for any required accessibility information (WCAG); or
(c) Checking Active: after the automatic generation process, accessibility checking is active on the output; or
(d) Checking Suggested: authors have the default option to have accessibility checking suggested.
NOTE: This applies only to automatic processes specified by the authoring tool developer. This does not apply when actions of authors prevent generation of accessible web content (e.g., by providing faulty accessibility information, by installing additional plug-ins, by writing custom automated scripts, etc.).
- 3 WCAG levels

Ed. This SC handles auto-generation when the author is still available to help (with support of course as dictated by the rest of Part B). Note how the (c) and (d) wording is harmonized with my transformation proposal (http://lists.w3.org/Archives/Public/w3c-wai-au/2010OctDec/0062.html).


(2) Remove SC B.2.2.2 Availability.
Because availability is addressed already by (was B.3.2.1) Features Active by Default and (was B.3.2.4) Feature Prominence.


(3) Minor tweak to publishing (CHANGES IN CAPS):
Publishing: ANY point at which the authors or authoring tool make web content available to end users (e.g., uploading a web page, committing a change in a wiki, LIVE STREAMING). 


(4) Implementing ATAG 2.0 Appendix E on "Real-Time Content Production" renamed "Authoring Tools for Live Web Content" to match WCAG 2.0's use of "Live"


VARIOUS COMMENTS:
==================
MS22: B.1.3 "...prior to publishing." Invalidates the SC. If a tool generates content in real time, there is no content to meet WCAG 2.0 prior to publishing. The concept has no meaning. Please remove "prior to publishing." In B.1.3.1, B.1.3.2, and B.1.3.3.

OC17: -B.1.3 - What is the significance of "prior to publishing" in each guideline?

IBM46: B.1.3: unclear what "prior to publishing" means. What if I'm using Microsoft Word to create a document, then I save it as HTML. That's not publishing. It's not "published" until I upload it to my website. Does this requirement only apply to tools that include publishing? Or would it mean that if I use one tool that generates automatic content but doesn't publish and then FTP to upload files to my website, my "set" of authoring tools is non-compliant with ATAG? Per the definition, ATAG applies to all of the tools used in the process.





Cheers,
Jan

-- 
(Mr) Jan Richards, M.Sc.
jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
Inclusive Design Research Centre (IDRC) | http://inclusivedesign.ca/
Faculty of Design | OCAD University
Received on Thursday, 11 November 2010 17:18:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 11 November 2010 17:18:56 GMT