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

Question: Is ace comprehensive with its suggestions? #179

Closed
jenstroeger opened this issue Apr 20, 2018 · 1 comment
Closed

Question: Is ace comprehensive with its suggestions? #179

jenstroeger opened this issue Apr 20, 2018 · 1 comment
Assignees
Labels

Comments

@jenstroeger
Copy link

jenstroeger commented Apr 20, 2018

(Ace 1.0.0, Node v6.14.1)

When I check an EPUB with ace, does it check the existing accessibility features only or does ace suggest a (comprehensive) list of missing annotations?

I noticed that ace pointed out missing role attributes for existing epub:type ones, but I’m curious to what extent and how thoroughly ace checks for missing attributes. For example, when I removed the epub:type from a footnote’s <aside> then ace wouldn’t issue a warning for that footnote. (Hmm… how would it know that the <aside> is supposed to be footnote anyway in plain HTML — I suppose it can’t 🤔)

Or to rephrase my question: if I run an EPUB through ace and ace doesn’t find issues, then that does not mean that the EPUB meets any of the accessibility requirements, correct? This question is perhaps related to the “conformsTo” discussion in issue #171.

@rdeltour
Copy link
Member

hi @jenstroeger (sorry for the late answer!)

When I check an EPUB with ace, does it check the existing accessibility features only or does ace suggest a (comprehensive) list of missing annotations?

I’m not sure I understand what you mean by "list of missing annotations"…
Ace intends to only report existing and confirmed accessibility issues.

I noticed that ace pointed out missing role attributes for existing epub:type ones, but I’m curious to what extent and how thoroughly ace checks for missing attributes. For example, when I removed the epub:type from a footnote’s <aside> then ace wouldn’t issue a warning for that footnote. (Hmm… how would it know that the <aside> is supposed to be footnote anyway in plain HTML — I suppose it can’t 🤔)

No, without an epub:type, Ace would not report any missing role, for the reason you note: it can’t tell whether the aside would represent a footnote or something else.

Or to rephrase my question: if I run an EPUB through ace and ace doesn’t find issues, then that does not mean that the EPUB meets any of the accessibility requirements, correct?

Absolutely correct: Ace will only report the issues that it can detect automatically. An EPUB passing Ace doesn’t necessary meet all the accessibility requirements; many of them require manual inspection!

Hope this helps, and again sorry for having left this issue unnoticed!
Btw, for such questions it’s usually preferable to use the support email address ([email protected]), since this issue tracker is more intended for bugs or feature requests 😉.

@rdeltour rdeltour self-assigned this May 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants