-
Notifications
You must be signed in to change notification settings - Fork 22
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
New rule: report absence of ARIA roles along side epub:type
#70
Comments
That would be useful, IMO. We want people to stop thinking of epub:type as an accessibility mechanism, and the guidance is to prefer ARIA for accessibility but use both if you need some specific reading system functionality only supported by epub:type. |
ok thanks, that's what I needed to know! |
Hi, |
You're right, it's not reported. To clarify, Ace will:
@laudrain, are you saying some |
Some epub:type yes:
|
to be followed in #87... |
Moving out of Beta 2 This rule can be quite disturbing at first for many people who've been told Waiting on #77 |
Sorry, looks like I missed some notifications. I wouldn't make this an error even when implemented. WCAG only requires that user interface components use ARIA roles. This is more like a best practice for a best practice. |
The DPUB ARIA roles have well-defined accessibility API mappings, and should be used in conjunction to
epub:type
.Ace could include a rule to check that, and report as a "moderate" violation.
@mattgarrish thoughts welcome
The text was updated successfully, but these errors were encountered: