a11y:exemption is not recognized by epubcheck #1566

Activity

1. mattgarrish commented on Jul 8, 2024

   

   mattgarrish

   on Jul 8, 2024

   Member

   More actions

   Ya, I don't think it's helpful for epubcheck to enforce what properties are allowed in the a11y vocabulary. It's not like the package document vocabularies in the core spec that have elements that require their use.

   It could maybe be a usage message to help people make sure they aren't misspelling property names, but we always expected to extend the vocabulary and this is the second time in the last year alone where we've done it.
2. rdeltour

   added this to the Next maintenance release milestone on Dec 26, 2024
3. rdeltour

   self-assigned this

   on Dec 26, 2024
4. rdeltour

   added

   status: in progressThe issue is being implemented by the development teamThe issue is being implemented by the development team

   type: false-positiveThis issue is about valid content being incorrectly rejectedThis issue is about valid content being incorrectly rejected

   on Dec 26, 2024
5. rdeltour commented on Dec 27, 2024

   

   rdeltour

   on Dec 27, 2024

   Member

   More actions

   I don't think it's helpful for epubcheck to enforce what properties are allowed in the a11y vocabulary. It's not like the package document vocabularies in the core spec that have elements that require their use.

   It could maybe be a usage message to help people make sure they aren't misspelling property names, but we always expected to extend the vocabulary and this is the second time in the last year alone where we've done it.

   Yeah, good point.

   There is currently no way in the EPUBCheck vocabulary declaration to say "these values are ok, and all other values are ok too but should be reported as usage". It's either a fully-checked vocabulary or a fully permissive one.

   For now, I'm just adding the a11y:exemption to the list of known properties, but will consider adding a new vocabulary type to implement what you suggest 👍
6. rdeltour

   added a commit that references this issue on Dec 27, 2024

   fix: recognize the `a11y:exemption` property

   ...

   This issue will close once commit 06f76ad is merged into the 'main' branch.

   06f76ad
7. rdeltour

   added

   status: has PRThe issue is being processed in a pull requestThe issue is being processed in a pull request

   and removed

   status: in progressThe issue is being implemented by the development teamThe issue is being implemented by the development team

   on Dec 27, 2024
8. rdeltour

   closed this as completedin 06f76adon Dec 29, 2024