@LaurenceLewis

3 Followers
9 Following
5 Posts
If you have not tried A11y Quick Check, a Chrome extension that identifies #accessibility issues and provides feedback on invalid use of HTML and ARIA use. If you use my other extension Visual ARIA, A11y Quick Check might be your next go to accessibility testing tool! https://chromewebstore.google.com/detail/a11y-quick-check/jlamgighkcjniljcdfpnhiemcakibepi?authuser=0&hl=en-GB&pli=1
A11y quick check

Easy to use quick checks to identify potential accessibility issues.

@SteveFaulkner as the author of ARIA in HTML would I be correct in interpreting HTML <textarea> as not allowing the inherent role to be overridden?

"No role other than textbox, which is NOT RECOMMENDED" meaning <textarea role=combobox is a violation of the spec. Which specification I’m not sure 🤔

ARIA in HTML for <textarea> says has ‘No role, meaning it indicates that authors MUST NOT overwrite the implicit ARIA semantics, or native semantics of the HTML element’.
Reason I ask is the code copied from Chrome Developer Tools, with classes and other attributes removed for brevity, role combobox overwrite textarea:
<textarea aria-controls="Alh6id" aria-owns="Alh6id" autocomplete="off" title="Search" aria-label="Search" aria-autocomplete="both" aria-expanded="false" aria-haspopup="false" id="APjFqb" maxlength="2048" name="q" role="combobox"></textarea>
I’m interested in the views of screen reader users and other users of assistive technology, and accessibility SMEs think of the Google search component that uses an html textarea with aria-owns to popup a div containing the results. How user friendly is this approach to building search results for users of assistivetech? #google #search #accessibility #aria