Accessibility metadata in epub content.opf #9365
Iacobus1983
started this conversation in
Ideas
Replies: 2 comments 5 replies
-
I've made this an issue. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I see the linked issue was merged in version 3.1.12.1. I added the following metadata to my source HTML file: <metadata>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="dcterms:conformsTo" content="EPUB Accessibility 1.1 - WCAG 2.1 Level AA"/>
<meta name="schema:accessMode" content="textual"/>
<meta name="schema:accessModeSufficient" content="textual"/>
<meta name="schema:accessibilityFeature" content="none"/>
<meta name="schema:accessibilityHazard" content="none"/>
<meta name="schema:accessibilitySummary" content="This publication strives to meet accepted Web Content Accessibility Guidelines (WCAG) at the AA level. Page numbers are present and navigation to pages is supported. This publication contains a comprehensive multi-level table of contents for navigation through the various chapters and sections."/>
</metadata> When converting to ePub file this all used to be missed. In 3.1.12.1 now everything is brought into the ePub except the schema:accessibilitySummary property. Is this a lingering little bug with that issue, or is there something wrong with my metadata please? Kind regards Quentin |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In view of EU Accessibility Act, I checked a pandoc-generated epub with DAISY Ace (1.3.2). I get some accessibility warnings.
In order to make the epubs compliant with accessibility requirements, it seems that minor addition to
content.opf
would be needed:xml:lang
attribute should be added topackage
element, most likely with the same value ofdc:language
element (see https://kb.daisy.org/publishing/docs/wcag/language-of-page.html)meta
elements:schema:accessMode
,schema:accessibilityFeature
andschema:accessibilityHazard
are mandatory;schema:accessModeSufficient
andschema:accessibilitySummary
are optional.Full support for metadata mentioned in point 2 would possibly require a user-defined input, e.g. within the metadata yaml file (perhaps similar to 743d1b3 ?)
Beta Was this translation helpful? Give feedback.
All reactions