- Important note: This Wiki page is edited by participants of the User Agent Accessibility Guidelines working group (UAWG). It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

Overview of Testing for UAAG

From WAI UA Wiki
Jump to: navigation, search

Guidelines:

UAAG 2.0 Guidelines

NOTE: These tests apply to browsers and media players - both embedded and software players.

PRINCIPLE 1: Perceivable

Guideline 1.1: Alternative content

These success criteria all involve preference settings - probably self-describing

Guideline 1.2: Missing content

These success criteria all involve preference settings - probably self-describing

Guideline 1.3: Highlighting

These success criteria all involve preference settings - probably self-describing

Guideline 1.4: Text configuration

These success criteria all involve preference settings - probably self-describing

Guideline 1.5: Volume configuration

Controlling the volume of individual audio tracks - ???

Guideline 1.6: Synthesized speech configuration

Controls for speech characteristics (rate, volume, pitch, range) and features such as a user defined dictionary, spell-out, options for speaking numbers and punctuation. - probably self-describing

Guideline 1.7: Style sheets configuration

Features to select, apply or turn off author or user supplied stylesheets - probably self-describing

Guideline 1.8: Viewports

  • Self-Described: customizing the look of the viewport highlighting
  • Semi-Automated or Automated: when the focus or selection is changed, the viewport content moves so that the focus is at least partially in view.
  • Semi-Automated or Automated: the viewport can be resized, overriding author intent
  •  ??? : provides scrollbars for container overflow, overriding author.
  • Automated: back button restores previous input focus or selection
  •  ???: user can close any top level window
  • Self-Described: preference settings for "open on request" ,"do not take focus", "same ui"
  • probably Self-Described : the user can determine the viewport position in the full rendered content

Guideline 1.9: Focus

Guideline 1.10: Source views

  • Self-Described: provide view of text source code
  • Self-Described: provide outline view of content using structural labels
  • Self-Described: preference/feature for configuring "important" elements for navigation (headings, tables, bookmarks, etc)

Guideline 1.11: Links

  • tbd

PRINCIPLE 2. Operable

Guideline 2.1: Keyboard access

2.1.1 Everything can be operated by keyboard

  • WCAG tests for the content
  • Automated??? for the user interface

2.1.2 Specify preferred keystrokes

  • Self-Described: preference/feature

2.1.3 No keyboard trap

  • Self-Described: feature identification (3 ways to move focus out of trap)

2.1.4 Separate Selection from Activation

  • Self-Described: preference/feature

2.1.5 Standard Text Area Navigation Conventions

Guideline 2.2: Event handlers

Guideline 2.3: Time-independence

Guideline 2.4: Flashing

Guideline 2.5: Preference settings

Guideline 2.6: Search.

Guideline 2.7: Structured navigation.

Guideline 2.8: Toolbar configuration.

Guideline 2.9: Media

PRINCIPLE 3: Understandable

Guideline 3.1: Unnecessary messages. Guideline 3.2: Mistakes. Guideline 3.3: Documentation Guideline 3.4: Predictable

PRINCIPLE 4. Programmatic access

Guideline 4.1: Programmatic access

PRINCIPLE 5. Specifications and conventions

Guideline 5.1: Desktop apps Guideline 5.2: Web & web apps Guideline 5.3: Accessibility features Guideline 5.4: Follow specifications