Is your feature request related to a problem? Please describe.
I've found accessibility guidance advising the use of the aria-disabled attribute instead of the disabled attribute for form controls. (See https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-disabled.) Modern ARIA-compliant browsers prevent activation of and editing in controls on which aria-disabled is set in the same manner as they do for disabled controls. However, they don't hide those controls from the screen reader, from the reading or tab order. (Instead, the screen reader informs the user that they're disabled.) It's essential to screen reader users to know that the controls are there.
However, USWDS 2.13.1 doesn't take note of aria-disabled, so the visual user has no cues that controls have been disabled by use of that attribute.
Describe the solution you'd like
Style controls with aria-disabled identically to controls with disabled.
Describe alternatives you've considered
An alternative would be to stick, as the web developer, with disabled, but the accessibility consideration seems to have merit.
Additional context
None.
Is your feature request related to a problem? Please describe.
I've found accessibility guidance advising the use of the
aria-disabledattribute instead of thedisabledattribute for form controls. (See https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-disabled.) Modern ARIA-compliant browsers prevent activation of and editing in controls on whicharia-disabledis set in the same manner as they do fordisabledcontrols. However, they don't hide those controls from the screen reader, from the reading or tab order. (Instead, the screen reader informs the user that they're disabled.) It's essential to screen reader users to know that the controls are there.However, USWDS 2.13.1 doesn't take note of
aria-disabled, so the visual user has no cues that controls have been disabled by use of that attribute.Describe the solution you'd like
Style controls with
aria-disabledidentically to controls withdisabled.Describe alternatives you've considered
An alternative would be to stick, as the web developer, with
disabled, but the accessibility consideration seems to have merit.Additional context
None.