RE: Considering order: labels for checkboxes and radio buttons

Correct, aria-flowto support is spotty.

BTW, aria-flowsto is not intended to manipulate or specify default reading order of things like widgets and their labels. Following a flowsto relationship requires special intent on the part of the user.

There were some ideas in ARIA 1.0 that were not tested in practice before the spec was finalized. The aria-flowsto and aria-flowsfrom properties are among them. While they are intended to solve a problem that does sometimes occur, and while their browser implementability was tested, their suitability for solving the problem and the utility they might provide to assistive technology users have not really been proven. That does not mean they cannot be proven; it just hasn't been anyone's priority.

Starting with ARIA 1.2, we have a new process that involves authoring and assistive technology implementation to help avoid such misses and long-term delays.

Best,
Matt

-----Original Message-----
From: Elizabeth Linnetz <elizabeth.linnetz@theprimacy.com> 
Sent: Monday, July 8, 2019 3:19 AM
To: Steve Green <steve.green@testpartners.co.uk>; w3c WAI List <w3c-wai-ig@w3.org>
Subject: RE: Considering order: labels for checkboxes and radio buttons

Out of curiosity, how much support is there for aria-flowto? We don't use it because according to the w3, support is really spotty - is there updated information on that somewhere? 

Thanks!

-----Original Message-----
From: Steve Green <steve.green@testpartners.co.uk> 
Sent: Thursday, July 4, 2019 7:36 AM
To: w3c WAI List <w3c-wai-ig@w3.org>
Subject: RE: Considering order: labels for checkboxes and radio buttons

There are two situations to consider. If a screen reader user is navigating in "forms mode", the behaviour of your two examples will be the same because only the radio button receives focus. If they are navigating in "virtual cursor mode", both the radio button and label are read out and the behaviour may well vary between screen readers. You would need to do some tests to see if the user experience is acceptable.

In the past I have found that adding an aria-label attribute to the radio button has improved the user experience and made it more consistent even though it is redundant from a WCAG compliance perspective and arguably should not change the behaviour at all.

Also, bear in mind that you can use the aria-flowto attribute to adjust the reading order for assistive technologies. That might be a way to improve the user experience if you are not able to make the changes you want to the visual appearance.

Steve Green
Managing Director
Test Partners Ltd



-----Original Message-----
From: Taliesin Smith <talilief@gmail.com> 
Sent: 04 July 2019 12:00
To: w3c WAI List <w3c-wai-ig@w3.org>
Subject: Considering order: labels for checkboxes and radio buttons

Hi Folks,
For blind access and accessibility does it matter if the HTML label element comes before or after its associated input element?

This seems like a really basic question, and I am not sure why I don’t actually have a solid answer for myself. Obvious for some control elements the label should, indeed come first, but for checkboxes, does it matter? Is there a preferred order?

Code sample:
<label for=“my-checkbox”>My Accessible Checkbox</label> <input type=“checkbox” id=“my-checkbox” >

<input type=“checkbox” id=“my-checkbox” > <label for=“my-checkbox”>My Accessible Checkbox</label>

Taliesin

Received on Wednesday, 10 July 2019 18:33:35 UTC