E-mail List Archives
Thread: ARIA with screen readers
Number of posts in this thread: 3 (In chronological order)
From: Sumit Patel
Date: Sat, Dec 25 2021 7:43AM
Subject: ARIA with screen readers
No previous message | Next message →
Hi all,
I was going through some of the ARIA examples in multiple websites.
some doubts popped up in my mind.
1. aria-required attribute In radio groups,
I have seen both the practices to make the screen reader to announce
the required attribute.
In the first, using aria-required attribute in the div tag.
Second one is providing the same to individual radio buttons
Are both acceptable since screen reader convey the required attribute
in both the scenarios?
2. Using aria-sort to convey the ascending / descending state for the
sortable table
I have observed Talkback screen reader is not conveying the state in
both activation and swipe navigation to the user. Seems like talkback
issue.
I have seen talkback is identifying the state in some of the examples.
but, they have used aria-live or aria-label to make it announce in
those examples. Seems like aria-sort is not supported with talkback
screen reader.
But, I couldn't find any github or any other discussion form link to
confirm it. if anyone has it, please share with me
Thanks in advance,
Regards,
Sumit
From: Birkir R. Gunnarsson
Date: Sun, Dec 26 2021 9:04AM
Subject: Re: ARIA with screen readers
← Previous message | Next message →
1. aria-required is valid on the grouping element of radio buttons
(the <fieldset> or <div> with role="group" or role="radiogroup"). I'd
put it there rather than on each individual radio button (if you are
using the HTML required attribute, I think you have to put it on the
individual radio inputs, it's not valid to put it on the <fieldset>).
The HTML spec recommends only using radio buttons if one is already
selected. If that's the case you wouldn't need to mark the group as
required since users can't de-select a radio button without selecting
another.
Businesses don't like this approach, however, because they don't want
to make any choices for the customer.
2. This is likely a Talkback bug (assuming the attribute is used on a
<th> element).
If you can find where to file it, go ahead. If you want others to
comment or follow up you can send the bug reference to this list.
Thanks
-Birkir
On 12/25/21, Sumit Patel < = EMAIL ADDRESS REMOVED = > wrote:
> Hi all,
>
> I was going through some of the ARIA examples in multiple websites.
> some doubts popped up in my mind.
>
> 1. aria-required attribute In radio groups,
> I have seen both the practices to make the screen reader to announce
> the required attribute.
> In the first, using aria-required attribute in the div tag.
> Second one is providing the same to individual radio buttons
> Are both acceptable since screen reader convey the required attribute
> in both the scenarios?
>
>
> 2. Using aria-sort to convey the ascending / descending state for the
> sortable table
> I have observed Talkback screen reader is not conveying the state in
> both activation and swipe navigation to the user. Seems like talkback
> issue.
> I have seen talkback is identifying the state in some of the examples.
> but, they have used aria-live or aria-label to make it announce in
> those examples. Seems like aria-sort is not supported with talkback
> screen reader.
>
> But, I couldn't find any github or any other discussion form link to
> confirm it. if anyone has it, please share with me
>
> Thanks in advance,
>
> Regards,
> Sumit
> > > > >
--
Work hard. Have fun. Make history.
From: Sumit Patel
Date: Sun, Dec 26 2021 10:25AM
Subject: Re: ARIA with screen readers
← Previous message | No next message
Thanks for the reply
I have recently seen one issue with voiceover in iPhone and iPad when
they've used aria-required for the div .
In between each radio buttons they have given tooltips which describes
the radio button option. It was working fine with other combinations.
but, with voiceover - both the radio buttons and tooltips were reading
as required on swipe navigation.
To avoid the issue we had to remove aria-required from the div tag and
put it on each individual radio buttons.
On 26/12/2021, Birkir R. Gunnarsson < = EMAIL ADDRESS REMOVED = > wrote:
> 1. aria-required is valid on the grouping element of radio buttons
> (the <fieldset> or <div> with role="group" or role="radiogroup"). I'd
> put it there rather than on each individual radio button (if you are
> using the HTML required attribute, I think you have to put it on the
> individual radio inputs, it's not valid to put it on the <fieldset>).
>
> The HTML spec recommends only using radio buttons if one is already
> selected. If that's the case you wouldn't need to mark the group as
> required since users can't de-select a radio button without selecting
> another.
> Businesses don't like this approach, however, because they don't want
> to make any choices for the customer.
>
> 2. This is likely a Talkback bug (assuming the attribute is used on a
> <th> element).
> If you can find where to file it, go ahead. If you want others to
> comment or follow up you can send the bug reference to this list.
> Thanks
> -Birkir
>
>
> On 12/25/21, Sumit Patel < = EMAIL ADDRESS REMOVED = > wrote:
>> Hi all,
>>
>> I was going through some of the ARIA examples in multiple websites.
>> some doubts popped up in my mind.
>>
>> 1. aria-required attribute In radio groups,
>> I have seen both the practices to make the screen reader to announce
>> the required attribute.
>> In the first, using aria-required attribute in the div tag.
>> Second one is providing the same to individual radio buttons
>> Are both acceptable since screen reader convey the required attribute
>> in both the scenarios?
>>
>>
>> 2. Using aria-sort to convey the ascending / descending state for the
>> sortable table
>> I have observed Talkback screen reader is not conveying the state in
>> both activation and swipe navigation to the user. Seems like talkback
>> issue.
>> I have seen talkback is identifying the state in some of the examples.
>> but, they have used aria-live or aria-label to make it announce in
>> those examples. Seems like aria-sort is not supported with talkback
>> screen reader.
>>
>> But, I couldn't find any github or any other discussion form link to
>> confirm it. if anyone has it, please share with me
>>
>> Thanks in advance,
>>
>> Regards,
>> Sumit
>> >> >> >> >>
>
>
> --
> Work hard. Have fun. Make history.
> > > > >