This document describes how user agents should expose semantics of PDF content to accessibility APIs. This helps users with disabilities to obtain and interact with information using assistive technologies. Documenting these mappings promotes interoperable exposure of
roles, states, properties, and events implemented by accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent.
Status of This Document
This section describes the status of this
document at the time of its publication. A list of current W3C
publications and the latest revision of this technical report can be found
in the
W3C standards and drafts index.
Publication as an Editor's Draft does not
imply endorsement by W3C and its Members.
This is a draft document and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to cite this document as other
than a work in progress.
This document was produced by a group
operating under the
W3C Patent
Policy.
W3C maintains a
public list of any patent disclosures
made in connection with the deliverables of
the group; that page also includes
instructions for disclosing a patent. An individual who has actual
knowledge of a patent that the individual believes contains
Essential Claim(s)
must disclose the information in accordance with
section 6 of the W3C Patent Policy.
TBD. Should we duplicate or cross-reference this content from the corresponding Core-AAM section?
1.2 Comparing Accessibility APIs
TBD. Should we duplicate or cross-reference this content from the corresponding Core-AAM section?
1.2.1 Accessible Names and Descriptions
TBD. Should we duplicate or cross-reference this content from the corresponding Core-AAM section?
2. Conformance
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.
The key word MAY in this document
is to be interpreted as described in
BCP 14
[RFC2119] [RFC8174]
when, and only when, it appears in all
capitals, as shown here.
2.1 RFC-2119 Keywords
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.
2.2 Normative and Informative Sections
The indication whether a section is normative or non-normative (informative) applies to the entire section including sub-sections.
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.
3. Important Terms
This section is non-normative.
TBD. Can we add only PDF-specific terms here and cross-reference the others from common dir?
term 1
definition 1
term 2
definition 2
4. Mapping WAI-ARIA to Accessibility APIs
TBD. Should we duplicate or cross-reference this content from the corresponding Core-AAM section?
4.1 Role mapping
TBD. Should we duplicate or cross-reference this content from the corresponding Core-AAM section?
4.1.1 General rules
TBD. Should we duplicate or cross-reference this content from the corresponding Core-AAM section?
TBD. Should we duplicate or cross-reference this content from the corresponding Core-AAM section?
4.2.2 State and Property Mapping Tables
4.2.2.1 Not Mapped
There are a number of occurrences in the table where a given state or property is declared "Not mapped". In some cases, this occurs for the default value of the state/property, and is
equivalent to its absence. User agents might find it quicker to map the value than check to see if it is the default. For computational efficiency, user agents MAY expose the state or
property value if doing so is equivalent to not mapping it. These cases are marked with an asterisk.
In other cases, it is mandatory that the state/property not be mapped, since exposing it implies a related affordance. An example is
aria-grabbed. Its absence not only indicates that the accessible object is not grabbed, but further defines it as not grab-able. These cases are marked as "Not mapped" without an asterisk.
B.1 Participants active in the ARIA WG at the time of publication
Irfan Ali (Educational Testing Service)
CB Averitt (Deque Systems, Inc)
Sina Bahram (Invited Expert)
Shirisha Balusani (Invited Expert)
Amelia Bellamy-Royds (Invited Expert)
Curt Bellew (Oracle Corporation)
Alex Bernier (Association BrailleNet)
Zoë Bijl (Invited Expert)
Jorge Blazquez Alonso (IBM Corporation)
Alice Boxhall (Google LLC)
Matthew Brennan (Facebook)
Kim Bunge (TPGi)
Shari Butler (Pearson plc)
Tammy Campoverde (UnitedHealth Group)
David Caro (Wikimedia Foundation)
Timothy Cole (University of Illinois at Urbana-Champaign)
Dominic Cooney (Facebook)
Michael Cooper (W3C Staff)
James Craig (Apple Inc.)
Jory Cunningham (Salesforce)
Jes Daigle (Bocoup)
Joanmarie Diggs (Igalia)
Jason Duan (IBM Corporation)
Isaac Durazo (Bocoup)
Howard Edwards (Bocoup)
Steve Faulkner (TPGi)
Reinaldo Ferraz (NIC.br)
Alexander Flenniken (Bocoup)
Bryan Garaventa (Level Access)
Matt Garrish (DAISY Consortium)
Jaunita George (Navy Federal Credit Union)
Raghavendra Giriyappa (IBM Corporation)
Michael Goddard (Bocoup)
Glen Gordon (TPGi)
Jon Gunderson (University of Illinois at Urbana-Champaign)
Markku Hakkinen (Educational Testing Service)
Sarah Higley (Microsoft Corporation)
Hans Hillen (TPGi)
Isabel Holdsworth (TPGi)
Stanley Hon (Microsoft Corporation)
Nicholas Hoyt (University of Illinois at Urbana-Champaign)
Shilpi Kapoor (BarrierBreak Technologies)
Matthew King (Facebook)
Greta Krafsig (The Washington Post)
Peter Krautzberger (Invited Expert)
JaEun Jemma Ku (University of Illinois at Urbana-Champaign)
Lori Lane (University of Illinois at Urbana-Champaign)
Charles LaPierre (Benetech)
Gez Lemon (TPGi)
Aaron Leventhal (Google LLC)
Brian Liu Xu (Microsoft Corporation)
David MacDonald (Invited Expert)
Carolyn MacLeod (IBM Corporation)
Daniel Marques (WIRIS Science)
Dominic Mazzoni (Google LLC)
Mark McCarthy (University of Illinois at Urbana-Champaign)
Jan McSorley (Pearson plc)
Erika Miguel (Bocoup)
Sheila Moussavi (Bocoup)
Rich Noah (Bocoup)
James Nurthen (Adobe)
Scott O'Hara (Microsoft Corporation)
Achraf Othman (MADA Center)
Vijaya Gowri Perumal (Newgen Knowledgeworks)
Christos Petrou (Centre for Inclusive Design)
Simon Pieters (Bocoup)
Ian Pouncey (TetraLogical Services Ltd)
Ruoxi Ran (W3C Staff)
Adrian Roselli (TPGi)
Janina Sajka (Invited Expert, The Linux Foundation)
Stefan Schnabel (SAP SE)
Harris Schneiderman (Deque Systems, Inc.)
Lisa Seeman-Kestenbaum (Invited Expert)
Boaz Sender (Bocoup)
Cynthia Shelly (Google LLC)
Tzviya Siegman (Wiley)
Sharon Snider (IBM Corporation)
Neil Soiffer (Invited Expert)
Volker Sorge (Invited Expert)
Francis Storr (Intel Corporation)
Melanie Sumner (Invited Expert)
Alexander Surkov (Igalia)
William Tennis (Navy Federal Credit Union)
Seth Thompson (Bocoup)
Scott Vinkle (Shopify)
Can Wang (Zhejiang University)
Wei Wang (Zhejiang University)
Léonie Watson (TetraLogical Services Ltd)
Jason White (Educational Testing Service)
Jan Williams (TPGi)
Evan Yamanishi (W. W. Norton)
Benjamin Young (Wiley)
Valerie Young (Bocoup)
Marco Zehe (Mozilla Foundation)
B.2 Enabling funders
This publication has been funded in part with U.S. Federal funds from the Department of Education, National Institute on Disability, Independent Living, and Rehabilitation Research (NIDILRR), initially under contract number ED-OSE-10-C-0067, then under contract number HHSP23301500054C, and now under HHS75P00120P00168. 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.