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

Accessibility and Personalization

From Digital Publishing Interest Group
Jump to: navigation, search

Personalization & Accessibility

Use case
The age of personalized content is coming and to make it effective, there must be an extensible format for tracking personalization data. Some items will be proprietary ideas and others will be standard basic human needs and preferences. Much work has already taken place to explore this and specifications exist outside the W3C. This use case is for the specification writers in the ecosystem, a place to collect what has been done and see what gaps remain and how/whether to integrate W3C specs with the specifications that currently exist. Ideally, accessibility data would sit along side any standard personalization data creating a continuum that doesn't rely on specific disability categories, except where/if needed, such as permissions for extended time on standardized tests.
Requirement(s)
  • Establish consistency across publication types (Right now, APIP for testing is speeding ahead in adoption/acceptance.)
  • Securely/Privately record data about the user
  • Standardize terminology so that accommodations or personalization are predictable/reliable
  • Space in the format for proprietary extensions (extensible)
  • Respect existing work (much has been done at IMS and elsewhere on this)
  • Potentially make it easy (to automatic) for W3C technologies to respond to existing (or new) meta data standards
Stakeholder(s)
ENTIRE PUBLISHING ECOSYSTEM
Ranking
TBD
Relations/dependencies
To be added once all of the user examples have been added.
Relevant W3C group(s)/specification(s)
External relevant group(s)/specification(s)
Comments
Submitted by
Suzanne Taylor
Status
NEW