diff options
| author | Patrick H. Lauke <redux@splintered.co.uk> | 2021-12-23 10:15:36 +0300 |
|---|---|---|
| committer | XhmikosR <xhmikosr@gmail.com> | 2022-01-04 10:50:53 +0300 |
| commit | 8469f695f99302f35053da4c621a651920c411f5 (patch) | |
| tree | 8a5a8941df0a5e5de87ad04febe42082c590de5c | |
| parent | bee3847e6d53da5787ada49ead9f25d6811f5622 (diff) | |
Strengthen and expand note about dynamic tabs with dropdown menus (#35588)
following on from https://github.com/twbs/bootstrap/pull/35213 this
- expands the note, making it clear it's not supported
- makes it a callout
| -rw-r--r-- | site/content/docs/4.6/components/navs.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/site/content/docs/4.6/components/navs.md b/site/content/docs/4.6/components/navs.md index 7d17523468..c2908ad7ca 100644 --- a/site/content/docs/4.6/components/navs.md +++ b/site/content/docs/4.6/components/navs.md @@ -309,7 +309,9 @@ If you're building our JavaScript from source, it [requires `util.js`]({{< docsr Dynamic tabbed interfaces, as described in the [<abbr title="Web Accessibility Initiative">WAI</abbr> <abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices](https://www.w3.org/TR/wai-aria-practices/#tabpanel), require `role="tablist"`, `role="tab"`, `role="tabpanel"`, and additional `aria-` attributes in order to convey their structure, functionality and current state to users of assistive technologies (such as screen readers). -Note that dynamic tabbed interfaces should <em>not</em> contain dropdown menus, as this causes both usability and accessibility issues. From a usability perspective, the fact that the currently displayed tab's trigger element is not immediately visible (as it's inside the closed dropdown menu) can cause confusion. From an accessibility point of view, there is currently no sensible way to map this sort of construct to a standard WAI ARIA pattern, meaning that it cannot be easily made understandable to users of assistive technologies. +{{< callout danger >}} +Note that the tab JavaScript plugin **does not** support tabbed interfaces that contain dropdown menus, as these cause both usability and accessibility issues. From a usability perspective, the fact that the currently displayed tab's trigger element is not immediately visible (as it's inside the closed dropdown menu) can cause confusion. From an accessibility point of view, there is currently no sensible way to map this sort of construct to a standard WAI ARIA pattern, meaning that it cannot be easily made understandable to users of assistive technologies. +{{< /callout >}} <div class="bd-example bd-example-tabs"> <ul class="nav nav-tabs" id="myTab" role="tablist"> |