WebAIM - Web Accessibility In Mind

E-mail List Archives

Browsers handling more widgets nativelyUsingtitle attribute on non-anchor elements?

for

From: Jonathan Avila
Date: May 4, 2016 5:32PM

> I personally think of "role=" as a interim state and not a good way to specify components. Just as role="Navigation" can be handled with a Nav tag,

I'd generally agree that many interactions cannot be defined for a single role and a pattern module such as that used by UIAutomation or AccessibilityTraits in iOS is one way to address this. For example, we could end up with a situation where tabs also have checkboxes and we would want a tab role with a checkbox pattern or something like that to be communicated and understand by AT. Some patterns could arguably be confusing to the user however, so it might be worth considering before implementing such a thing.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group 
<EMAIL REMOVED>
703.637.8957 (Office)

Visit us online: Website | Twitter | Facebook | Linkedin | Blog
Check out our Digital Accessibility Webinars!