Closed nekennedy closed 3 years ago
Thanks for the report! This seems to be related to #239 indeed, but the other way around.
Note that the specs are not clear about these role relationships (see w3c/dpub-aria#15), but in any case Ace should accept these as they are intended in DPUB ARIA.
I'll fix this in the next release.
Hello Romain, is this fixable as a new Axe patch, or by altering an existing one?
I don't think this is "fixable" with the current state of the specifications. doc-endnote
cannot currently be children of a list
, per ARIA rules.
There are discussions about actually deprecating doc-endnote
in a future version of DPUB ARIA.
That said, if we want to allow the construct while we wait for spec clarifications, I would look into the axe-path-only-list-item.js
patch script. But it's been a while I haven't dived in this code…
Thank you Romain about the specification status.
https://github.com/dequelabs/axe-core/issues/1677#issuecomment-718022025
Looking at this again. At this point both directory and doc-biblioentry are proposed to be deprecated, exactly for the reason that its inheritance creates confusion. Neither of these use cases is valid according to ARIA 1.1, so we're going to leave these as failures for axe-core.
"deprecate doc-biblioentry and doc-endnote": https://github.com/w3c/dpub-aria/pull/22 => https://w3c.github.io/dpub-aria/#doc-endnote
Fixed via: https://github.com/daisy/ace/pull/315 ...or more precisely, via: https://github.com/daisy/axe-core/pull/4
ACE 1.1.1 NODE 8.6.0
The second example in the dpub-aria spec for doc-endnote generates a critical failure, "Required ARIA child role not present: listitem".
Note sure if this is an ACE issue, AXE issue or a dpub one. Happy to generate a sample file if you need one. (Also think it may be related to this issue)
EXAMPLE 18 code:
Our current test code: