[graycyn]

Thanks, Kevin!

I had run my epub through Access-Aide plugin prior, this is what was already in the metadata when I ran it through the Ace by Daisy app:

    <meta property="schema:accessibilitySummary">This publication conforms to WCAG 2.0 AA.</meta>
    <meta property="schema:accessMode">textual</meta>
    <meta property="schema:accessMode">visual</meta>
    <meta property="schema:accessModeSufficient">textual</meta>
    <meta property="schema:accessibilityFeature">structuralNavigation</meta>

So I didn't have it *exactly* like the examples in your link, though I would've thought it would be good to go. So I tried changing to the version below, like your link:

   <meta property="schema:accessModeSufficient">textual,visual</meta>

I stripped the schema:accesibilityHazard line out, ran through Ace by Daisy again, NO DIFFERENCE! Same error. It wants that Hazard metadata!


There's NOTHING in the epub that wasn't put there by me, Sigil, Access-Aide or the Pagelist plugin. The only things I can remotely imagine triggering this are the non-transparent title page image (a shocker in night mode, but transparency creates black on black in most apps) and I do have a few Spanish words marked up with:

xml:lang="es"

I was so puzzled, last night I ran a very recently purchased epub (HarperCollins, Stargazer by Anne Hillerman) and Ace by Daisy did not flag it as having any serious violations (some 300+ minor ones, tho). I opened Stargazer up in Sigil, took a look and lo and behold, they have SEVERAL schema:accessibilityHazard statements, even though there doesn't appear to be anything more hazardous about their ebook than mine. Their title page image is also non-transparent, FWIW. No audio, video, fonts or miscellaneous in their book either. They had three images, all JPG.

Here's what they had:

    <meta property="schema:accessibilityHazard">noFlashingHazard</meta>
    <meta property="schema:accessibilityHazard">noSoundHazard</meta>
    <meta property="schema:accessibilityHazard">noMotionSimulationHazard</meta>

So the mystery remains. I just can't imagine why my little book would be flagged as needing this particular metadata. I can see no reason the HarperCollins book would require it either. But I guess I best have it in there.

Question, should I go with the value as none which appeared to satisfy ACE by Daisy, or copy what HC did?

I'm a hobbyist, I have no idea what all the accessibility requirements are, I'd just like to cover the bare-bones basics and have my book pass the check.