GitHub Community
What accessibility checks should be mandatory for reusable UI components? #182742
Answered
by
hrk62880
harshad-gandhi
asked this question in
Accessibility
-
Select Topic AreaQuestion GitHub Feature AreaActions BodyContextMany teams rely heavily on reusable UI components (buttons, modals, forms, tables, etc.). DiscussionFrom your experience, what accessibility checks should be mandatory when building or reviewing Some areas I’m particularly interested in:
GoalThe goal is to gather practical guidance that can help teams bake accessibility into components Looking forward to learning from the community 🙂 |
Beta Was this translation helpful? Give feedback.
Answered by
hrk62880
Dec 26, 2025
Replies: 2 comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From my experience, accessibility works best when it’s enforced at the component level rather
than relying on developers to remember it later.
Some checks we try to make mandatory for reusable UI components:
Keyboard support by default
All interactive components should be usable without a mouse, including logical tab order
and visible focus states.
Focus management
Components like modals and drawers should trap focus and return it to the triggering element
when closed.
Semantic HTML first
Prefer native elements (
button,label,input) before adding ARIA.In many cases, proper semantics remove the need for ARIA entirely.
Screen reader verification
At least one manual check using a s…