mirror of
https://github.com/twbs/bootstrap.git
synced 2025-01-09 02:46:15 +01:00
f4a1a35cf2
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
39 lines
1.5 KiB
HTML
39 lines
1.5 KiB
HTML
---
|
||
layout: examples
|
||
title: Fixed top navbar example
|
||
extra_css:
|
||
- "navbar-top-fixed.css"
|
||
---
|
||
|
||
<nav class="navbar navbar-expand-md navbar-dark fixed-top bg-dark">
|
||
<a class="navbar-brand" href="#">Fixed navbar</a>
|
||
<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarCollapse" aria-controls="navbarCollapse" aria-expanded="false" aria-label="Toggle navigation">
|
||
<span class="navbar-toggler-icon"></span>
|
||
</button>
|
||
<div class="collapse navbar-collapse" id="navbarCollapse">
|
||
<ul class="navbar-nav mr-auto">
|
||
<li class="nav-item active">
|
||
<a class="nav-link" href="#">Home <span class="sr-only">(current)</span></a>
|
||
</li>
|
||
<li class="nav-item">
|
||
<a class="nav-link" href="#">Link</a>
|
||
</li>
|
||
<li class="nav-item">
|
||
<a class="nav-link disabled">Disabled</a>
|
||
</li>
|
||
</ul>
|
||
<form class="form-inline mt-2 mt-md-0">
|
||
<input class="form-control mr-sm-2" type="text" placeholder="Search" aria-label="Search">
|
||
<button class="btn btn-outline-success my-2 my-sm-0" type="submit">Search</button>
|
||
</form>
|
||
</div>
|
||
</nav>
|
||
|
||
<main role="main" class="container">
|
||
<div class="jumbotron">
|
||
<h1>Navbar example</h1>
|
||
<p class="lead">This example is a quick exercise to illustrate how fixed to top navbar works. As you scroll, it will remain fixed to the top of your browser’s viewport.</p>
|
||
<a class="btn btn-lg btn-primary" href="{{< docsref "/components/navbar" >}}" role="button">View navbar docs »</a>
|
||
</div>
|
||
</main>
|