Thread Subject: Re: 7-C Prompts (in authoring tools)
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: Wed, Mar 19 2008 1:55 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Judy Brewer: "Re: 7-C Prompts (in authoring tools)"
- Previous message in thread: Sean Hayes: "Re: 7-C Prompts (in authoring tools)"
- Messages sorted by: Author | Thread | Date
> 7-C - PROMPTS
> An authoring tool must provide a mode which prompts authors to create
> accessible content in formats authored by those tools, for
> accessibility problems that the tool can correct. Tools may provide
> prompts for other problems as well.
So I'm left wondering what is sufficient here for a tool that allows one
to edit HTML. Many issues can be prompted for (even if not positively
identified as an issue) if the user can edit the source code directly.
For HTML, is it sufficient to prompt in an HTML tool for:
These are the things that Dreamweaver prompts for, and I believe it is
prompting for as much as any tool, if not more. Is this enough? If not,
is there no tool that does sufficient prompting? What is enough? I'm
getting concerned that the language is trending toward subjectivity.
> Note 1: It is neither expected nor possible that prompts be available
> for every type of accessible content.
Yeah, I saw this, but my comment and concern stands.
- Next message in Thread: Judy Brewer: "Re: 7-C Prompts (in authoring tools)"
- Previous message in Thread: Sean Hayes: "Re: 7-C Prompts (in authoring tools)"