diff options
| author | Patrick H. Lauke <[email protected]> | 2021-09-06 20:14:21 +0100 |
|---|---|---|
| committer | GitHub <[email protected]> | 2021-09-06 22:14:21 +0300 |
| commit | aa06dffdf65f15f6663159c9785432b82adde20f (patch) | |
| tree | 86b87180ae0a131f57b3354a342e2722fe480e3f /js/src/dropdown.js | |
| parent | 16aab88a67add236b6857207b32b85b536b1a0c6 (diff) | |
| download | bootstrap-aa06dffdf65f15f6663159c9785432b82adde20f.tar.xz bootstrap-aa06dffdf65f15f6663159c9785432b82adde20f.zip | |
Disabled link cleanup (#34886)
* Disabled link cleanup
per https://www.w3.org/TR/html-aria/#docconformance
> It is NOT RECOMMENDED to use `aria-disabled="true"` on an `a` element with an `href` attribute.
>
>NOTE
>If a link needs to be "disabled", remove the `href` attribute.
This PR removes the unnecessary `href="#"`, `tabindex="-1"`, and `aria-disabled="true"` from disabled links in both docs pages and examples. `aria-disabled="true"` *is* kept for disabled link-based buttons (that have `role="button"`) as there it's appropriate to use (you *want* to convey to assistive technologies that this thing you're claiming is a button is also disabled at the moment)
Further, the PR extends the "Link functionality caveat" to show the "proper" way (removing `href` and adding `.disabled` class only) to disable a link, but then explains what to do if that's not possible (and then keeps an example with all the traditional `href="#" tabindex="-1" aria-disabled="true"`, but explains clearly that it's not ideal). Same sort of explanation is also added to the pointer event utilities page
* Turn big note into actual normal doc text
Co-authored-by: Mark Otto <[email protected]>
Co-authored-by: Mark Otto <[email protected]>
Co-authored-by: XhmikosR <[email protected]>
Diffstat (limited to 'js/src/dropdown.js')
0 files changed, 0 insertions, 0 deletions