The Digital Publishing Accessibility API Mappings (DPub-AAM) defines how user agents map the Digital Publishing WAI-ARIA Module [[!dpub-aria-1.0]] markup to platform accessibility APIs. It is intended for user agent developers responsible for accessibility in their user agent so that they can support the accessibility content produced for digital publishing.

The implementation of this specification in user agents enables authors to produce more accessible digital publications, by conveying structural book constructs used by the digital publishing industry to assistive technologies. It does this by extending the Core Accessibility API Mappings 1.1 (CORE-AAM) [[!CORE-AAM]] and the Accessible Name and Description: Computation and API Mappings 1.1 (ACCNAME-AAM) [[!ACCNAME-AAM]] specifications for user agents. It provides Accessibility API Mapping guidance for the roles defined in the Digital Publish WAI-ARIA Module.

The DPub-AAM is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

This is a Candidate Recommendation of Digital Publishing Accessibility API Mappings 1.0 by the Digital Publishing ARIA Taskforce, a joint task force of the Accessible Rich Internet Applications Working Group and the Digital Publishing Interest Group. This is a call for implementations; the Accessible Rich Internet Applications Working Group requests that initial implementations be submitted by 30 June 2017. The Working Group targets 30 June 2017 to complete the testing process and produce the implementation report. A history of changes to Digital Publishing Accessibility API Mappings 1.0 is available in the appendix.

Exit Criteria: The Accessible Rich Internet Applications Working Group intends to exit the Candidate Recommendation stage and submit this document for consideration as a W3C Proposed Recommendation after documenting interoperable implementability of each feature. The expectations and procedure for this are listed in the Exit Criteria appendix.

Comments: The Accessible Rich Internet Applications Working Group primarily seeks feedback relation to implementation of Digital Publishing Accessibility API Mappings, but feedback on any aspect of the specification is accepted. To comment, file an issue in the W3C ARIA GitHub repository. If this is not feasible, send email to public-dpub-aria-comments@w3.org (comment archive). Comments are requested by 30 June 2017. In-progress updates to the document may be viewed in the publicly visible editors' draft.

Introduction

This specification indicates whether a section is normative or informative and the classification applies to the entire section. A statement "This section is normative" or "This section is informative" applies to all sub-sections of that section.

Normative sections provide requirements that user agents must follow for an implementation to conform to this specification. The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in Keywords for use in RFCs to indicate requirement levels [[!RFC2119]]. RFC-2119 keywords are formatted in uppercase and contained in a strong element with class="rfc2119". When the keywords shown above are used, but do not share this format, they do not convey formal information in the RFC 2119 sense, and are merely explanatory, i.e., informative. As much as possible, such usages are avoided in this specification.

Informative sections provide information useful to understanding the specification. Such sections may contain examples of recommended practice, but it is not required to follow such recommendations in order to conform to this specification.

Important Terms

Placeholder for glossary

Supporting Keyboard Navigation

Enabling keyboard navigation in web applications is a necessary step toward making accessible web applications possible. Conforming user agents MUST conform to Supporting Keyboard Navigation requirements in [[!CORE-AAM]].

Mapping WAI-ARIA to Accessibility APIs

General rules for exposing WAI-ARIA semantics

This section MUST conform to General rules for exposing WAI-ARIA semantics in [[!CORE-AAM]].

Conflicts between native markup semantics and WAI-ARIA

User agents MUST conform to Conflicts between native markup semantics and WAI-ARIA in [[!CORE-AAM]].

Exposing attributes that do not directly map to accessibility API properties

User agents MUST conform to Exposing attributes that do not directly map to accessibility API properties in [[!CORE-AAM]].

Role mapping

Platform accessibility APIs traditionally have had a finite set of predefined roles that are expected by assistive technologies on that platform and only one or two roles may be exposed. In contrast, WAI-ARIA allows multiple roles to be specified as an ordered set of space-separated valid role tokens. The additional roles are fallback roles similar to the concept of specifying multiple fonts in case the first choice font type is not supported.

General Rules

User agents MUST conform to the Role Mapping General Rules accessibility API computational requirements in [[!CORE-AAM]].

Role Mapping Table

Translators: For label text associated with the following table and its toggle buttons, see the mappingTableLabels object in the <head> section of this document.

This section defines how WAI-ARIA digital publishing roles map to platform accessibility APIs. Elements having roles with a prefix value of doc-, that are not listed in this role mapping table, have no normative mappings.

There are a number of roles mappings that are localized. The group needs to look into localizing for non-English languages.

Table describing mapping of WAI-ARIA roles to accessibility APIs.
WAI-ARIA Role MSAA + IAccessible2 Role + Other IAccessible2 Features UIA Control Type + Other Features ATK/AT-SPI Role AXAPI
doc-abstract Expose IAccessible2:
  • IA2_ROLE_SECTION
  • Object attribute xml-roles:doc-abstract.
  • Control Type is Text
  • Localized Control Type is 'abstract'

Expose ROLE_SECTION and object attribute xml-roles:doc-abstract.

AXRole: AXGroup
AXSubrole: AXApplicationGroup
AXRoleDescription: 'group'
doc-acknowledgments Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-acknowledgments.
  • Control Type is Text
  • Localized Control Type is 'acknowledgements'
  • Landmark Type is Custom
  • Localized Landmark Type is 'acknowledgements'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-acknowledgments.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-afterword Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-afterword.
  • Control Type is Text
  • Localized Control Type is 'afterword'
  • Landmark Type is Custom
  • Localized Landmark Type is 'afterword'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-afterword.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-appendix Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-appendix.
  • Control Type is Text
  • Localized Control Type is 'appendix'
  • Landmark Type is Custom
  • Localized Landmark Type is 'appendix'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-appendix.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-biblioentry Expose

ROLE_SYSTEM_LISTITEM + STATE_SYSTEM_READONLY

IAccessible2:

Object attribute xml-roles:doc-biblioentry.
  • Control Type is Text
  • Localized Control Type is 'biblioentry'

Expose ROLE_LIST_ITEM and object attribute xml-roles:doc-bilioentry.

 AXRole: AXGroup
AXSubrole: <nil>
AXRoleDescription: 'group'
doc-bibliography Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-bibliography.
  • Control Type is Text
  • Localized Control Type is 'bibliography'
  • Landmark Type is Custom
  • Localized Landmark Type is 'biblography'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-bibliography.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-biblioref Expose
  • ROLE_SYSTEM_LINK + STATE_LINKED
  • STATE_LINKED on all descendants

IAccessible2:

  • Object attribute xml-roles:doc-biblioref.
  • AccessibleHypertext interface
  • Control Type is Text
  • Localized Control Type is 'biblioref'

Expose ROLE_LINK and object attribute xml-roles:doc-biblioref.

AXRole: AXLink
AXSubrole: <nil>
AXRoleDescription: 'link'
doc-chapter Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-chapter.
  • Control Type is Text
  • Localized Control Type is 'chapter'
  • Landmark Type is Custom
  • Localized Landmark Type is 'chapter'

Expose ROLE_LANDMARK and object attribute xml-roles:chapter.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-colophon Expose

IA2_ROLE_SECTION

IAccessible2: Object attribute xml-roles:doc-colophon.

  • Control Type is Text
  • Localized Control Type is 'colophon'

Expose ROLE_SECTION and object attribute xml-roles:doc-colophon.

AXRole: AXGroup
AXSubrole: AXApplicationGroup
AXRoleDescription: 'group'
doc-conclusion Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-conclusion.
  • Control Type is Text
  • Localized Control Type is 'conclusion'
  • Landmark Type is Custom
  • Localized Landmark Type is 'conclusion'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-conclusion.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-cover Expose

ROLE_SYSTEM_GRAPHIC

IAccessible2: Object attribute xml-roles:doc-cover.

Control Type is Image

expose ROLE_IMAGE and object attribute xml-roles:doc-cover.

AXRole: AXImage
AXSubrole: <nil>
AXRoleDescription: 'image'
doc-credit Expose

IA2_ROLE_SECTION

IAccessible2:

Object attribute xml-roles:doc-credit
  • Control Type is Text
  • Localized Control Type is 'credit'

Expose ROLE_SECTION and object attribute xml-roles:doc-credit.

AXRole: AXGroup
AXSubrole: AXApplicationGroup
AXRoleDescription: 'group'
doc-credits Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-credits.
  • Control Type is Text
  • Localized Control Type is 'credits'
  • Landmark Type is Custom
  • Localized Landmark Type is 'credits'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-credits.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-dedication Expose

IA2_ROLE_SECTION

IAccessible2:

Object attribute xml-roles:doc-dedication
  • Control Type is Text
  • Localized Control Type is 'dedication'

Expose ROLE_SECTION and object attribute xml-roles:doc-dedication.

AXRole: AXGroup
AXSubrole: AXApplicationGroup
AXRoleDescription: 'group'
doc-endnote Expose

ROLE_SYSTEM_LISTITEM + STATE_SYSTEM_READONLY

IAccessible2:

Object attribute xml-roles:doc-endnote.
  • Control Type is Text
  • Localized Control Type is 'endnote'

Expose ROLE_LIST_ITEM and object attribute xml-roles:doc-endnote.

AXRole: AXGroup
AXSubrole: <nil>
AXRoleDescription: 'group'
doc-endnotes Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-endnotes.
  • Control Type is Text
  • Localized Control Type is 'endnotes'
  • Landmark Type is Custom
  • Localized Landmark Type is 'endnotes'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-endnotes.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-epigraph Expose

IA2_ROLE_SECTION

IAccessible2:

Object attribute xml-roles:doc-epigraph
  • Control Type is Text
  • Localized Control Type is 'epigraph'

Expose ROLE_SECTION and object attribute xml-roles:doc-epigraph.

AXRole: AXGroup
AXSubrole: AXApplicationGroup
AXRoleDescription: 'group'
doc-epilogue Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-epilogue.
  • Control Type is Text
  • Localized Control Type is 'epilogue'
  • Landmark Type is Custom
  • Localized Landmark Type is 'epilogue'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-epilogue.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-errata Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-errata
  • Control Type is Text
  • Localized Control Type is 'errata'
  • Landmark Type is Custom
  • Localized Landmark Type is 'errata'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-errata.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-example Expose

IA2_ROLE_SECTION

IAccessible2:

Object attribute xml-roles:doc-example
  • Control Type is Text
  • Localized Control Type is 'example'

Expose ROLE_SECTION and object attribute xml-roles:doc-example.

AXRole: AXGroup
AXSubrole: AXApplicationGroup
AXRoleDescription: 'group'
doc-footnote

Expose IAccessible2:

  • IA2_ROLE_FOOTNOTE
  • Object attribute: xml-roles:doc-footnote
  • Control Type is Text
  • Localized Control Type is 'footnote'

Expose ROLE_FOOTNOTE and object attribute xml-roles:doc-footnote.

AXRole: AXGroup
AXSubrole: AXApplicationGroup
AXRoleDescription: 'group'
doc-foreword Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-foreword
  • Control Type is Text
  • Localized Control Type is 'foreword'
  • Landmark Type is Custom
  • Localized Landmark Type is 'foreword'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-foreword.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-glossary Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-glossary
  • Control Type is Text
  • Localized Control Type is 'glossary'
  • Landmark Type is Custom
  • Localized Landmark Type is 'glossary'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-glossary.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-glossref Expose
  • ROLE_SYSTEM_LINK + STATE_LINKED
  • STATE_LINKED on all descendants

IAccessible2:

  • Object attribute xml-roles:doc-glossref.
  • AccessibleHypertext interface
  • Control Type is Text
  • Localized Control Type is 'glossref'

Expose ROLE_LINK and object attribute xml-roles:doc-glossref.

AXRole: AXLink
AXSubrole: <nil>
AXRoleDescription: 'link'
doc-index Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-index
  • Control Type is Text
  • Localized Control Type is 'index'
  • Landmark Type is Custom
  • Localized Landmark Type is 'index'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-index.

AXRole: AXGroup
AXSubrole: AXLandmarkNavigation
AXRoleDescription: 'navigation'
doc-introduction Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-introduction
  • Control Type is Text
  • Localized Control Type is 'introduction'
  • Landmark Type is Custom
  • Localized Landmark Type is 'introduction'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-introduction.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-noteref Expose
  • ROLE_SYSTEM_LINK + STATE_LINKED
  • STATE_LINKED on all descendants

IAccessible2:

  • Object attribute xml-roles:doc-noteref.
  • AccessibleHypertext interface
  • Control Type is Text
  • Localized Control Type is 'noteref'

Expose ROLE_LINK and object attribute xml-roles:doc-noteref.

AXRole: AXLink
AXSubrole: <nil>
AXRoleDescription: 'link'
doc-notice Expose

IA2_ROLE_NOTE

IAccessible2:

Object attribute xml-roles:doc-notice.
  • Control Type is Text
  • Localized Control Type is 'notice'

Expose ROLE_COMMENT and object attribute xml-roles:doc-notice.

 AXRole: AXGroup
AXSubrole: AXDocumentNote
AXRoleDescription: 'note'
doc-pagebreak Expose

ROLE_SYSTEM_SEPARATOR

IAccessible2:

Object attribute xml-roles:doc-pagebreak.
  • Control Type is Text
  • Localized Control Type is 'pagebreak'

Expose ROLE_SEPARATOR and object attribute xml-roles:doc-pagebreak.

AXRole: AXSplitter
AXSubrole: <nil>
AXRoleDescription: 'splitter'
doc-pagelist Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-pagelist
  • Control Type is Text
  • Localized Control Type is 'pagelist'
  • Landmark Type is Custom
  • Localized Landmark Type is 'pagelist'
 Expose

ROLE_LANDMARK and object attribute xml-roles:doc-pagelist.

AXRole: AXGroup
AXSubrole: AXLandmarkNavigation
AXRoleDescription: 'navigation'
doc-part Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-part
  • Control Type is Text
  • Localized Control Type is 'part'
  • Landmark Type is Custom
  • Localized Landmark Type is 'part'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-part.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-preface Expose IAccessible2:
  • IA2_ROLE_LANDMARKi
  • Object attribute xml-roles:doc-preface
  • Control Type is Text
  • Localized Control Type is 'preface'
  • Landmark Type is Custom
  • Localized Landmark Type is 'preface'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-pagebreak.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-prologue Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-prologue
  • Control Type is Text
  • Localized Control Type is 'prologue'
  • Landmark Type is Custom
  • Localized Landmark Type is 'prologue'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-prologue.

AXRole: AXGroup
AXSubrole: AXLandmarkRegion
AXRoleDescription: 'region'
doc-pullquote Expose IAccessible2:
  • IA2_ROLE_SECTION
  • Object attribute xml-roles:doc-pullquote
  • Control Type is Text
  • Localized Control Type is 'pullquote'

Expose ROLE_SECTION and object attribute xml-roles:doc-pullquote.

 AXRole: AXGroup
AXSubrole: AXApplicationGroup
AXRoleDescription: 'group'
doc-qna Expose

IA2_ROLE_SECTION

IAccessible2:

Object attribute xml-roles:doc-qna
  • Control Type is Text
  • Localized Control Type is 'qna'

Expose ROLE_SECTION and object attribute xml-roles:doc-qna.

AXRole: AXGroup
AXSubrole: AXApplicationGroup
AXRoleDescription: 'group'
doc-subtitle Expose IAccessible2:
  • IA2_ROLE_HEADING
  • Object attribute xml-roles:doc-subtitle
  • Control Type is Text
  • Localized Control Type is 'subtitle'

Expose ROLE_HEADING and object attribute xml-roles:doc-subtitle.

AXRole: AXHeading
AXSubrole: <nil>
AXRoleDescription: 'heading'
doc-tip Expose

IA2_ROLE_NOTE

IAccessible2:

Object attribute xml-roles:doc-tip
  • Control Type is Text
  • Localized Control Type is 'tip'

Expose ROLE_COMMENT and object attribute xml-roles:doc-tip.

AXRole: AXGroup
AXSubrole: AXDocumentNote
AXRoleDescription: 'note'
doc-toc Expose IAccessible2:
  • IA2_ROLE_LANDMARK
  • Object attribute xml-roles:doc-toc
  • Control Type is Text
  • Localized Control Type is 'toc'
  • Landmark Type is Custom
  • Localized Landmark Type is 'toc'

Expose ROLE_LANDMARK and object attribute xml-roles:doc-toc.

 AXRole: AXGroup
AXSubrole: AXLandmarkNavigation
AXRoleDescription: 'navigation'

[Note 2] This specification does not currently contain guidance for when user agents should fire system alert events. Some guidance may be added to the specification at a later date but it will be a recommendation (should), not a requirement (must).

State and Property Mapping

This section describes how to expose WAI-ARIA states and object properties. User agents MUST conform to the State and Property Mapping accessibility API computational requirements in [[!CORE-AAM]].

Special Processing Requiring Additional Computation

Name and Description

When computing an accessible name or accessible description, user agents MUST conform to the section titled Text Alternative Computation of the [[!ACCNAME-AAM]] specification.

Widget Values

User agents MUST conform to the Widget Values accessibility API computational requirements in [[!CORE-AAM]].

Relations

User agents MUST conform to the Relation accessibility API computational requirements in [[!CORE-AAM]].

Group Position

User agents MUST conform to the Group Position accessibility API computational requirements in [[!CORE-AAM]].

Actions

User agents MUST conform to the Actions accessibility API computational requirements in [[!CORE-AAM]].

Events

User agents fire events for user actions, WAI-ARIA state changes, changes to document content or node visibility, changes in selection, and operation of menus. Conforming user agents MUST support the [[!CORE-AAM]] Events mappings.

Special Document Handling Procedures

User agents MUST conform to the Special Document Handling Procedures in [[!CORE-AAM]].

Appendices

Candidate Recommendation Exit Criteria

For this specification to advance to Proposed Recommendation, it has to be shown that mappings defined in this specification are implemented on the target platforms. Consistent with the plan for the Digital Publishing WAI-ARIA Module 1.0 [[dpub-aria-1.0]] (Dpub-ARIA), the requirement is that each role is successfully mapped in at least two implementations and each implementation maps at least 75% of the roles.

Change Log

Substantive changes since the last public working draft

  • 14-Jul-2016: Remove special processing copied over from SVG-AAM for name and description computation.
  • 26-Sep-2016: For MacOSX modify doc-abstract, doc-acknowledgments, doc-afterword, doc-appendix, doc-bibliography, doc-chapter, doc-conclusion, doc-credits, doc-endnotes, doc-epilogue, doc-errata, doc-foreward, doc-glossary, doc-index, doc-introduction, doc-pagelist, doc-part, doc-pagebreak, doc-prologue, and doc-toc to be landmark regions.
  • 28-Sep-2016: doc-abstract, doc-colophon, doc-credit, doc-dedication, doc-epigraph, doc-example and doc-qna are all to IA2_ROLE_SECTION; doc-notice, doc-tip mapped to IA2_ROLE_NOTE; convert a number of MSAA and IA2 roles to have <code> styling
  • 30-Sep-2016: Update AX mapping for doc-index; remove requirement that roles with no mapping fall back to implicit roles
  • 5-Dec-2016: Provide UIA mappings
  • 6-Dec-2016: Remove UIA mapping for doc-pullquote
  • 20-Apr-2017: Update mappings. For AXAPI, the AXSubrole is now AXApplicationGroup for the following roles: doc-abstract, doc-colophon, doc-dedication, doc-epigraph, doc-example, doc-footnote, doc-pullquote, and doc-qna; the AXRoleDescription of doc-abstract is now 'group'; doc-pagebreak is now mapped to AXRole: AXSplitter, AXRoleDescription: 'splitter'; doc-notice and doc-tip are now mapped to AXSubrole: AXDocumentNote, AXRoleDescription: 'note'. For ATK/ATSPI2, doc-tip is now mapped to ROLE_COMMENT.
  • 20-Apr-2017: Map doc-pullquote for ATK/ATSPI2, IA2, and UIA.

Other substantive changes since the First Public Working Draft

  • 10-Mar-2016: Replace all ROLE_PANEL to ROLE_SECTION for ATK/ATSPI mappings
  • 10-Mar-2016: Replace doc-locator with doc-backlink
  • 10-Mar-2016: Remove doc-title
  • 10-Mar-2016: Remove doc-footnotes and add doc-endnote and doc-endnotes
  • 10-Mar-2016: Changed doc-pullquote to reflect no mappings
  • 10-Mar-2016: Change doc-cover to map to an image
  • 10-Mar-2016: Removed rendundant references section in the appendix
  • 10-Mar-2016: Fixed links for githumb.io in configuration
  • 10-Mar-2016: Added a change log
  • 10-Mar-2016: Remove editors note regarding @rel
  • 10-Mar-2016: change xml-roles mapping for doc-pagelist to reflect the actual role
  • 10-Mar-2016: Fix doc-prologue in table to not say doc-preface
  • 10-Mar-2016: Fix doc-conclusion to map to ROLE_LANDMARK for ATK/ATSPI
  • 10-Mar-2016: changed doc-pagebreak to map to separator roles on IA2 and ATK/ATSPI
  • 10-Mar-2016: modify doc-toc mapping to be consistent with doc-pagelist
  • 10-Mar-2016: modify doc-subtitle to be a form of heading
  • 10-Mar-2016: modify doc-pagebreak to be more like a separator
  • 10-Mar-2016: Map doc-biblioentry and doc-endnote to ROLE_LIST_ITEM for ATK/ATSPI2; map doc-notice to ROLE_COMMENT for ATK/ATSPI2

Acknowledgments

The following people contributed to the development of this document.

Participants active in the DPUB-ARIA task force at the time of publication

  • Michael Cooper (W3C Staff)
  • Heather Flanagan (Invited expert)
  • Matt Garrish (DAISY Consortium)
  • Markus Gylling (DAISY Consortium)
  • Ivan Herman (W3C Staff)
  • Deborah Kaplan (Invited expert)
  • George Kerscher (DAISY Consortium)
  • Peter Krautzberger (W3C Invited Experts)
  • Charles LaPierre (Benetech)
  • Shane McCarron (W3C Invited Experts)
  • Janina Sajka (Invited Expert, The Linux Foundation)
  • Richard Schwerdtfeger (IBM Corporation)
  • Tzviya Siegman (Wiley)

The group would like to thank all members of the DAISY and EPUB 3 working groups who developed the structural semantics vocabulary from which this module was drawn, with special thanks to Sanders Kleinfeld for his assistance analyzing the initial set of semantics for inclusion.

Enabling funders

This publication has been funded in part with Federal funds from the U.S. Department of Education, National Institute on Disability, Independent Living, and Rehabilitation Research (NIDILRR) under contract number ED-OSE-10-C-0067. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.