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

Level A:   Provide the ability to use structural markup.

This could work, but will need a definition.

Structured content is defined ( under "content (structured)"), how about something like:

"If the web content allows for structured content, and controls are included to edit text formatting, then controls for editing structured content should also be available."

The first bit is rather clumsy, I'm just trying to say: if the web content allows for structure. It applies to HTML & PDF, not so much to Flash.


Level AA:   Default to structural markup.

Do you think in most cases this means some amount of auto-generation by the tool, in which case B.1.1.2 might cover it?

Not really, 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!)

I'd like to say (even at level A) that they should default to structural controls over formatting controls, but you'd have to get into the nitty gritty of what is or is not structured vs formatting, and that would be quite HTML specific.

Also, another SC that has bearing here is:
B.2.2.1 Accessible Option Prominence (WCAG): If authors are provided with a choice of authoring actions for achieving the same authoring outcome (e.g. styling text), then options that will result in accessible web content (WCAG) are at least as prominent as options that will not.

That's a good point, and I had that in mind, it's just that there isn't anything that says controls for editing structured content should be there.

Kind regards,

-Alastair