Proposed: Definition of Relative Time Units

from email

Relative time units define time intervals for media navigation which may be preset, user configurable, and/or automatically calculated based upon media duration. When interacting with a time-based media presentation, a user may find it beneficial to move forward or backward via a time interval relative to their current position. For example, a user may find a concept unclear in a video lecture and elect to skip back 30 seconds from the current position to review what had been described.

Summary

Details

Proposed new 1.1.3

from email

1.1.3 Time-Based Media Alternatives: The user can configure any or all of the following for visually-rendered time-based media alternatives (e.g. captions, sign language video):

(a) Scale: the media alternative as a viewport that may occupy any rectangular region within the user agent's viewport.

(b) Position: the media alternative as a viewport so that it does not obscure the primary time-based media or its controls.

(c) Adjust Text: within Alternative media tracks in conformance with 1.4.1.

The user can scale and position alternative visual media tracks independent of the base video or audio player presentation. (Level AAA)

Intent of Success Criterion 1.1.3 :

Users who require or can benefit from alternative media tracks in video or audio may not find the default or authored position and size of those tracks to be usable. Enabling the user to move and scale any displayed alternate media tracks (e.g. captions) allows for the displayed content to be positioned and sized to meet the needs of the user.

Examples of Success Criterion 1.1.3 :

Justin has low vision and works in a noisy environment that makes it difficult to listen to instructional videos. When he enlarges the text of the captions to a viewable size, they block most of the video image. Justin selects an option that displays the caption track in a separate window, which he positions below the video image so the captions do not block the video image.

Jaime is deaf and is taking courses from on online university. She prefers to utilize ASL if it is available for online media, and a current course she is taking offers both captions and a signing avatar for the recorded lectures. Selecting the signing track, she finds the default size of the avatar window too small, making it difficult to follow. The avatar also overlays an important part of the lecture video content. Jaime drags the avatar out of the video player and enlarges it, so that both are equally sized and side by side.

Summary

Details

from email

Replacing: 4.1.1 Platform Accessibility Architecture: The user agent supports a platform accessibility architecture relevant to the operating environment. (Level A)

...with...

4.1.1 Platform Accessibility Services: If the user agent contains non-web-based user interfaces, then those user interfaces implement communication with platform accessibility services. [ed. On Monday AUWG may change the wording slightly to: " expose accessibility information through"]
Note: The (optional) explanation of conformance claim results should record the platform accessibility service(s) that were implemented."

Intent:

The intent of this success criterion is to ensure that user agent user interfaces that are not web applications are more accessible to users with disabilities who use assistive technologies that communicate with software via platform accessibility services. The requirement is stated generally because the specifics of what constitutes a platform accessibility service will differ on each platform.

The note regarding documenting the platform accessibility service(s) that were implemented in the conformance claim should encourage developers to implement services that are well supported by assistive technologies.

Examples:

UNCHANGED

Related Resources:

The following is a non-exhaustive list of documents related to communication with platform accessibility services for various platforms:

Desktop OS

GNOME Desktop on Linux: GNOME Accessibility Developers Guide
KDE Desktop on Linux: Developer's Information
Mac OS: Accessibility Overview
Microsoft Windows: Accessibility Overview
Mobile OS
Android: Example from Android Developer Reference
BlackBerry: BlackBerry Accessibility
iPhone OS: Accessibility Programming Guide for iPhone OS
Cross-OS environments
Java SE: Java SE Desktop Accessibility

Summary

(2 responses didn't contain an answer to this question)

Details

from email

5.x.x Enable Reporting of User Agent Accessibility Faults: Users can report faults in accessibility support within the user agent using a built-in facility for that purpose. (Level AAA)

Intent of Success Criterion 5.X :

Users of assistive technology such as screen readers may find that their assistive technology may not be compatible fully with their Web browser, or that the browser may not accessibly render content that has been authored in compliance with WCAG, resulting in a loss of information or convenience. In these instances, users with disabilities will benefit from being able to easily file a report with the user agent vendor to inform them of the incompatibility, similar to the feedback mechanisms currently available in some user agents to file bug reports.

Examples of Success Criterion 5.X :

Alice is a visually impaired college student who frequently uses a refreshable Braille display with her Web browser on her laptop. Usually, she does not encounter issues with displaying text from her browser on her refreshable braille display. However, occasionally she experiences difficulty with elements such as drop-down boxes or complex menus, where the text is only partially rendered on the braille display. Alice notices this incompatibility and navigates to the feedback section of her browser. After providing some basic information (such as AT device and computer hardware used), Alice is able to describe the problem she encountered and submit the report to the browser vendor.

Fred has low vision and uses screen magnification software to enlarge displayed information and alter color contrast. While reading content on a Web site in compliance with WCAG, Fred discovers that the scroll bars are not visible and he cannot scroll further down the page. Unable to read the information he needs, Fred selects the Feedback option from his browser's Tools menu, and is presented with a dialog where he can select which information to transmit to the browser vendor. He selects to include the current URL of the page he is trying to view, system information including OS and screen magnifier version, and enters a description of the problem he is having. Though not required, Fred chooses to provide his email address so that the vendor may contact him for further details or to provide a workaround.

Summary

(2 responses didn't contain an answer to this question)

Details