Thread Subject: Re: 1194.21 provisions still to be addressedin1194.22
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: Tom Brett
Date: Wed, May 02 2007 11:00 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Sean Hayes: "Re: 1194.21 provisions still to beaddressed in1194.22"
- Previous message in thread: Andi Snow-Weaver: "1194.21 provisions still to be addressed in1194.22"
- Messages sorted by: Author | Thread | Date
Instead of using
http://www.fedrcc.us//Enter.aspx?EventID=663738&CustomerID=321 for the link
to closed captioning please use this link:
The event id on the Wiki is incorrect.
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Sent: Wednesday, May 02, 2007 12:27 PM
To: = EMAIL ADDRESS REMOVED =
Subject: [teitac-websoftware] 1194.21 provisions still to be addressed
In our last meeting on April 18th, we finished up discussing the proposed
new Web part (1194.22) that is harmonized with WCAG 2.0 and would eliminate
the need to refer back to the software part (1194.21) for applets and
The following two provisions from 1194.21 are not included in the proposal
as they are not currently in WCAG 2.0.
- Applications shall not disrupt or disable activated features of other
products that are identified as accessibility features, where those
features are developed and documented according to industry standards.
Applications also shall not disrupt or disable activated features of any
operating system that are identified as accessibility features where the
application programming interface for those accessibility features has been
documented by the manufacturer of the operating system and is available to
the product developer.
- Applications shall not override user selected contrast and color
selections and other individual display attributes.
For HTML content, I think these are browser issues. Do we need to add these
as new provisions in the Web section (1194.22)? I am concerned that if we
add these, all multimedia content will fail.
- Next message in Thread: Sean Hayes: "Re: 1194.21 provisions still to beaddressed in1194.22"
- Previous message in Thread: Andi Snow-Weaver: "1194.21 provisions still to be addressed in1194.22"