Closed (fixed)
Project:
radix
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Sep 2015 at 13:49 UTC
Updated:
5 Nov 2015 at 21:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
dsnopekComment #3
dsnopekHere's the first pass at this!
Comment #4
jwilson3You're adding ARIA landmarks, which means you're making an attempt at assistive technology support. I think to improve that support, you might also wrap the
×in a<span aria-hidden="true">.This is a similar pattern being used in Drupal 8 core on the new accesible pagers, where the number "1" is hidden from screen readers with an
<span aria-hidden="true">and then an additional<span class="visually-hidden">Go to Page 1</span>is what is read. Sighted users only see "1".Comment #5
jwilson3Comment #6
cboyden commented@jwilson3 Thanks for the reference to the new Drupal 8 approach. The pattern could be different here, since we're talking about form elements instead of pagers, which are implemented as links.
The expected behavior of the
aria-labelproperty is that it overrides the text/visible label of the form element it's applied to. Screenreader support foraria-labelis good, soaria-hiddenandelement-invisibleshould not be needed. Speech input lags behind on ARIA support, but to the best of my knowledge the latest releases of major speech input products do supportaria-labelfor buttons.Comment #7
cboyden commentedOf course for the automated test suite to work, there has to be some text for it to find, and
aria-labelwon't work for that case.Comment #8
cboyden commentedWe just tested this patch with Jaws, NVDA, and Dragon. It's working as expected with all three.
Comment #9
dsnopekThanks, @cboyden! Committed :-)