W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2013

Re: Aria-labelledby for button: AT support when button is self-identified

From: Sailesh Panchang <spanchang02@yahoo.com>
Date: Fri, 27 Sep 2013 11:34:40 -0700 (PDT)
Message-ID: <1380306880.34827.YahooMailBasic@web125006.mail.ne1.yahoo.com>
To: Alexander Surkov <surkov.alexander@gmail.com>, Joseph Scheuhammer <clown@alum.mit.edu>
Cc: WCAG <w3c-wai-gl@w3.org>, "w3c-wai-pf@w3.org Formats" <w3c-wai-pf@w3.org>
Hello Joseph / Alexander,
Thanks for your input / comments.
I reported the incorrect reading of buttons with aria-labelledby to NVAccess.org and FS with reference to:
See the Add to Cart buttons in section 9 for Mini Laptop and Back To School Laptop on
http://www.deque.com/techniques-labeling-standard-html-form-controls#tech9
Response to bug filed on nvaccess.org:
"This only occurs in browse mode. If we rendered the label as specified in
 browse mode, you would see the heading itself and then the heading content
 duplicated as part of the button, so I think the current behaviour makes
 sense. However, it should probably honour the label as specified when
 tabbing and perhaps quick navigation."

Response from Freedom Scientific:
"We have spent some time in reviewing this information, and indeed have found
that JAWS 14.0 does exhibit this behavior, however in JAWS 15.0, some of the
behavior only exists in Internet Explorer.
Our development team has added these issues to their schedule for possible
resolution for JAWS 15.0.
Thanks again for reporting these issues to us, and we apologize for any
inconvenience."

I wrote back to FS thanking them and  urging them to include the bug fixes in next patch for JFW 14 because not all users can upgrade to a new version every time.
Thanks and regards,
Sailesh Panchang



--------------------------------------------
On Wed, 9/25/13, Joseph Scheuhammer <clown@alum.mit.edu> wrote:

 Subject: Re: Aria-labelledby for button: AT support when button is self-identified
 To: "Alexander Surkov" <surkov.alexander@gmail.com>
 Cc: "Sailesh Panchang" <spanchang02@yahoo.com>, "WCAG" <w3c-wai-gl@w3.org>, "w3c-wai-pf@w3.org Formats" <w3c-wai-pf@w3.org>
 Date: Wednesday, September 25, 2013, 11:12 AM
 
 Hi Alex,
 
 I looked at what FF (v23.0.1) is exposing using Sailesh's
 markup.
 
 For the first button <input>, FF exposes an accessible
 name of "Select Policy Whole Life Policy 1".  It's a
 concatenation of the value of the input and the h3 text
 referenced via aria-labelledby.
 
 Similarly, FF exposes, "Select Policy Term Policy 1" for the
 second button.
 
 > Question: AT should expose the aria-labelledby i.e. the
 h3 text and the value attribute of the button in the above
 example, right?
 
 The AT should relay what the browser is exposing through the
 accessibility API, or at least base their "output" on
 that.  As Alex, notes:
 
 > However some screen readers do "a little bit
 > more" than plain accessible name announcement,
 > 
 
 -- ;;;;joseph.
 
 
 'A: After all, it isn't rocket science.'
 'K: Right. It's merely computer science.'
              - J. D.
 Klaun -
 
 
 
 
Received on Friday, 27 September 2013 18:35:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:32:51 UTC