Thread Subject: possible need for another provision
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: Jim Tobias
Date: Mon, Mar 26 2007 11:05 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Whitney Quesenbery: "Re: possible need for another provision"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
In today's General Interface Subcommittee call, we had an extended
discussion about how
to make sure that accessibility features and compatibilities are easy enough
to discover and
activate. That is, how do we guarantee that an end user or sysadmin can
needed feature and install/configure/activate it.
Some of these may have to do with workarounds, AT compatibility, etc., in
detail. For example, a particular piece of software may work with a given
except for a few conditions. The VPAT may not be the best tool for
about that in detail. Getting this information out to the user or sysadmin
crucial in making the product actually accessible (instead of theoretically
We heard clear concerns as well, however, that in some cases some of this
may be proprietary, such as when it involves the specific technology
used by the vendor.
The question arose: is this issue the domain of the Documentation
Subcommittee? I think it
Here is the current draft of 1194.41(b):
End-users shall have access to a description of the accessibility and
features of products in alternate formats or alternate methods upon request,
I would modify it thus:
End-users and technology managers shall have access to a description of the
and compatibility features of products, including how to install, configure,
them. These descriptions shall be available in alternate formats or
upon request, at no additional charge.
- Next message in Thread: Whitney Quesenbery: "Re: possible need for another provision"
- Previous message in Thread: None