Thread Subject: Re: 7-C Prompts (in authoring tools)

Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.

From: Andrew Kirkpatrick
Date: Tue, Feb 26 2008 1:00 PM

Judy,
Some comments:

> The proposed version from Sean, Jan 9, states:
> "Authoring tools with a user interface must procured and
operated
> such that they provide, either alone or with additional tools, a mode
> which prompts authors to create accessible content."

I'm not sure that we're gaining anything by mandating that tools are
operated with prompting active - it is not likely enforceable, and to
the extent that it is enforceable it is entirely redundant to the
web/software standards.

This is my preference, apart from the above concern.

> The version from Judy, Jan 9, states:
> "Authoring tools with a user interface, to the extent they
> provide a
> prompting framework, must provide a mode which prompts authors to
> create accessible content."

Judy, what do you mean by a prompting framework? If the app prompts for
other things it should prompt for accessibility?

> The version from Peter, Jan 9, states:
> "An authoring tool, or suite of authoring tools used to author
> content, where that suite provides a user interface, must provide a
> mode which prompts authors to create accessible content."

This also raises a concern that is avoided in Sean's, which is that
sometimes 3rd party tools provide this function. I see this on the wiki
but not in your email.

AWK

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University