W3C home > Mailing lists > Public > public-aria@w3.org > February 2016

Re: Why is aria-expanded invalid with a checkbox?

From: Birkir Gunnarsson <birkir.gunnarsson@deque.com>
Date: Tue, 2 Feb 2016 18:26:49 -0500
Message-ID: <CA++QhYx=bRefo91X29PVX89CvPhmnoh+fayYrL_k08HL0Krjaw@mail.gmail.com>
To: James Nurthen <james.nurthen@oracle.com>
Cc: public-aria@w3.org
As a screen reader, if I move to a checkbox and hear:
"I hold a non immigrant visa, checkbox not checked collapsed"
(<input type="checkbox" aria-expanded="false" aria-controls="niv">
<div role="region" aria-label="None Immigrant Visa information" id="niv">


I would know that checking that checkbox will cause additional content
to appear.

You are right that aria-controls hints at the same thing, but it is
not necessarily tied to the display of a section of content.
It could be a submit button that becomes enabled only after I check
the checkbox.
It could also be a section that is already visible on the page but
checking the checkbox automatically changes default UI element

the use of aria-expanded would clearly tell me that a section of the
page will be expanded or collapsed as a result of me interacting with
the checkbox, the non-visual equivalent of seeing content appear and

I am just perplexed why aria-expanded is allowed on so many roles, (I
have some difficulty seeing the use cases for some of them), but not
on a check box.

On 2/2/16, James Nurthen <james.nurthen@oracle.com> wrote:
> I'd have thought that checked in combination with aria-controls was
> enough here.
> Unless the checked and expanded state can be different (which I don't
> believe they could be) I would just use checked and aria-controls.
> On 2/2/2016 2:58 PM, Birkir Gunnarsson wrote:
>> Oh wise ones.
>> I am working with a team that is implementing a form where checking a
>> check box expands a section further down the page.
>> They actually thought of putting aria-expanded and aria-controls on
>> the check box to communicate this info to assistive technologies.
>> I had to stop the because checkbox role is not one of the 40 or so
>> roles that allow the aria-expanded property.
>> I find this curious.
>> The situation I described, where sections of a dynamic form or webpage
>> are displayed or hidden in response to user checking or unchecking a
>> check box is quite common.
>> Sure, if the section of the page is, in content order, after the
>> checkbox that controls it, users do not necessarily need to be aware
>> of the change, but it is a very smart usability decision to inform the
>> user that checking a checkbox affects contents elsewhere on the
>> webpage.
>> My questions are:
>> 1. Why was aria-expanded not considered a valid attribute with check boxes
>> and,
>> 2. Can this case be revisited? If so I'd be happy to create an issue
>> ticket if necessary.
>> Thanks
>> -Birkir
> --
> Regards, James
> Oracle <http://www.oracle.com>
> James Nurthen | Principal Engineer, Accessibility
> Phone: +1 650 506 6781 <tel:+1%20650%20506%206781> | Mobile: +1 415 987
> 1918 <tel:+1%20415%20987%201918> | Video: james.nurthen@oracle.com
> <sip:james.nurthen@oracle.com>
> Oracle Corporate Architecture
> 500 Oracle Parkway | Redwood Cty, CA 94065
> Green Oracle <http://www.oracle.com/commitment> Oracle is committed to
> developing practices and products that help protect the environment

Birkir R. Gunnarsson
Senior Accessibility Subject Matter Expert | Deque Systems
2121 Cooperative Way, Suite 210
Herndon, VA, 20171

Ph: (919) 607-27 53
Twitter: @birkir_gun
Received on Tuesday, 2 February 2016 23:27:19 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:19 UTC