WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: HTML disabled or aria-disabled on checkbox

for

From: tim.harshbarger@deque.com
Date: Jun 7, 2023 8:17AM

I agree. Also, I do believe that the HTML disabled attribute can be styled with CSS.

While I do agree with what is said, I will mention that there are other opinions about this. The reality is that WCAG does not require that disabled elements be removed from the tab order. Also, there are some people who feel it can be easier for screen reader users to discover disabled controls if they are part of the tab order.

I only mention this because, while my opinion is different, I do think they have good points to make for their viewpoint on this subject.

Thanks!
Tim
-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen walker
Sent: Wednesday, June 7, 2023 8:01 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] HTML disabled or aria-disabled on checkbox

If you follow the first rule of ARIA,
https://www.w3.org/TR/aria-in-html/#rule1, then you'd use the "disabled"
HTML attribute.

The "disabled" HTML attribute will not only provide the styling but will also provide the *behavior* of an inactive element. You can't click on it or tab to it or press enter/space on it. It's inactive state will be conveyed to assistive technology if you navigate to that element using some navigation method of the AT, for example, the down arrow with a screen reader.

The aria-disabled attribute will *only* provide a hint to assistive technology that the element is inactive. It won't give you any behavior.
You'd have to make the element inactive by ignoring events on it via javascript.