Thread Subject: Platform: TEITAC/508 mapping to UAAG

From: Jim Allan
Date: Wed, Aug 08 2007 11:35 AM

• Return to this mailing list's archives
• View all messages in this thread
• Next message in thread: None
• Previous message in thread: None
• Messages sorted by: Author | Thread | Date

The following is a mapping from 508 platform provisions to User Agent
Accessibility Guidelines (UAAG). In brief, 508 is more general in its
requirements concerning 'platform'. UAAG is more specific. As a result there
are many UAAG checkpoints for the three 508 platform requirements.

The W3C User Agent Accessibility Guidelines can be found at
http://www.w3.org/TR/2002/REC-UAAG10-20021217/uaag10.html

The following 508 platform provision are from
http://teitac.org/wiki/Web_and_Software:_Analysis_of_impact_to_harmonization
_with_WCAG_2.0_and_ISO

508 provisions are delineated by '508' preceding the text and separated from
UAAG checkpoints by '===='
UAAG checkpoints are delineated by 'UAAG' preceding the text and separated
from other UAAG checkpoints by '----'

====
Software that is both platform and application: Software that is both a
'platform', and an 'application' running on another platform must:

508 1. expose the underlying platform's color, contrast, and other
individual display settings to applications running within its platform, so
that these applications can meet the User Preferences provision.

=======

UAAG 3.1 Toggle background images (P1)

1. Allow configuration not to render background image content.

Normative inclusions and exclusions

1. This checkpoint must be satisfied for all implemented image
specifications; see the section on conformance profiles.
2. When configured not to render background images, the user agent is not
required to retrieve them until the user requests them explicitly. When
background images are not rendered, user agents should render a solid
background color instead; see checkpoint 4.3 for information about text
colors.
3. This checkpoint only requires control of background images for
"two-layered" renderings, where the background is considered the first layer
and everything rendered above it is considered the second layer.

----

UAAG 7.1 Respect focus and selection conventions (P1)

1. Follow operating environment conventions that benefit accessibility
when implementing the selection, content focus, and user interface focus.

-----

UAAG 7.2 Respect input configuration conventions (P1)

1. Ensure that default input configurations of the user agent do not
interfere with operating environment accessibility conventions (e.g., for
keyboard accessibility).

-----

UAAG 7.3 Respect operating environment conventions (P2)

1. Follow operating environment conventions that benefit accessibility.
In particular, follow conventions that benefit accessibility for user
interface design, keyboard configuration, product installation, and
documentation.

----

UAAG 7.4 Provide input configuration indications (P2)

1. Follow operating environment conventions to indicate the input
configuration.
=====

505 2. define, expose, and translate accessibility service information
between applications running within its platform and the underlying
platform - so that those applications can meet the AT Interoperability
provision.

=====

UAAG 1.1 Full keyboard access (P1) Techniques for checkpoint 1.1

1. Ensure that the user can operate, through keyboard input alone, any
user agent functionality available through the user interface.

----

UAAG 1.2 Activate event handlers (P1) Techniques for checkpoint 1.2

1. Allow the user to activate, through keyboard input alone, all input
device event handlers that are explicitly associated with the element
designated by the content focus.
2. In order to satisfy provision one of this checkpoint, the user must be
able to activate as a group all event handlers of the same input device
event type. For example, if there are 10 handlers associated with the
onmousedown event type, the user must be able to activate the entire group
of 10 through keyboard input alone, and must not be required to activate
each handler separately.

Normative inclusions and exclusions

1. Provision one of this checkpoint applies to handlers of any input
device event type, including event types for keyboard, pointing device, and
voice input.
2. The user agent is not required to allow activation of event handlers
associated with a given device (e.g., the pointing device) in any order
other than what the device itself allows (e.g., a mouse down event followed
by a mouse drag event followed by a mouse up event).
3. The requirements for this checkpoint refer to any explicitly
associated input device event handlers associated with an element,
independent of the input modalities for which the user agent conforms. For
example, suppose that an element has an explicitly associated handler for
pointing device events. Even when the user agent only conforms for keyboard
input (and does not conform for the pointing device, for example), this
checkpoint requires the user agent to allow the user to activate that
handler with the keyboard.
4. This checkpoint is mutually exclusive of checkpoint 1.1 since the
current checkpoint may be excluded from a conformance profile, unlike other
keyboard operation requirements.

----

UAAG 2.1 Render content according to specification (P1) Techniques for
checkpoint 2.1

1. Render content according to format specification (e.g., for a markup
language or style sheet language).

Normative inclusions and exclusions

1. Rendering requirements include format-defined interactions between
author preferences and user preferences/capabilities (e.g., when to render
the alt attribute in HTML, the rendering order of nested OBJECT elements in
HTML, test attributes in SMIL, and the cascade in CSS2).
2. When a rendering requirement of another specification contradicts a
requirement of UAAG 1.0, the user agent may disregard the rendering
requirement of the other specification and still satisfy this checkpoint;
see the section on the relation of this document to general software design
guidelines and other specifications for more information.
3. The user agent is not required to satisfy this checkpoint for all
implemented specifications; see the section on conformance profiles for more
information.
4. This checkpoint excludes the requirements of checkpoint 2.6.

----

UAAG 2.3 Render conditional content (P1) Techniques for checkpoint 2.3

1. Allow configuration to provide access to each piece of unrendered
conditional content "C".
2. When a specification does not explain how to provide access to this
content, do so as follows:
* If C is a summary, title, alternative, description, or expansion
of another piece of content D, provide access through at least one of the
following mechanisms:
o (1a) render C in place of D;
o (2a) render C in addition to D;
o (3a) provide access to C by allowing the user to query D.
In this case, the user agent must also alert the user, on a per-element
basis, to the existence of C (so that the user knows to query D); and
o (4a) allow the user to follow a link to C from the context
of D.
* Otherwise, provide access to C through at least one of the
following mechanisms:
o (1b) render a placeholder for C, and allow the user to
view the original author-supplied content associated with each placeholder;
o (2b) provide access to C by query (e.g., allow the user to
query an element for its attributes). In this case, the user agent must also
alert the user, on a per-element basis, to the existence of C; and
o (3b) allow the user to follow a link in context to C.

Normative inclusions and exclusions

1. For the placeholder requirement of provision two of this checkpoint, a
request to view the original content associated with a placeholder is
considered an explicit user request to render that content.
2. The user agent is not required to include placeholders in the document
object. A placeholder that is part of the document object should conform to
the Web Content Accessibility Guidelines 1.0 [WCAG10].

----

UAAG 2.4 Allow time-independent interaction (P1) Techniques for checkpoint
2.4

1. For rendered content where user input is only possible within a finite
time interval controlled by the user agent, allow configuration to provide a
view where user interaction is time-independent.

Normative inclusions and exclusions

1. When satisfying this checkpoint for a real-time presentation, the user
agent may discard packets that continue to arrive after the construction of
the time-independent view (e.g., when paused or after the construction of a
static view).
2. This checkpoint does not apply when the user agent cannot recognize
the time interval in the presentation format, or when the user agent cannot
control the timing (e.g., because it is controlled by the server).

----

UAAG 2.5 Make captions, transcripts, audio descriptions available (P1)

1. Allow configuration or control to render text transcripts, collated
text transcripts, captions, and audio descriptions in content at the same
time as the associated audio tracks and visual tracks.

----

UAAG 2.6 Respect synchronization cues (P1)

1. Respect synchronization cues (e.g., in markup) during rendering.

----

UAAG 3.4 Toggle scripts (P1)

1. Allow configuration not to execute any executable content (e.g.,
scripts and applets).

Normative inclusions and exclusions

1. This checkpoint does not apply to plug-ins and other programs that are
not part of content.

Note: Scripts and applets may provide very useful functionality, not all of
which causes accessibility problems. Developers should not consider that the
user's ability to turn off scripts is an effective way to improve content
accessibility; turning off scripts means losing the benefits they offer.
Instead, developers should provide users with finer control over user agent
or content behavior known to raise accessibility barriers. The user should
only have to turn off scripts as a last resort.

----

UAAG 3.5 Toggle automatic content retrieval (P1)

1. Allow configuration so that the user agent only retrieves content on
explicit user request.

Normative inclusions and exclusions

1. When the user chooses not to retrieve (fresh) content, the user agent
may ignore that content; buffering is not required.
2. This checkpoint only applies when the user agent (not the server)
automatically initiates the request for fresh content. However, the user
agent is not required to satisfy this checkpoint for "client-side
redirects," i.e., author-specified instructions that a piece of content is
temporary and intermediate, and is replaced by content that results from a
second request.

----

UAAG 6.1 Programmatic access to HTML/XML infoset (P1)

1. Provide programmatic read access to XML content by making available
all of the information items defined by the W3C XML Infoset [INFOSET].
2. Provide programmatic read access to HTML content by making available
all of the following information items defined by the W3C XML Infoset
[INFOSET]:
* Document Information item: children, document element, base URI,
charset
* Element Information items: element-type name, children,
attributes, parent
* Attribute Information items: attribute-type name, normalized
value, specified, attribute type, references, owner element
* Character Information items: character code, parent element
* Comment Information items: content, parent
3. If the user can modify the state or value of a piece of HTML or XML
content through the user interface (e.g., by checking a box or editing a
text area), allow programmatic read access to the current state or value,
and allow the same degree of write access programmatically as is available
through the user interface.

----

UAAG 6.2 DOM access to HTML/XML content (P1)

1. Provide access to the content required in checkpoint 6.1 by conforming
to the following modules of the W3C Document Object Model (DOM) Level 2 Core
Specification [DOM2CORE] and exporting bindings for the interfaces they
define:
* for HTML: the Core module
* for XML: the Core and XML modules
2. As part of satisfying provision one of this checkpoint:
* In the Java and ECMAScript operating environments, export the
normative bindings specified in the DOM Level 2 Core Specification
[DOM2CORE], or
* In other operating environments, the exported bindings (e.g.,
C++) must be publicly documented.

Normative inclusions and exclusions

1. Refer to the "Document Object Model (DOM) Level 2 Core Specification"
[DOM2CORE] for information about which versions of HTML, XML, Java, and
ECMAScript are covered. Appendix D contains the Java bindings and Appendix E
contains the ECMAScript bindings.
2. The user agent is not required to export the bindings outside of the
user agent process (though doing so may be useful to assistive technology
developers).

----

UAAG 6.3 Programmatic access to non-HTML/XML content (P1)

1. For content other than HTML and XML, provide structured programmatic
read access to content.
2. If the user can modify the state or value of a piece of non-HTML/XML
content through the user interface (e.g., by checking a box or editing a
text area), allow programmatic read access to the current state or value,
and allow the same degree of write access programmatically as is available
through the user interface.
3. As part of satisfying provision one of this checkpoint, implement at
least one API according to this API cascade:
* The API is defined by a W3C Recommendation, or the API is
publicly documented and designed to enable interoperability with assistive
technologies.
* If no such API is available, or if available APIs do not enable
the user agent to satisfy the requirements,
o implement at least one publicly documented API to satisfy
the requirements, and
o follow operating environment conventions for the use of
input and output APIs.

Normative inclusions and exclusions

1. "Structured programmatic access" means access through an API to
recognized information items of the content (such as the information items
of the XML Infoset [INFOSET]). Plain text has little structure, so an API
that provides access to it will be correspondingly less complex than an API
for XML content. For content more structured than plain text, an API that
only provides access to a stream of characters does not satisfy the
requirement of providing structured programmatic access. This document does
not otherwise define what is sufficiently structured access.
2. An API is considered "available" if the specification of the API is
published (e.g., as a W3C Recommendation) in time for integration into a
user agent's development cycle.

----

UAAG 6.4 Programmatic access to information about rendered content (P1)

1. For graphical user agents, make available bounding dimensions and
coordinates of rendered graphical objects. Coordinates must be relative to
the point of origin in the graphical environment (e.g., with respect to the
desktop), not the viewport.
2. For graphical user agents, provide access to the following information
about each piece of rendered text: font family, font size, and foreground
and background colors.
3. As part of satisfying provisions one and two of this checkpoint,
implement at least one API according to the API cascade described in
provision two of checkpoint 6.3.

----

UAAG 6.6 Programmatic notification of changes (P1)

1. Provide programmatic notification of changes to content, states and
values of content, user agent user interface controls, selection, content
focus, and user interface focus.
2. As part of satisfying provision one of this checkpoint, implement at
least one API according to the API cascade of provision two of checkpoint
6.3.

Normative inclusions and exclusions

1. The user agent is not required to provide notification of changes in
the rendering of content (e.g., due to an animation effect or an effect
caused by a style sheet) unless the document object is modified as part of
those changes.

----

UAAG 6.7 Conventional keyboard APIs (P1)

1. Implement APIs for the keyboard as follows:
* Follow operating environment conventions.
* If no conventions exist, implement publicly documented APIs.

----

UAAG 6.9 DOM access to CSS style sheets (P2)

1. For user agents that implement Cascading Style Sheets (CSS), provide
programmatic access to style sheets by conforming to the CSS module of the
W3C Document Object Model (DOM) Level 2 Style Specification [DOM2STYLE] and
exporting bindings for the interfaces it defines.
2. As part of satisfying provision one of this checkpoint:
* In the Java and ECMAScript operating environments, export the
normative bindings specified in the CSS module of the DOM Level 2 Style
Specification [DOM2STYLE], or
* In other operating environments, the exported bindings (e.g.,
C++) must be publicly documented.

Normative inclusions and exclusions

1. For the purposes of satisfying this checkpoint, Cascading Style Sheets
(CSS) are defined by either CSS Level 1 [CSS1] or CSS Level 2 [CSS2].
2. Refer to the "Document Object Model (DOM) Level 2 Style Specification"
[DOM2STYLE] for information about which versions of Java and ECMAScript are
covered. Appendix B contains the Java bindings and Appendix C contains the
ECMAScript bindings.
3. The user agent is not required to export the bindings outside of the
user agent process.

----

UAAG 6.10 Timely exchanges through APIs (P2)

1. For APIs implemented to satisfy the requirements of this document,
ensure that programmatic exchanges proceed in a timely manner.

----

UAAG 9.5 No events on focus change (P2)

1. Allow configuration so that moving the content focus to or from an
enabled element does not automatically activate any explicitly associated
event handlers of any event type.

----

UAAG 9.6 Show event handlers (P2)

1. For the element with content focus, make available the list of input
device event types for which there are event handlers explicitly associated
with the element.

====

508 3. provide mechanisms for:
* moving the keyboard focus into and out of an application, and
* addressing central conflicts between keyboard mnemonics in the
application and the host platform.

====

UAAG 9.1 Provide content focus (P1)

1. Provide at least one content focus for each viewport (including
frames) where enabled elements are part of the rendered content.
2. Allow the user to make the content focus of each viewport the current
focus.

Normative inclusions and exclusions

1. When a viewport includes no enabled elements (either because the
format does not provide for this, or a given piece of content has no enabled
elements), the content focus requirements of the following checkpoints do
not apply: 1.2, 5.1, 5.4, 6.6, 7.1, 9.3, 9.4, 9.5, 9.6, 9.7, 10.2, and 11.5.

----

UAAG 9.2 Provide user interface focus (P1)

1. Provide a user interface focus.

Note: See checkpoint 7.1 for information about implementing user interface
focus according to operating environment conventions.

----

UAAG 9.3 Move content focus (P1)

1. Allow the user to move the content focus to any enabled element in the
viewport.
2. Allow configuration so that the content focus of a viewport only
changes on explicit user request.
3. If the author has not specified a navigation order, allow at least
forward sequential navigation, in document order, to each element in the set
established by provision one of this checkpoint.

Normative inclusions and exclusions

1. The user agent may also include disabled elements in the navigation
order.

----



Jim Allan, Webmaster & Statewide Technical Support Specialist
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964

• Next message in Thread: None
• Previous message in Thread: None