WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG 2.0: multiple buttons with the same nameaccessible

for

From: Jonathan Avila
Date: Nov 19, 2014 3:43PM

> the table can be marked up properly and this still will be a
problem in the form fields list or the buttons list.

This sounds like a screen reader bug/enhancement. AT makers and site authors have to share the responsibility. When relationships are exposed programmatically this is a strong case/need for AT follow through.

Jon

On Nov 19, 2014, at 4:37 PM, Lucy Greco < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >> wrote:

actualy the table can be marked up properly and this still will be a
problem in the form fields list or the buttons list. this goes back to the
problem i spoke about here the other day that the only information past
through when the screen reader user is using a list be it the links list or
button list or what have you is the label the describe by or table headers
do not get past through.



--
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces


On Wed, Nov 19, 2014 at 11:25 AM, Don Mauck < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >> wrote:

Wouldn't the table issue you bring up be a result of either not coding the
table correctly or not using you AT product correctly with whatever table
reading commands they use. I would argue that if you have correct row and
column headings you would know what you're buying, deleting, or anything
else you can do with that row, just my thoughts.