UAAG 1.0 Evaluation of IE 5.0 for Mac

Evaluation Information

For User Agent Accessibility Guidelines 1.0, 20020821/ draft.

User agent information

Internet Explorer 5.0, Microsoft

Operating system information

Macintosh OS 9.x

Specification information

Reviewer information

Tantek Celik (with Ian Jacobs), put title here, Microsoft(put email here)

Evaluation Summary

Complete: 1.3, 2.1, 2.2, 3.4, 3.6, 4.1, 4.2, 4.3, 4.7, 4.14, 5.4, 6.7, 6.8, 7.1, 7.2, 7.4, 9.1, 9.2, 9.8, 10.2, 10.6, 11.5, 11.6, 11.7
Almost Complete: 2.9, 2.10, 3.1, 6.10, 8.2, 9.3, 9.4, 9.7, 11.1, 12.3
Partially Implemented: 1.1, 1.2, 2.3, 2.8, 3.2, 3.3, 5.1, 5.3, 5.5, 6.1, 6.2, 6.5, 6.6, 6.9, 7.3, 8.1, 9.5, 10.1, 10.5, 10.7, 12.2
Not Implemented: 2.7, 3.5, 5.2, 9.6, 9.9, 9.10, 10.4, 11.2, 11.3, 11.4, 12.1, 12.4, 12.5
Not Rated: 6.4, 10.3

Checkpoint details

1.1 Full keyboard access. (P1) [PI]

Comments:

Inherit limiations in the Macintosh OS for full keyboard support

Provision details

1.1.1 [PI]

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

1.2 Activate event handlers. (P1) [PI]

Provision details

1.2.1 [PI]

Allow the user to activate, through keyboard input alone, all event handlers that are explicitly associated with the element designated by the content focus.

1.2.2 [PI]

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.

1.3 Provide text messages. (P1) [C]

Provision details

1.3.1 [C]

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.

2.1 Render content according to specification. (P1) [C]

Comments:

Complete for the following specifications HTML 4.01, CSS1 and PNG)

Provision details

2.1.1 [C]

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

2.2 Provide text view. (P1) [C]

Provision details

2.2.1 [C]

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.

2.3 Render conditional content. (P1) [PI]

Comments:

ALT for IMG: yes, ALT text is rendered in the place of the image when images turned off
TITLE for IMG element: Tooltip (mouse hover over image)
LONGDESC for IMG element: No
Content of OBJECT element: Yes, Render content when applets turned off.
ALT attribute of OBJECT: No
TITLE for MAP element: ??
ALT for AREA element: ??
ALT for INPUT element: No
ACRONYM element: ??
ABBR element: ??
SUMMARY for TABLE: ??
TITLE for FRAME: No
LONGDESC for FRAME: No
NOFRAME for FRAME: Yes
NOSCRIPT for SCRIPT: Yes
TITLE for any element: ??

Provision details

2.3.1 [PI]

Allow configuration to provide access to each piece of unrendered conditional content "C".

2.3.2 [PI]

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.

2.4 Allow time-independent interaction. (P1) [NA]

Provision details

2.4.1 [NA]

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.

2.5 Make captions, transcripts, audio descriptions available. (P1) [NA]

Provision details

2.5.1 [NA]

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.

2.6 Respect synchronization cues. (P1) [NA]

Provision details

2.6.1 [NA]

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

2.7 Repair missing content. (P2) [NI]

Provision details

2.7.1 [NI]

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.

2.8 No repair text. (P3) [PI]

Comments:

Generate no repair text: Yes
Allow config to generate repair: No.

Provision details

2.8.1 [PI]

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.

2.9 Render conditional content automatically. (P3) [AC]

Comments:

Most of 2.3 is done automatically

Provision details

2.9.1 [AC]

Allow configuration to render all conditional content automatically.

2.9.2 [AC]

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.

2.10 Don't render unsupported language. (P3) [AC]

Comments:

Use CSS to make LANG attribute rendered in context of the element

Provision details

2.10.1 [AC]

Allow configuration not to render text in unsupported scripts (i.e., writing systems) when that text would otherwise be rendered.

2.10.2 [AC]

When configured per provision one of this checkpoint, indicate to the user in context that author-supplied content has not been rendered.

3.1 Toggle background images. (P1) [AC]

Comments:

When images turned off, HTML background images not rendered, but CSS 'background-image' is.
{background-image: none ! important} will turn off all bg images

Provision details

3.1.1 [AC]

Allow configuration not to render background image content.

3.2 Toggle audio, video, animated images. (P1) [PI]

Comments:

Audio: C (even though not claiming conformance for sound)
Video: G (by turning off plug-ins, not claiming conformance for video)

Provision details

3.2.1 [PI]

Allow configuration not to render audio, video, or animated image content, except on explicit user request.

3.3 Toggle animated or blinking text. (P1) [PI]

Comments:

Blinking: C
Animated: P - No preference to make MARQUEE text static, but can display:none - Might be able to allow stop MARQUEE on per page basis (but no config).

Provision details

3.3.1 [PI]

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.

3.4 Toggle scripts. (P1) [C]

Provision details

3.4.1 [C]

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

3.5 Toggle automatic content retrieval. (P1) [NI]

Provision details

3.5.1 [NI]

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

3.6 Toggle images. (P2) [C]

Comments:

Exposed through UI
Can do IMG { display: none} (same for OBJECT but INPUT since no attribute selection in IE Mac 5.0. Also, don't want to hide image, should render alt.

Provision details

3.6.1 [C]

Allow configuration not to render image content.

4.1 Configure text scale. (P1) [C]

Comments:

We support text zoom.
We support the std OE utility

Provision details

4.1.1 [C]

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.

4.1.2 [C]

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.

4.1.3 [C]

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 Configure font family. (P1) [C]

Comments:

More granularity than required by UAAG 1.0.
We support the std OE utility

Provision details

4.2.1 [C]

Allow global configuration of the font family of all visually rendered text content.

4.2.2 [C]

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.

4.2.3 [C]

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 Configure text colors. (P1) [C]

Comments:

Yes in Web Content menu
We support the std OE picker

Provision details

4.3.1 [C]

Allow global configuration of the foreground and background color of all visually rendered text content.

4.3.2 [C]

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.

4.3.3 [C]

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.

4.4 Slow multimedia. (P1) [NA]

Provision details

4.4.1 [NA]

Allow the user to slow the presentation rate of rendered audio and animation content (including video and animated images).

4.4.2 [NA]

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.

4.4.3 [NA]

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.

4.4.4 [NA]

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.

4.5 Start, stop, pause, and navigate multimedia. (P1) [NA]

Provision details

4.5.1 [NA]

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.

4.5.2 [NA]

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.

4.6 Do not obscure captions. (P1) [NA]

Provision details

4.6.1 [NA]

For graphical viewports, allow configuration so that captions synchronized with a visual track in content are not obscured by it.

4.7 Global volume control. (P1) [C]

Provision details

4.7.1 [C]

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.

4.7.2 [C]

As part of satisfying provision one of this checkpoint, allow the user to choose zero volume (i.e., silent).

4.8 Independent volume control. (P1) [NA]

Provision details

4.8.1 [NA]

Allow independent control of the volumes of rendered audio content synchronized to play simultaneously.

4.9 Configure synthesized speech rate. (P1) [NA]

Provision details

4.9.1 [NA]

Allow configuration of the synthesized speech rate, according to the full range offered by the speech synthesizer.

4.10 Configure synthesized speech volume. (P1) [NA]

Provision details

4.10.1 [NA]

Allow control of the synthesized speech volume, independent of other sources of audio.

4.11 Configure synthesized speech characteristics. (P1) [NA]

Provision details

4.11.1 [NA]

Allow configuration of synthesized speech characteristics according to the full range of values offered by the speech synthesizer.

4.12 Specific synthesized speech characteristics. (P2) [NA]

Provision details

4.12.1 [NA]

Allow configuration of synthesized speech pitch. Pitch refers to the average frequency of the speaking voice.

4.12.2 [NA]

Allow configuration of synthesized speech pitch range. Pitch range specifies a variation in average frequency.

4.12.3 [NA]

Allow configuration of synthesized speech stress. Stress refers to the height of "local peaks" in the intonation contour of the voice.

4.12.4 [NA]

Allow configuration of synthesized speech richness. Richness refers to the richness or brightness of the voice.

4.13 Configure synthesized speech features. (P2) [NA]

Provision details

4.13.1 [NA]

Provide support for user-defined extensions to the synthesized speech dictionary.

4.13.2 [NA]

Provide support for spell-out: where text is spelled one character at a time, or according to language-dependent pronunciation rules.

4.13.3 [NA]

Allow at least two configurations for speaking numerals: one where numerals are spoken as individual digits, and one where full numbers are spoken.

4.13.4 [NA]

Allow at least two configurations for speaking punctuation: one where punctuation is spoken literally, and one where punctuation is rendered as natural pauses.

4.14 Choose style sheets. (P1) [C]

Comments:

NI in vanilla browser, but included through the "ChooseStyleSheet" Favelet http://favelets.com/
You can choose from several user style sheets (not just one default location)
(Turn of "Show style sheets")

Provision details

4.14.1 [C]

Allow the user to choose from and apply alternative author style sheets (such as linked style sheets).

4.14.2 [C]

Allow the user to choose from and apply at least one user style sheet.

4.14.3 [C]

Allow the user to turn off (i.e., ignore) author and user style sheets.

5.1 No automatic content focus change. (P2) [PI]

Comments:

Javascript off will prevent window.open, and focus follows window.open

Provision details

5.1.1 [PI]

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.

5.2 Keep viewport on top. (P2) [NI]

Provision details

5.2.1 [NI]

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.

5.3 Manual viewport open only. (P2) [PI]

Comments:

Javascript off will prevent window.open

Provision details

5.3.1 [PI]

Allow configuration so that viewports only open on explicit user request.

5.3.2 [PI]

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

5.3.3 [PI]

Allow the user to close viewports.

5.4 Selection and focus in viewport. (P2) [C]

Provision details

5.4.1 [C]

Ensure that when a viewport's selection or content focus changes, it is at least partially in the viewport after the change.

5.5 Confirm form submission. (P2) [PI]

Comments:

Only insecure forms

Provision details

5.5.1 [PI]

Allow configuration to prompt the user to confirm (or cancel) any form submission.

6.1 Programmatic access to HTML/XML infoset. (P1) [PI]

Provision details

6.1.1 [PI]

Provide programmatic read access to XML content by making available all of the information items defined by the W3C XML Infoset [INFOSET].

6.1.2 [PI]

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

6.1.3 [PI]

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.

6.2 DOM access to HTML/XML content. (P1) [PI]

Comments:

Implement 80% of DOM 1 core; Mapping to DOM 2 core unknown.
For write: Security problems

Provision details

6.2.1 [PI]

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.

6.2.2 [PI]

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.

6.3 Programmatic access to non-HTML/XML content. (P1) [NA]

Provision details

6.3.1 [NA]

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.

6.3.2 [NA]

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.

6.4 Programmatic access to information about rendered content. (P1) [NR]

Provision details

6.4.1 [NR]

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.

6.4.2 [NR]

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.

6.4.3 [NR]

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.

6.5 Programmatic operation of user agent user interface. (P1) [PI]

Comments:

P: Some possible through AppleScript 3.
VG: AppleScript is publicly documented in AppleScript Dictionary (available from script editor)

Provision details

6.5.1 [PI]

Provide programmatic read access to user agent user interface controls, selection, content focus, and user interface focus.

6.5.2 [PI]

Provide programmatic write access for those user agent user interface controls that the user can modify through the user interface.

6.5.3 [PI]

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.

6.6 Programmatic notification of changes. (P1) [PI]

Comments:

C: for content focus.
NI: for UI focus
C: For content mutation events - InnerHTML/OuterHTML; publicly document on MSDN; API is the IE DHTML.
NI: for UI state changes

Provision details

6.6.1 [PI]

Provide programmatic notification of changes to content, user agent user interface controls, selection, content focus, and user interface focus.

6.6.2 [PI]

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.

6.7 Conventional keyboard APIs. (P1) [C]

Provision details

6.7.1 [C]

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

6.8 API character encodings. (P1) [C]

Comments:

UTF-8 and UTF-16 supported (but DOM implementation not complete).

Provision details

6.8.1 [C]

For an API implemented to satisfy requirements of this document, support the character encodings required for that API.

6.9 DOM access to CSS style sheets. (P2) [PI]

Comments:

We implement the pieces people need to use": access to styles, properties, and values.

Provision details

6.9.1 [PI]

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.

6.9.2 [PI]

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.

6.10 Timely exchanges through APIs. (P2) [AC]

Comments:

OS is not multiprocess. OS Network support often hangs for long periods of time due to TCP/IP timeout protocols.

Provision details

6.10.1 [AC]

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

7.1 Respect focus and selection conventions. (P1) [C]

Comments:

We do more than sys conventions. We implement CSS access to focus.

Provision details

7.1.1 [C]

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

7.2 Respect input configuration conventions. (P1) [C]

Provision details

7.2.1 [C]

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

7.3 Respect operating environment conventions. (P2) [PI]

Comments:

Operating environment conventions. http://developer.apple.com/techpubs/mac/HIGuidelines/HIGuidelines-30.html
And universal access: http://developer.apple.com/techpubs/mac/HIGuidelines/HIGuidelines-40.html#MARKER-9-55

Provision details

7.3.1 [PI]

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

7.4 Provide input configuration indications. (P2) [C]

Comments:

CMD-keys are in menu items
Keyboard bindings are documented in help

Provision details

7.4.1 [C]

Follow operating environment conventions to indicate the input configuration.

8.1 Implement accessibility features. (P1) [PI]

Comments:

HTML4: P
CSS1: G
CSS2: P
PNG: NR

Provision details

8.1.1 [PI]

Implement the accessibility features of specifications (markup languages, style sheet languages, metadata languages, graphics formats, etc.).

8.2 Conform to specifications. (P2) [AC]

Comments:

HTML4: VG doesn't implement TABINDEX, LONGDESC and other accessibility features
CSS1: C
PNG: C

Provision details

8.2.1 [AC]

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

9.1 Provide content focus. (P1) [C]

Provision details

9.1.1 [C]

Provide at least one content focus for each viewport (including frames) where enabled elements are part of the rendered content.

9.1.2 [C]

Allow the user to make the content focus of each viewport the current focus.

9.2 Provide user interface focus. (P1) [C]

Provision details

9.2.1 [C]

Provide a user interface focus.

9.3 Move content focus. (P1) [AC]

Comments:

VG: Can't get to event handler elements. But does allow tabbing to links, form controls, tabindex 2. NI 3. C

Provision details

9.3.1 [AC]

Allow the user to move the content focus to any enabled element in the viewport.

9.3.2 [AC]

Allow configuration so that the content focus of a viewport only changes on explicit user request.

9.3.3 [AC]

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.

9.4 Restore viewport state history. (P1) [AC]

Provision details

9.4.1 [AC]

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.

9.4.2 [AC]

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.

9.5 No events on focus change. (P2) [PI]

Comments:

Can be done by turning off javascript support. But: Not documented, toggle not keyboard accessible.

Provision details

9.5.1 [PI]

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.

9.6 Show event handlers. (P2) [NI]

Provision details

9.6.1 [NI]

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.

9.7 Move content focus in reverse. (P2) [AC]

Comments:

Allows backwards navigation. Does not allow navigation to elements with event handlers.

Provision details

9.7.1 [AC]

Extend the functionality required in provision three of checkpoint 9.3 by allowing the same sequential navigation in reverse document order.

9.7.2 [AC]

As part of satisfying provision one of this checkpoint, the user agent must not include disabled elements in the navigation order.

9.8 Provide text search. (P2) [C]

Provision details

9.8.1 [C]

Allow the user to search within rendered text content for a sequence of characters from the document character set.

9.8.2 [C]

Allow the user to start a forward search (in document order) from any selected or focused location in content.

9.8.3 [C]

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.

9.8.4 [C]

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

9.8.5 [C]

Provide a case-insensitive search option for text in scripts (i.e., writing systems) where case is significant.

9.9 Allow structured navigation. (P2) [NI]

Provision details

9.9.1 [NI]

Allow the user to navigate efficiently to and among important structural elements in rendered content.

9.9.2 [NI]

As part of satisfying provision one of this checkpoint, allow forward and backward sequential navigation.

9.10 Configure important elements. (P3) [NI]

Provision details

9.10.1 [NI]

Allow configuration of the set of important elements and attributes identified for checkpoints 9.9 and 10.4.

9.10.2 [NI]

As part of satisfying provision one of this checkpoint, allow the user to include and exclude element types in the set.

10.1 Associate table cells and headers. (P1) [PI]

Comments:

Rendered according to HTML 4 table model.v
CAPTION element rendered
Summary attribute not rendered
abbr not rendered
THEAD and TFOOT can't be fixed with 'position: fixed' in CSS

Provision details

10.1.1 [PI]

For graphical user agents that render tables, for each table cell, allow the user to view associated header information.

10.2 Highlight selection, content focus, enabled elements, visited links. (P1) [C]

Comments:

Default UA focus has focus ring.
Done at OS level 4.
User style sheets. For text selection no good way to do this for selection.
follows OS defaults
Content focus: C
(uses outline) Enabled elements: C
Hyperlinks are underlined: C
Buttons have a border: C
Text fields have bevelled border: C
Select popups, lists have borders: C
Recently visited links: C (inherits from OS settings).

Provision details

10.2.1 [C]

Allow global configuration to highlight the following four classes of information in each viewport: the selection, content focus, enabled elements, and recently visited links.

10.2.2 [C]

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.3 [C]

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.

10.2.4 [C]

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.

10.3 Single highlight configuration. (P2) [NR]

Provision details

10.3.1 [NR]

Extend the functionality required by provision two of checkpoint 10.2 by allowing configuration through a single setting.

10.4 Provide outline view. (P2) [NI]

Provision details

10.4.1 [NI]

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.5 Provide link information. (P3) [PI]

Comments:

Content: C
Title: C, when hover
Internal: NI
Recent: C
Meta (Type/size/lang): NI

Provision details

10.5.1 [PI]

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.

10.6 Highlight current viewport. (P1) [C]

Comments:

C: Use standard OS convention of frontmost window
NI: Don't show which frame of frameset has focus.

Provision details

10.6.1 [C]

Highlight the viewport with the current focus (including any frame that takes current focus).

10.6.2 [C]

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

10.6.3 [C]

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.

10.7 Indicate viewport position. (P3) [PI]

Provision details

10.7.1 [PI]

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

11.1 Current user input configuration. (P1) [AC]

Comments:

We list keyboard shortcuts in user menus. Most keyboard shortcuts are indicated in menus.
Documented as well in help page. There are a few shortcuts that are not listed there.
We don't allow user override of default bindings.

Provision details

11.1.1 [AC]

Provide information to the user about current user preferences for input configurations.

11.2 Current author input configuration. (P2) [NI]

Provision details

11.2.1 [NI]

Provide a centralized view of the current author-specified input configuration.

11.3 Allow override of bindings. (P2) [NI]

Provision details

11.3.1 [NI]

Allow the user to override any binding that is part of the user agent default input configuration.

11.4 Single-key access. (P2) [NI]

Provision details

11.4.1 [NI]

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.

11.4.2 [NI]

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.

11.5 Default input configuration. (P2) [C]

Comments:

C: move focus: next/previous links, form controls [tab/shift-tab]
C: activate: Enter/return
C: search: Cmd-F C: search again: Cmd-G
C: text size changes: Cmd-[+|-] (zoom)
N/A: Volume
N/A: Audio and animations
C: next history/Cmd-rightbracket, Cmd-leftbracket
C: enter URI: Cmd-l
C: add to favs: Cmd-d
C: view favs: Cmd-2 or Cmd-j (depending on versoin)
C: stop loading: Cmd-.
C: Reload: Cmd-r or F5
NA: On Mac, use the windowshade button (hide/show). This is available at OS but not implemented by Mac IE.
C: F/R one viewport: PageUp/Down
C: Next/Previous line: arrows

Provision details

11.5.1 [C]

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

11.5.2 [C]

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.

11.6 User profiles. (P2) [C]

Comments:

One user profile supported

Provision details

11.6.1 [C]

For the configuration requirements of this document, allow the user to save user preferences in at least one user profile.

11.6.2 [C]

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

11.7 Tool bar configuration. (P3) [C]

Comments:

Done through drag and drop GUI.

Provision details

11.7.1 [C]

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.

11.7.2 [C]

Offer a predefined set of controls that may be added to or removed from tool bars.

11.7.3 [C]

Allow the user to restore the default tool bar configuration.

12.1 Provide accessible documentation. (P1) [NI]

Provision details

12.1.1 [NI]

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