View Single Post
Old 06-01-2022, 01:25 PM   #5
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,842
Karma: 6120478
Join Date: Nov 2009
Device: many
This has now been fixed in Sigil master.

Access-Aide can not handle audio and video, as the software has no idea if any audio or video files have anything in them that may spur aural or visual issues by users (ie accessibility hazards). You can of course, run Access-Aide before adding any multimedia files and then properly update the metadata in the opf related to Accessibility by hand.

In other words, properly manually update these:

Quote:
schema:accessMode: textual
schema:accessMode: visual
schema:accessModeSufficient: textual
schema:accessibilityFeature: structuralNavigation
schema:accessibilitySummary: This publication conforms to WCAG 2.0 AA.
schema:accessibilityHazard: none
The correct settings depend on exactly what multimedia elements you have added and whether they contain any hazards such as flashing images, etc.

Those types of judgements can only be made by the author/listener/watcher, not software like Access-Aide which is why Access-Aide stops when it detects these features being used.


See: http://kb.daisy.org/publishing/docs/...ard.html#value

Last edited by KevinH; 06-01-2022 at 01:38 PM.
KevinH is offline   Reply With Quote