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

RE: Default for auto-generated content (JM1 / IBM45)

From: Richards, Jan <jrichards@ocad.ca>
Date: Tue, 2 Nov 2010 22:15:04 -0400
To: Alastair Campbell <acampbell@nomensa.com>, "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <F2C77FB59A1A4840A01EF5F59B1826E20A283073CD@ocadmail.ocad.ca>
Hi Alastair,

Thanks for this.

Our wording for the auto-generated SC is now:

Auto-Generate Accessible Content (WCAG): If the authoring tool automatically generates content, then it provides the default option of having that web content meet the WCAG 2.0 success criteria when published

So "default" is in there. And the next SC after it in the new order is:

Template Auto-Selection (WCAG): If the authoring tool automatically selects templates or pre-authored content, then the selections meets the WCAG 2.0 success criteria when used:

So I think the default nature of the accessibility support is actually even more clear in the new organization.

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

From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On Behalf Of Alastair Campbell
Sent: November 1, 2010 6:33 PM
To: w3c-wai-au@w3.org
Subject: Default for auto-generated content (JM1 / IBM45)

Hi everyone,

I was going to reply to JM1, saying that it was covered, but there's a clash with comment IBM45. (Both regarding B.1.3.1, Accessible Auto-Generated Content.)

IBM45 essentially asked that a tool provide an option that complies, but it doesn't have to be the default.

JM1 asks that the guidelines "make clear that an authoring tool should produce accessible content with its default settings."

Having read the latest draft, I don't think the draft reply covers JM's issue:
"B.1.3.1 Accessible Auto-Generated Content (WCAG Level A): If the authoring tool automatically generates content, then it provides the option of having that web content meet the WCAG 2.0 success criteria when published."
http://www.w3.org/WAI/AU/2010/ED-ATAG20-20101028/#sc_b131

Surely default templates (and other automatically generated content) should be accessible by default?
I can understand allowing for other (non-accessible) options as well, and allowing the user to change the default, but as it stands the accessible option could be hidden in a dusty back-room dialogue box.

Was there another scenario at the face to face that necessitated "provides the option"? It seems to contradict the guideline & rational, and I would expect that to be a level A or perhaps AA requirement.

Kind regards,

-Alastair
Received on Wednesday, 3 November 2010 02:15:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 3 November 2010 02:15:54 GMT