Research to ensure Accessibility of Disabled Attribute for Screen Readers

[yoezlem]

User Story

As the Product Owner of the Solid Design System, I want to ensure that the disabled attribute is implemented in an accessible way and is correctly recognized by screen readers, so that usability is improved for people with disabilities and our components meet A11y standards.

Suggested Solution

Since we’re having issues with A11y related to the disabled attribute, we need an alternative solution here - one potential solution could be the content of the smahingmagazine article.

Technical Information

• https://www.smashingmagazine.com/2021/08/frustrating-design-patterns-disabled-buttons/#making-disabled-buttons-more-inclusive

DoR

• [x] Item has business value
• [ ] Item has been estimated by the team
• [x] Item is clear and well-defined
• [x] Item dependencies have been identified

DoD

• [ ] Documentation has been created/updated (if applicable)
• [ ] Migration Guide has been created/updated (if applicable)
• [ ] Relevant E2E tests (Features, A11y, Bug fixes) are created/updated
• [ ] Relevant stories (Features, A11y) are created/updated
• [ ] Implementation works successfully on feature branch

[yoezlem]

Will create a subtask ticket for that, for evaluating if there is an a11y way to technically provide the disabled form elements.