Accessibility finding
A control marked disabled still works, a field marked required is not checked, a dialog comes last in the Tab order
Accessibility Error Severity: Medium
Part of the audit ARIA contradicts the element or its real state. Finding id: accessibility.interactionProbes.
What it costs you
A screen reader announces the control as unavailable, so its users skip something that works for everyone else. Or the control should be off, and they can trigger it by accident.
What to do
Worth checking which side is right. If the control should be off, ignore clicks and key presses in its handler while aria-disabled is true, or use the native disabled attribute. If it should work, remove aria-disabled.
What it checks
- Marked disabled but still usable
- Required state not matched by validation
How to fix it
Make a disabled control do nothing
How to check: Run the interaction script again: the control no longer responds while it is marked disabled.
Make required mean the same in markup and validation
How to check: Submit the form with the field empty: it is refused and the message names the field.
Open dialogs with showModal()
How to check: Open the dialog with the keyboard and press Tab: focus is inside the dialog.
A real case
In WebAIM's 2026 scan of the top one million home pages, pages that used ARIA had more detected errors on average (59.1) than pages that did not (42).
How to verify by hand
A screen reader announcing the control before and after interaction.
What this relies on
The visual state is correct; the script forgot to update the attribute.