Checkpoint details

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.

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.

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

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.

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.

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

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.

3.5.1 Test details

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

3.6.1 Test details

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.

4.1.2 Test details

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.

4.2.2 Test details

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.

4.3.2 Test details

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.

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

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.

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

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

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).

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.

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.

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.

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

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

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].

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.

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.

9.6.1 Test details

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.

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).

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.

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.

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

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.

10.2.1 Test details

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.

10.2.2 Test details

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.

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

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).

10.4.1 Test details

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.

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

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.

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.

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

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

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.

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.

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.

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.

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.