w3c / a11y-discov-vocab

Repository for the maintenance of the schema.org accessibility property values for discoverability.
https://www.w3.org/community/a11y-discov-vocab/
Other
15 stars 8 forks source link

Onix code list additions #97

Closed clapierre closed 9 months ago

clapierre commented 10 months ago

The suggested improvements made by @chrisONIX in this previous pull request Also addressed items outlined in #95

Added the following, and fixed a number of link issues introduced in previous pull request regarding conformance links into ONIX code pages.

Here are some suggested proposals for crosswalk to ONIX - based on missing ONIX values in current version

latest version of code lists for ONIX are available here. [https://ns.editeur.org/onix/en] Accessibility features audioDescription - List 196 - code 28 braille - List 21 - code BRL (Braille edition) - there are other options as well. List 175 - code BRF - format is digital braille describedMath - List 196 - code 14 (Should be used with List 81 - code 48 - Mathematical content) displayTransformability - List 196 - code 36 highContrastAudio - List 196 - code 27 highContrastDisplay - List 196 - codes 26 & 37 largePrint - code list 21 - codes LTE and ULP latex - code list 196 - code 35 (Should be used with List 81 - code 48 - Mathematical content) none - code list 196 - code 09 page navigation - code list 196 - code 19 structuralNavigation - code list 196 - code 29 taggedPDF - code list 196 - code 05 unknown - code list 196 - code 08 unlocked - code list 144 - code 00 Hazards flashing - code list 143 - code 13 noFlashingHazard -code list 143 - code 14 motionSimulation - code list 143 - code 17 noMotionSimulationHazard - code list 143 - code 18 sound - code list 143 - code 15 noSoundHazard - code list 143 - code 16 unknown - code list 196 - code 08

Access Mode Access mode is dealt with in list 81 - which covers all digital products and their features for all the market. We encourage users to also use values from 196 - confirming accessibility.

auditory - code list 81 - main code 01 (plus 22, 13, 03, 04, 21, 22, 23) - covers the variety of audio content chemOnVisual - code list 81 - code 47 colorDependent (ONIX does the other way around - see code list 196 _ code 25 mathOnVisual -code list 81 - code 48 musicOnVisual - code list 81 - code 11 textOnVisual - code list 81 - code 49 textual - code list 81 - main code 10 (plus codes 16, 45) visual - code list 81 - codes 07, 18, 19, 20, 12, 46, 42, 50, 24

Access Mode Sufficient

textual - code list 196 - code 52.

mattgarrish commented 10 months ago
chrisONIX commented 10 months ago

For cross walk - accessModeSufficient - Auditory - I suggest removing list 81 - code 01 Audiobook. We have a proposal to have a new code in list 196 to say that the audio product is fully accessible - that will correspond better - so my suggestion is to leave this blank until we have a new code?

clapierre commented 10 months ago

@chrisONIX So have accessModeSufficient as blank but keep accessMode:audio with

Code 01: Audiobook plus types of audio content Code 22: Additional audio content not part of main content Code 13: Other speech content Code 03: Music recording Code 04: Other audio Code 21: Partial performance – spoken word Code 23: Promotional audio for other book product

chrisONIX commented 10 months ago

@clapierre yes to this comment - accessModeSufficient as blank but keep accessMode:audio with the list. We hope to have a new accessModeSufficient for issue 64 of ONIX code lists and then can update crosswalk - if that is ok with all?

clapierre commented 10 months ago

@mattgarrish any reason why I can't add @chrisONIX as a reviewer? Their name doesn't show up.

mattgarrish commented 10 months ago

I think the proper way to get in the list of possible reviewers is to join the community group, but it might be possible to do manual invites through the repository settings. You can only formally request a review from team members of a repository.

mattgarrish commented 9 months ago

Do you think we're good to merge this yet @clapierre ?

clapierre commented 9 months ago

Yes, I will merge this and then add the new Section for EAA exceptions and remove the AccessibilityAPI / Controls sections as they are no longer needed.