1944596 - If `aria-disabled="true"` is present on a container, and it is then removed or value changed to "false", all focusables inside container are still announced as "disabled" by NVDA.

Status: RESOLVED DUPLICATE of bug 1899960

(Core :: Disability Access APIs, defect)

Description

[Rich Caloggero]

Attachment: This tests case where aria-disabled on container as described above, as well as when aria-disabled on focusable element itself. also tests case where attribute's value is changed to "false" as well as when attribute completely removed.

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0

Steps to reproduce:

• set aria-disabled="true" on a container which contains at least one focusable item such as button or a
• focus on the focusable element and NVDA correctly reports "disabled"
• change state of aria-disabled on container to "false", or remove the attribute altogether
• focus the focusable item again with NVDA and NVDA still reports "disabled"

Actual results:

NVDA still reports "disabled" after aria-disabled removed or value changed to "false" when focusable element gains focus.

Chrome does not exhibit this behavior.

Expected results:

NVDA should have not announced "disabled" when the focusable element gained focus.

Comment 1

[Rich Caloggero]

Comment on attachment 9462546 [details]
This tests case where aria-disabled on container as described above, as well as when aria-disabled on focusable element itself. also tests case where attribute's value is changed to "false" as well as when attribute completely removed.

I erroneously stated that NVDA announced "disabled". THe correct announcement is "unavailable". Could not figure out how to change the bug description or steps to reproduce etc.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Disability Access APIs' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 3

[Rich Caloggero]

Attachment: Simpler test: only tests case where aira-disabled is removed or has it's value changed on a container.

Adding simpler test.

Comment 5

[James Teh [:Jamie]]

Chrome does not exhibit this behavior.

My testing suggests this isn't quite correct. Consider this test case:
data:text/html,<div id="group" role="group" aria-disabled="true"><input></div><button onclick="group.ariaDisabled = (group.ariaDisabled == 'true') ? 'false' : 'true';">Toggle
The text box starts as disabled. If you press the toggle button, the text box still remains disabled, even though aria-disabled has been removed from the group. Only when you tab to the text box does it suddenly lose its disabled state. This is better than Firefox, where the disabled state never gets cleared, but it's still not correct.