Thread Subject: Re: Proposal on authoring tools

From: Gregg Vanderheiden
Date: Thu, Jun 07 2007 8:40 AM

• Return to this mailing list's archives
• View all messages in this thread
• Next message in thread: Sailesh Panchang: "Re: Proposal on authoring tools"
• Previous message in thread: Brad Hodges: "Re: Proposal on authoring tools"
• Messages sorted by: Author | Thread | Date

Agree that we shouldn't repeat the general software access provisions here.

We should probably include a note (and this might be a more general issue
for EWG) that makes it clear that these are ADDITIONAL provision. Maybe
just using the title "additional provisions for authoring software".
Using "software" instead of "tools" may also help reinforce the fact that
the software rules would apply.

Also, if there are some important provisions missing for access to authoring
software then we probably should consider those for the software access
section in general.


Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.



> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Judy Brewer
> Sent: Thursday, June 07, 2007 8:46 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Proposal on authoring tools
>
> Hi David,
>
> We had some small group discussion of this, and people
> remarked that authoring tool user interface accessibility
> seemed to be generally covered by TEITAC software provisions
> on user interface accessibility. We therefore focused our
> energy on bringing forward a proposal on support for
> production of accessible content.
>
> However, it was also noted that it was possible that a few
> ATAG 2.0 provisions regarding accessibility of the user
> interface specific to authoring tools might not be
> sufficiently covered by the TEITAC user interface provisions.
> In my opinion it might still be useful to look through those
> provisions (A.1.1 through A.4.4) in the latest ATAG 2.0
> Working Draft
> http://www.w3.org/WAI/AU/2007/WD-ATAG20-20070530/WD-ATAG20-200
> 70530#part-tool-accessible
> and make sure that the essentials needed for people with
> disabilities to be able to author content are covered. For
> instance, you might want to look at A.3.8, [For the authoring
> tool user interface] "Ensure [that] previews are as
> accessible as existing user agents" which is one of the few
> that doesn't seem to be already covered under the general
> software provisions. But if relevant, it might be more
> appropriate to propose that under the software provisions
> than under this section on authoring tools.
>
> - Judy
>
> At 08:14 AM 6/7/2007 -0400, David Poehlman wrote:
> >Hi Judy and all,
> >
> >Should the iaccessability of the interface be addressed here or give
> >reference to other standards?
> >----- Original Message -----
> >From: "Judy Brewer" < = EMAIL ADDRESS REMOVED = >
> >To: < = EMAIL ADDRESS REMOVED = >
> >Sent: Thursday, June 07, 2007 1:32 AM
> >Subject: [teitac-websoftware] Proposal on authoring tools
> >
> >
> >The following proposal on authoring tools represents current work in
> >progress by a small group following the recent TEITAC
> face-to-face meeting.
> >Please add your comments as we continue to work on this, now on the
> >Web/Software list. For those who already contributed in the small
> >group, thank you for your input on the draft; the latest
> version here
> >attempts to capture your most recent feedback in our discussion, but
> >please continue to help refine this on the Web software list now.
> >
> >1. Authoring tools must have the ability to produce content which
> >passes the electronic content provisions.
> >
> >2. Authoring tools must, except by explicit user action, preserve
> >accessibility information necessary for meeting the
> electronic content
> >provisions.
> >
> >3. Authoring tools must allow the author to augment
> >automatically-generated content with accessibility information.
> >
> >4. For authoring tools with a user interface, authoring tools must
> >provide a mode which prompts authors to create accessible content.
> >
> >5. For authoring tools with a user interface, authoring tools must
> >provide a mode which assists authors in checking for
> accessibility problems.
> >
> >6. Authoring tools, when providing templates or other pre-authored
> >content, should provide templates that facilitate production of
> >accessible content, and pre-authored content that is accessible.
> >
> >7. Authoring tools should give prominence to the most accessible
> >authoring action for achieving an authoring outcome.
> >
> >Regards,
> >
> >- Judy
> >
> >
> >--
> >Judy Brewer +1.617.258.9741 http://www.w3.org/WAI
> >Director, Web Accessibility Initiative (WAI), World Wide Web
> Consortium
> >(W3C)
> >MIT/CSAIL Building 32-G526
> >32 Vassar Street
> >Cambridge, MA, 02139, USA
> >
> >

• Next message in Thread: Sailesh Panchang: "Re: Proposal on authoring tools"
• Previous message in Thread: Brad Hodges: "Re: Proposal on authoring tools"