WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Fourth rule of aria > aria-hidden

for

From: Beranek, Nicholas
Date: Jan 23, 2018 10:53AM

I would not call that an issue with Dragon. Dragon is going by the accessible name and, naturally, aria-label will take precedence in most cases to provide it. When we declare issues, we make sure to mention that ARIA is not just about screen readers, but rather all assistive technologies that use the accessibility API, at least to some degree, including dictation programs such as Dragon.

Dragon 13 started supporting ARIA in 2014. My understanding is that they support only what they need to, such as aria-labelledby, aria-label, ARIA roles such as "button", "link", "checkbox", and "radio". It doesn't appear to be impacted by ARIA properties such as aria-hidden. For example, I was able to perform a simple "click link" command on an element that I set to aria-hidden="true".

We held a team discussion regarding the latest changes to WCAG 2.1 as we prepare for its official REC status hopefully in June. This reminds me of one of the new success criteria: SC 2.4.12 Label in Name (formerly Accessible Name). It states that the visible label must match the programmatic label. It benefits users with speech recognition programs since the aria-label and aria-labelledby attributes are supported and take precedence. This is already a best practice in our handbook, but it will be great to enforce it under a success criterion.

Nick Beranek
Capital One