Add accessibility metadata to the test books
Closed this issue · 4 comments
We now expect accessibility metadata to be available in EPUB publications. Our test titles should meet this requirement.
Below is the metadata I think that can be cut and pasted into most test books. Some may need to be modified. If there are no page list, for example, the values should be removed.
<dc:publisher> DAISY Consortium </dc:publisher>
property="dcterms:conformsTo" id="conf"> EPUB Accessibility 1.1 - WCAG 2.2 Level AA
<meta> id="certifier"> property="a11y:certifiedBy" refines="#conf"> epubtest working group </meta>
Members of the Working Group that wrote the specifications.
property="dcterms:date" refines="#certifier">2024-01-15
property="schema:structuralNavigation"
MathML
property="schema:accessMode">textual
<meta> property="schema:accessMode">visual</meta>
<meta property="schema:accessModeSufficient">textual</meta>
<meta> property="schema:accessibilityFeature">displayTransformability</meta>
property="schema:accessibilityFeature">readingOrder
<meta> property="schema:accessibilityFeature">tableOfContents</meta>
<meta> property="schema:accessibilityFeature">unlocked</meta>
<meta> property="schema:accessibilityFeature">pageBreakMarkers</meta>
property="schema:pageNavigation
property="schema:accessibilityFeature">alternativeText
noFlashingHazard
noSoundHazard
noMotionSimulationHazard
This publication strives to conform to WCAG 2.0 Level AA.</metadata>
I asked Matt to review the metadata section. What is below has Matt's blessing.
<metadata>
<dc:publisher>DAISY Consortium</dc:publisher>
<meta property="dcterms:conformsTo" id="conf">EPUB Accessibility 1.1 - WCAG 2.2 Level AA</meta>
<meta id="certifier" property="a11y:certifiedBy" refines="#conf">epubtest working group</meta>
<meta property="dcterms:date" refines="#certifier">2024-01-15</meta>
<meta property="schema:accessibilityFeature">structuralNavigation"</meta>
<meta property="schema:accessibilityFeature">MathML</meta>
<meta property="schema:accessMode">textual</meta>
<meta property="schema:accessMode">visual</meta>
<meta property="schema:accessModeSufficient">textual</meta>
<meta property="schema:accessibilityFeature">displayTransformability</meta>
<meta property="schema:accessibilityFeature">readingOrder</meta>
<meta property="schema:accessibilityFeature">tableOfContents</meta>
<meta property="schema:accessibilityFeature">unlocked</meta>
<meta property="schema:accessibilityFeature">pageBreakMarkers</meta>
<meta property="schema:accessibilityFeature">pageNavigation</meta>
<meta property="schema:accessibilityFeature">alternativeText</meta>
<meta property="schema:accessibilityHazard">noFlashingHazard</meta>
<meta property="schema:accessibilityHazard">noSoundHazard</meta>
<meta property="schema:accessibilityHazard">noMotionSimulationHazard</meta>
<meta property="schema:accessibilitySummary">This publication strives to conform to WCAG 2.0 Level AA.</meta>
<!-- Not in all test books:
<meta property="schema:accessibilityFeature">captions</meta>
<meta property="schema:accessibilityFeature">longDescription</meta>
-->
</metadata>
Looks great George, I made a tiny edit for formatting (markup has to go in code blocks in these forms, otherwise it appears as rendered HTML with just words and no tags)
I found in the OPF a Schema version number. At first I thought it was to the version of Schema being used. I discovered in the readme file that this is how the version number of the test book is identified.
I will change this to 2.0.0