WebTV Use Cases

From HTML WG Wiki
Jump to: navigation, search

Ref ACTION 251

1. "Use Case One – Tablet Joins Home Network"

Extends Use Case One – Tablet Joins Home Network

This use case requires the user to interact with a web-based interface on the "tablet" device (which could be any connected device on the network). This interface MUST meet the applicable Success Criteria defined in the Web Content Accessibility Guidelines 2.0 WCAG 2.0 and the User Agent Accessibility Guidelines 2.0 UAAG 2.0.

The "subscriber" may wish to consume alternative content like Audio Description, subtitles or captions, on only one of the devices, synchronized with all other devices.

Particularly relevant sections of WCAG 2.0 include:

  • Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
  • Guideline 1.2 Time-based Media: Provide alternatives for time-based media.
  • Guideline 2.1 Keyboard Accessible: Make all functionality available from a keyboard.
  • Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.

2. "Use Case Two – TV Triggers 2nd Screen"

Extends Use Case Two – TV Triggers 2nd Screen

  • The "overlay" as well as the associated HTML5 application MUST meet the applicable Success Criteria defined in the Web Content Accessibility Guidelines 2.0 WCAG 2.0 and the User Agent Accessibility Guidelines 2.0 UAAG 2.0.
  • The viewer MUST be able to access all of the content in the overlay and all controls required to interact with, activate or dismiss the overlay.
  • An interface should be provided that allows the viewer to add the contents of the overlay to a queue so that they may consume it at a later time.
  • An option to dismiss/ignore all overlays or add all overlays to a queue should be a globally configurable option.

3. "Use Case Three – Tablet EPG"

Extends Use Case Three – Tablet EPG

This use case requires the user to interact with a web-based interface on the "tablet" device (the Electronic Programming Guide). This interface MUST meet the applicable Success Criteria defined in the Web Content Accessibility Guidelines 2.0 WCAG 2.0 and the User Agent Accessibility Guidelines 2.0 UAAG 2.0.

  • The viewer MUST be able to browse list of recommended programming, including relevant metadata, such as what types of alternative media is available for each program.
  • All controls to browse, mark programming for recording, or save it to a queue to watch later MUST be accessible to the user on all devices.
  • The viewer should be able to launch the programming on both devices so alternative media could be consumed on one device only (consuming alternative content like audio descriptions on the tablet with attached headphones, which allows the viewer not to distract other viewers with alternative tracks not relevant to them.)

4. "Use Case Four – Content Sharing"

Extends Use Case Four – Content Sharing

As above, the user will be required to interact with a web-based interface on the "tablet" device. This interface MUST meet the applicable Success Criteria defined in the Web Content Accessibility Guidelines 2.0 WCAG 2.0 and the User Agent Accessibility Guidelines 2.0 UAAG 2.0.

The ability to share content using connected 3rd party services will most likely require the user to authenticate with these services. Any interface required to do so, or to share content, MUST be accessible.

All metadata, including which alternative media tracks are available should be included with the shared content.

5. "Use Case Five – Content Search"

Extends Use Case Five – Content Search

This use case requires the user to interact with a web-based interface on the "tablet" device. This interface MUST meet the applicable Success Criteria defined in the Web Content Accessibility Guidelines 2.0 WCAG 2.0 and the User Agent Accessibility Guidelines 2.0 UAAG 2.0, including the search interface, any results of that search and the ability to interact or launch search results.

6. "Use Case Six – Tuner Control thru Web Application"

Extends Use Case Six – Tuner Control thru Web Application

  • The web application and any Electronic Programming guide MUST meet the applicable Success Criteria defined in the Web Content Accessibility Guidelines 2.0 WCAG 2.0 and the User Agent Accessibility Guidelines 2.0 UAAG 2.0.
  • The metadata included in the EPG should also include information on types of alternative content that are available for the program.
  • The viewer should also be able to filter search results based on this metadata e.g. only show programming with alternative description tracks available.

7. "Use Case Seven – Channel Bounded Applications"

Extends Use Case Seven – Channel Bounded Applications

Once again, this use case requires the user to interact with a web-based interface on the "tablet" device. This interface MUST meet the applicable Success Criteria defined in the Web Content Accessibility Guidelines 2.0 WCAG 2.0 and the User Agent Accessibility Guidelines 2.0 UAAG 2.0.

  • Channel bound applications should be presented in an accessible format and MUST be able to be dismissed by the user.
  • Viewer should have the ability to bookmark or queue ancillary information and access it later.
  • The existence/availability of channel bound applications should be discoverable, but non-intrusive.
  • All channel bound applications should be globally configurable (dismiss/ignore all, save for later). This is to avoid being a distraction to users, e.g. using a screen reader.