Accessibility: mark up .input-button as semantic buttons #323
+18
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As described here: #286 the 'button's coded into deep-chat are not semantic buttons and as such are accessible to keyboard/switch users nor screen-reader users.
role="button"
This PR adds the semantic
role
attribute with thevalue
ofbutton
to the.input-button
elements so it announces to screen-readers that it is a button.Disabled buttons
It also adds other semantics such as
aria-disabled="true"
instead of just styling the buttons to look disabled so screen-reader users hear when the button is disabledNote: rather than having
aria-disabled="false"
when the button is enabled, instead we remove the attributeLoading/busy buttons
It also adds other semantics such as
aria-busy="true"
instead of just styling the buttons to look busy so screen-reader users hear when the button is loading.Note: rather than having
aria-busy="false"
when the button is not busy, instead we remove the attributeKeyboard/Switch accessibility
:hover
styles in CSS are duplicated for :focus-visible so non-mouse users can see when the button is in focus.