Thread Subject: Gaps in Web Requirements - logical readingorder
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.
Return to this mailing list's archives
From: Andi Snow-Weaver
Date: Sun, Dec 17 2006 6:05 AM
Subject: Gaps in Web Requirements - logical readingorder
In our discussion of the existing Web requirements in Section 508, we
identified several gaps for which we may want to recommend adding some
provisions.
One of the gaps identifed was logical reading order [1].
Note that WCAG 2.0 does have a provision at Level 1 addressing reading
order:
When the sequence in which content is presented affects its meaning, a
correct reading sequence can be programmatically determined.
When we discussed this before, some thought that reading order was
addressed by 22(d) (Documents shall be organized so they are readable
without requiring an associated style sheet. ) But last week we agreed to
recommend removing 22(d) and Jim Thatcher has an action item to develop a
proposal on structure and/or reading order instead.
If Jim's proposal doesn't include reading order, do we need to add one
similar to what is currently in WCAG 2.0?
[1] http://teitac.org/mailarchives/mail_message.php?id=1055&listid=3
Andi
From: Peter Korn
Date: Mon, Dec 18 2006 11:30 AM
Subject: Re: Gaps in Web Requirements - logical reading order
Hi Andi,
With respect to reading order, we addressed this in the UNIX
Accessibility API via our AccessibleRelation interface. In addition to
using relations to indicating labeling (e.g. "this static text field
labels that edit text field"), we also use it for document flow. So in
places where the document flow is not obvious, we uses the "flows"
relation to indicate document flow or "reading order".
Perhaps a mechanism like this would be one sufficient technique for
addressing this WCAG 2.0 provision - at least when the information is to
be exposed to assistive technologies.
> In our discussion of the existing Web requirements in Section 508, we
> identified several gaps for which we may want to recommend adding some
> provisions.
>
> One of the gaps identifed was logical reading order [1].
>
> Note that WCAG 2.0 does have a provision at Level 1 addressing reading
> order:
>
> When the sequence in which content is presented affects its meaning, a
> correct reading sequence can be programmatically determined.
>
> When we discussed this before, some thought that reading order was
> addressed by 22(d) (Documents shall be organized so they are readable
> without requiring an associated style sheet. ) But last week we agreed to
> recommend removing 22(d) and Jim Thatcher has an action item to develop a
> proposal on structure and/or reading order instead.
>
> If Jim's proposal doesn't include reading order, do we need to add one
> similar to what is currently in WCAG 2.0?
>
> [1] http://teitac.org/mailarchives/mail_message.php?id=1055&listid=3
>
> Andi
>
>
WebAIM is an initiative of:
