Thread Subject: Another proposal for re-structuring 'software' and 'web'
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.
From: Peter Wallack
Date: Wed, Jul 11 2007 11:45 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: Another proposal for re-structuring 'software'and 'web'"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Here's a re-work that I did, treating 'Web applications' as a child of
'Software', in an attempt to remove redundancies and eliminate
loopholes. I re-worked Sections 1, 3 and 6, but only those provisions
that appeared to relate to the thing that common wisdom would generally
define as 'software'. Anything in red represents either deletions of
existing text (strikethrough) or re-arrangement of existing text from
other provisions that would now be obsolete. (Many apologies in advance
for using color-coding as the only way to convey info.) New section 3.5
represents the vestigial remains of 6. In a very few cases, I modified
the text for other purposes, like 1.2-H's onerous 14 pt font
requirement. Other edits were kept to a minimum, so in some cases a bit
of wordsmithing is still needed to make things gramatically correct.<br>
<br>
1. Requirements for All Product and Services<br>
<ul>
<li>1.2-B - Flashing: Products must not flash more than 3 times in
any one second period, unless...</li>
<li>1.2-G - Color: Color coding must not be used as the only means of
conveying
information, indicating an action, prompting a response, or
distinguishing a visual element.</li>
<li>1.2-H - Text size: All information provided in text must be a
minimum of 3/16 inch (4.8
mm) high, based on the uppercase letter "I" or, where the display size
is not part of the product <font color="#ff0000">and the user is not
permitted to adjust font sizes</font>, 14 pt type.</li>
<li><font color="#ff0000"><strike>1.2-I - Contrast: Note: Contrast is
currently split out between
software and
hardware. If this approach is successful, then this placeholder
provision will be deleted.</strike></font></li>
</ul>
3. Software & General Behavior Provisions
<blockquote>
<ul>
<li>3.1 All Products</li>
<ul>
<li>3.1-A - Disruption of Access Features: Applications must not,
except by specific user request, disrupt the
features of the platform that have an accessibility usage in the
platform developer documentation. </li>
<li>3.1-B - Timing: For each time limit that is set by the
software,
at least one of the following is true:</li>
<li>3.1-C - Software as platform and application: Software that
is
both a 'platform', and an 'application' running on another platform
must...<span class="toctext"></span></li>
</ul>
<li><span class="toctext">3.2 If the Product has Visual Output or
Display</span></li>
<ul>
<li>3.2-A - Contrast: <font color="#ff0000"><strike>When a
product permits a user to adjust color
and contrast settings, </strike></font>at least one color selection
capable of
producing a minimum luminosity
contrast ratio of 7:1 must be provided.</li>
<li>3.2-B - Animation: <font color="#ff0000"><font
color="#000000">When an informational animation is displayed</font><strike>
that will last for more
than three seconds</strike></font>, software must give the user a means
to pause and
restart the animation. When a decorative animation is displayed <font
color="#ff0000"><strike>that
will last for more than three seconds</strike></font>, software must
give the user a
means to stop the animation. <font color="#ff0000">Moving, blinking,
scrolling, or auto-updating
information can be
paused by the user unless it is part of an activity where timing or
movement is essential. Moving content that is pure decoration can be
stopped by the user.</font></li>
<li>3.2-C - User Preferences: Applications must utilize user
selected
contrast and color
selections and other individual display attributes when the
availability of those selections are developed and documented according
to industry standards.<span class="toctext"></span></li>
</ul>
<li><span class="toctext">3.3 If the Product has Standard Keyboard
or Keyboard Interface</span></li>
<ul>
<li>3.3-A - Keyboard: All functionality of the user interface is
operable through a
keyboard interface without requiring specific timings for individual
keystrokes, except where the underlying function requires input that
depends on the path of the user's movement and not just the endpoints.<span
class="toctext"></span></li>
</ul>
<li><span class="toctext">3.4 If Software runs on platform with
Operating System with AT Support</span></li>
<ul>
<li>3.4-A - AT Interoperability: Software that provides user
interface objects must either use the
accessibility services provided by platform software or other services
to cooperate with assistive technologies when such services allow the
software to meet the accessibility provisions of this standard. Using
such services, software must:</li>
<li><font color="#ff0000">3.4-B - Consistent Identification:
Components that have the same
functionality within a product must be identified consistently.When
bitmap images are used to identify
controls, status indicators,
or other programmatic elements, the meaning assigned to those images
must be consistent throughout an application's performance.</font></li>
<li>3.4-C - Focus Indicator: Software must provide a visual
indication of which user interface
object currently has the keyboard focus. If the object is a text entry
field, a visual indication of the text insertion point must be
provided, and is sufficient. <font color="#ff0000">The focus indicator
must be programmatically determinable so that assistive
technology can track focus and focus changes.</font></li>
<li><font color="#ff0000">3.4-D - Non-text Content: All non-text
content has a text
alternative that
presents equivalent information, except for the situations listed
below...</font></li>
</ul>
<li><font color="#ff0000">3.5 If Web Applications</font></li>
<ul>
<li>3.5-A - Repeated Blocks: A mechanism must be available to
bypass
blocks of content that are repeated on multiple Web pages.</li>
<li>3.5-B - Link Purpose: The purpose of each link can be
determined
from the link text or the
link text together with it's programmatically determined link context.</li>
<li>3.5-C - Information and Relationships: Information and
relationships conveyed through presentation can be
programmatically determined or are available in text, and notification
of changes to these is available to user agents, including assistive
technologies. </li>
</ul>
</ul>
</blockquote>
<pre class="moz-signature" cols="72">--
Peter Wallack
Accessibility Program Director
Oracle Corporation</pre>
</body>
</html>
- Next message in Thread: Gregg Vanderheiden: "Re: Another proposal for re-structuring 'software'and 'web'"
- Previous message in Thread: None
WebAIM is an initiative of:
