You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ONIX list 196 code 10No reading system accessibility options disabled (except) could probably be mapped onto schema:accessibilityControl metadata, for all its values, i. e. fullKeyboardControl, fullMouseControl, fullSwitchControl, fullTouchControl, fullVideoControl, fullVoiceControl.
In my understanding, controls are part of the reading system accessibility options. As a matter of fact, the ONIX definition of code 10 clearly says "No accessibility features offered by the reading system, device or reading software (including but not limited to choice of text size or typeface, choice of text or background color, text-to-speech) are disabled, overridden or otherwise unusable with the product".
Interactive content implemented in JS (events managt) could be concerned typically (without any way for the RS to apply its options).
Furthermore, this means that this ONIX metadata does not describe the reading system controls themselves, but rather indicates wether the current EPUB prevents or not the reading system to run any of these controls (if available in the RS of course). In this sense, this ONIX metadata is properly an ebook property, that should be kept on the EPUB, as a complement to the reading system properties. As a matter of fact, they both need to be compliant so that the controls can work for the end user.
Could schema.org schema:accessibilityControl metadata be assigned both to the EPUBs and to the RS?
The text was updated successfully, but these errors were encountered:
ONIX list 196 code 10 No reading system accessibility options disabled (except) could probably be mapped onto
schema:accessibilityControl
metadata, for all its values, i. e.fullKeyboardControl, fullMouseControl, fullSwitchControl, fullTouchControl, fullVideoControl, fullVoiceControl
.In my understanding, controls are part of the reading system accessibility options. As a matter of fact, the ONIX definition of code 10 clearly says "No accessibility features offered by the reading system, device or reading software (including but not limited to choice of text size or typeface, choice of text or background color, text-to-speech) are disabled, overridden or otherwise unusable with the product".
Interactive content implemented in JS (events managt) could be concerned typically (without any way for the RS to apply its options).
Furthermore, this means that this ONIX metadata does not describe the reading system controls themselves, but rather indicates wether the current EPUB prevents or not the reading system to run any of these controls (if available in the RS of course). In this sense, this ONIX metadata is properly an ebook property, that should be kept on the EPUB, as a complement to the reading system properties. As a matter of fact, they both need to be compliant so that the controls can work for the end user.
Could schema.org
schema:accessibilityControl
metadata be assigned both to the EPUBs and to the RS?The text was updated successfully, but these errors were encountered: