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

Default for auto-generated content (JM1 / IBM45)

From: Alastair Campbell <acampbell@nomensa.com>
Date: Mon, 1 Nov 2010 22:32:30 +0000
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <808133E8-D5D7-406A-9733-B09CB6182CC8@nomensa.com>
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."

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,

Received on Monday, 1 November 2010 22:33:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:39:59 UTC