You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(design): forward aria attributes to inputs #511
Two accessibility gaps in @elixir-cloud/design, found while adding field validation to the Cloud Registry service form (#453, PR #510):
Input components don't pass aria-* attributes (e.g. aria-invalid, aria-describedby) to their inner native inputs, so screen readers don't announce field errors that consumers attach.
The collapsible component's trigger never updates aria-expanded, so its open/closed state isn't announced.
Proposed fix
Forward aria-* attributes (at least aria-invalid, aria-describedby, aria-label, aria-required) from the host element to the inner input in the input-like components.
Keep aria-expanded on the collapsible trigger in sync with its state.
Acceptance criteria
Tests show the forwarded attributes on the inner inputs and aria-expanded toggling.
No change to the components' public APIs other than the forwarding.
Activity
salihudickson commentedon Oct 31, 2026
was about to suggest this, I'll take it up.
salihudickson commentedon Oct 31, 2026
Besides aria attributes, I think it we should also forward a list of other native attributes depending on the component.