Thread Subject: Current WCAG wording that relates to some TEITAC provisions
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: Gregg Vanderheiden
Date: Thu, Nov 08 2007 9:45 AM
Subject: Current WCAG wording that relates to some TEITAC provisions
Below are some current WCAG wording that relate to some TEITAC provisions.
It might be useful to put these in the SandBox for reference
TEITAC PROVISION
3-M - Reading Sequence
When the sequence in which information is presented affects its meaning, a
correct reading sequence must be programmatically determinable. The
navigation sequence must be consistent with the reading sequence.
* Note: In order to achieve this provision, objects in data operated
on by the software which can be presented in 2 dimensions, would need to be
associated with sufficient information to identify a logical one dimensional
presentation of the same objects, that the software can obtain as readily as
it can obtain the 2 dimensional objects themselves.
* Note: For products with closed functionality the visual and (linear)
audible presentation should match navigation
WCAG language:
1.3.2 Meaningful Sequence: When the sequence in which content is presented
affects its meaning, a correct reading sequence can be programmatically
<http://www.w3.org/WAI/GL/WCAG20/#programmaticallydetermineddef>
determined. (Level A) How to Meet 1.3.2
<http://www.w3.org/WAI/WCAG20/quickref/20071102/Overview.php#content-structu
re-separation-sequence> Understanding
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20071102/content-st
ructure-separation-sequence.html> 1.3.2
2.4.3 Focus Order (Relationships): If a Web page
<http://www.w3.org/WAI/GL/WCAG20/#webpagedef> can be navigated sequentially
<http://www.w3.org/WAI/GL/WCAG20/#nav-seqdef> , focusable components receive
focus in an order that follows information and relationships conveyed
through presentation <http://www.w3.org/WAI/GL/WCAG20/#presentationdef> .
(Level A) How to Meet 2.4.3
<http://www.w3.org/WAI/WCAG20/quickref/20071102/Overview.php#navigation-mech
anisms-focus-order> Understanding
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20071102/navigation
-mechanisms-focus-order.html> 2.4.3
2.4.11 Focus Order (Visual): If a Web page can be navigated sequentially and
the focus order affects operability, focusable components receive focus in
an order that is consistent with the visual layout order of the web page.
(Level AAA) How to Meet 2.4.11
<http://www.w3.org/WAI/WCAG20/quickref/20071102/Overview.php#navigation-mech
anisms-focus-order-visual> Understanding
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20071102/navigation
-mechanisms-focus-order-visual.html> 2.4.11
TEITAC PROVISION
RE 3-N - Link Purpose
On Web pages, it must be possible to determine the purpose of each link from
the link text or the link text together with its programmatically determined
link context.
* Note: In order to achieve this provision, links encoded in data
operated on by the software would need to be associated with link text that
the software can obtain as readily as it can obtain the link itself.
WCAG language:
2.4.4 Link Purpose (In Context): The purpose of each link
<http://www.w3.org/WAI/GL/WCAG20/#linkpurposedef> can be determined from
the [link text] alone, or from the link text together with its
programmatically <http://www.w3.org/WAI/GL/WCAG20/#pdlinkcontextdef>
determined link context, except where the purpose of the link would be
ambiguous to users in general
<http://www.w3.org/WAI/GL/WCAG20/#ambiguouslinkdef> . (Level A) How to Meet
2.4.4
<http://www.w3.org/WAI/WCAG20/quickref/20071102/Overview.php#navigation-mech
anisms-refs> Understanding
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20071102/navigation
-mechanisms-refs.html> 2.4.4
2.4.9 Link Purpose (Link Only): A mechanism is available to allow the
purpose of each link to be identified from link text alone. (Level AAA) How
to Meet 2.4.9
<http://www.w3.org/WAI/WCAG20/quickref/20071102/Overview.php#navigation-mech
anisms-link> Understanding
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20071102/navigation
-mechanisms-link.html> 2.4.9
TEITAC PROVISION
3-O - Information and Relationships
Information and relationships conveyed through presentation can be
programatically determined or are available in text, and notification of
changes to these is available to user agents, including assistive
technologies. For example:
1. row and column headers are identified for data tables
* Note: In order to achieve this provision, table objects in data
operated on by the software would need to be associated with sufficient
information to identify any row and column headers for the table, that the
software can obtain as readily as it can obtain the table itself.
2. 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.
* Note: In order to achieve this provision, cells in table objects
with multiple logical levels of headers in data operated on by the software
would need to be associated with sufficient information to identify any row
and column headers for the table cell, that the software can obtain as
readily as it can obtain the table cell itself
3. markup is used to identify section headings
4. markup is used to identify form element labels
editorial suggestion for first paragraph: Information and relationships
conveyed through presentation must be either programatically determinable or
are available in text, and notification of changes to these is available to
user agents, including assistive technologies. For example:
WCAG language:
1.3.1 Info and Relationships: Information, structure, and relationships
<http://www.w3.org/WAI/GL/WCAG20/#relationshipsdef> conveyed through
presentation <http://www.w3.org/WAI/GL/WCAG20/#presentationdef> can be
programmatically
<http://www.w3.org/WAI/GL/WCAG20/#programmaticallydetermineddef> determined
or are available in text. (Level A) How to Meet 1.3.1
<http://www.w3.org/WAI/WCAG20/quickref/20071102/Overview.php#content-structu
re-separation-programmatic> Understanding
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20071102/content-st
ructure-separation-programmatic.html> 1.3.1
Gregg
------------------------
Gregg C Vanderheiden Ph.D.
Professor - Depts of Ind. Engr. & BioMed Engr.
Director - Trace R & D Center
University of Wisconsin-Madison
< <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848
DSS Player at http://tinyurl.com/dho6b
If Attachement is a mail.dat try <http://www.kopf.com.br/winmail/>
http://www.kopf.com.br/winmail/
<http://trace.wisc.edu:8080/mailman/listinfo/>
From: Hoffman, Allen
Date: Thu, Nov 08 2007 10:25 AM
Subject: Re: Current WCAG wording that relates to some TEITACprovisions
All:
Some of the language changes from WCAG to proposed section 3 provisions
are to broaden the scope for more than a web interface only. Please
keep that in mind when comparing these items, but if scope is now too
broad or not defined specifically, then we should certainly consider any
changes needed.
Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
WebAIM is an initiative of:
