Thread Subject: Re: Group D: 22(d) Readable without stylesheets
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: Jim Allan
Date: Wed, Dec 20 2006 10:25 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Brett, Thomas F: "Re: Group D: 22(d) Readable without stylesheets"
- Previous message in thread: Jim Allan: "Re: Group D: 22(d) Readable without stylesheets"
- Messages sorted by: Author | Thread | Date
Is source code order considered "programatically determined?"
Programatically determined implies the use of some algorithm to determine
the "meaningful order". It is my experience, at least as far as screen
readers and keyboard access to web pages, that CSS positioning is ignored
and reading order begins at the top of the source code and proceeds.
Navigation also proceeds from the top of the source for screen readers and
keyboard navigators except when the order has been be modified with the
Source-code-order (SCO) is the base state of the content. I don't think any
algorithm is needed to follow the SCO.
I think SCO should be included in "programatically determined."
> Jim Thatcher wrote on Tuesday, December 19, 2006 9:57 AM
> Current wording. 1194.22(d) Documents shall be organized so they are
> readable without requiring an associated style sheet.
> The discussion on the list on this item 1194.22(d) (Readable without style
> sheets) has been succinctly summarized by Andi on the wiki,
> http://teitac.org/wiki/Web_and_Software:_Correct_coding#22.28d.29. On the
> last call (12/13) I took the action item to submit a proposal relative to
> this provision.
> Proposal: Delete provision 1194.22(d) (Readable without style sheets).
> The problem is that it is possible with CSS positioning to wreak havoc on
> the source code order of the content and the order can be meaningful. Thus
> following WCAG 2.0 we need a provision that guarantees that AT can come up
> with a meaningful reading order. The following proposal takes the wording
> from the current WCAG 2.0 Editors Draft
> Proposal: (Meaningful sequence) When the sequence in which content is
> presented affects its meaning, a correct reading sequence can be
> programmatically determined.
> This proposal is also added to the Wiki - the agenda for the 12/20 meeting
> Jim Thatcher
> Accessibility Consulting
- Next message in Thread: Brett, Thomas F: "Re: Group D: 22(d) Readable without stylesheets"
- Previous message in Thread: Jim Allan: "Re: Group D: 22(d) Readable without stylesheets"