From 57af6bf8b2d311024e4a147fe49bbf0291817dd9 Mon Sep 17 00:00:00 2001 From: Peter Krautzberger Date: Fri, 27 Oct 2023 16:41:42 +0200 Subject: [PATCH 1/2] chore: github action to run prettier Matches w3c/graphics-aria#10, including dependabot for the action. --- .github/workflows/dependabot.yaml | 12 ++++++++++++ .github/workflows/prettier.yaml | 26 ++++++++++++++++++++++++++ 2 files changed, 38 insertions(+) create mode 100644 .github/workflows/dependabot.yaml create mode 100644 .github/workflows/prettier.yaml diff --git a/.github/workflows/dependabot.yaml b/.github/workflows/dependabot.yaml new file mode 100644 index 0000000..17d094f --- /dev/null +++ b/.github/workflows/dependabot.yaml @@ -0,0 +1,12 @@ +# Set update schedule for GitHub Actions + +version: 2 +updates: + + - package-ecosystem: "github-actions" + directory: "/" + schedule: + interval: "weekly" + open-pull-requests-limit: 10 + commit-message: + prefix: "chore: dependabot" diff --git a/.github/workflows/prettier.yaml b/.github/workflows/prettier.yaml new file mode 100644 index 0000000..767039d --- /dev/null +++ b/.github/workflows/prettier.yaml @@ -0,0 +1,26 @@ +name: Prettier +# minimally modified from https://github.com/creyD/prettier_action#example-2-using-the-only_changed-or-same_commit-option-on-pr + +on: + pull_request: + branches: + - main + +jobs: + prettier: + runs-on: ubuntu-latest + + steps: + - name: Checkout + uses: actions/checkout@v3 + with: + # Make sure the actual branch is checked out when running on pull requests + ref: ${{ github.head_ref }} + # This is important to fetch the changes to the previous commit + fetch-depth: 0 + + - name: Prettify code + uses: creyD/prettier_action@v4.3 + with: + prettier_options: --write *.html --print-width 200 + commit_message: "chore: prettier" From f7d6bd9f931011e9b70f91a056de12f657d89093 Mon Sep 17 00:00:00 2001 From: pkra Date: Fri, 27 Oct 2023 14:42:19 +0000 Subject: [PATCH 2/2] chore: prettier --- Overview.html | 12537 +++++++++++++++++++++++++++++------------------- index.html | 8515 ++++++++++++++++---------------- 2 files changed, 11987 insertions(+), 9065 deletions(-) diff --git a/Overview.html b/Overview.html index 156d73e..7c7b019 100644 --- a/Overview.html +++ b/Overview.html @@ -1,2365 +1,3667 @@ - - - - - - - - -Digital Publishing WAI-ARIA Module 1.1 - - - - - - - - - - - - - - - + + + - - - - -
-

-

Digital Publishing WAI-ARIA Module 1.1

-

W3C Candidate Recommendation Snapshot

-
- More details about this document -
-
This version:
- https://www.w3.org/TR/2023/CR-dpub-aria-1.1-20230629/ -
-
Latest published version:
- https://www.w3.org/TR/dpub-aria-1.1/ -
-
Latest editor's draft:
https://w3c.github.io/dpub-aria/
-
History:
- Commit history -
- -
Implementation report:
- https://w3c.github.io/test-results/dpub-aria/ -
- - - -
Editors:
- Matt Garrish (DAISY Consortium) -
- Tzviya Siegman (Wiley) -
-
- Former editors: -
- Shane McCarron (Spec-Ops) -
- Markus Gylling (DAISY Consortium) -
- -
Feedback:
- GitHub w3c/dpub-aria - (pull requests, - new issue, - open issues) -
- -
Repository
- Github Repository -
Changes
-
-
- - -

- Copyright - © - 2015-2023 - - World Wide Web Consortium. - W3C® - liability, - trademark and - permissive document license rules apply. -

-
-
-

Abstract

-

Enabling users of assistive technologies to find their way through web content requires embedding - semantic metadata about web document structural divisions. This is particularly important for structural - divisions of long-form documents and goes along with embedding semantic metadata about web-application - widgets and behaviors for assistive technologies. This specification defines a set of WAI-ARIA roles - specific to helping users of assistive technologies navigate through such long-form documents.

- -

This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

-
-

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 technical reports index at - https://www.w3.org/TR/.

-

Feature development for this version is complete, and this is a wide review draft published to obtain - feedback before finalization of the specification.

- -

There have been only minor clarifications since the First Public Working - Draft.

- -

While feedback on any aspect of the specification is encouraged, we would particularly like feedback on - the addition of the doc-pageheader and doc-pagefooter roles.

-

- This document was published by the Accessible Rich Internet Applications Working Group as - a Candidate Recommendation Snapshot using the - Recommendation track. -

Publication as a Candidate Recommendation does not - imply endorsement by W3C and its Members. A Candidate Recommendation Snapshot has received - wide review, is intended to - gather - implementation experience, - and has commitments from Working Group members to + + + + +

+

+ +

+

Digital Publishing WAI-ARIA Module 1.1

+

W3C Candidate Recommendation Snapshot

+
+ More details about this document +
+
This version:
+
+ https://www.w3.org/TR/2023/CR-dpub-aria-1.1-20230629/ +
+
Latest published version:
+
+ https://www.w3.org/TR/dpub-aria-1.1/ +
+
Latest editor's draft:
+
https://w3c.github.io/dpub-aria/
+
History:
+
+ Commit history +
+ +
Implementation report:
+
+ https://w3c.github.io/test-results/dpub-aria/ +
+ +
Editors:
+
+ Matt Garrish (DAISY Consortium) +
+
+ Tzviya Siegman (Wiley) +
+
Former editors:
+
+ Shane McCarron (Spec-Ops) +
+
+ Markus Gylling (DAISY Consortium) +
+ +
Feedback:
+
+ GitHub w3c/dpub-aria + (pull requests, new issue, + open issues) +
+ +
Repository
+
+ Github Repository +
+
Changes
+
+
+ +

+ Copyright + © 2015-2023 + + World Wide Web Consortium. W3C® + liability, trademark and + permissive document license rules apply. +

+
+
+
+

Abstract

+

+ Enabling users of assistive technologies to find their way through web content requires embedding semantic metadata about web document structural divisions. This is particularly important for + structural divisions of long-form documents and goes along with embedding semantic metadata about web-application widgets and behaviors for assistive technologies. This specification defines a + set of WAI-ARIA roles specific to helping users of assistive technologies navigate through such long-form documents. +

+ +

+ This document is part of the WAI-ARIA suite described in the + WAI-ARIA Overview. +

+
+
+

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 technical reports index at https://www.w3.org/TR/. +

+

Feature development for this version is complete, and this is a wide review draft published to obtain feedback before finalization of the specification.

+ +

There have been only minor clarifications since the First Public Working Draft.

+ +

+ While feedback on any aspect of the specification is encouraged, we would particularly like feedback on the addition of the + doc-pageheader and doc-pagefooter roles. +

+

+ This document was published by the Accessible Rich Internet Applications Working Group as a Candidate Recommendation Snapshot using the + Recommendation track. +

+

+ Publication as a Candidate Recommendation does not imply endorsement by W3C and its Members. A Candidate Recommendation Snapshot has received + wide review, is intended to gather + implementation experience, and has commitments from Working Group members to royalty-free licensing - for implementations.

- This Candidate Recommendation is not expected to advance to Proposed - Recommendation any earlier than 29 August 2023. -

- - 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 which the individual believes contains - Essential Claim(s) - must disclose the information in accordance with - section 6 of the W3C Patent Policy. - -

- This document is governed by the - 2 November 2021 W3C Process Document. -

- -

1. Introduction

This section is non-normative.

- - -

WAI-ARIA is a technical specification that - defines a common host language semantic accessibility API and framework that enables web browsers to map - the accessibility semantics in web content to platform-specific accessibility APIs. This enables web - content to be interoperable with platform assistive technologies similar to native platform applications - without platform dependencies.

- -

This specification is a modular extension of WAI-ARIA designed for the digital publishing industry. The goals of this specification - include:

- -
    -
  • Expanding [WAI-ARIA] to produce structural semantic extensions to accommodate the digital - publishing industry.
    • -
  • Align with a new governance model for modularization and extensions to WAI-ARIA.
    • -
  • Provide structural semantics extensions that will support both assistive technologies and enable - semantic navigation, styling and interactive features used by readers.
    • -
- -

The roles defined in this specification are derived from the EPUB Structural Semantics Vocabulary.

- -

For a more detailed explanation of WAI-ARIA - please refer to the WAI-ARIA Introduction and how it - applies to Rich Internet Application Accessibility.

- -

1.1 Target Audience

- - -

This specification defines a module of WAI-ARIA for digital publishing, including roles, states, properties - and values. It impacts several audiences:

- -
    -
  • User agents that process content containing WAI-ARIA and Digital Publishing WAI-ARIA features;
    • -
  • Assistive technologies that provide specialized reading experiences to - users with disabilities;
    • -
  • Authors of digital publications;
    • -
  • Authoring tools that help authors create conforming digital publications; and
    • -
  • Conformance checkers, that verify appropriate use of WAI-ARIA and this Digital Publishing - WAI-ARIA module.
    • -
- -

Each conformance requirement indicates the audience to which it applies.

- -

Although this specification is applicable to the above audiences, it is not specifically targeted to, - nor is it intended to be the sole source of information for, any of these audiences. In the future, - additional documents will be created to assist authors in applying these WAI-ARIA semantics for the publishing - industry and to define how the information in this document is mapped to platform accessibility - APIs.

-
- -

1.2 User Agent Support

- - -

This module builds on the general User Agent - support principles defined in [WAI-ARIA] by also providing the ability for user agents to - enhance the general user interface presented to readers.

-
- -

1.3 Co-Evolution of WAI-ARIA and Host - Languages

- - -

The Digital Publishing WAI-ARIA module - follows the model for co-evolution of - WAI-ARIA and host languages - defined in [WAI-ARIA]. It is intended to augment semantics in supporting languages like [HTML], - [SVG2] and EPUB, or to be used as an accessibility enhancement technology in other markup-based - languages that do not explicitly include support for ARIA. It clarifies semantics to assistive - technologies when authors create new types of objects, via style and script, that are not yet - directly supported by the language of the page, because the invention of new types of objects is - faster than standardized support for them appears in web languages.

- -

It is not appropriate to create objects with style and script when the host language provides a - semantic element for that type of objects. While WAI-ARIA can improve the accessibility of these objects, accessibility is best provided - by allowing the user agent to handle the object natively. For example, it is not better to use a - heading role on a div element than it is to use a native heading - element, such as an h1.

- -

It is expected that, over time, host languages will evolve to provide semantics for objects that - currently can only be declared with this specification. This is natural and desirable, as one goal - of WAI-ARIA is to help stimulate the - emergence of more semantic and accessible markup. When native semantics for a given feature become - available, it is appropriate for authors to use the native feature and stop using this module for - that feature. Legacy content may continue to use the Digital Publishing WAI-ARIA module, however, so the need for - user agents to support it remains.

- -

While specific features of this module may lose importance over time, the general possibility of the - Digital Publishing WAI-ARIA module to add - semantics to web pages or open web-based standards, such as EPUB, is expected to be a persistent - need. Host languages may not implement all the semantics this module provides, and various host - languages may implement different subsets of the features. New types of objects are continually - being developed, and one goal of this specification is to provide a way to make such objects - accessible, because authoring practices often advance faster than host language standards. In this - way, this module and host languages both evolve together but at different rates.

- -

Some host languages exist to create semantics for features other than the user interface. For - example, SVG expresses the semantics behind production of graphical objects, not of user interface - components that those objects may represent. Host languages such as these might, by design, not - provide native semantics that map to this specification's features. In these cases, the Digital - Publishing WAI-ARIA module could be - adopted as a long-term approach to add semantic information to these host languages.

-
- -

1.4 Authoring Practices

- - -

1.4.1 Authoring Tools

- - -

Many of the requirements in the definitions of the WAI-ARIA and Digital Publishing WAI-ARIA roles, states and - properties can be checked automatically during the development process, similar to - other quality control processes used for validating code. To assist authors who are creating - digital publications, such as EPUB, can compare the semantic structure of Digital Publishing - WAI-ARIA roles from the DOM to that defined in this specification and notify - the author of errors or simply create templates that enforce that structure.

-
- -

1.4.2 Testing Practices and Tools

- - -

The accessibility of interactive content cannot be confirmed by static checks alone. Developers - of interactive content should test for device-independent access to widgets and applications, and should verify accessibility API access to all content and changes during - user interaction.

-
-
- -

1.5 Assistive Technologies

- - -

Programmatic access to accessibility semantics is essential for assistive technologies. For more - information, refer to the Assistive - Technologies section in [WAI-ARIA].

-
-
-

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 words MAY, MUST, MUST NOT, and SHOULD in this document - are to be interpreted as described in + for implementations. +

+

This Candidate Recommendation is not expected to advance to Proposed Recommendation any earlier than 29 August 2023.

+

+ 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 which the individual + believes contains + Essential Claim(s) + must disclose the information in accordance with + section 6 of the W3C Patent Policy. +

+

+ This document is governed by the + 2 November 2021 W3C Process Document. +

+
+ +
+
+

1. Introduction

+ +
+

This section is non-normative.

+ +

+ WAI-ARIA is a technical specification that defines a common host language semantic accessibility + API and framework that enables web browsers to map the accessibility semantics in web content to platform-specific accessibility APIs. + This enables web content to be interoperable with platform assistive technologies similar to native platform applications without platform dependencies. +

+ +

+ This specification is a modular extension of WAI-ARIA designed for the digital publishing industry. The goals of this specification + include: +

+ +
    +
  • + Expanding [WAI-ARIA] to produce structural semantic extensions to accommodate the digital publishing industry. +
    • +
  • Align with a new governance model for modularization and extensions to WAI-ARIA.
    • +
  • Provide structural semantics extensions that will support both assistive technologies and enable semantic navigation, styling and interactive features used by readers.
    • +
+ +

The roles defined in this specification are derived from the EPUB Structural Semantics Vocabulary.

+ +

+ For a more detailed explanation of WAI-ARIA please refer to the + WAI-ARIA Introduction and how it applies to Rich Internet Application Accessibility. +

+ +
+
+

1.1 Target Audience

+ +
+ +

+ This specification defines a module of WAI-ARIA for digital publishing, including + roles, + states, + properties and values. It impacts several audiences: +

+ +
    +
  • + User agents that process content containing + WAI-ARIA and Digital Publishing WAI-ARIA features; +
    • +
  • + Assistive technologies that provide + specialized reading experiences to users with disabilities; +
    • +
  • Authors of digital publications;
    • +
  • Authoring tools that help authors create conforming digital publications; and
    • +
  • + Conformance checkers, that verify appropriate use of WAI-ARIA and this Digital Publishing + WAI-ARIA module. +
    • +
+ +

Each conformance requirement indicates the audience to which it applies.

+ +

+ Although this specification is applicable to the above audiences, it is not specifically targeted to, nor is it intended to be the sole source of information for, any of these audiences. In + the future, additional documents will be created to assist authors in applying these WAI-ARIA semantics for the publishing industry + and to define how the information in this document is mapped to platform accessibility APIs. +

+
+ +
+
+

1.2 User Agent Support

+ +
+ +

+ This module builds on the general User Agent support principles defined in [WAI-ARIA] by also providing the ability for user agents to enhance the general user interface presented to readers. +

+
+ +
+
+

+ 1.3 Co-Evolution of WAI-ARIA and Host Languages +

+ +
+ +

+ The Digital Publishing WAI-ARIA module follows the model for + co-evolution of WAI-ARIA and host languages defined in [WAI-ARIA]. It is intended to augment semantics in supporting languages like [HTML], [SVG2] and EPUB, or to be used as an accessibility enhancement technology in other markup-based languages that do not explicitly include support for ARIA. It clarifies semantics to assistive + technologies when authors create new types of objects, via style and script, that are not yet directly supported by the language of the page, because the invention of new types of objects is + faster than standardized support for them appears in web languages. +

+ +

+ It is not appropriate to create objects with style and script when the host language provides a semantic element for that type of objects. While + WAI-ARIA can improve the accessibility of these objects, accessibility is best provided by allowing the user agent to handle the + object natively. For example, it is not better to use a heading role on a + div element than it is to use a native heading element, such as an h1. +

+ +

+ It is expected that, over time, host languages will evolve to provide semantics for objects that currently can only be declared with this specification. This is natural and desirable, as one + goal of WAI-ARIA is to help stimulate the emergence of more semantic and accessible markup. When native semantics for a given + feature become available, it is appropriate for authors to use the native feature and stop using this module for that feature. Legacy content may continue to use the Digital Publishing + WAI-ARIA module, however, so the need for user agents to support it remains. +

+ +

+ While specific features of this module may lose importance over time, the general possibility of the Digital Publishing + WAI-ARIA module to add semantics to web pages or open web-based standards, such as EPUB, is expected to be a persistent need. Host + languages may not implement all the semantics this module provides, and various host languages may implement different subsets of the features. New types of objects are continually being + developed, and one goal of this specification is to provide a way to make such objects accessible, because authoring practices often advance faster than host language standards. In this way, + this module and host languages both evolve together but at different rates. +

+ +

+ Some host languages exist to create semantics for features other than the user interface. For example, SVG expresses the semantics behind production of graphical objects, not of user + interface components that those objects may represent. Host languages such as these might, by design, not provide native semantics that map to this specification's features. In these cases, + the Digital Publishing WAI-ARIA module could be adopted as a long-term approach to add semantic information to these host + languages. +

+
+ +
+
+

1.4 Authoring Practices

+ +
+ +
+
+

1.4.1 Authoring Tools

+ +
+ +

+ Many of the requirements in the definitions of the WAI-ARIA and Digital Publishing + WAI-ARIA roles, + states and + properties can be checked automatically during the development process, similar + to other quality control processes used for validating code. To assist authors who are creating digital publications, such as EPUB, can compare the semantic structure of Digital Publishing + WAI-ARIA roles from the DOM to that defined in this specification and notify the + author of errors or simply create templates that enforce that structure. +

+
+ +
+
+

1.4.2 Testing Practices and Tools

+ +
+ +

+ The accessibility of interactive content cannot be confirmed by static checks alone. Developers of interactive content should test for device-independent access to + widgets and applications, and should verify accessibility + API access to all content and changes during user interaction. +

+
+
+ +
+
+

1.5 Assistive Technologies

+ +
+ +

+ Programmatic access to accessibility semantics is essential for assistive technologies. For more information, refer to the + Assistive Technologies section in [WAI-ARIA]. +

+
+
+
+
+

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 words MAY, MUST, MUST NOT, and SHOULD in this document are to be interpreted as + described in BCP 14 - [RFC2119] [RFC8174] - when, and only when, they appear in all capitals, as shown here. + [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. +

+

Normative sections provide requirements that authors, user agents and assistive technologies MUST follow for an implementation to conform to this specification.

+ +

+ Non-normative 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 to conform to this specification.

-

Normative sections provide requirements that authors, user agents and assistive technologies MUST follow - for an implementation to conform to this specification.

- -

Non-normative 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 to - conform to this specification.

-
-

3. Digital Publishing Roles

- - -

This section defines additions to the WAI-ARIA - roles model and describes the characteristics and properties of all roles. See ARIA Roles for - descriptions of the fields provided by this module.

- -

3.1 Definition of Roles

- - -

Below is an alphabetical list of WAI-ARIA - roles to be used by rich internet application authors.

- -
doc-abstract
-
A short summary of the principal ideas, concepts, and conclusions of the work, or of a - section or excerpt within it.
-
doc-acknowledgments
-
A section or statement that acknowledges significant contributions by persons, organizations, - governments, and other entities to the realization of the work.
-
doc-afterword
-
A closing statement from the author or a person of importance, typically providing insight - into how the content came to be written, its significance, or related events that have - transpired since its timeline.
-
doc-appendix
-
A section of supplemental information located after the primary content that informs the - content but is not central to it.
-
doc-backlink
-
A link that allows the user to return to a related location in the content (e.g., from a - footnote to its reference or from a glossary definition to where a term is used).
-
doc-biblioentry
-
[Deprecated in DPUB-ARIA 1.1] A single reference to an external source in a bibliography. A - biblioentry typically provides more detailed information than its reference(s) in the - content (e.g., full title, author(s), publisher, publication date, etc.).
-
doc-bibliography
-
A list of external references cited in the work, which may be to print or digital - sources.
-
doc-biblioref
-
A reference to a bibliography entry.
-
doc-chapter
-
A major thematic section of content in a work.
-
doc-colophon
-
A short section of production notes particular to the edition (e.g., describing the typeface - used), often located at the end of a work.
-
doc-conclusion
-
A concluding section or statement that summarizes the work or wraps up the narrative.
-
doc-cover
-
An image that sets the mood or tone for the work and typically includes the title and - author.
-
doc-credit
-
An acknowledgment of the source of integrated content from third-party sources, such as - photos. Typically identifies the creator, copyright, and any restrictions on reuse.
-
doc-credits
-
A collection of credits.
-
doc-dedication
-
An inscription at the front of the work, typically addressed in tribute to one or more - persons close to the author.
-
doc-endnote
-
[Deprecated in DPUB-ARIA 1.1] One of a collection of notes that occur at the end of a work, - or a section within it, that provides additional context to a referenced passage of - text.
-
doc-endnotes
-
A collection of notes at the end of a work or a section within it.
-
doc-epigraph
-
A quotation set at the start of the work or a section that establishes the theme or sets the - mood.
-
doc-epilogue
-
A concluding section of narrative that wraps up or comments on the actions and events of the - work, typically from a future perspective.
-
doc-errata
-
A set of corrections discovered after initial publication of the work, sometimes referred to - as corrigenda.
-
doc-example
-
An illustration of a key concept of the work, such as a code listing, case study or - problem.
-
doc-footnote
-
Ancillary information, such as a citation or commentary, that provides additional context to - a referenced passage of text.
-
doc-foreword
-
An introductory section that precedes the work, typically not written by the author of the - work.
-
doc-glossary
-
A brief dictionary of new, uncommon, or specialized terms used in the content.
-
doc-glossref
-
A reference to a glossary definition.
-
doc-index
-
A navigational aid that provides a detailed list of links to key subjects, names and other - important topics covered in the work.
-
doc-introduction
-
A preliminary section that typically introduces the scope or nature of the work.
-
doc-noteref
-
A reference to a footnote or endnote, typically appearing as a superscripted number or symbol - in the main body of text.
-
doc-notice
-
Notifies the user of consequences that might arise from an action or event. Examples include - warnings, cautions and dangers.
-
doc-pagebreak
-
A separator denoting the position before which a break occurs between two contiguous pages in - a statically paginated version of the content.
-
doc-pagelist
-
A navigational aid that provides a list of links to the page breaks in the content.
-
doc-pagefooter
-
A section of text appearing at the bottom of a page that provides context about the current - work and location within it. The page footer is distinct from the body text and normally - follows a repeating template that contains (possibly truncated) items such as the document - title, current section, author name(s), and page number.
-
doc-pageheader
-
A section of text appearing at the top of a page that provides context about the current work - and location within it. The page header is distinct from the body text and normally follows - a repeating template that contains (possibly truncated) items such as the document title, - current section, author name(s), and page number.
-
doc-part
-
A major structural division in a work that contains a set of related sections dealing with a - particular subject, narrative arc, or similar encapsulated theme.
-
doc-preface
-
An introductory section that precedes the work, typically written by the author of the - work.
-
doc-prologue
-
An introductory section that sets the background to a work, typically part of the - narrative.
-
doc-pullquote
-
A distinctively placed or highlighted quotation from the current content designed to draw - attention to a topic or highlight a key point.
-
doc-qna
-
A section of content structured as a series of questions and answers, such as an interview or - list of frequently asked questions.
-
doc-subtitle
-
An explanatory or alternate title for the work, or a section or component within it.
-
doc-tip
-
Helpful information that clarifies some aspect of the content or assists in its - comprehension.
-
doc-toc
-
A navigational aid that provides an ordered list of links to the major sectional headings in - the content. A table of contents may cover an entire work, or only a smaller section of - it.
-
- -
-

doc-abstract (role)

- -
-

A short summary of the principal ideas, concepts, and conclusions of the work, or of a - section or excerpt within it.

- -
-
- Example 1 - 
<section role="doc-abstract" aria-label="Abstract">
+
+
+
+

3. Digital Publishing Roles

+ +
+ +

+ This section defines additions to the WAI-ARIA + roles model and describes the characteristics and properties of all + roles. See + ARIA Roles for descriptions of the fields provided by this module. +

+ +
+
+

3.1 Definition of Roles

+ +
+ +

+ Below is an alphabetical list of WAI-ARIA + roles to be used by rich internet application authors. +

+ +
+
doc-abstract
+
A short summary of the principal ideas, concepts, and conclusions of the work, or of a section or excerpt within it.
+
doc-acknowledgments
+
A section or statement that acknowledges significant contributions by persons, organizations, governments, and other entities to the realization of the work.
+
doc-afterword
+
+ A closing statement from the author or a person of importance, typically providing insight into how the content came to be written, its significance, or related events that have transpired + since its timeline. +
+
doc-appendix
+
A section of supplemental information located after the primary content that informs the content but is not central to it.
+
doc-backlink
+
A link that allows the user to return to a related location in the content (e.g., from a footnote to its reference or from a glossary definition to where a term is used).
+
doc-biblioentry
+
+ [Deprecated in DPUB-ARIA 1.1] A single reference to an external source in a bibliography. A biblioentry typically provides more detailed information than its reference(s) in the content + (e.g., full title, author(s), publisher, publication date, etc.). +
+
doc-bibliography
+
A list of external references cited in the work, which may be to print or digital sources.
+
doc-biblioref
+
A reference to a bibliography entry.
+
doc-chapter
+
A major thematic section of content in a work.
+
doc-colophon
+
A short section of production notes particular to the edition (e.g., describing the typeface used), often located at the end of a work.
+
doc-conclusion
+
A concluding section or statement that summarizes the work or wraps up the narrative.
+
doc-cover
+
An image that sets the mood or tone for the work and typically includes the title and author.
+
doc-credit
+
An acknowledgment of the source of integrated content from third-party sources, such as photos. Typically identifies the creator, copyright, and any restrictions on reuse.
+
doc-credits
+
A collection of credits.
+
doc-dedication
+
An inscription at the front of the work, typically addressed in tribute to one or more persons close to the author.
+
doc-endnote
+
[Deprecated in DPUB-ARIA 1.1] One of a collection of notes that occur at the end of a work, or a section within it, that provides additional context to a referenced passage of text.
+
doc-endnotes
+
A collection of notes at the end of a work or a section within it.
+
doc-epigraph
+
A quotation set at the start of the work or a section that establishes the theme or sets the mood.
+
doc-epilogue
+
A concluding section of narrative that wraps up or comments on the actions and events of the work, typically from a future perspective.
+
doc-errata
+
A set of corrections discovered after initial publication of the work, sometimes referred to as corrigenda.
+
doc-example
+
An illustration of a key concept of the work, such as a code listing, case study or problem.
+
doc-footnote
+
Ancillary information, such as a citation or commentary, that provides additional context to a referenced passage of text.
+
doc-foreword
+
An introductory section that precedes the work, typically not written by the author of the work.
+
doc-glossary
+
A brief dictionary of new, uncommon, or specialized terms used in the content.
+
doc-glossref
+
A reference to a glossary definition.
+
doc-index
+
A navigational aid that provides a detailed list of links to key subjects, names and other important topics covered in the work.
+
doc-introduction
+
A preliminary section that typically introduces the scope or nature of the work.
+
doc-noteref
+
A reference to a footnote or endnote, typically appearing as a superscripted number or symbol in the main body of text.
+
doc-notice
+
Notifies the user of consequences that might arise from an action or event. Examples include warnings, cautions and dangers.
+
doc-pagebreak
+
A separator denoting the position before which a break occurs between two contiguous pages in a statically paginated version of the content.
+
doc-pagelist
+
A navigational aid that provides a list of links to the page breaks in the content.
+
doc-pagefooter
+
+ A section of text appearing at the bottom of a page that provides context about the current work and location within it. The page footer is distinct from the body text and normally follows + a repeating template that contains (possibly truncated) items such as the document title, current section, author name(s), and page number. +
+
doc-pageheader
+
+ A section of text appearing at the top of a page that provides context about the current work and location within it. The page header is distinct from the body text and normally follows a + repeating template that contains (possibly truncated) items such as the document title, current section, author name(s), and page number. +
+
doc-part
+
A major structural division in a work that contains a set of related sections dealing with a particular subject, narrative arc, or similar encapsulated theme.
+
doc-preface
+
An introductory section that precedes the work, typically written by the author of the work.
+
doc-prologue
+
An introductory section that sets the background to a work, typically part of the narrative.
+
doc-pullquote
+
A distinctively placed or highlighted quotation from the current content designed to draw attention to a topic or highlight a key point.
+
doc-qna
+
A section of content structured as a series of questions and answers, such as an interview or list of frequently asked questions.
+
doc-subtitle
+
An explanatory or alternate title for the work, or a section or component within it.
+
doc-tip
+
Helpful information that clarifies some aspect of the content or assists in its comprehension.
+
doc-toc
+
+ A navigational aid that provides an ordered list of links to the major sectional headings in the content. A table of contents may cover an entire work, or only a smaller section of it. +
+
+ +
+

doc-abstract (role)

+ +
+

A short summary of the principal ideas, concepts, and conclusions of the work, or of a section or excerpt within it.

+ +
+
+ Example 1 +
+ 
<section role="doc-abstract" aria-label="Abstract">
    <p>Accessibility of web content requires semantic information about widgets, structures,
       and behaviors …</p>
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-abstract:
CharacteristicValue
Superclass Role:section
Related Concepts:EPUB abstract - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-acknowledgments (role)

- -
-

A section or statement that acknowledges significant contributions by persons, organizations, - governments, and other entities to the realization of the work.

- -
-
- Example 2 - 
<section role="doc-acknowledgments">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-abstract: +
CharacteristicValue
Superclass Role: + section +
Related Concepts: + EPUB abstract [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-acknowledgments (role)

+ +
+

A section or statement that acknowledges significant contributions by persons, organizations, governments, and other entities to the realization of the work.

+ +
+
+ Example 2 +
+ 
<section role="doc-acknowledgments">
    <p>I would like to extend my sincere gratitude to … </p>
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-acknowledgments:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB acknowledgments [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-afterword (role)

- -
-

A closing statement from the author or a person of importance, typically providing insight - into how the content came to be written, its significance, or related events that have - transpired since its timeline.

- -
-
- Example 3 - 
<section role="doc-afterword">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-acknowledgments: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB acknowledgments [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-afterword (role)

+ +
+

+ A closing statement from the author or a person of importance, typically providing insight into how the content came to be written, its significance, or related events that have + transpired since its timeline. +

+ +
+
+ Example 3 +
+ 
<section role="doc-afterword">
    <h2>Afterword: Why I Wrote This Book</h2>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-afterword:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB afterword - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-appendix (role)

- -
-

A section of supplemental information located after the primary content that informs the - content but is not central to it.

- -
-
- Example 4 - 
<section role="doc-appendix">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-afterword: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB afterword [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-appendix (role)

+ +
+

A section of supplemental information located after the primary content that informs the content but is not central to it.

+ +
+
+ Example 4 +
+ 
<section role="doc-appendix">
    <h2>Appendix A. Historical Timeline</h2>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-appendix:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB appendix - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- - + + - -
-

doc-biblioentry (role)

- -
-

[Deprecated in DPUB-ARIA 1.1] A single reference to an external source in a bibliography. A - biblioentry typically provides more detailed information than its reference(s) in the - content (e.g., full title, author(s), publisher, publication date, etc.).

- -
Note

The doc-biblioentry - role was designed for use as a list item, but due to clarifications in the WAI-ARIA - specification, it is not valid as a child of the list role. As the - doc-bibliography role already identifies a section of bibliography entries, - authors are instead advised to use the list and listitem roles - when native HTML elements cannot be used to structure the entries.

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-biblioentry:
CharacteristicValue
Related Concepts:EPUB biblioentry - [EPUB-SSV]
Name From:author
Accessible Name Required:True
-
- -
-

doc-bibliography (role)

- -
-

A list of external references cited in the work, which may be to print or digital - sources.

- -

The element carrying the doc-bibliography - role MUST contain at least one descendant list containing the - bibliography entries (if the entries are subdivided, for example alphabetically, the element - would contain more than one list).

- -

User Agents MUST expose the list items in these lists using the platform accessibility API - mappings for an individual entry.

- -

Lists nested within an entry have no special significance. User Agents MUST NOT expose these - list items using the platform accessibility API mappings for an individual entry.

- -

Authors MUST NOT apply the doc-bibliography role directly to the list containing - the entries.

- -
-
- Example 6 - 
<section role="doc-bibliography">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-backlink: +
CharacteristicValue
Superclass Role: + link +
Related Concepts: + EPUB referrer [EPUB-SSV] +
Inherited States and Properties: + +
Name From: +
    +
  • contents
    • +
  • author
    • +
+
Accessible Name Required:True
+
+ +
+

doc-biblioentry (role)

+ +
+

+ [Deprecated in DPUB-ARIA 1.1] A single reference to an external source in a bibliography. A biblioentry typically provides more detailed information than its reference(s) in the content + (e.g., full title, author(s), publisher, publication date, etc.). +

+ +
+
Note
+

+ The doc-biblioentry role was designed for use as a list item, but due to clarifications in the + WAI-ARIA specification, it is not valid as a child of the + list role. As the + doc-bibliography role already identifies a section of bibliography entries, authors are instead advised to use the + list and + listitem roles when native HTML elements cannot be used to structure the entries. +

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-biblioentry: +
CharacteristicValue
Related Concepts: + EPUB biblioentry [EPUB-SSV] +
Name From:author
Accessible Name Required:True
+
+ +
+

doc-bibliography (role)

+ +
+

A list of external references cited in the work, which may be to print or digital sources.

+ +

+ The element carrying the doc-bibliography role + MUST contain at least one descendant list containing the bibliography entries (if the entries are subdivided, for example alphabetically, the element would + contain more than one list). +

+ +

+ User Agents MUST expose the list items in these lists using the platform accessibility API mappings for an + individual entry. +

+ +

+ Lists nested within an entry have no special significance. User Agents MUST NOT expose these list items using the platform accessibility + API mappings for an individual entry. +

+ +

Authors MUST NOT apply the doc-bibliography role directly to the list containing the entries.

+ +
+
+ Example 6 +
+ 
<section role="doc-bibliography">
    <h2>Select Bibliography</h2>
    <ul>
       …
    </ul>
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-bibliography:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB bibliography [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-biblioref (role)

- -
-

A reference to a bibliography entry.

- -
-
- Example 7 - 
<p>
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-bibliography: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB bibliography [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-biblioref (role)

+ +
+

A reference to a bibliography entry.

+ +
+
+ Example 7 +
+ 
<p>
    As <a role="doc-biblioref"
       href="#b8cab5dd-bc24-459c-9858-7afa9da69b64">Steinbeck</a>
    says in his great novel …
 </p>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-biblioref:
CharacteristicValue
Superclass Role:link
Related Concepts:EPUB biblioref - [EPUB-SSV]
Inherited States and Properties: -
Name From: -
    -
  • contents
    • -
  • author
    • -
-
Accessible Name Required:True
-
- -
-

doc-chapter (role)

- -
-

A major thematic section of content in a work.

- -
-
- Example 8 - 
<section role="doc-chapter">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-biblioref: +
CharacteristicValue
Superclass Role: + link +
Related Concepts: + EPUB biblioref [EPUB-SSV] +
Inherited States and Properties: + +
Name From: +
    +
  • contents
    • +
  • author
    • +
+
Accessible Name Required:True
+
+ +
+

doc-chapter (role)

+ +
+

A major thematic section of content in a work.

+ +
+
+ Example 8 +
+ 
<section role="doc-chapter">
    <h2>Chapter 1. Loomings.</h2>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-chapter:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB chapter - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-colophon (role)

- -
-

A short section of production notes particular to the edition (e.g., describing the typeface - used), often located at the end of a work.

- -
-
- Example 9 - 
<section role="doc-colophon" aria-label="About the type">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-chapter: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB chapter [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-colophon (role)

+ +
+

A short section of production notes particular to the edition (e.g., describing the typeface used), often located at the end of a work.

+ +
+
+ Example 9 +
+ 
<section role="doc-colophon" aria-label="About the type">
    <p>This publication was set using … </p>
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-colophon:
CharacteristicValue
Superclass Role:section
Related Concepts:EPUB colophon - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-conclusion (role)

- -
-

A concluding section or statement that summarizes the work or wraps up the narrative.

- -
-
- Example 10 - 
<section role="doc-conclusion">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-colophon: +
CharacteristicValue
Superclass Role: + section +
Related Concepts: + EPUB colophon [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-conclusion (role)

+ +
+

A concluding section or statement that summarizes the work or wraps up the narrative.

+ +
+
+ Example 10 +
+ 
<section role="doc-conclusion">
    <h2>Summary</h2>
    <p>A central task in feminist scholarship is to expose and dismantle the stereotypes … </p>
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-conclusion:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB conclusion - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-cover (role)

- -
-

An image that sets the mood or tone for the work and typically includes the title and - author.

- -
-
- Example 11 - 
<img role="doc-cover" src="coverimage.jpg" alt="A Room of One's Own by Virginia Woolf"/>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-cover:
CharacteristicValue
Superclass Role:img
Related Concepts:EPUB cover - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-credit (role)

- -
-

An acknowledgment of the source of integrated content from third-party sources, such as - photos. Typically identifies the creator, copyright, and any restrictions on reuse.

- -
-
- Example 12 - 
<p role="doc-credit">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-conclusion: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB conclusion [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-cover (role)

+ +
+

An image that sets the mood or tone for the work and typically includes the title and author.

+ +
+
+ Example 11 +
+ 
<img role="doc-cover" src="coverimage.jpg" alt="A Room of One's Own by Virginia Woolf"/>
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-cover: +
CharacteristicValue
Superclass Role: + img +
Related Concepts: + EPUB cover [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-credit (role)

+ +
+

An acknowledgment of the source of integrated content from third-party sources, such as photos. Typically identifies the creator, copyright, and any restrictions on reuse.

+ +
+
+ Example 12 +
+ 
<p role="doc-credit">
    Page 62, Table 3.1 from <cite>“Economic Foundations of Cost-Effectiveness Analysis”</cite>
    by A. M. Garber and C. E. Phelps …
 </p>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-credit:
CharacteristicValue
Superclass Role:section
Related Concepts:EPUB credit - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-credits (role)

- -
-

A collection of credits.

- -
-
- Example 13 - 
<section role="doc-credits">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-credit: +
CharacteristicValue
Superclass Role: + section +
Related Concepts: + EPUB credit [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-credits (role)

+ +
+

A collection of credits.

+ +
+
+ Example 13 +
+ 
<section role="doc-credits">
    <h2>Photo Credits</h2>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-credits:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB credits - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-dedication (role)

- -
-

An inscription at the front of the work, typically addressed in tribute to one or more - persons close to the author.

- -
-
- Example 14 - 
<p role="doc-dedication">To my family, without whom this would have never been possible.</p>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-dedication:
CharacteristicValue
Superclass Role:section
Related Concepts:EPUB dedication - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-endnote (role)

- -
-

[Deprecated in DPUB-ARIA 1.1] One of a collection of notes that occur at the end of a work, - or a section within it, that provides additional context to a referenced passage of - text.

- -
Note

The doc-endnote - role was designed for use as a list item, but due to clarifications - in the WAI-ARIA specification, it is not valid as a child of the list role. As - the doc-endnotes role already identifies a section of endnotes, authors are - instead advised to use the list and listitem roles when native - HTML elements cannot be used to structure the entries.

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-endnote:
CharacteristicValue
Superclass Role:listitem
Related Concepts:EPUB rearnote - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
-
- -
-

doc-endnotes (role)

- -
-

A collection of notes at the end of a work or a section within it.

- -

The element carrying the doc-endnotes - role MUST contain at least one descendant list containing the - endnotes (if the notes are subdivided, for example by chapter, the element would contain - more than one list).

- -

User Agents MUST expose the list items in these lists using the platform accessibility API - mappings for an individual endnote.

- -

Lists nested within an endnote have no special significance. User Agents MUST NOT expose - these list items using the platform accessibility API mappings for an individual - endnote.

- -

Authors MUST NOT declare elements with the role doc-footnote within the endnotes - as it is redundant with the implied role.

- -

Authors MUST NOT apply the doc-endnotes role directly to the list containing the - endnotes.

- -
-
- Example 15 - 
<section role="doc-endnotes">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-credits: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB credits [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-dedication (role)

+ +
+

An inscription at the front of the work, typically addressed in tribute to one or more persons close to the author.

+ +
+
+ Example 14 +
+ 
<p role="doc-dedication">To my family, without whom this would have never been possible.</p>
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-dedication: +
CharacteristicValue
Superclass Role: + section +
Related Concepts: + EPUB dedication [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-endnote (role)

+ +
+

[Deprecated in DPUB-ARIA 1.1] One of a collection of notes that occur at the end of a work, or a section within it, that provides additional context to a referenced passage of text.

+ +
+
Note
+

+ The doc-endnote role was designed for use as a list item, but due to + clarifications in the WAI-ARIA specification, it is not valid as a child of the + list role. As the + doc-endnotes role already identifies a section of endnotes, authors are instead advised to use the + list and + listitem roles when native HTML elements cannot be used to structure the entries. +

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-endnote: +
CharacteristicValue
Superclass Role: + listitem +
Related Concepts: + EPUB rearnote [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
+
+ +
+

doc-endnotes (role)

+ +
+

A collection of notes at the end of a work or a section within it.

+ +

+ The element carrying the doc-endnotes role + MUST contain at least one descendant list containing the endnotes (if the notes are subdivided, for example by chapter, the element would contain more than one + list). +

+ +

+ User Agents MUST expose the list items in these lists using the platform accessibility API mappings for an + individual endnote. +

+ +

+ Lists nested within an endnote have no special significance. User Agents MUST NOT expose these list items using the platform accessibility + API mappings for an individual endnote. +

+ +

+ Authors MUST NOT declare elements with the role doc-footnote within the endnotes as it is + redundant with the implied role. +

+ +

Authors MUST NOT apply the doc-endnotes role directly to the list containing the endnotes.

+ +
+
+ Example 15 +
+ 
<section role="doc-endnotes">
    <h2>Notes</h2>
    <ol>
       <li id="6baa07af">
@@ -2371,12 +3673,16 @@ 

       …
    </ol>
 </section>
-
- -
-
- Example 16 - 
<section role="doc-endnotes">
+
+ +
+
+ Example 16 +
+ 
<section role="doc-endnotes">
    <h2>Notes</h2>
    <section>
       <h3>Canto I</h3>
@@ -2389,179 +3695,283 @@ 

    </section>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-endnotes:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB rearnotes - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-epigraph (role)

- -
-

A quotation set at the start of the work or a section that establishes the theme or sets the - mood.

- -
-
- Example 17 - 
<blockquote role="doc-epigraph">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-endnotes: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB rearnotes [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-epigraph (role)

+ +
+

A quotation set at the start of the work or a section that establishes the theme or sets the mood.

+ +
+
+ Example 17 +
+ 
<blockquote role="doc-epigraph">
    <p>“Would you tell me please, which way I ought to go from here?”</p>
    <p>“That depends a good deal on where you want to get to,” said the cat.</p>
 </blockquote>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-epigraph:
CharacteristicValue
Superclass Role:section
Related Concepts:EPUB epigraph - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-epilogue (role)

- -
-

A concluding section of narrative that wraps up or comments on the actions and events of the - work, typically from a future perspective.

- -
-
- Example 18 - 
<section role="doc-epilogue">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-epigraph: +
CharacteristicValue
Superclass Role: + section +
Related Concepts: + EPUB epigraph [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-epilogue (role)

+ +
+

A concluding section of narrative that wraps up or comments on the actions and events of the work, typically from a future perspective.

+ +
+
+ Example 18 +
+ 
<section role="doc-epilogue">
    <header>
       <h2>Epilogue</h2>
       <p>SPOKEN BY PROSPERO</p>
@@ -2569,442 +3979,701 @@ 

    <p>Now my charms are all o'erthrown, …</p>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-epilogue:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB epilogue - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-errata (role)

- -
-

A set of corrections discovered after initial publication of the work, sometimes referred to - as corrigenda.

- -
-
- Example 19 - 
<section role="doc-errata">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-epilogue: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB epilogue [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-errata (role)

+ +
+

A set of corrections discovered after initial publication of the work, sometimes referred to as corrigenda.

+ +
+
+ Example 19 +
+ 
<section role="doc-errata">
    <h2>Corrections</h2>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-errata:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB errata - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-example (role)

- -
-

An illustration of a key concept of the work, such as a code listing, case study or - problem.

- -
-
- Example 20 - 
<figure role="doc-example">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-errata: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB errata [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-example (role)

+ +
+

An illustration of a key concept of the work, such as a code listing, case study or problem.

+ +
+
+ Example 20 +
+ 
<figure role="doc-example">
    <figcaption>Example 1 — Hello World!</figcaption>
    …
 </figure>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-example:
CharacteristicValue
Superclass Role:figure
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-footnote (role)

- -
-

Ancillary information, such as a citation or commentary, that provides additional context to - a referenced passage of text.

- -

The doc-footnote - role is only for representing individual notes that occur within the - body of a work. For collections of notes that occur at the end of a section, see - doc-endnotes.

- -
-
- Example 21 - 
<aside id="6baa07af" role="doc-footnote">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-example: +
CharacteristicValue
Superclass Role: + figure +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-footnote (role)

+ +
+

Ancillary information, such as a citation or commentary, that provides additional context to a referenced passage of text.

+ +

+ The doc-footnote role is only for representing individual notes that occur + within the body of a work. For collections of notes that occur at the end of a section, see doc-endnotes. +

+ +
+
+ Example 21 +
+ 
<aside id="6baa07af" role="doc-footnote">
    * Additional results of this study and similar studies can be found at …
 </aside>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-footnote:
CharacteristicValue
Superclass Role:section
Related Concepts:EPUB footnote - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
-
- -
-

doc-foreword (role)

- -
-

An introductory section that precedes the work, typically not written by the author of the - work.

- -
-
- Example 22 - 
<section role="doc-foreword">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-footnote: +
CharacteristicValue
Superclass Role: + section +
Related Concepts: + EPUB footnote [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
+
+ +
+

doc-foreword (role)

+ +
+

An introductory section that precedes the work, typically not written by the author of the work.

+ +
+
+ Example 22 +
+ 
<section role="doc-foreword">
    <h2>Foreword</h2>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-foreword:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB foreword - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-glossary (role)

- -
-

A brief dictionary of new, uncommon, or specialized terms used in the content.

- -

The structure of a glossary SHOULD make it possible for end users to identify each term and - associated definition (e.g., using the [HTML] dfn element).

- -
-
- Example 23 - 
<section role="doc-glossary" aria-label="glossary">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-foreword: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB foreword [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-glossary (role)

+ +
+

A brief dictionary of new, uncommon, or specialized terms used in the content.

+ +

+ The structure of a glossary SHOULD make it possible for end users to identify each term and associated definition (e.g., using the [HTML] dfn element). +

+ +
+
+ Example 23 +
+ 
<section role="doc-glossary" aria-label="glossary">
    <dl>
       …
       <dt id="bcc0f155"><dfn>Credit default swap</dfn></dt>
@@ -3015,198 +4684,310 @@ 

       …
    </dl>
 </section>
-
- -
-
- Example 24 - 
<section role="doc-glossary" aria-labelledby="glosshd">
+
+ +
+
+ Example 24 +
+ 
<section role="doc-glossary" aria-labelledby="glosshd">
    <h2 id="glosshd">Glossay of Technical Terms</h2>
    <ul>
       <li id="gtt00110001"><dfn>algorithm</dfn> A set of rules …</li>
       …
    </ul>
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-glossary:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB glossary - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-glossref (role)

- -
-

A reference to a glossary definition.

- -
-
- Example 25 - 
<p>
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-glossary: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB glossary [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-glossref (role)

+ +
+

A reference to a glossary definition.

+ +
+
+ Example 25 +
+ 
<p>
    This is indicated in the cost of a
    <a href="#bcc0f155" role="doc-glossref">credit default swap</a> …
 </p>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-glossref:
CharacteristicValue
Superclass Role:link
Related Concepts:EPUB glossref - [EPUB-SSV]
Inherited States and Properties: -
Name From: -
    -
  • contents
    • -
  • author
    • -
-
Accessible Name Required:True
-
- -
-

doc-index (role)

- -
-

A navigational aid that provides a detailed list of links to key subjects, names and other - important topics covered in the work.

- -
-
- Example 26 - 
<section role="doc-index">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-glossref: +
CharacteristicValue
Superclass Role: + link +
Related Concepts: + EPUB glossref [EPUB-SSV] +
Inherited States and Properties: + +
Name From: +
    +
  • contents
    • +
  • author
    • +
+
Accessible Name Required:True
+
+ +
+

doc-index (role)

+ +
+

A navigational aid that provides a detailed list of links to key subjects, names and other important topics covered in the work.

+ +
+
+ Example 26 +
+ 
<section role="doc-index">
    <h2>Index</h2>
    <section>
       <h2>A</h2>
@@ -3217,521 +4998,857 @@ 

    </section>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-index:
CharacteristicValue
Superclass Role: - navigation -
Related Concepts:EPUB index - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-introduction (role)

- -
-

A preliminary section that typically introduces the scope or nature of the work.

- -
-
- Example 27 - 
<section role="doc-introduction">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-index: +
CharacteristicValue
Superclass Role: + navigation +
Related Concepts: + EPUB index [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-introduction (role)

+ +
+

A preliminary section that typically introduces the scope or nature of the work.

+ +
+
+ Example 27 +
+ 
<section role="doc-introduction">
    <p>Everyone has some experience with marketing … </p>
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-introduction:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB introduction [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-noteref (role)

- -
-

A reference to a footnote or endnote, typically appearing as a superscripted number or symbol - in the main body of text.

- -
-
- Example 28 - 
<p> … as studies have shown.<a href="#fn01" id="fnref01" role="doc-noteref">[1]</a></p>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-noteref:
CharacteristicValue
Superclass Role:link
Related Concepts:EPUB noteref - [EPUB-SSV]
Inherited States and Properties: -
Name From: -
    -
  • contents
    • -
  • author
    • -
-
Accessible Name Required:True
-
- -
-

doc-notice (role)

- -
-

Notifies the user of consequences that might arise from an action or event. Examples include - warnings, cautions and dangers.

- -
-
- Example 29 - 
<section role="doc-notice">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-introduction: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB introduction [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-noteref (role)

+ +
+

A reference to a footnote or endnote, typically appearing as a superscripted number or symbol in the main body of text.

+ +
+
+ Example 28 +
+ 
<p> … as studies have shown.<a href="#fn01" id="fnref01" role="doc-noteref">[1]</a></p>
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-noteref: +
CharacteristicValue
Superclass Role: + link +
Related Concepts: + EPUB noteref [EPUB-SSV] +
Inherited States and Properties: + +
Name From: +
    +
  • contents
    • +
  • author
    • +
+
Accessible Name Required:True
+
+ +
+

doc-notice (role)

+ +
+

Notifies the user of consequences that might arise from an action or event. Examples include warnings, cautions and dangers.

+ +
+
+ Example 29 +
+ 
<section role="doc-notice">
    <img src="warning.png" alt="warning icon"/>
    <p>Just because you can include a font doesn’t mean you should.
       Think carefully about readability. Also, be respectful of intellectual property.
       There are many excellent free open-source fonts available.</p>
 </section>
-
- -

Authors SHOULD include a label when the notice needs to be navigable to.

- -
-
- Example 30 - 
<div role="doc-notice" aria-label="Explosion Risk">
+
+ +

Authors SHOULD include a label when the notice needs to be navigable to.

+ +
+
+ Example 30 +
+ 
<div role="doc-notice" aria-label="Explosion Risk">
    <p><em>Danger!</em> Mixing reactive materials may cause an explosion.</p>
 </div>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-notice:
CharacteristicValue
Superclass Role:note
Related Concepts:EPUB notice - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-pagebreak (role)

- -
-

A separator denoting the position before which a break occurs between two contiguous pages in - a statically paginated version of the content.

- -

Page break locators are also commonly used to provide static markers in purely digital - publications (i.e., where no statically paginated equivalent exists). These markers provide - consistent navigation regardless of differences in font and screen size that can otherwise - affect the dynamic pagination of the content.

- -

Authors MUST ensure the name of the page break is an end user-consumable page number that - identifies the page that is beginning so that assistive technologies can announce the page - as needed (e.g., in a command to identify the current page).

- -

The page break locator MUST precede the content of the page it identifies. If a page includes - a header (doc-pageheader), the page break locator SHOULD be located before it, - even if the header includes a visible page number. The page break locator may be used with - the page number in a page header if the number precedes all other content in the header.

- -

When reproducing page break locators from a static page equivalent, it is sometimes the case - that words are hyphenated across pages. When this happens, the page break locator SHOULD be - placed either before or after the word to ensure it does not interfere with text-to-speech - playback.

- -
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-notice: +
CharacteristicValue
Superclass Role: + note +
Related Concepts: + EPUB notice [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-pagebreak (role)

+ +
+

A separator denoting the position before which a break occurs between two contiguous pages in a statically paginated version of the content.

+ +

+ Page break locators are also commonly used to provide static markers in purely digital publications (i.e., where no statically paginated equivalent exists). These markers provide + consistent navigation regardless of differences in font and screen size that can otherwise affect the dynamic pagination of the content. +

+ +

+ Authors MUST ensure the name of the page break is an end user-consumable page number that identifies the page that is beginning so that assistive technologies + can announce the page as needed (e.g., in a command to identify the current page). +

+ +

+ The page break locator MUST precede the content of the page it identifies. If a page includes a header (doc-pageheader), the page break locator SHOULD be located before it, even if the header includes a visible page number. The page break locator may be used with the page + number in a page header if the number precedes all other content in the header. +

+ +

+ When reproducing page break locators from a static page equivalent, it is sometimes the case that words are hyphenated across pages. When this happens, the page break locator + SHOULD be placed either before or after the word to ensure it does not interfere with text-to-speech playback. +

+ + -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-pagebreak:
CharacteristicValue
Superclass Role:separator
Related Concepts:EPUB pagebreak - [EPUB-SSV]
Inherited States and Properties: -
Name From: -
    -
  • contents
    • -
  • author
    • -
-
Accessible Name Required:True
Children Presentational:True
-
- -
-

doc-pagelist (role)

- -
-

A navigational aid that provides a list of links to the page breaks in the content.

- -
-
- Example 32 - 
<nav role="doc-pagelist">
+            
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-pagebreak: +
CharacteristicValue
Superclass Role: + separator +
Related Concepts: + EPUB pagebreak [EPUB-SSV] +
Inherited States and Properties: + +
Name From: +
    +
  • contents
    • +
  • author
    • +
+
Accessible Name Required:True
Children Presentational:True
+
+ +
+

doc-pagelist (role)

+ +
+

A navigational aid that provides a list of links to the page breaks in the content.

+ +
+
+ Example 32 +
+ 
<nav role="doc-pagelist">
    <h2>Pages</h2>
    <ol>
       <li><a href="chapter.xhtml#Page_1">1</a></li>
@@ -3739,279 +5856,431 @@ 

       …
    </ol>
 </nav>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-pagelist:
CharacteristicValue
Superclass Role:navigation
Related Concepts:EPUB page-list - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- - + + - -
-

doc-pageheader (role)

- -
-

A section of text appearing at the top of a page that provides context about the current work - and location within it. The page header is distinct from the body text and normally follows - a repeating template that contains (possibly truncated) items such as the document title, - current section, author name(s), and page number.

- -

The doc-pageheader role MUST be used on every instance of the page header.

- -

Assistive technologies MAY allow the user to read the document content continuously without - interruption from the page header.

- -
-
- Example 34 - 
<section role="doc-pageheader">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-pagefooter: +
CharacteristicValue
Superclass Role: + section +
Inherited States and Properties: + +
Name From:prohibited
Accessible Name Required:False
+
+ +
+

doc-pageheader (role)

+ +
+

+ A section of text appearing at the top of a page that provides context about the current work and location within it. The page header is distinct from the body text and normally follows + a repeating template that contains (possibly truncated) items such as the document title, current section, author name(s), and page number. +

+ +

The doc-pageheader role MUST be used on every instance of the page header.

+ +

Assistive technologies MAY allow the user to read the document content continuously without interruption from the page header.

+ +
+
+ Example 34 +
+ 
<section role="doc-pageheader">
    <div>War and Peace</div>
    <div>321</div>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-pageheader:
CharacteristicValue
Superclass Role:section
Inherited States and Properties: -
Name From:prohibited
Accessible Name Required:False
-
- -
-

doc-part (role)

- -
-

A major structural division in a work that contains a set of related sections dealing with a - particular subject, narrative arc, or similar encapsulated theme.

- -
-
- Example 35 - 
<section role="doc-part">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-pageheader: +
CharacteristicValue
Superclass Role: + section +
Inherited States and Properties: + +
Name From:prohibited
Accessible Name Required:False
+
+ +
+

doc-part (role)

+ +
+

A major structural division in a work that contains a set of related sections dealing with a particular subject, narrative arc, or similar encapsulated theme.

+ +
+
+ Example 35 +
+ 
<section role="doc-part">
    <h2>Part One</h2>
    <section role="doc-chapter">
       <h2>Chapter 1</h2>
@@ -4019,179 +6288,283 @@ 
do
    </section>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-part:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB part - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-preface (role)

- -
-

An introductory section that precedes the work, typically written by the author of the - work.

- -
-
- Example 36 - 
<section role="doc-preface">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-part: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB part [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-preface (role)

+ +
+

An introductory section that precedes the work, typically written by the author of the work.

+ +
+
+ Example 36 +
+ 
<section role="doc-preface">
    <h2>Introduction:A Guide to the Galaxy</h2>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-preface:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB preface - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-prologue (role)

- -
-

An introductory section that sets the background to a work, typically part of the - narrative.

- -
-
- Example 37 - 
<section role="doc-prologue">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-preface: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB preface [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-prologue (role)

+ +
+

An introductory section that sets the background to a work, typically part of the narrative.

+ +
+
+ Example 37 +
+ 
<section role="doc-prologue">
    <header>
       <h2>Prologue</h2>
       <p>Chorus</p>
@@ -4199,199 +6572,307 @@ 

    <p>Two households, both alike in dignity, …</p>
    …
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-prologue:
CharacteristicValue
Superclass Role:landmark
Related Concepts:EPUB prologue - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-pullquote (role)

- -
-

A distinctively placed or highlighted quotation from the current content designed to draw - attention to a topic or highlight a key point.

- -

Unlike a passage quoted from another source, a pullquote is a direct repetition of text in - the current document. As a result, authors must ensure that the presentational occurrence is - hidden from users of assistive technologies (e.g., using the aria-hidden - attribute).

- -

The following example shows the identification of a pullquote that will be presented - elsewhere (e.g., via a script). In this case, the pullquote is not hidden as the marked text - is not presentational.

- -
-
- Example 38 - 
<p>… I may die, but first you, my tyrant and tormentor, shall curse the sun that gazes on your misery.
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-prologue: +
CharacteristicValue
Superclass Role: + landmark +
Related Concepts: + EPUB prologue [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-pullquote (role)

+ +
+

A distinctively placed or highlighted quotation from the current content designed to draw attention to a topic or highlight a key point.

+ +

+ Unlike a passage quoted from another source, a pullquote is a direct repetition of text in the current document. As a result, authors must ensure that the presentational occurrence is + hidden from users of assistive technologies (e.g., using the aria-hidden attribute). +

+ +

+ The following example shows the identification of a pullquote that will be presented elsewhere (e.g., via a script). In this case, the pullquote is not hidden as the marked text is not + presentational. +

+ +
+
+ Example 38 +
+ 
<p>… I may die, but first you, my tyrant and tormentor, shall curse the sun that gazes on your misery.
    <span id="pq01" role="doc-pullquote">Beware, for I am fearless and therefore powerful.</span>
    I will watch with the wiliness of a snake, that I may sting with its venom. … </p>
-
- -

The next example shows a pullquote that duplicates the text. This quote is hidden because it - is for presentational purposes only.

- -
-
- Example 39 - 
<p>… Better habits pave the way to growth, and growth leads to greater happiness.</p>
+
+ +

The next example shows a pullquote that duplicates the text. This quote is hidden because it is for presentational purposes only.

+ +
+
+ Example 39 +
+ 
<p>… Better habits pave the way to growth, and growth leads to greater happiness.</p>
 <aside role="doc-pullquote" aria-hidden="true">
    Better habits pave the way to growth, and growth leads to greater happiness.
 </aside>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-pullquote:
CharacteristicValue
Superclass Role:section
Related Concepts:EPUB pullquote - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-qna (role)

- -
-

A section of content structured as a series of questions and answers, such as an interview or - list of frequently asked questions.

- -
-
- Example 40 - 
<section role="doc-qna">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-pullquote: +
CharacteristicValue
Superclass Role: + section +
Related Concepts: + EPUB pullquote [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-qna (role)

+ +
+

A section of content structured as a series of questions and answers, such as an interview or list of frequently asked questions.

+ +
+
+ Example 40 +
+ 
<section role="doc-qna">
    <h2>Interview with the Author</h2>
    <dl>
       <dt>Q: When did you begin writing this book?</dt>
@@ -4399,273 +6880,428 @@ 
doc-
       …
    </dl>
 </section>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-qna:
CharacteristicValue
Superclass Role:section
Related Concepts:EPUB qna - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-subtitle (role)

- -
-

An explanatory or alternate title for the work, or a section or component within it.

- -
-
- Example 41 - 
<header>
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-qna: +
CharacteristicValue
Superclass Role: + section +
Related Concepts: + EPUB qna [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-subtitle (role)

+ +
+

An explanatory or alternate title for the work, or a section or component within it.

+ +
+
+ Example 41 +
+ 
<header>
    <h2>Chapter 2 The Battle</h2>
    <p role="doc-subtitle">Once more unto the breach</p>
 </header>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-subtitle:
CharacteristicValue
Superclass Role:sectionhead
Related Concepts:EPUB subtitle - [EPUB-SSV]
Inherited States and Properties: -
Name From: -
    -
  • contents
    • -
  • author
    • -
-
Accessible Name Required:False
-
- -
-

doc-tip (role)

- -
-

Helpful information that clarifies some aspect of the content or assists in its - comprehension.

- -
-
- Example 42 - 
<aside role="doc-tip">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-subtitle: +
CharacteristicValue
Superclass Role: + sectionhead +
Related Concepts: + EPUB subtitle [EPUB-SSV] +
Inherited States and Properties: + +
Name From: +
    +
  • contents
    • +
  • author
    • +
+
Accessible Name Required:False
+
+ +
+

doc-tip (role)

+ +
+

Helpful information that clarifies some aspect of the content or assists in its comprehension.

+ +
+
+ Example 42 +
+ 
<aside role="doc-tip">
    <h3>Tip</h3>
    <p>You can assign a variable a new value that is the result
       of an expression involving its previous value.</p>
 </aside>
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-tip:
CharacteristicValue
Superclass Role:note
Related Concepts:EPUB help - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
- -
-

doc-toc (role)

- -
-

A navigational aid that provides an ordered list of links to the major sectional headings in - the content. A table of contents may cover an entire work, or only a smaller section of - it.

- -
-
- Example 43 - 
<nav role="doc-toc">
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-tip: +
CharacteristicValue
Superclass Role: + note +
Related Concepts: + EPUB help [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+ +
+

doc-toc (role)

+ +
+

+ A navigational aid that provides an ordered list of links to the major sectional headings in the content. A table of contents may cover an entire work, or only a smaller section of it. +

+ +
+
+ Example 43 +
+ 
<nav role="doc-toc">
    <h2>Contents</h2>
    <ol role="directory">
       <li><a href="preface_001.xhtml">Original Transcriber’s Notes:</a></li>
@@ -4675,407 +7311,566 @@ 
doc-
       …
    </ol>
 </nav>
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-toc: +
CharacteristicValue
Superclass Role: + navigation +
Related Concepts: + EPUB toc [EPUB-SSV] +
Inherited States and Properties: + +
Name From:author
Accessible Name Required:False
+
+
+
+
+
+

4. Privacy and Security Considerations

+
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-toc:
CharacteristicValue
Superclass Role:navigation
Related Concepts:EPUB toc - [EPUB-SSV]
Inherited States and Properties: -
Name From:author
Accessible Name Required:False
-
-
-
-

4. Privacy and Security Considerations

This section is non-normative.

- - -

This specification introduces no new security considerations.

- -

In accordance with Web Platform - Design Principles, this specification provides no programatic interface to determine if - information is being used by assistive technologies. However, this specificaton does allow an author to - present different information to users of assistive technologies from the information available to users - who do not use assistive technologies. This is possible using many features of the DPUB-ARIA - specification, just as this is possible using many other parts of the web technology stack. This content - disparity could be abused to perform active - fingerprinting of users of assistive technologies.

-
- -

A. Change Log

This section is non-normative.

- - -

A.1 Substantive changes since the First - Public Working Draft

- - -
    - -
  • 20-Sep-2021: Clarified ambiguities in the formatting and processing of endnote and bibliography - lists and require that the doc-footnote role not be used within endnotes. See issue 38.
    • -
-
- -

A.2 Substantive changes since the DPUB-ARIA 1.0 - Recommendation

- - - -
-
-

B. Acknowledgments

This section is non-normative.

- - -

The following people contributed to the development of this document.

- -

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

- - -
    -
  • Michael Cooper (W3C Staff)
    • -
  • Joanmarie Diggs (Igalia, S.L.)
    • -
  • Matt Garrish (DAISY Consortium)
    • -
  • James Nurthen (Adobe)
    • -
  • Tzviya Siegman (Wiley)
    • -
-
-

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.

-
- -
- - -

C. References

C.1 Normative references

- -
[EPUB-SSV]
- EPUB Structural Semantics Vocabulary. IDPF. URL: http://www.idpf.org/epub/vocab/structure/ -
[HTML]
- HTML Standard. Anne van Kesteren; Domenic Denicola; Ian Hickson; Philip Jägenstedt; Simon Pieters. WHATWG. Living Standard. URL: https://html.spec.whatwg.org/multipage/ -
[RFC2119]
- Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. IETF. March 1997. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc2119 -
[RFC8174]
- Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words. B. Leiba. IETF. May 2017. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc8174 -
-

C.2 Informative references

- -
[dpub-aam-1.0]
- Digital Publishing Accessibility API Mappings. Richard Schwerdtfeger; Joanmarie Diggs. W3C. 14 December 2017. W3C Recommendation. URL: https://www.w3.org/TR/dpub-aam-1.0/ -
[fingerprinting-guidance]
- Mitigating Browser Fingerprinting in Web Specifications. Nick Doty. W3C. 28 March 2019. W3C Working Group Note. URL: https://www.w3.org/TR/fingerprinting-guidance/ -
[infra]
- Infra Standard. Anne van Kesteren; Domenic Denicola. WHATWG. Living Standard. URL: https://infra.spec.whatwg.org/ -
[SVG2]
- Scalable Vector Graphics (SVG) 2. Amelia Bellamy-Royds; Bogdan Brinza; Chris Lilley; Dirk Schulze; David Storey; Eric Willigers. W3C. 4 October 2018. W3C Candidate Recommendation. URL: https://www.w3.org/TR/SVG2/ -
[WAI-ARIA]
- Accessible Rich Internet Applications (WAI-ARIA) 1.1. Joanmarie Diggs; Shane McCarron; Michael Cooper; Richard Schwerdtfeger; James Craig. W3C. 14 December 2017. W3C Recommendation. URL: https://www.w3.org/TR/wai-aria-1.1/ -
-
\ No newline at end of file + /** + * @param {HTMLElement} dfn + * @param {HTMLElement} panel + * @param {{ x: number, y: number }} clickPosition + */ + function displayPanel(dfn, panel, { x, y }) { + panel.hidden = false; + // distance (px) between edge of panel and the pointing triangle (caret) + const MARGIN = 20; + + const dfnRects = dfn.getClientRects(); + // Find the `top` offset when the `dfn` can be spread across multiple lines + let closestTop = 0; + let minDiff = Infinity; + for (const rect of dfnRects) { + const { top, bottom } = rect; + const diffFromClickY = Math.abs((top + bottom) / 2 - y); + if (diffFromClickY < minDiff) { + minDiff = diffFromClickY; + closestTop = top; + } + } + + const top = window.scrollY + closestTop + dfnRects[0].height; + const left = x - MARGIN; + panel.style.left = `${left}px`; + panel.style.top = `${top}px`; + + // Find if the panel is flowing out of the window + const panelRect = panel.getBoundingClientRect(); + const SCREEN_WIDTH = Math.min(window.innerWidth, window.screen.width); + if (panelRect.right > SCREEN_WIDTH) { + const newLeft = Math.max(MARGIN, x + MARGIN - panelRect.width); + const newCaretOffset = left - newLeft; + panel.style.left = `${newLeft}px`; + /** @type {HTMLElement} */ + const caret = panel.querySelector(".caret"); + caret.style.left = `${newCaretOffset}px`; + } + + // As it's a dialog, we trap focus. + // TODO: when becomes a implemented, we should really + // use that. + trapFocus(panel, dfn); + } + + /** + * @param {HTMLElement} panel + * @param {HTMLElement} dfn + * @returns + */ + function trapFocus(panel, dfn) { + /** @type NodeListOf elements */ + const anchors = panel.querySelectorAll("a[href]"); + // No need to trap focus + if (!anchors.length) return; + + // Move focus to first anchor element + const first = anchors.item(0); + first.focus(); + + const trapListener = createTrapListener(anchors, panel, dfn); + panel.addEventListener("keydown", trapListener); + + // Hiding the panel releases the trap + const mo = new MutationObserver((records) => { + const [record] = records; + const target = /** @type HTMLElement */ (record.target); + if (target.hidden) { + panel.removeEventListener("keydown", trapListener); + mo.disconnect(); + } + }); + mo.observe(panel, { attributes: true, attributeFilter: ["hidden"] }); + } + + /** + * + * @param {NodeListOf} anchors + * @param {HTMLElement} panel + * @param {HTMLElement} dfn + * @returns + */ + function createTrapListener(anchors, panel, dfn) { + const lastIndex = anchors.length - 1; + let currentIndex = 0; + return (event) => { + switch (event.key) { + // Hitting "Tab" traps us in a nice loop around elements. + case "Tab": { + event.preventDefault(); + currentIndex += event.shiftKey ? -1 : +1; + if (currentIndex < 0) { + currentIndex = lastIndex; + } else if (currentIndex > lastIndex) { + currentIndex = 0; + } + anchors.item(currentIndex).focus(); + break; + } + + // Hitting "Enter" on an anchor releases the trap. + case "Enter": + hidePanel(panel); + break; + + // Hitting "Escape" returns focus to dfn. + case "Escape": + hidePanel(panel); + dfn.focus(); + return; + } + }; + } + + /** @param {HTMLElement} panel */ + function hidePanel(panel) { + if (!panel) return; + panel.hidden = true; + panel.classList.remove("docked"); + } + })(); + + + + diff --git a/index.html b/index.html index e49076a..62f91c9 100644 --- a/index.html +++ b/index.html @@ -1,54 +1,60 @@ - + - - Digital Publishing WAI-ARIA Module 1.1 - - - - - - - - - + + + + + + + - - -
-

Enabling users of assistive technologies to find their way through web content requires embedding - semantic metadata about web document structural divisions. This is particularly important for structural - divisions of long-form documents and goes along with embedding semantic metadata about web-application - widgets and behaviors for assistive technologies. This specification defines a set of WAI-ARIA roles - specific to helping users of assistive technologies navigate through such long-form documents.

- -

This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

-
-
-

Feature development for this version is complete. This is a Candidate Recommendation Draft published to obtain - implementation feedback before finalization of the specification.

-

While feedback on any aspect of the specification is encouraged, we would particularly like feedback on - the addition of the doc-pageheader and doc-pagefooter roles.

-

There have been only minor clarifications since the First Public Working - Draft.

-
-
-
-

Introduction

- -

WAI-ARIA is a technical specification that - defines a common host language semantic accessibility API and framework that enables web browsers to map - the accessibility semantics in web content to platform-specific accessibility APIs. This enables web - content to be interoperable with platform assistive technologies similar to native platform applications - without platform dependencies.

- -

This specification is a modular extension of WAI-ARIA designed for the digital publishing industry. The goals of this specification - include:

- -
    -
  • Expanding [[WAI-ARIA]] to produce structural semantic extensions to accommodate the digital - publishing industry.
    • -
  • Align with a new governance model for modularization and extensions to WAI-ARIA.
    • -
  • Provide structural semantics extensions that will support both assistive technologies and enable - semantic navigation, styling and interactive features used by readers.
    • -
- -

The roles defined in this specification are derived from the EPUB Structural Semantics Vocabulary.

- -

For a more detailed explanation of WAI-ARIA - please refer to the WAI-ARIA Introduction and how it - applies to Rich Internet Application Accessibility.

- -
-

Target Audience

- -

This specification defines a module of WAI-ARIA for digital publishing, including [=roles=], [=states=], [=ARIA/properties=] - and values. It impacts several audiences:

- -
    -
  • [=User agents=] that process content containing WAI-ARIA and Digital Publishing WAI-ARIA features;
    • -
  • [=assistive technology|Assistive technologies=] that provide specialized reading experiences to - users with disabilities;
    • -
  • Authors of digital publications;
    • -
  • Authoring tools that help authors create conforming digital publications; and
    • -
  • Conformance checkers, that verify appropriate use of WAI-ARIA and this Digital Publishing - WAI-ARIA module.
    • -
- -

Each conformance requirement indicates the audience to which it applies.

- -

Although this specification is applicable to the above audiences, it is not specifically targeted to, - nor is it intended to be the sole source of information for, any of these audiences. In the future, - additional documents will be created to assist authors in applying these WAI-ARIA semantics for the publishing - industry and to define how the information in this document is mapped to platform accessibility - APIs.

-
- -
-

User Agent Support

- -

This module builds on the general User Agent - support principles defined in [[WAI-ARIA]] by also providing the ability for user agents to - enhance the general user interface presented to readers.

-
- -
-

Co-Evolution of WAI-ARIA and Host - Languages

- -

The Digital Publishing WAI-ARIA module - follows the model for co-evolution of - WAI-ARIA and host languages - defined in [[WAI-ARIA]]. It is intended to augment semantics in supporting languages like [[HTML]], - [[SVG2]] and EPUB, or to be used as an accessibility enhancement technology in other markup-based - languages that do not explicitly include support for ARIA. It clarifies semantics to assistive - technologies when authors create new types of objects, via style and script, that are not yet - directly supported by the language of the page, because the invention of new types of objects is - faster than standardized support for them appears in web languages.

- -

It is not appropriate to create objects with style and script when the host language provides a - semantic element for that type of objects. While WAI-ARIA can improve the accessibility of these objects, accessibility is best provided - by allowing the user agent to handle the object natively. For example, it is not better to use a - heading role on a div element than it is to use a native heading - element, such as an h1.

- -

It is expected that, over time, host languages will evolve to provide semantics for objects that - currently can only be declared with this specification. This is natural and desirable, as one goal - of WAI-ARIA is to help stimulate the - emergence of more semantic and accessible markup. When native semantics for a given feature become - available, it is appropriate for authors to use the native feature and stop using this module for - that feature. Legacy content may continue to use the Digital Publishing WAI-ARIA module, however, so the need for - user agents to support it remains.

- -

While specific features of this module may lose importance over time, the general possibility of the - Digital Publishing WAI-ARIA module to add - semantics to web pages or open web-based standards, such as EPUB, is expected to be a persistent - need. Host languages may not implement all the semantics this module provides, and various host - languages may implement different subsets of the features. New types of objects are continually - being developed, and one goal of this specification is to provide a way to make such objects - accessible, because authoring practices often advance faster than host language standards. In this - way, this module and host languages both evolve together but at different rates.

- -

Some host languages exist to create semantics for features other than the user interface. For - example, SVG expresses the semantics behind production of graphical objects, not of user interface - components that those objects may represent. Host languages such as these might, by design, not - provide native semantics that map to this specification's features. In these cases, the Digital - Publishing WAI-ARIA module could be - adopted as a long-term approach to add semantic information to these host languages.

-
- -
-

Authoring Practices

- -
-

Authoring Tools

- -

Many of the requirements in the definitions of the WAI-ARIA and Digital Publishing WAI-ARIA [=roles=], [=states=] and - [=ARIA/properties=] can be checked automatically during the development process, similar to - other quality control processes used for validating code. To assist authors who are creating - digital publications, such as EPUB, can compare the semantic structure of Digital Publishing - WAI-ARIA roles from the DOM to that defined in this specification and notify - the author of errors or simply create templates that enforce that structure.

-
- -
-

Testing Practices and Tools

- -

The accessibility of interactive content cannot be confirmed by static checks alone. Developers - of interactive content should test for device-independent access to widgets and applications, and should verify accessibility API access to all content and changes during - user interaction.

-
-
- -
-

Assistive Technologies

- -

Programmatic access to accessibility semantics is essential for assistive technologies. For more - information, refer to the Assistive - Technologies section in [[WAI-ARIA]].

-
-
-
-

Normative sections provide requirements that authors, user agents and assistive technologies MUST follow - for an implementation to conform to this specification.

- -

Non-normative 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 to - conform to this specification.

-
-
-

Digital Publishing Roles

- -

This section defines additions to the WAI-ARIA - roles model and describes the characteristics and properties of all roles. See ARIA Roles for - descriptions of the fields provided by this module.

- -
-

Definition of Roles

- -

Below is an alphabetical list of WAI-ARIA - roles to be used by rich internet application authors.

- -

Placeholder for compact list of roles

- -
- doc-abstract - -
-

A short summary of the principal ideas, concepts, and conclusions of the work, or of a - section or excerpt within it.

- - 
<section role="doc-abstract" aria-label="Abstract">
+        copyrightStart: "2015",
+        processVersion: 2018,
+        github: "w3c/dpub-aria",
+        doJsonLd: true,
+        trace: true,
+        maxTocLevel: 4,
+
+        dpubModURLs: {
+          ED: "",
+          WD: "",
+          CRD: "",
+          REC: "",
+        },
+        ariaSpecURLs: {
+          ED: "https://w3c.github.io/aria/",
+          WD: "https://www.w3.org/TR/wai-aria-1.1/",
+          CRD: "https://www.w3.org/TR/wai-aria-1.1/",
+          REC: "https://www.w3.org/TR/wai-aria-1.1/",
+        },
+        accNameURLs: {
+          ED: "https://w3c.github.io/accname/",
+          WD: "https://www.w3.org/TR/accname-aam-1.2/",
+          FPWD: "https://www.w3.org/TR/accname-aam-1.2/",
+          CRD: "https://www.w3.org/TR/accname-aam-1.2/",
+          REC: "https://www.w3.org/TR/accname-aam-1.2/",
+        },
+        coreMappingURLs: {
+          ED: "https://w3c.github.io/core-aam/",
+          WD: "https://www.w3.org/TR/core-aam-1.2/",
+          FPWD: "https://www.w3.org/TR/core-aam-1.2/",
+          CRD: "https://www.w3.org/TR/core-aam-1.2/",
+          REC: "https://www.w3.org/TR/core-aam-1.2/",
+        },
+        practicesURLs: {
+          ED: "https://w3c.github.io/aria-practices/",
+          WD: "https://www.w3.org/TR/wai-aria-practices-1.2/",
+          FPWD: "https://www.w3.org/TR/wai-aria-practices-1.2/",
+          CRD: "https://www.w3.org/TR/wai-aria-practices-1.2/",
+          REC: "https://www.w3.org/TR/wai-aria-practices-1.2/",
+        },
+        preProcess: [linkCrossReferences],
+        postProcess: [ariaAttributeReferences],
+        definitionMap: [],
+        xref: ["core-aam", "accname", "wai-aria", "dom", "infra"],
+      };
+    
+  
+  
+    

+      

+        Enabling users of assistive technologies to find their way through web content requires embedding semantic metadata about web document structural divisions. This is particularly important for
+        structural divisions of long-form documents and goes along with embedding semantic metadata about web-application widgets and behaviors for assistive technologies. This specification defines a
+        set of WAI-ARIA roles specific to helping users of assistive technologies navigate through such long-form documents.
+      

+
+      
This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

+    

+    

+      
Feature development for this version is complete. This is a Candidate Recommendation Draft published to obtain implementation feedback before finalization of the specification.

+      

+        While feedback on any aspect of the specification is encouraged, we would particularly like feedback on the addition of the doc-pageheader and doc-pagefooter roles.
+      

+      
There have been only minor clarifications since the First Public Working Draft.

+    

+    

+    

+      
Introduction

+
+      

+        WAI-ARIA is a technical specification that defines a common host language semantic accessibility API and framework that enables web
+        browsers to map the accessibility semantics in web content to platform-specific accessibility APIs. This enables web content to be interoperable with platform assistive technologies similar to
+        native platform applications without platform dependencies.
+      

+
+      

+        This specification is a modular extension of WAI-ARIA designed for the digital publishing industry. The goals of this specification
+        include:
+      

+
+      
    
+        
  • Expanding [[WAI-ARIA]] to produce structural semantic extensions to accommodate the digital publishing industry.
    • 
+        
  • Align with a new governance model for modularization and extensions to WAI-ARIA.
    • 
+        
  • Provide structural semantics extensions that will support both assistive technologies and enable semantic navigation, styling and interactive features used by readers.
    • 
+      

+
+      
The roles defined in this specification are derived from the EPUB Structural Semantics Vocabulary.

+
+      

+        For a more detailed explanation of WAI-ARIA please refer to the
+        WAI-ARIA Introduction and how it applies to Rich Internet Application Accessibility.
+      

+
+      

+        
Target Audience

+
+        

+          This specification defines a module of WAI-ARIA for digital publishing, including [=roles=], [=states=], [=ARIA/properties=] and
+          values. It impacts several audiences:
+        

+
+        
    
+          
  • 
+            [=User agents=] that process content containing WAI-ARIA and Digital Publishing
+            WAI-ARIA features;
+          
    • 
+          
  • [=assistive technology|Assistive technologies=] that provide specialized reading experiences to users with disabilities;
    • 
+          
  • Authors of digital publications;
    • 
+          
  • Authoring tools that help authors create conforming digital publications; and
    • 
+          
  • 
+            Conformance checkers, that verify appropriate use of WAI-ARIA and this Digital Publishing
+            WAI-ARIA module.
+          
    • 
+        

+
+        
Each conformance requirement indicates the audience to which it applies.

+
+        

+          Although this specification is applicable to the above audiences, it is not specifically targeted to, nor is it intended to be the sole source of information for, any of these audiences. In
+          the future, additional documents will be created to assist authors in applying these WAI-ARIA semantics for the publishing industry
+          and to define how the information in this document is mapped to platform accessibility APIs.
+        

+      

+
+      

+        
User Agent Support

+
+        

+          This module builds on the general User Agent support principles defined in [[WAI-ARIA]] by also providing the ability for user
+          agents to enhance the general user interface presented to readers.
+        

+      

+
+      

+        
Co-Evolution of WAI-ARIA and Host Languages

+
+        

+          The Digital Publishing WAI-ARIA module follows the model for
+          co-evolution of WAI-ARIA and host languages defined in [[WAI-ARIA]].
+          It is intended to augment semantics in supporting languages like [[HTML]], [[SVG2]] and EPUB, or to be used as an accessibility enhancement technology in other markup-based languages that do
+          not explicitly include support for ARIA. It clarifies semantics to assistive technologies when authors create new types of objects, via style and script, that are not yet directly supported
+          by the language of the page, because the invention of new types of objects is faster than standardized support for them appears in web languages.
+        

+
+        

+          It is not appropriate to create objects with style and script when the host language provides a semantic element for that type of objects. While
+          WAI-ARIA can improve the accessibility of these objects, accessibility is best provided by allowing the user agent to handle the
+          object natively. For example, it is not better to use a heading role on a div element than it is to use a native heading element, such as an h1.
+        

+
+        

+          It is expected that, over time, host languages will evolve to provide semantics for objects that currently can only be declared with this specification. This is natural and desirable, as one
+          goal of WAI-ARIA is to help stimulate the emergence of more semantic and accessible markup. When native semantics for a given
+          feature become available, it is appropriate for authors to use the native feature and stop using this module for that feature. Legacy content may continue to use the Digital Publishing
+          WAI-ARIA module, however, so the need for user agents to support it remains.
+        

+
+        

+          While specific features of this module may lose importance over time, the general possibility of the Digital Publishing
+          WAI-ARIA module to add semantics to web pages or open web-based standards, such as EPUB, is expected to be a persistent need. Host
+          languages may not implement all the semantics this module provides, and various host languages may implement different subsets of the features. New types of objects are continually being
+          developed, and one goal of this specification is to provide a way to make such objects accessible, because authoring practices often advance faster than host language standards. In this way,
+          this module and host languages both evolve together but at different rates.
+        

+
+        

+          Some host languages exist to create semantics for features other than the user interface. For example, SVG expresses the semantics behind production of graphical objects, not of user
+          interface components that those objects may represent. Host languages such as these might, by design, not provide native semantics that map to this specification's features. In these cases,
+          the Digital Publishing WAI-ARIA module could be adopted as a long-term approach to add semantic information to these host
+          languages.
+        

+      

+
+      

+        
Authoring Practices

+
+        

+          
Authoring Tools

+
+          

+            Many of the requirements in the definitions of the WAI-ARIA and Digital Publishing
+            WAI-ARIA [=roles=], [=states=] and [=ARIA/properties=] can be checked automatically during the development process, similar to
+            other quality control processes used for validating code. To assist authors who are creating digital publications, such as EPUB, can compare the semantic structure of Digital Publishing
+            WAI-ARIA roles from the DOM to that defined in this specification and notify the
+            author of errors or simply create templates that enforce that structure.
+          

+        

+
+        

+          
Testing Practices and Tools

+
+          

+            The accessibility of interactive content cannot be confirmed by static checks alone. Developers of interactive content should test for device-independent access to
+            widgets and applications, and should verify accessibility API access to all content and changes during user
+            interaction.
+          

+        

+      

+
+      

+        
Assistive Technologies

+
+        

+          Programmatic access to accessibility semantics is essential for assistive technologies. For more information, refer to the
+          Assistive Technologies section in [[WAI-ARIA]].
+        

+      

+    

+    

+      
Normative sections provide requirements that authors, user agents and assistive technologies MUST follow for an implementation to conform to this specification.

+
+      

+        Non-normative 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 to conform to this specification.
+      

+    

+    

+      
Digital Publishing Roles

+
+      

+        This section defines additions to the WAI-ARIA roles model and describes the characteristics and properties of
+        all roles. See ARIA Roles for descriptions of the fields provided by this module.
+      

+
+      

+        
Definition of Roles

+
+        

+          Below is an alphabetical list of WAI-ARIA roles to be used by rich internet application
+          authors.
+        

+
+        
Placeholder for compact list of roles

+
+        

+          doc-abstract
+
+          

+            
A short summary of the principal ideas, concepts, and conclusions of the work, or of a section or excerpt within it.

+
+            
+<section role="doc-abstract" aria-label="Abstract">
    <p>Accessibility of web content requires semantic information about widgets, structures,
       and behaviors …</p>
-</section>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-abstract:
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB abstract
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-acknowledgments
-
-					

-						
A section or statement that acknowledges significant contributions by persons, organizations,
-							governments, and other entities to the realization of the work.

-
-						
<section role="doc-acknowledgments">
+</section>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-abstract:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB abstract [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-acknowledgments
+
+          

+            
A section or statement that acknowledges significant contributions by persons, organizations, governments, and other entities to the realization of the work.

+
+            
+<section role="doc-acknowledgments">
    <p>I would like to extend my sincere gratitude to … </p>
-</section>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-acknowledgments:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB acknowledgments [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-afterword
-
-					

-						
A closing statement from the author or a person of importance, typically providing insight
-							into how the content came to be written, its significance, or related events that have
-							transpired since its timeline.

-
-						
<section role="doc-afterword">
+</section>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-acknowledgments:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB acknowledgments [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-afterword
+
+          

+            

+              A closing statement from the author or a person of importance, typically providing insight into how the content came to be written, its significance, or related events that have
+              transpired since its timeline.
+            

+
+            
+<section role="doc-afterword">
    <h2>Afterword: Why I Wrote This Book</h2>
    …
-</section>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-afterword:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB afterword
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-appendix
-
-					

-						
A section of supplemental information located after the primary content that informs the
-							content but is not central to it.

-
-						
<section role="doc-appendix">
+</section>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-afterword:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB afterword [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-appendix
+
+          

+            
A section of supplemental information located after the primary content that informs the content but is not central to it.

+
+            
+<section role="doc-appendix">
    <h2>Appendix A. Historical Timeline</h2>
    …
-</section>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-appendix:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB appendix
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements: 
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-backlink
-
-					

-						
A link that allows the user to return to a related location in the content (e.g., from a
-							footnote to its reference or from a glossary definition to where a term is used).

-
-						
<aside id="fn01" role="doc-footnote">
+</section>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-appendix:
+            
CharacteristicValue
Is Abstract:
Superclass Role:landmark
Subclass Roles:
Base Concept:
Related Concepts:EPUB appendix [[EPUB-SSV]]
Required Context Role:
Required Owned Elements:
Required States and Properties:
Supported States and Properties:
Inherited States and Properties:
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational:
Implicit Value for Role:

+        

+
+        

+          doc-backlink
+
+          

+            
A link that allows the user to return to a related location in the content (e.g., from a footnote to its reference or from a glossary definition to where a term is used).

+
+            
+<aside id="fn01" role="doc-footnote">
    <a role="doc-backlink" href="#fnref01">1.</a>
    Additional results of this study and
    similar studies can be found at …
-</aside>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-backlink:
CharacteristicValue
Is Abstract: 
Superclass Role:link
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB referrer
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:
-									
    
-										
  • contents
    • 
-										
  • author
    • 
-									

-								
Accessible Name Required:True
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-biblioentry
-
-					

-						
[Deprecated in DPUB-ARIA 1.1] A single reference to an external source in a bibliography. A
-							biblioentry typically provides more detailed information than its reference(s) in the
-							content (e.g., full title, author(s), publisher, publication date, etc.).

-
-						
The doc-biblioentry
-							role was designed for use as a list item, but due to clarifications in the WAI-ARIA
-							specification, it is not valid as a child of the list role. As the
-								doc-bibliography role already identifies a section of bibliography entries,
-							authors are instead advised to use the list and listitem roles
-							when native HTML elements cannot be used to structure the entries.

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-biblioentry:
CharacteristicValue
Is Abstract: 
Superclass Role: 
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB biblioentry
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:True
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-bibliography
-
-					

-						
A list of external references cited in the work, which may be to print or digital
-							sources.

-
-						
The element carrying the doc-bibliography
-							role MUST contain at least one descendant list containing the
-							bibliography entries (if the entries are subdivided, for example alphabetically, the element
-							would contain more than one list).

-
-						
User Agents MUST expose the list items in these lists using the platform accessibility API
-							mappings for an individual entry.

-
-						
Lists nested within an entry have no special significance. User Agents MUST NOT expose these
-							list items using the platform accessibility API mappings for an individual entry.

-
-						
Authors MUST NOT apply the doc-bibliography role directly to the list containing
-							the entries.

-
-						
<section role="doc-bibliography">
+</aside>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-backlink:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:link
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB referrer [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:
+                  
    
+                    
  • contents
    • 
+                    
  • author
    • 
+                  

+                
Accessible Name Required:True
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-biblioentry
+
+          

+            

+              [Deprecated in DPUB-ARIA 1.1] A single reference to an external source in a bibliography. A biblioentry typically provides more detailed information than its reference(s) in the content
+              (e.g., full title, author(s), publisher, publication date, etc.).
+            

+
+            

+              The doc-biblioentry role was designed for use as a list item, but due to clarifications in the WAI-ARIA specification, it is not valid as a child of the
+              list role. As the doc-bibliography role already identifies a section of bibliography entries, authors are instead advised to use the list and
+              listitem roles when native HTML elements cannot be used to structure the entries.
+            

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-biblioentry:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB biblioentry [[EPUB-SSV]]
Required Context Role:
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:True
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-bibliography
+
+          

+            
A list of external references cited in the work, which may be to print or digital sources.

+
+            

+              The element carrying the doc-bibliography role MUST contain at least one descendant list containing the bibliography entries (if the entries are
+              subdivided, for example alphabetically, the element would contain more than one list).
+            

+
+            
User Agents MUST expose the list items in these lists using the platform accessibility API mappings for an individual entry.

+
+            
Lists nested within an entry have no special significance. User Agents MUST NOT expose these list items using the platform accessibility API mappings for an individual entry.

+
+            
Authors MUST NOT apply the doc-bibliography role directly to the list containing the entries.

+
+            
+<section role="doc-bibliography">
    <h2>Select Bibliography</h2>
    <ul>
       …
    </ul>
-</section>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-bibliography:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB bibliography [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements: 
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-biblioref
-
-					

-						
A reference to a bibliography entry.

-
-						
<p>
+</section>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-bibliography:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB bibliography [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-biblioref
+
+          

+            
A reference to a bibliography entry.

+
+            
+<p>
    As <a role="doc-biblioref"
       href="#b8cab5dd-bc24-459c-9858-7afa9da69b64">Steinbeck</a>
    says in his great novel …
-</p>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-biblioref:
CharacteristicValue
Is Abstract: 
Superclass Role:link
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB biblioref
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:
-									
    
-										
  • contents
    • 
-										
  • author
    • 
-									

-								
Accessible Name Required:True
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-chapter
-
-					

-						
A major thematic section of content in a work.

-
-						
<section role="doc-chapter">
+</p>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-biblioref:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:link
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB biblioref [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:
+                  
    
+                    
  • contents
    • 
+                    
  • author
    • 
+                  

+                
Accessible Name Required:True
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-chapter
+
+          

+            
A major thematic section of content in a work.

+
+            
+<section role="doc-chapter">
    <h2>Chapter 1. Loomings.</h2>
    …
-</section>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-chapter:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB chapter
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-colophon
-
-					

-						
A short section of production notes particular to the edition (e.g., describing the typeface
-							used), often located at the end of a work.

-
-						
<section role="doc-colophon" aria-label="About the type">
+</section>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-chapter:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB chapter [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-colophon
+
+          

+            
A short section of production notes particular to the edition (e.g., describing the typeface used), often located at the end of a work.

+
+            
+<section role="doc-colophon" aria-label="About the type">
    <p>This publication was set using … </p>
-</section>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-colophon:
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB colophon
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-conclusion
-
-					

-						
A concluding section or statement that summarizes the work or wraps up the narrative.

-
-						
<section role="doc-conclusion">
+</section>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-colophon:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB colophon [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-conclusion
+
+          

+            
A concluding section or statement that summarizes the work or wraps up the narrative.

+
+            
+<section role="doc-conclusion">
    <h2>Summary</h2>
    <p>A central task in feminist scholarship is to expose and dismantle the stereotypes … </p>
-</section>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-conclusion:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB conclusion
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-cover
-
-					

-						
An image that sets the mood or tone for the work and typically includes the title and
-							author.

-
-						
<img role="doc-cover" src="coverimage.jpg" alt="A Room of One's Own by Virginia Woolf"/>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-cover:
CharacteristicValue
Is Abstract: 
Superclass Role:img
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB cover
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-credit
-
-					

-						
An acknowledgment of the source of integrated content from third-party sources, such as
-							photos. Typically identifies the creator, copyright, and any restrictions on reuse.

-
-						
<p role="doc-credit">
+</section>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-conclusion:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB conclusion [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-cover
+
+          

+            
An image that sets the mood or tone for the work and typically includes the title and author.

+
+            
<img role="doc-cover" src="coverimage.jpg" alt="A Room of One's Own by Virginia Woolf"/>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-cover:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:img
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB cover [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-credit
+
+          

+            
An acknowledgment of the source of integrated content from third-party sources, such as photos. Typically identifies the creator, copyright, and any restrictions on reuse.

+
+            
+<p role="doc-credit">
    Page 62, Table 3.1 from <cite>“Economic Foundations of Cost-Effectiveness Analysis”</cite>
    by A. M. Garber and C. E. Phelps …
-</p>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-credit:
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB credit
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-credits
-
-					

-						
A collection of credits.

-
-						
<section role="doc-credits">
+</p>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-credit:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB credit [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-credits
+
+          

+            
A collection of credits.

+
+            
+<section role="doc-credits">
    <h2>Photo Credits</h2>
    …
-</section>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-credits:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB credits
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-dedication
-
-					

-						
An inscription at the front of the work, typically addressed in tribute to one or more
-							persons close to the author.

-
-						
<p role="doc-dedication">To my family, without whom this would have never been possible.</p>

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-dedication:
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB dedication
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-endnote
-
-					

-						
[Deprecated in DPUB-ARIA 1.1] One of a collection of notes that occur at the end of a work,
-							or a section within it, that provides additional context to a referenced passage of
-							text.

-
-						
The doc-endnote
-							role was designed for use as a list item, but due to clarifications
-							in the WAI-ARIA specification, it is not valid as a child of the list role. As
-							the doc-endnotes role already identifies a section of endnotes, authors are
-							instead advised to use the list and listitem roles when native
-							HTML elements cannot be used to structure the entries.

-					

-
-					
-						
-						
-							
-								
-								
-							
-						
-						
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-							
-								
-								
-							
-						
-					
Characteristics of doc-endnote:
CharacteristicValue
Is Abstract: 
Superclass Role:listitem
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB rearnote
-									[[EPUB-SSV]]
Required Context Role: 
Required Owned Elements: 
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required: 
Inherits Name Required: 
Children Presentational: 
Inherits Presentational: 
Implicit Value for Role: 

-				

-
-				

-					doc-endnotes
-
-					

-						
A collection of notes at the end of a work or a section within it.

-
-						
The element carrying the doc-endnotes
-							role MUST contain at least one descendant list containing the
-							endnotes (if the notes are subdivided, for example by chapter, the element would contain
-							more than one list).

-
-						
User Agents MUST expose the list items in these lists using the platform accessibility API
-							mappings for an individual endnote.

-
-						
Lists nested within an endnote have no special significance. User Agents MUST NOT expose
-							these list items using the platform accessibility API mappings for an individual
-							endnote.

-
-						
Authors MUST NOT declare elements with the role doc-footnote within the endnotes
-							as it is redundant with the implied role.

-
-						
Authors MUST NOT apply the doc-endnotes role directly to the list containing the
-							endnotes.

-
-						
<section role="doc-endnotes">
+</section>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-credits:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB credits [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-dedication
+
+          

+            
An inscription at the front of the work, typically addressed in tribute to one or more persons close to the author.

+
+            
<p role="doc-dedication">To my family, without whom this would have never been possible.</p>

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-dedication:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB dedication [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-endnote
+
+          

+            
[Deprecated in DPUB-ARIA 1.1] One of a collection of notes that occur at the end of a work, or a section within it, that provides additional context to a referenced passage of text.

+
+            

+              The doc-endnote role was designed for use as a list item, but due to clarifications in the WAI-ARIA specification, it is not valid as a child of the
+              list role. As the doc-endnotes role already identifies a section of endnotes, authors are instead advised to use the list and
+              listitem roles when native HTML elements cannot be used to structure the entries.
+            

+          

+
+          
+            
+            
+              
+                
+                
+              
+            
+            
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+              
+                
+                
+              
+            
+          

+              Characteristics of
+              doc-endnote:
+            
CharacteristicValue
Is Abstract: 
Superclass Role:listitem
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB rearnote [[EPUB-SSV]]
Required Context Role:
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required: 
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 

+        

+
+        

+          doc-endnotes
+
+          

+            
A collection of notes at the end of a work or a section within it.

+
+            

+              The element carrying the doc-endnotes role MUST contain at least one descendant list containing the endnotes (if the notes are subdivided, for example
+              by chapter, the element would contain more than one list).
+            

+
+            
User Agents MUST expose the list items in these lists using the platform accessibility API mappings for an individual endnote.

+
+            
Lists nested within an endnote have no special significance. User Agents MUST NOT expose these list items using the platform accessibility API mappings for an individual endnote.

+
+            
Authors MUST NOT declare elements with the role doc-footnote within the endnotes as it is redundant with the implied role.

+
+            
Authors MUST NOT apply the doc-endnotes role directly to the list containing the endnotes.

+
+            
+<section role="doc-endnotes">
    <h2>Notes</h2>
    <ol>
       <li id="6baa07af">
@@ -1834,9 +1871,11 @@ 
Definition of Roles

       </li>
       …
    </ol>
-</section>

+</section>
- 
<section role="doc-endnotes">
+            
+<section role="doc-endnotes">
    <h2>Notes</h2>
    <section>
       <h3>Canto I</h3>
@@ -1848,656 +1887,679 @@ 
Definition of Roles

       </div>
    </section>
    …
-</section>

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-endnotes:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB rearnotes - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-epigraph - -
-

A quotation set at the start of the work or a section that establishes the theme or sets the - mood.

- - 
<blockquote role="doc-epigraph">
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-endnotes: +
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB rearnotes [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-epigraph + +
+

A quotation set at the start of the work or a section that establishes the theme or sets the mood.

+ + 
+<blockquote role="doc-epigraph">
    <p>“Would you tell me please, which way I ought to go from here?”</p>
    <p>“That depends a good deal on where you want to get to,” said the cat.</p>
-</blockquote>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-epigraph:
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB epigraph - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-epilogue - -
-

A concluding section of narrative that wraps up or comments on the actions and events of the - work, typically from a future perspective.

- - 
<section role="doc-epilogue">
+</blockquote>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-epigraph: +
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB epigraph [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-epilogue + +
+

A concluding section of narrative that wraps up or comments on the actions and events of the work, typically from a future perspective.

+ + 
+<section role="doc-epilogue">
    <header>
       <h2>Epilogue</h2>
       <p>SPOKEN BY PROSPERO</p>
    </header>
    <p>Now my charms are all o'erthrown, …</p>
    …
-</section>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-epilogue:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB epilogue - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-errata - -
-

A set of corrections discovered after initial publication of the work, sometimes referred to - as corrigenda.

- - 
<section role="doc-errata">
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-epilogue: +
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB epilogue [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-errata + +
+

A set of corrections discovered after initial publication of the work, sometimes referred to as corrigenda.

+ + 
+<section role="doc-errata">
    <h2>Corrections</h2>
    …
-</section>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-errata:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB errata - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-example - -
-

An illustration of a key concept of the work, such as a code listing, case study or - problem.

- - 
<figure role="doc-example">
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-errata: +
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB errata [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-example + +
+

An illustration of a key concept of the work, such as a code listing, case study or problem.

+ + 
+<figure role="doc-example">
    <figcaption>Example 1 — Hello World!</figcaption>
    …
-</figure>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-example:
CharacteristicValue
Is Abstract: 
Superclass Role:figure
Subclass Roles: 
Base Concept: 
Related Concepts:
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-footnote - -
-

Ancillary information, such as a citation or commentary, that provides additional context to - a referenced passage of text.

- -

The doc-footnote - role is only for representing individual notes that occur within the - body of a work. For collections of notes that occur at the end of a section, see - doc-endnotes.

- - 
<aside id="6baa07af" role="doc-footnote">
+</figure>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-example: +
CharacteristicValue
Is Abstract: 
Superclass Role:figure
Subclass Roles: 
Base Concept: 
Related Concepts:
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-footnote + +
+

Ancillary information, such as a citation or commentary, that provides additional context to a referenced passage of text.

+ +

+ The doc-footnote role is only for representing individual notes that occur within the body of a work. For collections of notes that occur at the end + of a section, see doc-endnotes. +

+ + 
+<aside id="6baa07af" role="doc-footnote">
    * Additional results of this study and similar studies can be found at …
-</aside>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-footnote:
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB footnote - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required: 
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-foreword - -
-

An introductory section that precedes the work, typically not written by the author of the - work.

- - 
<section role="doc-foreword">
+</aside>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-footnote: +
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB footnote [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required: 
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-foreword + +
+

An introductory section that precedes the work, typically not written by the author of the work.

+ + 
+<section role="doc-foreword">
    <h2>Foreword</h2>
    …
-</section>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-foreword:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB foreword - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-glossary - -
-

A brief dictionary of new, uncommon, or specialized terms used in the content.

- -

The structure of a glossary SHOULD make it possible for end users to identify each term and - associated definition (e.g., using the [[HTML]] dfn element).

- - 
<section role="doc-glossary" aria-label="glossary">
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-foreword: +
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB foreword [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-glossary + +
+

A brief dictionary of new, uncommon, or specialized terms used in the content.

+ +

The structure of a glossary SHOULD make it possible for end users to identify each term and associated definition (e.g., using the [[HTML]] dfn element).

+ + 
+<section role="doc-glossary" aria-label="glossary">
    <dl>
       …
       <dt id="bcc0f155"><dfn>Credit default swap</dfn></dt>
@@ -2507,200 +2569,209 @@ 
Definition of Roles

       </dd>
       …
    </dl>
-</section>
+</section> - 
<section role="doc-glossary" aria-labelledby="glosshd">
+            
+<section role="doc-glossary" aria-labelledby="glosshd">
    <h2 id="glosshd">Glossay of Technical Terms</h2>
    <ul>
       <li id="gtt00110001"><dfn>algorithm</dfn> A set of rules …</li>
       …
    </ul>
-</section>

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-glossary:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB glossary - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-glossref - -
-

A reference to a glossary definition.

- - 
<p>
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-glossary: +
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB glossary [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-glossref + +
+

A reference to a glossary definition.

+ + 
+<p>
    This is indicated in the cost of a
    <a href="#bcc0f155" role="doc-glossref">credit default swap</a> …
-</p>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-glossref:
CharacteristicValue
Is Abstract: 
Superclass Role:link
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB glossref - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From: -
    -
  • contents
    • -
  • author
    • -
-
Accessible Name Required:True
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-index - -
-

A navigational aid that provides a detailed list of links to key subjects, names and other - important topics covered in the work.

- - 
<section role="doc-index">
+</p>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-glossref: +
CharacteristicValue
Is Abstract: 
Superclass Role:link
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB glossref [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From: +
    +
  • contents
    • +
  • author
    • +
+
Accessible Name Required:True
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-index + +
+

A navigational aid that provides a detailed list of links to key subjects, names and other important topics covered in the work.

+ + 
+<section role="doc-index">
    <h2>Index</h2>
    <section>
       <h2>A</h2>
@@ -2710,1479 +2781,1535 @@ 
Definition of Roles

       </ul>
    </section>
    …
-</section>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-index:
CharacteristicValue
Is Abstract: 
Superclass Role: - navigation -
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB index - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-introduction - -
-

A preliminary section that typically introduces the scope or nature of the work.

- - 
<section role="doc-introduction">
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-index: +
CharacteristicValue
Is Abstract: 
Superclass Role: + navigation +
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB index [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-introduction + +
+

A preliminary section that typically introduces the scope or nature of the work.

+ + 
+<section role="doc-introduction">
    <p>Everyone has some experience with marketing … </p>
-</section>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-introduction:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB introduction [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-noteref - -
-

A reference to a footnote or endnote, typically appearing as a superscripted number or symbol - in the main body of text.

- - 
<p> … as studies have shown.<a href="#fn01" id="fnref01" role="doc-noteref">[1]</a></p>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-noteref:
CharacteristicValue
Is Abstract: 
Superclass Role:link
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB noteref - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From: -
    -
  • contents
    • -
  • author
    • -
-
Accessible Name Required:True
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-notice - -
-

Notifies the user of consequences that might arise from an action or event. Examples include - warnings, cautions and dangers.

- - 
<section role="doc-notice">
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-introduction: +
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB introduction [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-noteref + +
+

A reference to a footnote or endnote, typically appearing as a superscripted number or symbol in the main body of text.

+ + 
<p> … as studies have shown.<a href="#fn01" id="fnref01" role="doc-noteref">[1]</a></p>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-noteref: +
CharacteristicValue
Is Abstract: 
Superclass Role:link
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB noteref [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From: +
    +
  • contents
    • +
  • author
    • +
+
Accessible Name Required:True
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-notice + +
+

Notifies the user of consequences that might arise from an action or event. Examples include warnings, cautions and dangers.

+ + 
+<section role="doc-notice">
    <img src="warning.png" alt="warning icon"/>
    <p>Just because you can include a font doesn’t mean you should.
       Think carefully about readability. Also, be respectful of intellectual property.
       There are many excellent free open-source fonts available.</p>
-</section>
+</section> -

Authors SHOULD include a label when the notice needs to be navigable to.

+

Authors SHOULD include a label when the notice needs to be navigable to.

- 
<div role="doc-notice" aria-label="Explosion Risk">
+            
+<div role="doc-notice" aria-label="Explosion Risk">
    <p><em>Danger!</em> Mixing reactive materials may cause an explosion.</p>
-</div>

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-notice:
CharacteristicValue
Is Abstract: 
Superclass Role:note
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB notice - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-pagebreak - -
-

A separator denoting the position before which a break occurs between two contiguous pages in - a statically paginated version of the content.

- -

Page break locators are also commonly used to provide static markers in purely digital - publications (i.e., where no statically paginated equivalent exists). These markers provide - consistent navigation regardless of differences in font and screen size that can otherwise - affect the dynamic pagination of the content.

- -

Authors MUST ensure the name of the page break is an end user-consumable page number that - identifies the page that is beginning so that assistive technologies can announce the page - as needed (e.g., in a command to identify the current page).

- -

The page break locator MUST precede the content of the page it identifies. If a page includes - a header (doc-pageheader), the page break locator SHOULD be located before it, - even if the header includes a visible page number. The page break locator may be used with - the page number in a page header if the number precedes all other content in the header.

- -

When reproducing page break locators from a static page equivalent, it is sometimes the case - that words are hyphenated across pages. When this happens, the page break locator SHOULD be - placed either before or after the word to ensure it does not interfere with text-to-speech - playback.

- -
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-notice: +
CharacteristicValue
Is Abstract: 
Superclass Role:note
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB notice [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-pagebreak + +
+

A separator denoting the position before which a break occurs between two contiguous pages in a statically paginated version of the content.

+ +

+ Page break locators are also commonly used to provide static markers in purely digital publications (i.e., where no statically paginated equivalent exists). These markers provide + consistent navigation regardless of differences in font and screen size that can otherwise affect the dynamic pagination of the content. +

+ +

+ Authors MUST ensure the name of the page break is an end user-consumable page number that identifies the page that is beginning so that assistive technologies can announce the page as + needed (e.g., in a command to identify the current page). +

+ +

+ The page break locator MUST precede the content of the page it identifies. If a page includes a header (doc-pageheader), the page break locator SHOULD be located before it, + even if the header includes a visible page number. The page break locator may be used with the page number in a page header if the number precedes all other content in the header. +

+ +

+ When reproducing page break locators from a static page equivalent, it is sometimes the case that words are hyphenated across pages. When this happens, the page break locator SHOULD be + placed either before or after the word to ensure it does not interfere with text-to-speech playback. +

+ + -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-pagebreak:
CharacteristicValue
Is Abstract: 
Superclass Role:separator
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB pagebreak - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From: -
    -
  • contents
    • -
  • author
    • -
-
Accessible Name Required:True
Inherits Name Required:
Children Presentational:True
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-pagelist - -
-

A navigational aid that provides a list of links to the page breaks in the content.

- - 
<nav role="doc-pagelist">
+<div id="pg04" role="doc-pagebreak">4</div>
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-pagebreak: +
CharacteristicValue
Is Abstract: 
Superclass Role:separator
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB pagebreak [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From: +
    +
  • contents
    • +
  • author
    • +
+
Accessible Name Required:True
Inherits Name Required:
Children Presentational:True
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-pagelist + +
+

A navigational aid that provides a list of links to the page breaks in the content.

+ + 
+<nav role="doc-pagelist">
    <h2>Pages</h2>
    <ol>
       <li><a href="chapter.xhtml#Page_1">1</a></li>
       <li><a href="chapter.xhtml#Page_2">2</a></li>
       …
    </ol>
-</nav>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-pagelist:
CharacteristicValue
Is Abstract: 
Superclass Role:navigation
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB page-list - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-pagefooter - -
-

A section of text appearing at the bottom of a page that provides context about the current - work and location within it. The page footer is distinct from the body text and normally - follows a repeating template that contains (possibly truncated) items such as the document - title, current section, author name(s), and page number.

- -

The doc-pagefooter role MUST be used on every instance of the page footer.

- -

The doc-pagefooter MUST NOT contain the doc-pagebreak.

- -

The doc-pagefooter MUST NOT contain footnotes (doc-footnote).

- -

Assistive technologies MAY allow the user to read the document content continuously without - interruption from the page footer.

- - 
<section role="doc-pagefooter">
+</nav>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-pagelist: +
CharacteristicValue
Is Abstract: 
Superclass Role:navigation
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB page-list [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-pagefooter + +
+

+ A section of text appearing at the bottom of a page that provides context about the current work and location within it. The page footer is distinct from the body text and normally + follows a repeating template that contains (possibly truncated) items such as the document title, current section, author name(s), and page number. +

+ +

The doc-pagefooter role MUST be used on every instance of the page footer.

+ +

The doc-pagefooter MUST NOT contain the doc-pagebreak.

+ +

The doc-pagefooter MUST NOT contain footnotes (doc-footnote).

+ +

Assistive technologies MAY allow the user to read the document content continuously without interruption from the page footer.

+ + 
+<section role="doc-pagefooter">
    <div>Leo Tolstoy</div>
    <div>321</div>
    …
-</section>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-pagefooter:
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:prohibited
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-pageheader - -
-

A section of text appearing at the top of a page that provides context about the current work - and location within it. The page header is distinct from the body text and normally follows - a repeating template that contains (possibly truncated) items such as the document title, - current section, author name(s), and page number.

- -

The doc-pageheader role MUST be used on every instance of the page header.

- -

Assistive technologies MAY allow the user to read the document content continuously without - interruption from the page header.

- - 
<section role="doc-pageheader">
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-pagefooter: +
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:prohibited
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-pageheader + +
+

+ A section of text appearing at the top of a page that provides context about the current work and location within it. The page header is distinct from the body text and normally follows + a repeating template that contains (possibly truncated) items such as the document title, current section, author name(s), and page number. +

+ +

The doc-pageheader role MUST be used on every instance of the page header.

+ +

Assistive technologies MAY allow the user to read the document content continuously without interruption from the page header.

+ + 
+<section role="doc-pageheader">
    <div>War and Peace</div>
    <div>321</div>
    …
-</section>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-pageheader:
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:prohibited
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-part - -
-

A major structural division in a work that contains a set of related sections dealing with a - particular subject, narrative arc, or similar encapsulated theme.

- - 
<section role="doc-part">
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-pageheader: +
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:prohibited
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-part + +
+

A major structural division in a work that contains a set of related sections dealing with a particular subject, narrative arc, or similar encapsulated theme.

+ + 
+<section role="doc-part">
    <h2>Part One</h2>
    <section role="doc-chapter">
       <h2>Chapter 1</h2>
       …
    </section>
    …
-</section>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-part:
CharacteristicValue
Is Abstract:
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB part - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-preface - -
-

An introductory section that precedes the work, typically written by the author of the - work.

- - 
<section role="doc-preface">
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-part: +
CharacteristicValue
Is Abstract:
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB part [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-preface + +
+

An introductory section that precedes the work, typically written by the author of the work.

+ + 
+<section role="doc-preface">
    <h2>Introduction:A Guide to the Galaxy</h2>
    …
-</section>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-preface:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB preface - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-prologue - -
-

An introductory section that sets the background to a work, typically part of the - narrative.

- - 
<section role="doc-prologue">
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-preface: +
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB preface [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-prologue + +
+

An introductory section that sets the background to a work, typically part of the narrative.

+ + 
+<section role="doc-prologue">
    <header>
       <h2>Prologue</h2>
       <p>Chorus</p>
    </header>
    <p>Two households, both alike in dignity, …</p>
    …
-</section>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-prologue:
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB prologue - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-pullquote - -
-

A distinctively placed or highlighted quotation from the current content designed to draw - attention to a topic or highlight a key point.

- -

Unlike a passage quoted from another source, a pullquote is a direct repetition of text in - the current document. As a result, authors must ensure that the presentational occurrence is - hidden from users of assistive technologies (e.g., using the aria-hidden - attribute).

- -

The following example shows the identification of a pullquote that will be presented - elsewhere (e.g., via a script). In this case, the pullquote is not hidden as the marked text - is not presentational.

- - 
<p>… I may die, but first you, my tyrant and tormentor, shall curse the sun that gazes on your misery.
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-prologue: +
CharacteristicValue
Is Abstract: 
Superclass Role:landmark
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB prologue [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-pullquote + +
+

A distinctively placed or highlighted quotation from the current content designed to draw attention to a topic or highlight a key point.

+ +

+ Unlike a passage quoted from another source, a pullquote is a direct repetition of text in the current document. As a result, authors must ensure that the presentational occurrence is + hidden from users of assistive technologies (e.g., using the aria-hidden attribute). +

+ +

+ The following example shows the identification of a pullquote that will be presented elsewhere (e.g., via a script). In this case, the pullquote is not hidden as the marked text is not + presentational. +

+ + 
+<p>… I may die, but first you, my tyrant and tormentor, shall curse the sun that gazes on your misery.
    <span id="pq01" role="doc-pullquote">Beware, for I am fearless and therefore powerful.</span>
-   I will watch with the wiliness of a snake, that I may sting with its venom. … </p>
+ I will watch with the wiliness of a snake, that I may sting with its venom. … </p> -

The next example shows a pullquote that duplicates the text. This quote is hidden because it - is for presentational purposes only.

+

The next example shows a pullquote that duplicates the text. This quote is hidden because it is for presentational purposes only.

- 
<p>… Better habits pave the way to growth, and growth leads to greater happiness.</p>
+            
+<p>… Better habits pave the way to growth, and growth leads to greater happiness.</p>
 <aside role="doc-pullquote" aria-hidden="true">
    Better habits pave the way to growth, and growth leads to greater happiness.
-</aside>

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-pullquote:
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB pullquote - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role:
-
- -
- doc-qna - -
-

A section of content structured as a series of questions and answers, such as an interview or - list of frequently asked questions.

- - 
<section role="doc-qna">
+</aside>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-pullquote: +
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB pullquote [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role:
+
+ +
+ doc-qna + +
+

A section of content structured as a series of questions and answers, such as an interview or list of frequently asked questions.

+ + 
+<section role="doc-qna">
    <h2>Interview with the Author</h2>
    <dl>
       <dt>Q: When did you begin writing this book?</dt>
       <dd>A: I first got the idea …</dd>
       …
    </dl>
-</section>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-qna:
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB qna - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-subtitle - -
-

An explanatory or alternate title for the work, or a section or component within it.

- - 
<header>
+</section>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-qna: +
CharacteristicValue
Is Abstract: 
Superclass Role:section
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB qna [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-subtitle + +
+

An explanatory or alternate title for the work, or a section or component within it.

+ + 
+<header>
    <h2>Chapter 2 The Battle</h2>
    <p role="doc-subtitle">Once more unto the breach</p>
-</header>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-subtitle:
CharacteristicValue
Is Abstract: 
Superclass Role:sectionhead
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB subtitle - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From: -
    -
  • contents
    • -
  • author
    • -
-
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-tip - -
-

Helpful information that clarifies some aspect of the content or assists in its - comprehension.

- - 
<aside role="doc-tip">
+</header>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-subtitle: +
CharacteristicValue
Is Abstract: 
Superclass Role:sectionhead
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB subtitle [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From: +
    +
  • contents
    • +
  • author
    • +
+
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-tip + +
+

Helpful information that clarifies some aspect of the content or assists in its comprehension.

+ + 
+<aside role="doc-tip">
    <h3>Tip</h3>
    <p>You can assign a variable a new value that is the result
       of an expression involving its previous value.</p>
-</aside>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-tip:
CharacteristicValue
Is Abstract: 
Superclass Role:note
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB help - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
- -
- doc-toc - -
-

A navigational aid that provides an ordered list of links to the major sectional headings in - the content. A table of contents may cover an entire work, or only a smaller section of - it.

- - 
<nav role="doc-toc">
+</aside>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Characteristics of + doc-tip: +
CharacteristicValue
Is Abstract: 
Superclass Role:note
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB help [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
+
+ +
+ doc-toc + +
+

+ A navigational aid that provides an ordered list of links to the major sectional headings in the content. A table of contents may cover an entire work, or only a smaller section of it. +

+ + 
+<nav role="doc-toc">
    <h2>Contents</h2>
    <ol role="directory">
       <li><a href="preface_001.xhtml">Original Transcriber’s Notes:</a></li>
@@ -4191,105 +4318,106 @@ 
Definition of Roles

       <li><a href="chapter_001.xhtml">Chapter 1. Loomings.</a></li>
       …
    </ol>
-</nav>
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Characteristics of doc-toc:
CharacteristicValue
Is Abstract: 
Superclass Role:navigation
Subclass Roles: 
Base Concept: 
Related Concepts:EPUB toc - [[EPUB-SSV]]
Required Context Role: 
Required Owned Elements:
Required States and Properties: 
Supported States and Properties: 
Inherited States and Properties: 
Name From:author
Accessible Name Required:False
Inherits Name Required:
Children Presentational:
Inherits Presentational: 
Implicit Value for Role: 
-
-
-
-
-

Privacy and Security Considerations

- -

This specification introduces no new security considerations.

- -

In accordance with Web Platform - Design Principles, this specification provides no programatic interface to determine if - information is being used by assistive technologies. However, this specificaton does allow an author to - present different information to users of assistive technologies from the information available to users - who do not use assistive technologies. This is possible using many features of the DPUB-ARIA - specification, just as this is possible using many other parts of the web technology stack. This content - disparity could be abused to perform active - fingerprinting of users of assistive technologies.

-
- -
-

Change Log

- -
-

Substantive changes since the First - Public Working Draft

- -
    - -
  • 20-Sep-2021: Clarified ambiguities in the formatting and processing of endnote and bibliography - lists and require that the doc-footnote role not be used within endnotes. See issue 38.
    • -
-
- -
-

Substantive changes since the DPUB-ARIA 1.0 - Recommendation

- -
    -
  • 24-Feb-2021: Changed required accessible name for doc-part to false to match the - other landmark roles. See issue - 34.
    • -
  • 02-Oct-2020: Added new doc-pageheader and doc-pagefooter roles. See issue 28.
    • -
  • 31-July-2020: Clarified that the name of doc-pagebreak is the page number of the - page that is beginning. See issue - 27.
    • -
  • 31-July-2020: Removed term and definition as required children of - doc-glossary to accommodate various ways glossaries can be constructed. See issue 9.
    • -
  • 25-July-2020: Recommend that doc-pagebreak name be end user-consumable. See issue 17.
    • -
  • 24-July-2020: Changed the superclass of doc-example to figure to make - compatible with use on HTML figure. See issue 19.
    • -
  • 23-July-2020: Deprecated the doc-biblioentry and doc-endnote roles due - to the inability of them to be recognized as children of list. See issue 15.
    • -
  • 23-July-2020: Updated doc-pagebreak to allow name from contents. See issue 12.
    • -
  • 15-Mar-2018: Fixed superclass of doc-pullquote to section to match the - mapping in the [[dpub-aam-1.0]]. See issue - 7.
    • -
  • 15-Mar-2018: Updated doc-subtitle to allow name from contents. See issue 6.
    • -
-
-
-
-

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)
    • -
  • Joanmarie Diggs (Igalia, S.L.)
    • -
  • Matt Garrish (DAISY Consortium)
    • -
  • James Nurthen (Adobe)
    • -
  • Tzviya Siegman (Wiley)
    • -
-
-
-
- +
+

Change Log

+ +
+

Substantive changes since the First Public Working Draft

+ +
    + +
  • + 20-Sep-2021: Clarified ambiguities in the formatting and processing of endnote and bibliography lists and require that the doc-footnote role not be used within endnotes. See + issue 38. +
    • +
+
+ +
+

Substantive changes since the DPUB-ARIA 1.0 Recommendation

+ +
    +
  • + 24-Feb-2021: Changed required accessible name for doc-part to false to match the other landmark roles. See issue 34. +
    • +
  • 02-Oct-2020: Added new doc-pageheader and doc-pagefooter roles. See issue 28.
    • +
  • + 31-July-2020: Clarified that the name of doc-pagebreak is the page number of the page that is beginning. See issue 27. +
    • +
  • + 31-July-2020: Removed term and definition as required children of doc-glossary to accommodate various ways glossaries can be constructed. See + issue 9. +
    • +
  • 25-July-2020: Recommend that doc-pagebreak name be end user-consumable. See issue 17.
    • +
  • + 24-July-2020: Changed the superclass of doc-example to figure to make compatible with use on HTML figure. See + issue 19. +
    • +
  • + 23-July-2020: Deprecated the doc-biblioentry and doc-endnote roles due to the inability of them to be recognized as children of list. See + issue 15. +
    • +
  • 23-July-2020: Updated doc-pagebreak to allow name from contents. See issue 12.
    • +
  • + 15-Mar-2018: Fixed superclass of doc-pullquote to section to match the mapping in the [[dpub-aam-1.0]]. See + issue 7. +
    • +
  • 15-Mar-2018: Updated doc-subtitle to allow name from contents. See issue 6.
    • +
+
+
+
+

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)
    • +
  • Joanmarie Diggs (Igalia, S.L.)
    • +
  • Matt Garrish (DAISY Consortium)
    • +
  • James Nurthen (Adobe)
    • +
  • Tzviya Siegman (Wiley)
    • +
+
+
+
+