This wiki has been archived and is now read-only.

UseCase Directory

From Digital Publishing Interest Group
Jump to: navigation, search

Note: This is a dated set of use cases. Please see Portable Web Publications Use Cases and Requirements for the latest version of use cases. This page is the TOC of the use case collection. All uses cases added are linked to from this page.

If you are about to add a new use case, start by creating a new page, and then clone the template as a starting point.

Use cases that are in need of further analysis and/or expert input are marked below with a INPUT NEEDED suffix. If you are an expert in the area, you should help us out!

Styling and Layout





Adaptive Layout

Device Adaption


User Adaption


Domain-Specific Content Types









Content & Markup

Structural Semantics



Accessibility and Personalization

WCAG 2.0 & Education Environment / Educational Publishing

Pre-School through Middle School

  • Captions & Early Readers
  • When students are too young to judge how much additional time they might need (or the activity is too new/innovative)

Specialized Subject Areas (e.g. Chemistry, Grammar, Poetry)

(Can include providing authors with ability to polish pronunciations, pauses and stresses, as well as solutions such as subject-specific markup.)

  • When implementations are tested, they might be tested with simpler content than what publishers need to use. Publishers should be able to submit samples to a test suite for verifying subject-specific readiness.

Allowing Versions

(versions & third-party, second-party or first-party patches.)

  • Allow Different Math Pronunciations
  • Facilitate Post Production Crowdsourcing of SVG Descriptions
  • A publisher uses the latest WAI-ARIA and good semantics to make an interactive widget accessible on many assistive technologies, but there's a catch 22 as a key technology has a bug. (For example, VoiceOver doesn't handle merged table cells well currently.) Having identified the issue, a publisher wants to easily send a different version to the problematic assistive technology.
  • A 3rd party wants to provide improve the accessibility of an interactive widget
  • In an environment where accessibility has been customized, a publisher's customer support technical team needs to quickly identify the version in use and get detail on the reasons for the version, where it was tested, etc.
  • In an environment where content is generated through crowdsourcing, a graduate student (for example) who uses assistive technology needs clear identification of the source of the content they receive and to be able to allow/disallow content depending on the source, at their own discretion.

General Accessibility Use Cases (including Math)


User Descriptions



Social Reading and Annotations

Use Cases Targeting Full Publication

Use Cases Targeting Specific Segments

Advanced Use Cases

Annotation Packages

Annotation Publication

Other Use Cases

Packaging and Distribution

Publishing Workflow Effectiveness



Pagination/DOM interaction