Thread Subject: Re: Reorganized Web and Software provisions
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: Andi Snow-Weaver
Date: Tue, Aug 14 2007 5:20 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: Reorganized Web and Software provisions"
- Previous message in thread: Gregg Vanderheiden: "Re: Reorganized Web and Software provisions"
- Messages sorted by: Author | Thread | Date
The ANSI and ISO approach is find if you're talking about native
applications that only run on one platform. But it creates a problem for
multi-platform applications. Either the application has to have a lot of
special case code in it to provide support when platforms don't or the
accessibility compliance of the application will be different for different
< = EMAIL ADDRESS REMOVED = To
u> "'TEITAC Web/Software
Sent by: Subcommittee'"
teitac-websoftwar < = EMAIL ADDRESS REMOVED =
= EMAIL ADDRESS REMOVED = >
08/13/2007 11:11 Re: [teitac-websoftware]
PM Reorganized Web and Software
Please respond to
= EMAIL ADDRESS REMOVED =
I think Peter is right here.
In ANSI and ISO we took this approach and then noted that software can take
advantage of systems functions but must supply them themselves if the
system does not (or the program in such a way that the system functions are
Gregg C Vanderheiden Ph.D.
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Peter
Sent: Monday, August 13, 2007 5:38 PM.
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Reorganized Web and Software provisions
No surprise here - I like this format a lot! Of course, we still have to
contend with the use of words like 'product', 'content', 'page',
'document', 'software', etc. that are embedded within the provisions. For
example, in the provision:
Software must provide a visual indication of which user interface object
currently has the keyboard focus
is the word 'software' especially significant? Is it meant to refer to the
user agent, or is it being used in a generic sense? To the extent that
these words assign responsibility to specific layers of the tech stack, I
am all for them; otherwise, we probably want to avoid them altogether,
leading us to wording like:
There must be a visual indication of which user interface object currently
has the keyboard focus
My preference would be to keep the provision totally generic, and then
have technical guidance docs that delve into responsibility via suggested
Another flavor of this restructuring, which eliminates repetitive 'if'
statements, could be:
1.3 Non-text content
1.8 Consistent use of components
1.9 Size, shape, location
1.10 Audio Turnoff
1.11 Reading order
1.14 Information and relationships
1.15 User Interface Components
1.16 User Preferences
1.17 Color adjustment
1.18 Disruption of access features
1.20 Keyboard Operation
1.21 Focus Cursor.
1.22 At interoperability
1.23 Both platform and app
If Web content, documents, or documents combined with presentation
instructions (such as style sheets): [text taken directly from
Andi's proposal for 1.2 Contrast]:
1.4 Human Language
1.5 Language of Parts
1.12 Bypass blocks
1.13 Link purpose.
Accessibility Program Director
Andi Snow-Weaver wrote:
I've reworked the merged Web and Software proposal  based on our
discussion on August 1st. 
Here is a summary of the changes:
- Removed the distinction between simple and interactive content since we
could not agree on the distinction in all cases. This is now a simple list
that can be applied to Web pages, other types of content, and software.
Where provisions are not generally applicable, language limiting
applicability has been added to the provision. Details below.
- Changed the category title to Electronic Content and User Interface
- Removed the "Animation" and "Bitmap Icons" provisions
- Added proposals for "Color", "Contrast", and "User Preferences"
- Added provisions from WCAG 2.0 that we have agreed to add:
--- Human Language
--- Language of parts
--- Size, shape, location - also added Peter's proposed additional
--- Audio Turnoff
- Added a sentence about tab order in software to the "Reading Sequence"
- Added applicability clause limiting "Bypass Blocks" and "Link Purpose"
Web pages only.
- Added applicability clause limiting "AT Interoperability" to platforms
that have AT interoperability support
- Added an example for form element labels to "Information and
Please review this carefully. At tomorrow's call, we will discuss these
changes. Our final draft is due on Friday.
I will update the harmonization tables later today.
- Next message in Thread: Gregg Vanderheiden: "Re: Reorganized Web and Software provisions"
- Previous message in Thread: Gregg Vanderheiden: "Re: Reorganized Web and Software provisions"