diff options
| author | Patrick H. Lauke <[email protected]> | 2021-09-09 12:49:06 +0100 |
|---|---|---|
| committer | GitHub <[email protected]> | 2021-09-09 14:49:06 +0300 |
| commit | f4a1a35cf245566018b109af7b56d69cd6f13975 (patch) | |
| tree | 73562082588f273ec1e28d6131176f909fb1af10 /docs/_includes/css/code.html | |
| parent | 408252eff147c1f48a45db1ea47697c89dd9dace (diff) | |
| download | bootstrap-f4a1a35cf245566018b109af7b56d69cd6f13975.tar.xz bootstrap-f4a1a35cf245566018b109af7b56d69cd6f13975.zip | |
v4: Disabled link cleanup (#34924)
manual backport of #34886
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
Diffstat (limited to 'docs/_includes/css/code.html')
0 files changed, 0 insertions, 0 deletions