Thread Subject: Re: 3-k scope question
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: Thu, Sep 06 2007 8:10 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Jared Smith: "Re: 3-k scope question"
- Previous message in thread: Hoffman, Allen: "Re: 3-k scope question"
- Messages sorted by: Author | Thread | Date
There are two things addressed by 3-K - reading order and navigation
sequence. Reading order covers everything. Navigation sequence
addresses navigable elements within that reading order. I think some
minor word-smithing can clarify this:
When the sequence in which information is presented affects its
meaning, a correct reading sequence can be programmatically
determined. The sequential navigation must be consistent with the
reading sequence.
- This removes "interactive components" altogether.
- Two sentences for readability and clarifies that navigation must be
consistent with the reading sequence.
- Changes "is" to "must be".
- This provision should be titled "Reading and Navigation Sequence"
Jared Smith
On 9/6/07, Hoffman, Allen < = EMAIL ADDRESS REMOVED = > wrote:
>
>
> Question:
> In 3-K "reading sequence", we only address "interactive elements". I don't
> think this would cover columnar information, tables, or other
> non-interactive but sequentially critical information. I think we might
> just use the "chunks" or "components" concept here to better use, since this
> is not only for web where one can rely on tab order, for a specific set of
> things only.
>
> Can we revisit this soon?
>
> Allen Hoffman -- DHS
- Next message in Thread: Jared Smith: "Re: 3-k scope question"
- Previous message in Thread: Hoffman, Allen: "Re: 3-k scope question"
WebAIM is an initiative of:
