accessModeSufficient value check is broken, as the metadata accepts a list of values
#238
Comments
|
@rdeltour knowledge base propose also with a space separator: |
|
EPUB can't represent the expected ItemList defined in schema.org, so this is one of the cases where we had to come up with a workaround. Both tend to be acceptable, and we should probably be permissive from a validation standpoint. The KB actually mixes both, as the full example uses commas but the individual definition does not. (I have a memory that we decided to use commas somewhere near the end of the a11y spec revision just to make clear that there was a list as the value, but it's not an enforced requirement in any document.) |
|
Skimming the techniques document, we did put this statement in:
http://www.idpf.org/epub/a11y/techniques/#meta-002 It's not a normative document, though, so "requirement" here is just a descriptive statement of what we were expecting. |
Ace reports violations but it does not matter: - `accessibilityApi` as invalid because only `ARIA` is allowed - `accessModeSufficient` as invalid for a list of values (issue: daisy/ace#238) - `accessibilityFeature="printPageNumbers"` because there's no `<nav epub:type="page-list">`
|
Sorry but I don't see the resolution of this issue ! Should we remove: |
|
@laudrain have you updated to v1.1.1? (released on Monday July 8) |
|
Ah yes, thanks. I'll do it immediately |
|
Perfect, no more issue in 1.1.1! |
|
@rdeltour ace --version still gives 1.1.0 |
yes, I realized that yesterday, with feedback from @clapierre. |
Reported by @garconvacher:
The following markup:
will be reported as:
The text was updated successfully, but these errors were encountered: