canonical / canonical/vanilla-framework

Investigate aria-disabled vs disabled

Open
#4,299 6 comments 0 reactions 0 assignees View on GitHub
Accessibility Triaged: Pragma Triaged: v4 WG: Validated
Dominant language
HTML
Stars
983
Forks
216
Avg merge
3d 13h
Merged PRs (30d)
3

Description

There are some accessibility issues with using the native browser `disabled` attribute, as it hides the element from Assistive Tech.

The general advice is to use aria-disabled attribute but this doesn't come with the functionality of actually making the button disabled, or any of the styles. We need to look into how important it is to move to using aria-disabled, as it would be a lot of work.

https://a11y-101.com/development/aria-disabled

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the issue's accessibility concern and the linked aria-disabled guidance. Determine how important replacing native disabled attributes would be, including the lost disabling behavior and styles, and document the scope and recommendation as the completed investigation.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
accessibility
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.