RE: Applying ATAG to status updates

Hi Jan,

Post our status-updates discussion, I read into this more: "B.2.1.1 (was B.1.1.1) Accessible Content Production (WCAG): Authors can use the authoring tool to produce accessible web content."

In previous iterations I'd interpreted that as: any content you can produce with it should be accessible to whatever WCAG level you are aiming for.

I would test it by going through each interface feature  as an author, and seeing what the output was. E.g. can I add headings and it produces appropriate heading markup? When I add an image can I add alt text etc.
That doesn't mean that the heading levels are right or that the alternative text is appropriate, but that the interface and transformation from edited view -> rendered content is good.

A pass meant (to me) that the content you could add using the interface, you could add accessibly. (I.e. the accessibility matched the apparent functionality.)

However, reading the implementation guidance: "that authors who have the motivation and knowledge to create accessible web content using an authoring tool are not prevented from doing so."

I see what you mean about it being a low bar!

I would rather strengthen it than remove it. The SC could be read either way, so perhaps an update to the implementation guidance such as:
"The intent of this success criterion is to ensure that authors can create accessible web content for any type of content they are able to add though the interface."
Perhaps with a caveat about not applying to raw-code based interfaces?

Otherwise, I don't see anything in the B section that requires an HTML-based editor to implement headings, lists, or other types of structural content that would be required for creating WCAG 2 conformant pages.

Kind regards,

-Alastair