Thread Subject: Reorganized Web and Software provisions
Note
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.
Return to this mailing list's archives
From: Andi Snow-Weaver
Date: Mon, Aug 13 2007 9:55 AM
Subject: Reorganized Web and Software provisions
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_provisions_2
[2]
http://teitac.org/wiki/Web_and_Software:_Analysis_of_impact_to_harmonization_with_WCAG_2.0_and_ISO
Andi
From: Peter Wallack
Date: Mon, Aug 13 2007 4:40 PM
Subject: Re: Reorganized Web and Software provisions
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
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:<br>
<i>Software must provide a visual indication of which user interface
object currently has the keyboard focus</i><br>
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:<br>
<i><b>There must be</b> a visual indication of which user interface
object currently has the keyboard focus<br>
</i>My preference would be to keep the provision totally generic, and
then have technical guidance docs that delve into responsibility via
suggested techniques.<i><br>
</i><br>
Another flavor of this restructuring, which eliminates repetitive 'if'
statements, could be:<br>
<ul>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Color"><span
class="tocnumber"></span></a><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Color"><span
class="tocnumber">1.1</span> <span class="toctext">Color</span></a><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Non-text_content"><span
class="tocnumber"></span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Non-text_content"><span
class="tocnumber">1.3</span> <span class="toctext">Non-text content</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Pausing"><span
class="tocnumber">1.6</span> <span class="toctext">Pausing</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Flashing"><span
class="tocnumber">1.7</span> <span class="toctext">Flashing</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Consistent_use_of_components"><span
class="tocnumber">1.8</span> <span class="toctext">Consistent use of
components</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Size.2C_shape.2C_location"><span
class="tocnumber">1.9</span> <span class="toctext">Size, shape,
location</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Audio_Turnoff"><span
class="tocnumber">1.10</span> <span class="toctext">Audio Turnoff</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Reading_order"><span
class="tocnumber">1.11</span> <span class="toctext">Reading order</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Information_and_relationships"><span
class="tocnumber">1.14</span> <span class="toctext">Information and
relationships</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#User_Interface_Components"><span
class="tocnumber">1.15</span> <span class="toctext">User Interface
Components</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#User_Preferences"><span
class="tocnumber">1.16</span> <span class="toctext">User Preferences</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Color_adjustment"><span
class="tocnumber">1.17</span> <span class="toctext">Color adjustment</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Disruption_of_access_features"><span
class="tocnumber">1.18</span> <span class="toctext">Disruption of
access features</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Timing"><span
class="tocnumber">1.19</span> <span class="toctext">Timing</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Keyboard_Operation"><span
class="tocnumber">1.20</span> <span class="toctext">Keyboard Operation</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Focus_Cursor"><span
class="tocnumber">1.21</span> <span class="toctext">Focus Cursor</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#At_interoperability"><span
class="tocnumber">1.22</span> <span class="toctext">At
interoperability</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Both_platform_and_app"><span
class="tocnumber">1.23</span> <span class="toctext">Both platform and
app</span></a></li>
<li class="toclevel-2"><span class="toctext">If </span>Web content,
documents, or documents combined with presentation instructions (such
as style sheets): [text taken directly from Andi's proposal for<a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Contrast"><span
class="tocnumber"> 1.2</span> <span class="toctext">Contrast]:</span></a></li>
<ul>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Contrast"><span
class="tocnumber">1.2</span> <span class="toctext">Contrast</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Human_Language"><span
class="tocnumber">1.4</span> <span class="toctext">Human Language</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Language_of_Parts"><span
class="tocnumber">1.5</span> <span class="toctext">Language of Parts</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Bypass_blocks"><span
class="tocnumber">1.12</span> <span class="toctext">Bypass blocks</span></a></li>
<li class="toclevel-2"><a
href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2#Link_purpose"><span
class="tocnumber">1.13</span> <span class="toctext">Link purpose</span></a></li>
</ul>
</ul>
<br>
<pre class="moz-signature" cols="72">Peter Wallack
Accessibility Program Director
Oracle Corporation</pre>
<br>
<br>
Andi Snow-Weaver wrote:
<blockquote
cite="mid: = EMAIL ADDRESS REMOVED = "
type="cite">
<pre wrap="">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]
<a class="moz-txt-link-freetext" href="http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2">http://teitac.org/wiki/Web_and_Software:_Reorganized_Web_and_Software_provisions_2</a>
[2]
<a class="moz-txt-link-freetext" href="http://teitac.org/wiki/Web_and_Software:_Analysis_of_impact_to_harmonization_with_WCAG_2.0_and_ISO">http://teitac.org/wiki/Web_and_Software:_Analysis_of_impact_to_harmonization_with_WCAG_2.0_and_ISO</a>
Andi
From: Gregg Vanderheiden
Date: Mon, Aug 13 2007 10:15 PM
Subject: Re: Reorganized Web and Software provisions
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
From: Andi Snow-Weaver
Date: Tue, Aug 14 2007 5:20 AM
Subject: Re: Reorganized Web and Software provisions
Gregg,
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
platforms.
Andi
Gregg
Vanderheiden
< = EMAIL ADDRESS REMOVED = To
u> "'TEITAC Web/Software
Sent by: Subcommittee'"
teitac-websoftwar < = EMAIL ADDRESS REMOVED =
= EMAIL ADDRESS REMOVED = >
itac.org cc
Subject
08/13/2007 11:11 Re: [teitac-websoftware]
PM Reorganized Web and Software
provisions
Please respond to
TEITAC
Web/Software
Subcommittee
<teitac-websoftwa
= EMAIL ADDRESS REMOVED =
g>
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:
1.1 Color
1.3 Non-text content
1.6 Pausing
1.7 Flashing
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.19 Timing
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.2 Contrast
1.4 Human Language
1.5 Language of Parts
1.12 Bypass blocks
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_provisions_2
[2]
http://teitac.org/wiki/Web_and_Software:_Analysis_of_impact_to_harmonization_with_WCAG_2.0_and_ISO
Andi:
From: Gregg Vanderheiden
Date: Tue, Aug 14 2007 7:30 AM
Subject: Re: Reorganized Web and Software provisions
True
Which is why we say the application is responsible but they can take
advantage of any system level services in fulfilling it.
So the application benefits from services provided by the OS - if they are
provided.
Then we recommend that the OS provide them to make it easier for
applications on their platforms.
Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Andi Snow-Weaver
> Sent: Tuesday, August 14, 2007 6:18 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Reorganized Web and
> Software provisions
>
> Gregg,
>
> 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
> platforms.
>
> Andi
>
>
>
>
>
> Gregg
>
> Vanderheiden
>
> < = EMAIL ADDRESS REMOVED =
> To
> u> "'TEITAC Web/Software
>
> Sent by: Subcommittee'"
>
> teitac-websoftwar
> < = EMAIL ADDRESS REMOVED =
> = EMAIL ADDRESS REMOVED = >
>
> itac.org
> cc
>
>
>
> Subject
> 08/13/2007 11:11 Re:
> [teitac-websoftware]
> PM Reorganized Web and
> Software
> provisions
>
>
>
> Please respond to
>
> TEITAC
>
> Web/Software
>
> Subcommittee
>
> <teitac-websoftwa
>
> = EMAIL ADDRESS REMOVED =
>
> g>
>
>
>
>
>
>
>
>
>
> 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:
> 1.1 Color
> 1.3 Non-text content
> 1.6 Pausing
> 1.7 Flashing
> 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.19 Timing
> 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.2 Contrast
> 1.4 Human Language
> 1.5 Language of Parts
> 1.12 Bypass blocks
> 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_S
> oftware_provisions_2
> [2]
>
> http://teitac.org/wiki/Web_and_Software:_Analysis_of_impact_to
> _harmonization_with_WCAG_2.0_and_ISO
>
> Andi:
>
>
From: Barrett, Don
Date: Tue, Aug 14 2007 9:00 AM
Subject: Re: Reorganized Web and Software provisions
Excellent Andi!! They really read very very well; I like this new
arrangement very much.
One suggestion for folks to quickly think about:
For "User Interface Components,"
The only example we provide involves frame naming. I would like to see
the frame naming example moved to the examples under "Information and
Relationships," and if possible, come up with more poignant examples for
"User Interface Components," given the richness of scripting and form
elements which it references. Frames there just don't do it for me; can
anyone think of richer examples for that standard?
Don
and
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Snow-Weaver
Sent: Monday, August 13, 2007 11:51 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [teitac-websoftware] Reorganized Web and Software provisions
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_pr
ovisions_2
[2]
http://teitac.org/wiki/Web_and_Software:_Analysis_of_impact_to_harmoniza
tion_with_WCAG_2.0_and_ISO
Andi
From: Gregg Vanderheiden
Date: Tue, Aug 14 2007 9:40 AM
Subject: Re: Reorganized Web and Software provisions
Interesting.
It would solve some problems but looks like it introduces others... Hmmmmm.
Will have to study this more.
I have some comments on individual provisions - but I will post them
separately so facilitate discussion.
Interesting....
Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Andi Snow-Weaver
> Sent: Monday, August 13, 2007 10:51 AM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [teitac-websoftware] Reorganized Web and Software provisions
>
>
> 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_S
> oftware_provisions_2
> [2]
> http://teitac.org/wiki/Web_and_Software:_Analysis_of_impact_to
> _harmonization_with_WCAG_2.0_and_ISO
>
> Andi
>
>
From: Andi Snow-Weaver
Date: Tue, Aug 14 2007 12:20 PM
Subject: Re: Reorganized Web and Software provisions
Don,
I have no problem with adding more examples to User Interface Components.
The reason we included frame names there is because that's where the
technique is defined in WCAG 2.0.
Andi
"Barrett, Don"
<Don.Barrett@ed.g
ov> To
Sent by: "TEITAC Web/Software Subcommittee"
teitac-websoftwar < = EMAIL ADDRESS REMOVED =
= EMAIL ADDRESS REMOVED = >
itac.org cc
Subject
08/14/2007 09:56 Re: [teitac-websoftware]
AM Reorganized Web and Software
provisions
Please respond to
TEITAC
Web/Software
Subcommittee
<teitac-websoftwa
= EMAIL ADDRESS REMOVED =
g>
Excellent Andi!! They really read very very well; I like this new
arrangement very much.
One suggestion for folks to quickly think about:
For "User Interface Components,"
The only example we provide involves frame naming. I would like to see
the frame naming example moved to the examples under "Information and
Relationships," and if possible, come up with more poignant examples for
"User Interface Components," given the richness of scripting and form
elements which it references. Frames there just don't do it for me; can
anyone think of richer examples for that standard?
Don
and
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Snow-Weaver
Sent: Monday, August 13, 2007 11:51 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [teitac-websoftware] Reorganized Web and Software provisions
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_pr
ovisions_2
[2]
http://teitac.org/wiki/Web_and_Software:_Analysis_of_impact_to_harmoniza
tion_with_WCAG_2.0_and_ISO
Andi
WebAIM is an initiative of:
