Thread Subject: Re: intro to 8.1 final?

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: Andi Snow-Weaver
Date: Fri, Oct 19 2007 2:15 PM

Allen,

We agreed at Wednesday's meeting to accept Sean's proposal to remove 8.1
and add notes to the relevant provisions in section 3.

Andi




"Hoffman, Allen"
<Allen.Hoffman@dh
s.gov> To
Sent by: "TEITAC Web/Software Subcommittee"
teitac-websoftwar < = EMAIL ADDRESS REMOVED =
= EMAIL ADDRESS REMOVED = >
itac.org cc

Subject
10/19/2007 02:53 [teitac-websoftware] intro to 8.1
PM final?


Please respond to
TEITAC
Web/Software
Subcommittee
<teitac-websoftwa
= EMAIL ADDRESS REMOVED =
g>







Just a question:
Are we planning to include the references in notes for several of these
items to account for the 8.1 section as discussed recently? if so, is this
to appear in the next release?

If this is already done, never mind me, if not I can finish this up today
and submit.

3-F - Non-text Objects

Non-text Objects: All non-text objects that are presented to the user must
have a text alternative that presents equivalent information, except for
the
situations listed below.

list of 8 items
* Controls-Input: If non-text objects is a control or accepts user input,
then it must have a name that describes its purpose. (See also User
Interface
Components provisions)
* Media: If non-text objects is synchronized multimedia, live audio-only or
live video-only content, then text alternatives at least identify non-text
objects:
All non-text objects must have a text alternative that presents equivalent
information, except for the situations listed below.
* Media: If a non-text object is synchronized multimedia, live audio-only
or live video-only content, then text alternatives at least identify the
non-text
object with a descriptive text label. (For synchronized multimedia, see
also Audio and/or Video provisions)
* Controls-Input: If a non-text object is a control or accepts user input,
then it must have a name that describes its purpose. (See also User
Interface
Components provisions)
* Test:' If a non-text object is a test or exercise that must be presented
in non-text format, then text alternatives at least identify the non-text
object
with a descriptive text label. (For multimedia, see also Audio and/or Video
provisions)
* Sensory: If a non-text object is primarily intended to create a specific
sensory experience, then text alternatives at least identify the non-text
object
with a descriptive text label. (For multimedia, see also Audio and/or Video
provisions)
* CAPTCHA: If the purpose of a non-text object is to confirm that content
is being accessed by a person rather than a computer then text alternatives
that
identify and describe the purpose of the non-text object must be provided
and alternative forms in different modalities must be provided to
accommodate
different disabilities.
* Decoration, Formatting, Invisible Objects: If a non-text object is pure
decoration, or used only for visual formatting, or if it is not presented
to users,
then it is implemented such that it can be ignored by assistive technology.


Comment:
Insert note to include 8.1-a.
A content format that supports non-text objects must provide an encoding
mechanism to associate non-text objects with textual descriptions that a
user-agent can display to meet this provision.

3-G - Human Language

When presentation of electronic documents supports it, the default human
language of electronic documents can be programmatically determined.

Comment:
Insert note to include 8.1-k:
Note: Content formats which support multiple languages must provide a
programmatically determinable mechanism to identify both the primary
language, and the language of any sections that are in another language
from the primary language to meet this provision.


3-H - Language of Parts

When presentation of electronic documents supports it, the human language
of each passage or phrase in electronic documents can be programmatically
determined.

Comment:
Insert note to include 8.1-k:
Note: Content formats which support multiple languages must provide a
programmatically determinable mechanism to identify both the primary
language, and the language of any sections that are in another language
from the primary language to meet this provision.


3-M - Reading Sequence

When the sequence in which information is presented affects its meaning, a
correct reading sequence can be programmatically determined and sequential
navigation
of interactive components is consistent with that sequence.

Comment:
insert note to include 8.1-C.
Note: A content format that supports 2 dimensional display of information
must provide an encoding mechanism to identify the logical linear reading
order of the content displayable by a user-agent to meet this provision.


3-O - Information and Relationships

Information and relationships conveyed through presentation can be
programmatically determined or are available in text, and notification of
changes to these
is available to user agents, including assistive technologies. For example:


list of 4 items
1. row and column headers are identified for data tables
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.
3. markup is used to identify section headings
4. markup is used to identify form element labels
list end

Comment:
Insert note to include 8.1-D - Table Headers and 8.`1-e.

Note: A content format that supports row and column headers in data tables
must provide an encoding mechanism to identify row and column headers for
data tables displayable by a user-agent to meet this provision. A content
format that supports data tables that have two or more logical levels of
row or column headers must provide an encoding mechanism to associate
row and column headers with data cells, displayable by a user-agent to meet
this provision.

editorial suggestion for first paragraph: Information and relationships
conveyed through presentation must be either programmatically determinable
or are
available in text, and notification of changes to these is available to
user agents, including assistive technologies. For example:

Rationale: The existing 508 provisions on table headers are technology
specific to HTML. This more general provision is more applicable to Web
content in
other technologies.

Discussion of Work in Progress
* (Peter K) This provision pretty clearly assumes it is
talking about a document, but it doesn't mention it explicitly
(and there, an XML/HTML document). In (2), (3), and (4) it
directs
the explicit use of "markup" to do things (all of which are
covered in 3-V).
This provision should either be removed as redundant, or scoped
to
explicitly apply to (web) documents.
* (Jared S) Should remove "markup"
* (Jared S) Disagrees with removing this provision
* Need to get agreement if the current text is acceptable


3-P - User Interface Components

For all user interface components, including form elements and those
generated by scripts, the name and role must be programmatically
determined. States,
properties, and values that can be set by the user must be programmatically
determined and can be programmatically set. Notification of changes to
these
items must be available to user agents, including assistive technologies.
For example: Frames must be titled with text that facilitates frame
identification
and navigation.

Rationale: To ensure that interactive elements in non-HTML technologies, or
those implemented by re-purposing HTML elements with JavaScript, properly
expose
information for AT interoperability.



Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303

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