| 
Evaluation Information
For User Agent Accessibility Guidelines 1.0, 20020821/ draft.
- User agent information
- IBM Home Page
Reader 3.02,
IBM
- Operating system information
- Specification information
- Reviewer information
Evaluation Summary
- Complete
-
1.1, 1.3, 2.1, 2.2, 2.3, 2.7, 2.8, 2.9, 3.1, 3.2, 3.3, 3.4, 3.5, 4.1, 4.2, 4.3, 4.7, 4.8, 4.9, 4.10, 4.11, 4.12, 4.13, 4.14, 5.4, 6.1, 6.2, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 7.1, 7.3, 7.4, 9.1, 9.2, 9.3, 9.5, 9.7, 9.8, 9.9, 9.10, 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 11.1, 11.5, 11.6, 12.1, 12.2, 12.3, 12.4, 12.5
- Almost Complete
-
3.6, 7.2, 11.4
- Partially Implemented
-
1.2, 5.5, 8.1, 10.1
- Not Implemented
-
5.1, 5.3, 9.6, 11.2, 11.3
- Not Rated
-
2.10, 5.2, 6.4, 8.2, 9.4, 11.7
Checkpoint details
Comments:
- All functions can be operated using the
keyboard alone. Text can be selected by marking the beginning and end of text
with shortcut keys or the HPR menu. Cut, copy, paste can be accessed with
common shortcut keys as well as with the Alt and arrow keys through the menus.
F6 takes the user through all the views and the address bar. HPR can be
installed by just pressing Enter a number of times or by tabbing to different
text fields and buttons. All documentation and web page elements such as form
controls and tables can be accessed using standard Windows keys (arrows, PgUp,
PgDn, Home, End, Tab) as well as numeric keypad keys.
Provision details
-
Ensure that the user can operate through keyboard input alone any user agent functionality available through the user interface.
Provision details
-
Allow the user to activate, through keyboard input alone, all event handlers that are explicitly associated with the element designated by the content focus.
-
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.
Comments:
- Spoken messages that are not web page
content or HPR menus and dialogs are rendered in the information view or on the
status line. The user can read the status line with Ctrl + Shift + F1 and the
information view with
F6.
Provision details
-
Ensure that every message (e.g., prompt, alert, notification, etc.) that is a non-text element and is part of the user agent user interface has a text equivalent.
Comments:
- All content is available visually in the
Graphics View dependent on IE's support. Most content is available in speech
and in the text view except for objects, applets, some plug-ins, ABBR, and
ACRONYM. For applets, alt, title, or code and content is rendered in text and
speech. For objects, the codebase, data, or classid attribute and content is
rendered in text and speech. For image links and areas, the alt text, title, or
the href is rendered and a longdesc if available. Longdesc is rendered as a
link pointing to another page containing the longdesc content. For controls and
forms, meta text is rendered describing the type attribute and the FORM tag.
Also, the number of map areas and select options are rendered as meta text. For
frames, the title, name, or src attribute is rendered in the information view
or in a dialog list control. For tables, colspan and rowspan are rendered if
there is more than 1, and headers are rendered if there are more than 3 rows or
3 columns. Settings are available to control the rendering of images with no or
null alt text and the headers for table rows and columns. For all links, the
user can press a status line key (Ctrl + Shift + F1) to hear the href which is
displayed on the status line. For all elements, the title attribute is also
displayed on the status line and spoken using the status line key.
Provision details
-
Render content according to format specification (e.g., for a markup language or style sheet language).
Comments:
- Provides a source view of documents and
source view of frame elements
Provision details
-
For content authored in text formats, provide a view of the text source. For the purposes of this checkpoint, a text format is any media object given an Internet media type of "text" (e.g., "text/plain", "text/html", or "text/*") as defined in RFC 2046 [RFC2046], section 4.1.
Comments:
- See implementation notes under Checkpoint
2.1 for applet, object, img, area, input, abbr, and acronym, conditional
content settings, and the status line key. Table summaries are rendered in the
information view and speech when the Where am I key is pressed. HPR does not
render NOFRAMES, NOSCRIPT, the longdesc for FRAME or IFRAME, or multimedia
conditional
content.
Provision details
-
Allow configuration to provide access to each piece of unrendered conditional content "C".
-
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: (1a) render C in place of D; (2a) render C in addition to D; (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); (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: (1b) render a placeholder for C, and allow the user to view the original author-supplied content associated with each placeholder; (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; (3b) allow the user to follow a link in context to C.
Provision details
-
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.
Provision details
-
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.
Provision details
-
Respect synchronization cues (e.g., in markup) during rendering.
Comments:
- See implementation notes under 2.1 and
10.1 for content repair techniques and cell header repair
strategies.
Provision details
-
Allow configuration to generate repair text when the user agent recognizes that the author has failed to provide conditional content that was required by the format specification.
Comments:
- HPR
does not render an element with alt="" unless the user has turned on the
setting to announce images with no alt
text.
Provision details
-
Allow at least two configurations for when the user agent recognizes that conditional content required by the format specification is present but empty content: generate no repair text, or generate repair as described in checkpoint 2.7.
Comments:
- HPR: Yes, see the implementation notes
under 2.3 and
2.1.
Provision details
-
Allow configuration to render all conditional content automatically.
-
As part of satisfying provision one of this checkpoint, provide access according to specification, or where unspecified, by applying one of the techniques 1a, 2a, or 1b defined in checkpoint 2.3.
Provision details
-
Allow configuration not to render text in unsupported scripts (i.e., writing systems) when that text would otherwise be rendered.
-
When configured per provision one of this checkpoint, indicate to the user in context that author-supplied content has not been rendered.
Comments:
- Embeds IE so inherits accessibility
features of
IE
Provision details
-
Allow configuration not to render background image content.
Comments:
- Embeds IE so inherits accessibility
features of
IE
Provision details
-
Allow configuration not to render audio, video, or animated image content, except on explicit user request.
Comments:
- Embeds IE so inherits accessibility
features of
IE
Provision details
-
Allow configuration to render animated or blinking text content as motionless, unblinking text. Blinking text is text whose visual rendering alternates between visible and invisible, at any rate of change.
Comments:
- Embeds IE so inherits accessibility
features of
IE
Provision details
-
Allow configuration not to execute any executable content (e.g., scripts and applets).
Comments:
- Embeds IE so inherits accessibility
features of
IE
Provision details
-
Allow configuration so that the user agent only retrieves content on explicit user request.
Comments:
- Dependent on IE and Internet Options to
handle this in the Graphics view. Of course, no images are rendered in the text
view but alt text is rendered instead. Also, for images with null alt text or
have no alt text and are not a link, the user can choose whether or not to
render the image "placeholder" or
not.
Provision details
-
Allow configuration not to render image content.
Comments:
- The user can control text size through a
text settings dialog or the Windows system settings for all views except the
Graphics view, the menus, and dialogs. The text size can be selected uniquely
for headings, list items, links, visited links, search results, and meta text.
HPR has a small to large font size setting for both the text and graphics
views. They can also use Internet Options and style sheets to control font size
in the graphics
view.
Provision details
-
Allow global configuration of the scale of visually rendered text content. Preserve distinctions in the size of rendered text as the user increases or decreases the scale.
-
As part of satisfying provision one of this checkpoint, provide a configuration option to override rendered text sizes specified by the author or user agent defaults.
-
As part of satisfying provision one of this checkpoint, offer a range of text sizes to the user that includes at least: the range offered by the conventional utility available in the operating environment that allows users to choose the text size (e.g., the font size), or if no such utility is available, the range of text sizes supported by the conventional APIs of the operating environment for drawing text.
Comments:
- The user can control font type, style, and
effects in the same way as they control font size (see
4.1).
Provision details
-
Allow global configuration of the font family of all visually rendered text content.
-
As part of satisfying provision one of this checkpoint, provide a configuration option to override font families specified by the author or by user agent defaults.
-
As part of satisfying provision one of this checkpoint, offer a range of font families to the user that includes at least: the range offered by the conventional utility available in the operating environment that allows users to choose the font family, or if no such utility is available, the range of font families supported by the conventional APIs of the operating environment for drawing text.
Comments:
- The user can control foreground and
background colors in the same way as they control font size (see
4.1).
Provision details
-
Allow global configuration of the foreground and background color of all visually rendered text content.
-
As part of satisfying provision one of this checkpoint, provide a configuration option to override foreground and background colors specified by the author or user agent defaults.
-
As part of satisfying provision one of this checkpoint, offer a range of colors to the user that includes at least: the range offered by the conventional utility available in the operating environment that allows users to choose colors, or if no such utility is available, the range of colors supported by the conventional APIs of the operating environment for specifying colors.
Provision details
-
Allow the user to slow the presentation rate of rendered audio and animation content (including video and animated images).
-
As part of satisfying provision one of this checkpoint, for a visual track, provide at least one setting between 40% and 60% of the original speed.
-
As part of satisfying provision one of this checkpoint, for a prerecorded audio track including audio-only presentations, provide at least one setting between 75% and 80% of the original speed.
-
When the user agent allows the user to slow the visual track of a synchronized multimedia presentation to between 100% and 80% of its original speed, synchronize the visual and audio tracks (per checkpoint 2.6). Below 80%, the user agent is not required to render the audio track.
Provision details
-
Allow the user to stop, pause, and resume rendered audio and animation content (including video and animated images) that last three or more seconds at their default playback rate.
-
Allow the user to navigate efficiently within audio and animations (including video and animated images) that last three or more seconds at their default playback rate.
Provision details
-
For graphical viewports, allow configuration so that captions synchronized with a visual track in content are not obscured by it.
Comments:
- For HPR-generated audio. Speech can be
turned on or off for the whole HPR environment or for just external
applications supported by HPR (so that a user can use their screen reader
instead of HPR speech, if desired). HPR volume control is relative to the
system and physical volume control settings. For controlling volume in web page
objects and plug-ins, HPR is dependent on IE and Internet Options and the
plug-in
interfaces.
Provision details
-
Allow global configuration of the volume of all rendered audio, with an option to override audio volumes specified by the author or user agent defaults.
-
As part of satisfying provision one of this checkpoint, allow the user to choose zero volume (i.e., silent).
Comments:
- Volume can be controlled individually for
default text, headings, links, visited links, search results, meta text, list
items, messages, and menus and dialogs. Speech can be turned on or off for
external applications supported by HPR so that a user can use their screen
reader instead of HPR speech, if
desired.
Provision details
-
Allow independent control of the volumes of rendered audio content synchronized to play simultaneously.
Comments:
- See implementation notes under 4.7 and
4.8.
Provision details
-
Allow configuration of the synthesized speech rate, according to the full range offered by the speech synthesizer.
Comments:
- HPR supports SAPI tags for gender, age,
rate, volume, effects (robotic and whisper), and language. Except for language,
these speech characteristics can be controlled individually for default text,
headings, links, visited links, search results, meta text, list items,
messages, and menus and dialogs. The language setting is controlled by a user
request, or automatically by using the lang attribute for any element, if it
exists, or by analyzing the text for a web page using an HPR
algorithm.
Provision details
-
Allow control of the synthesized speech volume, independent of other sources of audio.
Comments:
- HPR allows configuration of gender, age,
and effects (monotone or robotic). These characteristics group pitch, stress,
richness and
etc..
Provision details
-
Allow configuration of synthesized speech characteristics according to the full range of values offered by the speech synthesizer.
Comments:
- HPR allows configuration of gender, age,
and effects (monotone or robotic). These characteristics group pitch, stress,
richness and
etc..
Provision details
-
Allow configuration of synthesized speech pitch. Pitch refers to the average frequency of the speaking voice.
-
Allow configuration of synthesized speech pitch range. Pitch range specifies a variation in average frequency.
-
Allow configuration of synthesized speech stress. Stress refers to the height of "local peaks" in the intonation contour of the voice.
-
Allow configuration of synthesized speech richness. Richness refers to the richness or brightness of the voice.
Provision details
-
Provide support for user-defined extensions to the synthesized speech dictionary.
-
Provide support for spell-out: where text is spelled one character at a time, or according to language-dependent pronunciation rules.
-
Allow at least two configurations for speaking numerals: one where numerals are spoken as individual digits, and one where full numbers are spoken.
-
Allow at least two configurations for speaking punctuation: one where punctuation is spoken literally, and one where punctuation is rendered as natural pauses.
Comments:
- Embeds IE so inherits accessibility
features of
IE
Provision details
-
Allow the user to choose from and apply alternative author style sheets (such as linked style sheets).
-
Allow the user to choose from and apply at least one user style sheet.
-
Allow the user to turn off (i.e., ignore) author and user style sheets.
Provision details
-
Allow configuration so that if a viewport opens without explicit user request, neither its content focus nor its user interface focus automatically becomes the current focus.
Provision details
-
For graphical user interfaces, allow configuration so that the viewport with the current focus remains "on top" of all other viewports with which it overlaps.
Provision details
-
Allow configuration so that viewports only open on explicit user request.
-
When configured per provision one of this checkpoint, instead of opening a viewport automatically, alert the user and allow the user to open it with an explicit request (e.g., by confirming a prompt or following a link generated by the user agent).
-
Allow the user to close viewports.
Provision details
-
Ensure that when a viewport's selection or content focus changes, it is at least partially in the viewport after the change.
Comments:
- Only can be configured to provide a
prompt if the information submitted is not through a secure (encrypted)
connection.
Provision details
-
Allow configuration to prompt the user to confirm (or cancel) any form submission.
Provision details
-
Provide programmatic read access to XML content by making available all of the information items defined by the W3C XML Infoset [INFOSET].
-
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
-
If the user can modify HTML and XML content ("write access") through the user interface (e.g., through form controls), allow for the same modifications programmatically.
Provision details
-
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.
-
As part of satisfying provision one of this checkpoint, Export the normative bindings specified in the DOM Level 2 Core Specification [DOM2CORE] (namely, for Java [JAVA] and ECMAScript [ECMASCRIPT] operating environments). For other environments, the bindings exported to satisfy provision one of this checkpoint (e.g., C++ bindings) must be publicly documented.
Provision details
-
For content other than HTML and XML, provide structured programmatic read access to content, and write access to those parts of content that the user can modify through the user interface.
-
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, implement at least one publicly documented API to satisfy the requirements, and follow operating environment conventions for the use of input and output APIs.
Provision details
-
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.
-
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.
-
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.
Comments:
- HPR uses standard Windows
controls.
Provision details
-
Provide programmatic read access to user agent user interface controls, selection, content focus, and user interface focus.
-
Provide programmatic write access for those user agent user interface controls that the user can modify through the user interface.
-
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.
Comments:
- Embeds IE so inherits accessibility
features of
IE
Provision details
-
Provide programmatic notification of changes to content, user agent user interface controls, selection, content focus, and user interface focus.
-
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.
Comments:
- HPR is a standard Windows C++ MFC
application that uses Microsoft MSDN Workshop, HTML Help Workshop, Speech SDK,
and Platform SDK libraries. HPR does not implement MSAA
interfaces.
Provision details
-
Implement APIs for the keyboard as follows: Follow operating environment conventions. If no conventions exist, implement publicly documented APIs.
Comments:
- HPR implements and handles keys for menus,
dialogs, and navigating web pages using standard APIs, but HPR does not handle
accesskey attributes on web
pages.
Provision details
-
For an API implemented to satisfy requirements of this document, support the character encodings required for that API.
Comments:
- Yes, but dependent on the IE web browser
control and COM interfaces to the IE DOM. The IE Encoding menu does not show
any UTF-16 encodings as
options.
Provision details
-
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.
-
As part of satisfying provision one of this checkpoint: Export the normative bindings specified in the CSS module of the DOM) Level 2 Style Specification [DOM2STYLE] (namely, for Java [JAVA] and ECMAScript [ECMASCRIPT] operating environments). For other environments, the bindings exported to satisfy provision one of this checkpoint must be publicly documented.
Comments:
- Access through the IE web browser control
for the Graphics view
only.
Provision details
-
For APIs implemented to satisfy the requirements of this document, ensure that programmatic exchanges proceed in a timely manner.
Provision details
-
Follow operating environment conventions that benefit accessibility when implementing the selection, content focus, and user interface focus.
Comments:
- HPR implements default keyboard bindings
for the most part. Some exceptions include different meanings for the arrow
keys, PgUp, PgDn, Home and End depending on the reading mode; Spacebar for
resume reading instead of list selection; and Ctrl + B and Ctrl + D instead of
Shift + arrow keys for selecting text on web
pages.
Provision details
-
Ensure that default input configurations of the user agent do not interfere with operating environment accessibility conventions (e.g., for keyboard accessibility).
Comments:
- HPR uses standard Windows controls,
standard Windows keys, a standard installation program (InstallShield), and
HTML documentation. Checkpoint 7.4 Follow operating environment conventions to
indicate the input configuration. User agent only (Techniques for 7.4) ; Key
bindings are underlined in menus and spoken and shortcut keys are displayed on
the menus and spoken. Also, see implementation notes for
11.1.
Provision details
-
Follow operating environment conventions that benefit accessibility. In particular, follow conventions that benefit accessibility for user interface design, keyboard configuration, product installation, and documentation.
Provision details
-
Follow operating environment conventions to indicate the input configuration.
Comments:
- Partial. HPR renders in text and speech
the CAPTION, THEAD, TFOOT for tables as they are encountered in a table. HPR
renders in text and speech the headers or scope attribute as each new row or
column cell is read for tables with more than 3 rows or columns. The user can
turn on or off the reading of headers. HPR does not support TBODY, COLGROUP,
COL, axis, tabindex, or accesskey in text or speech. Also, see implementation
notes under Checkpoint
2.1.
Provision details
-
Implement the accessibility features of specifications (markup languages, style sheet languages, metadata languages, graphics formats, etc.).
Provision details
-
Use and conform to either W3C Recommendations when they are available and appropriate for a task, or non-W3C specifications that enable the creation of content that conforms at level A or better to the Web Content Accessibility Guidelines 1.0 [WCAG10].
Comments:
- F6 takes the user through all the views
and the address bar. FRAMES and IFRAMES are selected using Ctrl + Tab or Ctrl +
Shift + Tab, or the frameset can be displayed in a dialog with all the frames
in a list for navigation and then selection by arrows or letters and then
Enter.
Provision details
-
Provide at least one content focus for each viewport (including frames) where enabled elements are part of the rendered content.
-
Allow the user to make the content focus of each viewport the current focus.
Comments:
- Users can move focus forward and backward
by word, character, item, lines, links, tables, table cells, headings, and form
controls by selecting a reading mode and then using arrow keys. Users can
always use the Tab and Shift-Tab to move to links and controls, and Ctrl +
arrows to move by words. A user can navigate a list of links and controls in a
dialog by typing the first letters of a link or control. The user also can
enable and use the HPR 2.5 numeric keypad keys for navigation instead of the
keyboard keys. Also, there are ways such as reading the whole page, Controls
reading, and Table Jump reading, to read just the start of a group of elements,
such as select menus, map areas, and tables, without reading each element.
Searching for meta text, such as the words form, map, select, or submit, is a
more direct way to navigate a web page. The tabindex attribute is not
supported.
Provision details
-
Provide a user interface focus.
Comments:
- When a user returns to the previous page
in HPR's history, HPR returns them to the last point of regard on an item basis
and then highlights and begins speaking from the beginning of that
item.
Provision details
-
Allow the user to move the content focus to any enabled element in the viewport.
-
Allow configuration so that the content focus of a viewport only changes on explicit user request.
-
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.
Provision details
-
For user agents that implement a viewport history mechanism, for each state in a viewport's browsing history, maintain information about the point of regard, content focus, and selection.
-
When the user returns to any state in the viewport history (e.g., via the "back button"), restore the saved values for the point of regard, content focus, and selection.
Comments:
- Only when scripts are disabled
Provision details
-
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.
Provision details
-
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.
Comments:
- There are reading modes for moving focus
forward or backward to all links (hypertext, image links, map areas, controls)
or just to form controls. The Tab and Shift + Tab keys and numeric keypad keys
1, 2, and 3 always move focus to all links in all reading modes. The Links List
dialog is another way to move focus to any link. The user can also access links
along with other types of elements using other reading modes and numeric keypad
keys. Search functions provide another
mechanism.
Provision details
-
Extend the functionality required in provision three of checkpoint 9.3 by allowing the same sequential navigation in reverse document order.
-
As part of satisfying provision one of this checkpoint, the user agent must not include disabled elements in the navigation order.
Comments:
- The user presses a key (Ctrl + F) to bring
up a dialog to begin a forward or backward search from the current point of
regard, case sensitive or not, within the current frame or page or across the
Internet. The user can also begin a search from the address bar by typing a /
then string to search the current page or ? then string to search the Internet.
Shortcut keys allow the user to find the previous or next match. The user is
notified if there is no match in the direction in which they are searching. The
graphics and text views are always scrolled to show the item containing the
search string. The user can select distinctive text or speech settings to
distinguish search results from the surrounding text in the speech and text
views. In addition to plain text, the user can search for meta text (like
"Start of form 1"), alternative text for images, and text associated with
controls (any text seen in the text
view).
Provision details
-
Allow the user to search within rendered text content for a sequence of characters from the document character set.
-
Allow the user to start a forward search (in document order) from any selected or focused location in content.
-
When there is a match, do both of the following: move the viewport so that the matched text content is within it, and allow the user to search for the next instance of the text from the location of the match.
-
Alert the user when there is no match or after the last match in content (i.e., prior to starting the search over from the beginning of content).
-
Provide a case-insensitive search option for text in scripts (i.e., writing systems) where case is significant.
Comments:
- Provides structured navigation by
frames/iframes, links and controls, just controls, tops of tables, table cells
across rows and up and down columns, headings, lines, characters, words, and
items (like paragraphs). The user is told when the top or bottom or first or
last of a structure is reached. The user can also jump to the next or previous
block of text or links, which helps to skipping navigation bars. Also, the user
can hear about maps and select menus and their number of items but then skip
over the areas and options. For orientation, there are Where am I and page
summary keys. Structured navigation by lists, applets, divisions, images, maps,
and objects is not available in HPR 3.0, but an HPR user can navigate by item
and/or link to all those elements except for
divisions.
Provision details
-
Allow the user to navigate efficiently to and among important structural elements in rendered content.
-
As part of satisfying provision one of this checkpoint, allow forward and backward sequential navigation.
Comments:
- Through user style sheets and navigation
options
Provision details
-
Allow configuration of the set of important elements and attributes identified for checkpoints 9.9 and 10.4.
-
As part of satisfying provision one of this checkpoint, allow the user to include and exclude element types in the set.
Comments:
- Partial. Colspan and rowspan are rendered
before or after cell content according to a setting. Table summary, table
number on the page, and row and column position within the table are rendered
in the information view and speech when the Where am I key is pressed. The
CAPTION, THEAD, TFOOT are rendered in text and speech as they are encountered
in a table. HPR renders in text and speech the headers or scope attribute or a
TH as each new row or column cell is read for tables with more than 3 rows or 3
columns. The user can turn on or off the reading of headers. The user can also
press a key to hear the top or bottom cell of a column or the rightmost or
leftmost cell of a row without losing their current cell position. HPR does not
support TBODY, COLGROUP, COL, abbr, or axis in text or speech.; Does not
support header and scope
Provision details
-
For graphical user agents that render tables, for each table cell, allow the user to view associated header information.
Comments:
- The current selection and content focus is
highlighted in all views, menus, and dialogs except for controls in the
graphics view. HPR is dependent on Internet Options and style sheets for
configuration of highlighting in the Graphics view. Highlighting is configured
in all other views and UI through the Windows system settings. Low vision users
can use ZoomText and Big Shot with
HPR.
Provision details
-
Allow global configuration to highlight the following four classes of information in each viewport: the selection, content focus, enabled elements, and recently visited links.
-
For graphical user interfaces, as part of satisfying provision one of this checkpoint, allow at least one configuration where the highlight mechanisms for the four classes of information: differ from each other, and do not rely on rendered text foreground and background colors alone.
-
For graphical user interfaces, as part of satisfying provision one of this checkpoint, if a highlight mechanism involves text size, font family, rendered text foreground and background colors, or text decorations, offer at least the following range of values: for text size, the range required by provision three of checkpoint 4.1. for font family, the range required by provision three of checkpoint 4.2. for text foreground and background colors and decorations, the range offered by the conventional utility available in the operating environment for users to choose rendered text colors or decorations (e.g., the standard font and color dialog box resources supported by the operating system). If no such utility is available, the range supported by the conventional APIs of the operating environment for specifying text colors or drawing text.
-
Highlight enabled elements according to the granularity specified in the format. For example, an HTML user agent rendering a PNG image as part of a client-side image map is only required to highlight the image as a whole, not each enabled region. An SVG user agent rendering an SVG image with embedded graphical links is required to highlight each (enabled) link that may be rendered independently according to the SVG specification.
Comments:
- See 10.2 for highlighting configuration
for selection and focus. The user can distinguish the font size, style, type,
or effects in addition to color for links/controls and visited links in the
text view. Links and visited links can also be distinguished with speech (see
checkpoint 4.13), sounds, and leading and trailing text in the speech and text
views. Links/controls and visited links in the graphics view are set through
Internet Options. No distinctive settings exist for fee
links.
Provision details
-
Extend the functionality required by provision two of checkpoint 10.2 by allowing configuration through a single setting.
Comments:
- The user can select distinctive speech and
text settings (full range supported by Windows) for links (including controls)
and visited links for the current session for the speech and text views using
user style sheets or configuration options. Through Internet Options, the user
can select settings for links and visited links in the Graphics view.
Distinctive speech and text settings for image maps and fee links are not
available.
Provision details
-
Make available to the user an "outline" view of rendered content, composed of labels for important structural elements (e.g., heading text, table titles, form titles, and other labels that are part of the content).
Comments:
- The
user can get the link URL and title attribute (if it exists) by reading the
status line (Ctrl + Shift + F1). Visited links have distinctive speech and text
settings. Alt text and longdesc is rendered for image links. If automatic
language detection is on, the link is read in the author-specified language.
However, whether the link is internal, involves a fee, and information about
type, size, and natural language are not
rendered.
Provision details
-
To help the user decide whether to traverse a link in content, make available the following information about it: link element content, link title, whether the link is internal to the resource (e.g., the link is to a target in the same Web page), whether the user has traversed the link recently, and information about the type, size, and natural language of linked Web resources.
Comments:
- When a frame receives focus, the number of
the frame, the total number of frames, and the title is spoken and displayed in
the information view. When an HPR view or the application gains focus, the
current view name is spoken and displayed on the status line. However, visually
HPR does not outline which view or frame has
focus.
Provision details
-
Highlight the viewport with the current focus (including any frame that takes current focus).
-
For graphical viewports, as part of satisfying provision one of this checkpoint, provide at least one highlight mechanism that does not rely on rendered text foreground and background colors alone (e.g., use a thick outline).
-
If the techniques used to satisfy provision one of this checkpoint involve rendered text size, font family, rendered text foreground and background colors, or text decorations, allow global configuration and offer same ranges of values required by provision three of checkpoint 10.2.
Comments:
- When the selection or content focus
changes due to navigation or searching, both the graphics and text view scrolls
to show the new location. (There are still some glitches with the graphics
view.) The speech, text, and graphics view are
synchronized.
Provision details
-
Indicate the viewport's position relative to rendered content (e.g., the proportion of an audio or video clip that has been played, the proportion of a Web page that has been viewed, etc.).
Comments:
- The user can always get help by pressing
F1. When reading web pages, F1 displays online help in the form of an HTML web
page that explains all HPR features. To get a general, concise reference list
and description of keys, the user presses Shift + F1. From that help page,
there is a link that takes the user to a detailed list and description of keys
that are grouped by "input configurations" (basic keys that work everywhere,
numeric keypad keys, menu and dialog keys, reading mode keys, and keys that
work within different kinds of web page structures like forms and tables). All
access keys are underlined in the menus and spoken, and all shortcut keys are
displayed in the menus and spoken. HPR does not support web page access keys.
Possible key conflicts with 3 popular screen readers are documented in the HPR
online
help.
Provision details
-
Provide information to the user about current user preferences for input configurations.
Provision details
-
Provide a centralized view of the current author-specified input configuration.
Comments:
-
Provision details
-
Allow the user to override any binding that is part of the user agent default input configuration.
Comments:
- Of the 26 funtionalities identified in
11.5, HPR has single key bindings for 19 of them. The ones without single keys
are increase and decrease text size (text settings dialog), increase and
decrease global volume (speech settings dialog), fast reverse (none), history
forward (Alt + right arrow), and add to favorites (menu or Plus then minus).
However, every function can be accessed by pressing a series of single
keys.
Provision details
-
Allow the user to override any binding in the user agent default keyboard configuration with a binding to either a key plus modifier keys or to a single key.
-
For each functionality in the set required by checkpoint 11.5, allow the user to configure a single-key binding. A single-key binding is one where a single key press performs the task, with zero modifier keys.
Comments:
- Bindings exist for all functions except
fast reverse, and more than one binding is available for most of the functions.
The numeric keypad key bindings are available for compatibility with key
bindings in earlier versions of HPR and to allow one hand navigation. The user
can show and hide viewports through the menu system but not with shortcut
keys.
Provision details
-
Ensure that the user agent default input configuration includes bindings for the following functionalities required by other checkpoints in this document: move content focus to the next enabled element in document order, and move content focus to the previous enabled element in document order (checkpoints 9.3 and 9.7); activate the link designed by the content focus (checkpoints 1.1 and 9.1); search for text, search again for same text (checkpoint 9.8); increase the scale of rendered text, and decrease the scale of rendered text (checkpoint 4.1); increase global volume, and decrease global volume (checkpoint 4.7); stop, pause, resume, and navigate efficiently selected audio and animations, including video and animated images (checkpoint 4.5).
-
If the user agent supports the following functionalities, the default input configuration must also include bindings for them: next history state (forward), and previous history state (back); enter URI for a new resource; add a URI to favorites (i.e., bookmarked resources); view favorites; reload a resource; interrupt a request to reload a resource; for graphical viewports: navigation forward and backward through rendered content by approximately the height of the viewport; for user agents that render content in lines of (at least) text: move point of regard to next line, and previous line.
Comments:
- All HPR settings are saved in the Windows
registry under the Windows login name for the current user. So user "profiles"
are switched by logging into Windows under a different login name. Each
settings dialog has a Defaults button to return those settings to their default
values.
Provision details
-
For the configuration requirements of this document, allow the user to save user preferences in at least one user profile.
-
Allow the user to choose from among available user agent default profiles, profiles created by the same user, and no profile (i.e., the user agent default settings).
Comments:
-
Provision details
-
For graphical user agent user interfaces with tool bars, allow the user to configure the position of user agent user interface controls on those tool bars.
-
Offer a predefined set of controls that may be added to or removed from tool bars.
-
Allow the user to restore the default tool bar configuration.
Comments:
- All documentation is available in
accessible HTML format installed on the user's system and on the IBM
Accessibility Center web site. The main help file that describes all HPR keys
and functions is one file for easier searching. From HPR, the documentation can
also be saved as a plain ASCII text file to read with other programs or for
easier Braille printing. Tutorial text can be found in ASCII text files
installed in the user's hpr3 directory even though we don't point that out to
the
user.
Provision details
-
Ensure that at least one version of the user agent documentation conforms to at least level Double-A of the Web Content Accessibility Guidelines 1.0 [WCAG10].
Comments:
- All configurable settings can be accessed
from one Settings menu. Each setting, their default, and their range of values
are documented in one main section in the main online help. The Table of
Contents in help has a direct link to the Settings section. When focus is on
each setting, the user can press F1 to get contextual help for that setting.
There are also sections in the online help that describe low vision features,
Braille features, and screen reader
compatibility.
Provision details
-
Document all user agent features that benefit accessibility.
Comments:
- See implementation comment under
11.
Provision details
-
Document the default user agent input configuration (e.g., the default keyboard bindings).
Comments:
- See implementation comment under 12.2.
There's not one but 4 sections that mainly address accessibility (settings, low
vision, braille, screen reader
compatibility).
Provision details
-
Document changes from the previous version of the user agent to features that benefit accessibility, including features of the user interface.
Comments:
- All changes from previous releases of HPR
are documented in the second section of online help called "What's New in HPR
3.0."
Provision details
-
Provide a centralized view of all features of the user agent that benefit accessibility, in a dedicated section of the documentation.
Jon
Gunderson (jongund@uiuc.edu)
Ian Jacobs (ij@w3.org)
Matt May (mcm@w3.org)
Last revised:
$Date: 2002/12/18 17:14:20 $
|
Copyright
2000, 2001, 2002 W3C (MIT, INRIA, Keio), All Rights Reserved. W3C
liability,
trademark, document
useand software
licensingrules apply.