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

OPF package accessiblity metadata a11y:certifierCredential raises error "undefined property" when link instead of meta #1140

Closed
danielweck opened this issue May 8, 2020 · 1 comment · Fixed by #1151
Assignees
Labels
spec: EPUB 3.x Impacting the support of EPUB 3.x specifications status: accepted Ready to be further processed type: false-positive This issue is about valid content being incorrectly rejected
Milestone

Comments

@danielweck
Copy link
Member

(tested with EPUB Check 4.2.2 - via the Pagina Mac app)

http://kb.daisy.org/publishing/docs/metadata/evaluation.html#a11y:certifierCredential

The property can either be a text field with the name of the credential held, or it can be a link to a description of the credential.

Relevant test files:

https://github.com/w3c/epubcheck/blob/master/src/test/resources/30/single/opf/valid/vocab-a11y-declared.opf#L11

https://github.com/w3c/epubcheck/blob/master/src/test/resources/30/single/opf/valid/vocab-a11y-undeclared.opf#L10

@rdeltour rdeltour self-assigned this Jun 22, 2020
@rdeltour rdeltour added spec: EPUB 3.x Impacting the support of EPUB 3.x specifications status: accepted Ready to be further processed type: false-positive This issue is about valid content being incorrectly rejected labels Jun 22, 2020
@rdeltour rdeltour added this to the 4.2.3 milestone Jun 22, 2020
@rdeltour
Copy link
Member

Good catch @danielweck, thanks! This will be fixed by #1151 in v4.2.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec: EPUB 3.x Impacting the support of EPUB 3.x specifications status: accepted Ready to be further processed type: false-positive This issue is about valid content being incorrectly rejected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants