Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ONIX technique for List 196 Code 99 #468

Open
rickj opened this issue Nov 7, 2024 · 6 comments
Open

ONIX technique for List 196 Code 99 #468

rickj opened this issue Nov 7, 2024 · 6 comments
Labels
a11y-display-guide Issue with the UX Guide principles or techniques

Comments

@rickj
Copy link
Collaborator

rickj commented Nov 7, 2024

In a conversation with a publisher, they were struggling with understanding how their information in https://ns.editeur.org/onix/en/196/99 would be displayed.

In looking at https://www.editeur.org/files/ONIX%203/APPNOTE%20Accessibility%20metadata%20in%20ONIX%20(advanced).pdf at the top of page 28 it provides no guidance.

In looking at https://w3c.github.io/publ-a11y/a11y-meta-display-guide/2.0/draft/techniques/onix-metadata/#conformance-group I see no technique for displaying this information.

@gautierchomel
Copy link
Collaborator

I agree this information should be shown, even if used only a few times today.

I am unsure if the correct place is in Additional Accessibility Information or if we should consider adding it to the Accessibility Summary section as it relates to the metadata pieces where the Publishing organisation speaks directly to the consumer.

@gautierchomel gautierchomel added the a11y-display-guide Issue with the UX Guide principles or techniques label Nov 13, 2024
@rickj
Copy link
Collaborator Author

rickj commented Dec 19, 2024

Checking back on this, as I have publishers looking for clarity.

@chrisONIX
Copy link

chrisONIX commented Dec 19, 2024

@rickj What kind of guidance are you looking for in ONIX guidelines?
We can add examples of how to use this in ONIX document but we can not make a recommendation for how to display it.
Plus some text about what this is for? Let us know what would be useful in the ONIX guidelines.

We have published guidelines link to the EU GPSR requirements linked to contact information which has to be displayed on websites that sell goods to consumers in Europe and the sort of displays we are seeing for physical products would probably be the same for digital products and that maybe appropriate for this discussion as it is a very similar process.

https://www.editeur.org/files/ONIX%203/APPNOTE%20Product%20safety%20requirements%20in%20ONIX.pdf

@GeorgeKerscher
Copy link
Collaborator

It does not look like schema has a field for this. I believe it is a best practice for publishers to have an accessibility area that is linked from the home page. On this accessibility page there should be contact inform where issues can be reported.

There is always the accessibility summary where the publisher can put their contact information. If the community feels that this should be a recommendation, we could put it in the example in the accessibility summary.

@rickj
Copy link
Collaborator Author

rickj commented Dec 23, 2024

I think that is the recommendation I'd like to have. If there is content in this ONIX field, it should be appended to the Accessibility Summary

@GeorgeKerscher
Copy link
Collaborator

I like this approach! So if ONIX has this information, it could immediately followthe accessibility summary or it could be concatinated. In the case where the publisher also puts this information in the EPUB schema accessibility summary itself, it would appear twice, which I do not think is too bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a11y-display-guide Issue with the UX Guide principles or techniques
Projects
None yet
Development

No branches or pull requests

4 participants