WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Dojo Dijit Checkboxes Double Announcing in Screen Readers

for

Number of posts in this thread: 4 (In chronological order)

From: Graham Armfield
Date: Mon, Mar 02 2015 7:32AM
Subject: Dojo Dijit Checkboxes Double Announcing in Screen Readers
No previous message | Next message →

Dear All,

I'm helping someone with the accessibility of a website that's using the
Dojo Dijit controls.

They are finding that with the Dijit checkboxes the state gets announced in
a confusing way by screen readers.

The initial code looks like this (I've edited out the various data-dojo
attributes)

<input type="checkbox" id="blah" class="blah" checked aria-checked="true">

The label for this control is correctly linked:
<label for="blah">Select All</label>

JAWS screen reader announces "Checked Select all, checked" when the
checkbox is checked and "Unchecked Select all, checked" when the checkbox
is not checked.

Initially I thought this may be because of the unnecessary doubling up of
the state in the aria-checked attribute. I felt this was superfluous since
the control is a native HTML checkbox.

Even after removal of the aria-checked attribute the result is still the
same.

I'm not sure what to suggest next, has anyone any experience of using Dijit
checkboxes and making them fully accessible?

Thanks
Regards
Graham Armfield



coolfields.co.uk <http://www.coolfields.co.uk/>;
M:07905 590026
T: 01483 856613
@coolfields <https://twitter.com/coolfields>

From: Jonathan Avila
Date: Mon, Mar 02 2015 7:38AM
Subject: Re: Dojo Dijit Checkboxes Double Announcing in Screen Readers
← Previous message | Next message →

> <input type="checkbox" id="blah" class="blah" checked aria-checked="true">

It's possible that the use of aria-checked state along with the HTML checked property is causing the issue. ARIA states are either true or false while HTML properties such as checked indicate it is checked while when it is not checked there is no checked property set.

Jonathan

-- 
Jonathan Avila 
Chief Accessibility Officer
SSB BART Group 
= EMAIL ADDRESS REMOVED =
Phone 703.637.8957  
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter


-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Graham Armfield
Sent: Monday, March 02, 2015 9:32 AM
To: WebAIM Discussion List
Subject: [WebAIM] Dojo Dijit Checkboxes Double Announcing in Screen Readers

Dear All,

I'm helping someone with the accessibility of a website that's using the Dojo Dijit controls.

They are finding that with the Dijit checkboxes the state gets announced in a confusing way by screen readers.

The initial code looks like this (I've edited out the various data-dojo
attributes)

<input type="checkbox" id="blah" class="blah" checked aria-checked="true">

The label for this control is correctly linked:
<label for="blah">Select All</label>

JAWS screen reader announces "Checked Select all, checked" when the checkbox is checked and "Unchecked Select all, checked" when the checkbox is not checked.

Initially I thought this may be because of the unnecessary doubling up of the state in the aria-checked attribute. I felt this was superfluous since the control is a native HTML checkbox.

Even after removal of the aria-checked attribute the result is still the same.

I'm not sure what to suggest next, has anyone any experience of using Dijit checkboxes and making them fully accessible?

Thanks
Regards
Graham Armfield



coolfields.co.uk <http://www.coolfields.co.uk/>;
M:07905 590026
T: 01483 856613
@coolfields <https://twitter.com/coolfields>

From: Graham Armfield
Date: Mon, Mar 02 2015 8:03AM
Subject: Re: Dojo Dijit Checkboxes Double Announcing in Screen Readers
← Previous message | Next message →

Jonthan said:
>It's possible that the use of aria-checked state along with the
>HTML checked property is causing the issue. ARIA states
>are either true or false while HTML properties such as
>checked indicate it is checked while when it is not checked
>there is no checked property set.

Thanks for your response Jonathan. Removing the aria-checked attribute is
something I thought of straight away. But after removing the attribute the
result was still the same.


Regards
Graham Armfield



coolfields.co.uk <http://www.coolfields.co.uk/>;
M:07905 590026
T: 01483 856613
@coolfields <https://twitter.com/coolfields>

From: JAKE JOEHL
Date: Mon, Mar 02 2015 8:58PM
Subject: Re: Dojo Dijit Checkboxes Double Announcing in Screen Readers
← Previous message | No next message

I have noticed this on numerous occasions, not only with checkboxes and not only with VoiceOver. To me it is just a minor nuisance, but I suppose it does need to be improved upon. I'm thinking mainly of surveys I've taken where the questions and/or their accompanying answer choices will be repeated twice or even more times. I'm reminded of a situation that happened at my volunteer job not long ago. I am the Social Media Assistant for a nonprofit disability-related organization based here in Illinois called JJ's List. We have a website where people can review the disability awareness—or disability unawareness—of businesses. One of the businesses that joined our directory not so long ago was Survey Monkey. What happened was that a review was posted by a screen reader user indicating that the Survey Monkey website worked great with screen readers, which it still does. But this reviewer also posted that one minor bug they found was that in several cases, the screen readers that said reviewer used all echoed things multiple times. Someone then contacted our founder saying that this review had been posted, and that the reviewer had actually claimed they couldn't use their surveys. This wasn't true, since the reviewer had in fact reported positive results when trying to access Survey Monkey. So the email was forwarded to me, and I helped them join our directory.
Jake
Please visit me at http://jazzyjj.dreamwidth.org .



On Mar 2, 2015, at 9:03 AM, Graham Armfield < = EMAIL ADDRESS REMOVED = > wrote:

Jonthan said:
> It's possible that the use of aria-checked state along with the
> HTML checked property is causing the issue. ARIA states
> are either true or false while HTML properties such as
> checked indicate it is checked while when it is not checked
> there is no checked property set.

Thanks for your response Jonathan. Removing the aria-checked attribute is
something I thought of straight away. But after removing the attribute the
result was still the same.


Regards
Graham Armfield



coolfields.co.uk <http://www.coolfields.co.uk/>;
M:07905 590026
T: 01483 856613
@coolfields <https://twitter.com/coolfields>