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

[EPUB Accessibility 1.1] refines examples and EPUB 2 #2042

Closed
gregoriopellegrino opened this issue Mar 8, 2022 · 2 comments · Fixed by #2109
Closed

[EPUB Accessibility 1.1] refines examples and EPUB 2 #2042

gregoriopellegrino opened this issue Mar 8, 2022 · 2 comments · Fixed by #2109
Labels
Accessibility11 Issues addressed in the Accessibility 1.1 revision Spec-Accessibility The issue affects the EPUB Accessibility 1.1 Recommendation

Comments

@gregoriopellegrino
Copy link
Contributor

In the document examples 6, 7 and 8 show metadata with the refines attribute. This attribute does not seem to be compatible with EPUB 2. What to do in this case?

Still many publications in EPUB 2 are available in the market (some even fairly affordable) and it is not certain that they will be upgraded to EPUB 3 soon.

For a11y:certifierCredential and a11y:certifierReport I don't see big problems (if there are not more than one in a file), but for the certication date (dcterms:date) having the metadata without refines be very ambiguous. Is there another way? May we add a note to use the example only in EPUB 3?

Do we put a note for all examples?

@mattgarrish
Copy link
Member

There's nothing we can do to work around it. You can't structure the data, or chain it like in EPUB 3, so you have to live with ambiguities.

It's not a unique problem for the accessibility metadata, so I don't know that we need to call it out. I expect anyone trying to process EPUB 2 metadata is aware of the flaws. A human reading it, on the other hand, will figure out the association by proximity of the statements.

@mattgarrish mattgarrish added the Spec-Accessibility The issue affects the EPUB Accessibility 1.1 Recommendation label Mar 8, 2022
@mattgarrish
Copy link
Member

Maybe we can note this in the "application to older versions" section rather than put notes everywhere that epub 2 metadata is not very expressive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility11 Issues addressed in the Accessibility 1.1 revision Spec-Accessibility The issue affects the EPUB Accessibility 1.1 Recommendation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants