W3C home > Mailing lists > Public > w3c-wai-au@w3.org > January to March 2011

RE: Proposal to remove "B.2.1.1" (was B.1.1.1)

From: Richards, Jan <jrichards@ocad.ca>
Date: Thu, 24 Feb 2011 23:26:29 -0500
To: Alastair Campbell <acampbell@nomensa.com>
CC: AUWG <w3c-wai-au@w3.org>
Message-ID: <F2C77FB59A1A4840A01EF5F59B1826E20A30E8F841@ocadmail.ocad.ca>
Hi Alastair,

Sorry, for the late reply, it's been a busy week...my comments inline:


> -----Original Message-----
> From: Alastair Campbell [mailto:acampbell@nomensa.com]
> Sent: February 22, 2011 1:52 PM
> To: Richards, Jan
> Cc: AUWG
> Subject: RE: Proposal to remove "B.2.1.1" (was B.1.1.1)
> 
> Hi Jan,
> 
> You'd suggested:
> 
> "B.X.X.X Structured Content Support: Authoring tools support the incorporation
> of
> document structure by one of the following:
>    (a) Auto-generated structure: Author entries are incorporated into
>        document structure that is automatically generated by the authoring
> tool, or
> 
>    (b) Author mechanisms: Editing-views include options for adding document
> structure."
> 
> That's good, do we need to narrow the scope though? Unless I'm missing
> something an authoring tool that creates non-markup content could not fulfil
> that guideline?
> 
> For example:
> B.X.X.X Structured Content Support: Where edited content can include markup
> with programmatically determinable relationships, the authoring tool supports
> the incorporation of document structure by one of the following:...

Or...
B.X.X.X Structured Content Support: For web content technologies that include mechanisms for specifying document structure, authoring tools support the incorporation of document structure by one of the following:
(a) Auto-generated structure: Author entries are incorporated into document structure that is automatically generated by the authoring tool, or
(b) Author mechanisms: Editing-views include options for adding document structure.

Cheers,
Jan

> 
> 
> A slight tangent was:
> 
> AC: The use-case I come across most is web based WYSIWYG editors (e.g. TinyMCE
> / CKeditor). Most of these editors allow you to use structural markup (with
> varying levels of quality), however, a CMS might remove headings so that
> authors can't mess up their automated accessibility results. (Having no
> headings passes the old nested-headings tests!)"
> 
> JR: OK but it would fail WCAG2.0 2.4.10 Section Headings
> 
> AC: Yes, the resulting content would fail WCAG. However, without a guideline
> like the one above, the authoring tool wouldn't fail ATAG for removing the
> heading control / drop-down from the interface.
> 
> Kind regards,
> 
> -Alastair
Received on Friday, 25 February 2011 04:26:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 25 February 2011 04:26:43 GMT