Re: Patch to add aria labels to SelectionBox arrow buttons
Keith Creasy <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.request-tracker.devel |
|---|---|
| Message-ID | <[email protected]> |
I tested with two screen readers but here is more information. It is widely supported. For general information about WAI ARIA see http://www.w3.org/WAI/intro/aria Current support is at least mentioned at https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA The bottom line is that using ARIA attributes breaks nothing, if screen readers and browsers don't know about it then it is ignored. If you or someone else wants to change the value of the button to have a real label you can and, again, nothing is broken. There just isn't a good reason not to use it here as a way to support accessibility without having to change your user interface. Having said that, if someone wants to solve it a different way it won't hurt my feelings but it does need to be fixed.. -----Original Message----- From: rt-devel [mailto:[email protected]] On Behalf Of Kevin Falcone Sent: Monday, June 30, 2014 5:29 PM To: [email protected] Subject: Re: [rt-devel] Patch to add aria labels to SelectionBox arrow buttons On Mon, Jun 30, 2014 at 05:43:13PM +0000, Keith Creasy wrote: > Screen readers such as “JAWS” and “NVDA” that provide access to web > pages for blind users do not read the arrow buttons on the selection > box. This patch adds aria-label attributes “Add”, “Move up”, and “Move down” to assist them. Knowing that not all devs are immediately aware of the aria-label convention, do you have a pointer to something 'official' about it (and how well it's supported by screen readers). I don't mind adding things to core to support user agents, but want to make sure I have a better understanding of it. -kevin -- RT Training - Boston, September 9-10 http://bestpractical.com/training