Thread Subject: Re: Reorganized Web and Software provisions

From: Gregg Vanderheiden
Date: Mon, Aug 13 2007 10:15 PM

• Return to this mailing list's archives
• View all messages in this thread
• Next message in thread: Andi Snow-Weaver: "Re: Reorganized Web and Software provisions"
• Previous message in thread: Peter Wallack: "Re: Reorganized Web and Software provisions"
• Messages sorted by: Author | Thread | Date

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 not
used).




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






_____


From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Peter
Wallack
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
techniques.

Another flavor of this restructuring, which eliminates repetitive 'if'
statements, could be:

*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Color>
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Color> 1.1 Color
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Non-text_content>
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Non-text_content> 1.3 Non-text content
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Pausing> 1.6 Pausing
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Flashing> 1.7 Flashing
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Consistent_use_of_components> 1.8 Consistent use of components
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Size.2C_shape.2C_location> 1.9 Size, shape, location
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Audio_Turnoff> 1.10 Audio Turnoff
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Reading_order> 1.11 Reading order
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Information_and_relationships> 1.14 Information and relationships
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#User_Interface_Components> 1.15 User Interface Components
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#User_Preferences> 1.16 User Preferences
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Color_adjustment> 1.17 Color adjustment
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Disruption_of_access_features> 1.18 Disruption of access features
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Timing> 1.19 Timing
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Keyboard_Operation> 1.20 Keyboard Operation
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Focus_Cursor> 1.21 Focus Cursor
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#At_interoperability> 1.22 At interoperability
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Both_platform_and_app> 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
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Contrast> 1.2 Contrast]:

*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Contrast> 1.2 Contrast
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Human_Language> 1.4 Human Language
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Language_of_Parts> 1.5 Language of Parts
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Bypass_blocks> 1.12 Bypass blocks
*
<http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provi
sions_2#Link_purpose> 1.13 Link purpose





Peter Wallack
Accessibility Program Director
Oracle Corporation



Andi Snow-Weaver wrote:

I've reworked the merged Web and Software proposal [1] based on our
discussion on August 1st. [2]

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
Provisions
- 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
explanatory sentence.
--- Audio Turnoff
- Added a sentence about tab order in software to the "Reading Sequence"
provision
- Added applicability clause limiting "Bypass Blocks" and "Link Purpose" to
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
Relationships"

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.

[1]
http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provis
ions_2
[2]
http://teitac.org/wiki/Web_and_Software:_Analysis_of_impact_to_harmonization
_with_WCAG_2.0_and_ISO

Andi

• Next message in Thread: Andi Snow-Weaver: "Re: Reorganized Web and Software provisions"
• Previous message in Thread: Peter Wallack: "Re: Reorganized Web and Software provisions"