Thread Subject: proposed EWG wording changes

Return to this mailing list's archives

From: Michele Budris
Date: Tue, Aug 14 2007 5:55 PM
Subject: proposed EWG wording changes

Here are changes I'm proposing. The purpose of the changes is
strictly for making them easier to read. If I have changed any of the
meanings, please raise it as an issue. That is not the intent of any
of the changes.

Text to be removed is striked out, added words are in red italics. A
reminder that the word "can" means the provision is optional. There
were many provisions (such as Information and Relationships) where
I've changed it from a "can" to a "must" since I'm assuming you feel
this must be done, but there are a couple of ways to accomplish it.
If I have made a change to make a provision a requirement instead of
something that is optional to do by making this change, please let me
know.

Reminder, old section 508 wording was to use "shall," we now use "must."
If something is optional to do, the correct word is "may" or "should"

Thanks,
Michele


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:
provide assistive technology with object information including but
not limited to:
role, state(s), boundary, name, and description
the row and column an object is in, and the headers for the row and
column for that object if it is in a table
any table row & column, and row & column headers (if the object is in
a table)
current value and any minimum or maximum values, if the object
represents one of a range of values
relationship this object has as a label for another object, or being
labeled by another object
parent or containing element, and any children objects
text contents, text attributes, and the boundary of text rendered to
the screen
provide assistive technology with a list of actions that can be
executed on an object and allow assistive technology to
programmatically execute any of those actions;
allow assistive technology to track and modify focus, text insertion
point, and selection attributes of user interface objects;
provide assistive technology with notification of events relevant to
user interactions, including but not limited to changes in the
object's state(s), value, name, description, or boundary
Note: This provision applies to forms in the software.

Flashing (Web)
Content and applications must do not contain anything that flashes
more than 3 times in any one second period or the flashing is below
the general flash and red flash thresholds.

Non-text Content
All non-text content has must have a text alternative that presents
equivalent information, except for the situations listed below.
Controls-Input: If non-text content is a control or accepts user
input, then it has must have a name that describes its purpose. (See
also User Interface Components provisions)
Media: If non-text content is multimedia, live audio-only or live
video-only content, then text alternatives at least identify the non-
text content with a descriptive text label. (For multimedia, see also
Audio and/or Video provisions)
Test: If non-text content is a test or exercise that must be
presented in non-text format, then text alternatives at least
identify the non-text content with a descriptive text label. (For
multimedia, see also Audio and/or Video provisions)
Sensory: If non-text content is primarily intended to create a
specific sensory experience, then text alternatives at least identify
the non-text content with a descriptive text label. (For multimedia,
see also Audio and/or Video provisions)
Completely Automated Public Turing Test to Tell Computers and Humans
Apart (CAPTCHA): If the purpose of non-text content is to confirm
that content is being accessed by a person rather than a computer
then text alternatives that identify and describe the purpose of the
non-text content are must be provided and alternative forms in
different modalities are must be provided to accommodate different
disabilities.
Decoration, Formatting, Invisible Content: If non-text content is
pure decoration, or used only for visual formatting, or if it is not
presented to users, then it is implemented such that it can be
ignored by assistive technology.

Keyboard Operation
All functionality of the product operable through the user interface
is must be operable through a keyboard interface without requiring
specific timings for individual keystrokes. The only exception is
where the underlying function requires input that depends on the path
of the user's movement and not just the endpoints.
Note: This exception relates to the underlying function, not the
input technique. For example, if using handwriting to enter text, the
input technique (handwriting) requires path dependent input but the
underlying function (text input) does not.
Note: This does not forbid and should not discourage providing mouse
input or other input methods, such as gestures, in addition to
keyboard operation.

Link Purpose
Current text: On Web pages, the purpose of each link can be
determined from the link text or the link text together with it's
programmatically determined link context.
EWG: On Web pages, you must be able to determine the purpose of each
link from the link text or the link text together with it's
programmatically determined link context.

Information and Relationships
Information and relationships conveyed through presentation can must
be either programmatically determined or are available in text, and
notification of changes to these is available to user agents,
including assistive technologies. For example:
row and column headers are identified for data tables
markup is used to associate data cells and header cells for data
tables that have two or more logical levels of row or column headers.
markup is used to identify section headings
markup is used to identify form element labels

User Interface Components
Current text: For all user interface components, including form
elements and those generated by scripts, the name and role must be
programmatically determined, states, properties, and values that can
be set by the user must be programmatically determined and can be
programmatically set, and notification of changes to these items is
available to user agents, including assistive technologies. For example:
Frames must be titled with text that facilitates frame identification
and navigation.
EWG: For all user interface components, including form elements and
those generated by scripts, the name and role must be
programmatically determined. For states, properties, and values that
can be set by the user must be programmatically determined and can be
programmatically set. Notification of changes to these items is must
be available to user agents, including assistive technologies. For
example:
Frames must be titled with text that facilitates frame identification
and navigation.

Pausing
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.
EWG: Moving, blinking, scrolling, or auto-updating information must
allow can be paused pausing by the user unless it is part of an
activity where timing or movement is essential. Moving content that
is pure decoration must allow can be stopped by the user to stop it.

Reading Sequence
When the sequence in which information is presented affects its
meaning, a correct reading sequence must can be programmatically
determined and sequential navigation of interactive components must
be is consistent with that sequence.

From: Jared Smith
Date: Wed, Aug 15 2007 10:25 AM
Subject: Re: proposed EWG wording changes

Just a few comments/thoughts:

- In most places, we list the exception first and then the
requirement. For instance, "if it is in a table, the row and column
the object is in, and the headers for the row and column for that
object" would better match the rest of the provisions (plus, I think
it reads a bit easier).

- I think the changes on the User Interface Components provision might
make it unclear that the 2nd and 3rd sentences apply only to user
interface components. Recommended change for 2nd sentence: "States,
properties, and values *of these components* that can be set by the
user..."

- The new Pausing provision loses a little meaning. The edit now
suggests that the moving content itself must allow the stopping. Also,
it has been mentioned a few times that the Pausing provision should
allow hiding of decorative content, but this has not yet been
included, or it has been omitted by a decision I'm not aware of.

Suggested wording:
"A mechanism must be provided to pause moving, blinking, scrolling, or
auto-updating information unless it is part of an activity where
timing or movement is essential. A mechanism must be provided to stop
*or hide* moving content that is pure decoration."

- Under Reading Sequence, change to "... a correct reading sequence
must be programmatically *determinable*..." Programmatic determination
happens when the user accesses it. Authors must only ensure that the
information is programmatically determinable.

Jared Smith