Thread Subject: Re: proposed EWG wording changes

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: Jared Smith
Date: Wed, Aug 15 2007 10:25 AM

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

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University