Age | Commit message (Collapse) | Author |
|
Correct table lightening variable to match the variable name defined and described in the loop variable section above
|
|
remove a unnecessary <abbr> tag
|
|
Co-authored-by: XhmikosR <xhmikosr@gmail.com>
|
|
|
|
Co-authored-by: XhmikosR <xhmikosr@gmail.com>
|
|
|
|
|
|
While it is understood that this is just an example, the visible text (label) of "Works with selects" and the `aria-label="Floating label select example"` created a [WCAG 2.5.3 Label in name](https://www.w3.org/WAI/WCAG21/quickref/#label-in-name) failure.
As the `aria-label` isn't necessary here since this `select` is already provided an accessible name by its `label` element, removing the unnecessary `aria-label` seems the best course of action as:
* removing it solves the WCAG issue
* it removes the potential implication to developers that they'd even _need_ an `aria-label` here, let alone indirectly suggesting that it's ok for the visible text and accessible name to be out of alignment
|
|
documentation (#35328)
Co-authored-by: XhmikosR <xhmikosr@gmail.com>
|
|
|
|
|
|
(#35223)
* Add missing `role="search"` and `type="search"` in navbar doc and examples
* Update site/content/docs/5.1/components/navbar.md
* Remove warning callout about ensuring correct search role in navbar doc
Co-authored-by: Gaël Poupard <ffoodd@users.noreply.github.com>
Co-authored-by: XhmikosR <xhmikosr@gmail.com>
|
|
|
|
Co-authored-by: XhmikosR <xhmikosr@gmail.com>
|
|
Co-authored-by: louismaximepiton <louismaxime.piton@orange.com>
|
|
* docs(RTL): fix typo in Hello World! sentence
* chore(docs): Cspell arabic words update
|
|
(#35124)
Co-authored-by: XhmikosR <xhmikosr@gmail.com>
|
|
|
|
* Separate container classes from enable-grid-classes optoin
* Document the new option
* Mention in migration guide
Co-authored-by: XhmikosR <xhmikosr@gmail.com>
|
|
|
|
|
|
Co-authored-by: XhmikosR <xhmikosr@gmail.com>
|
|
|
|
https://github.com/twbs/bootstrap/issues/34885
|
|
Changes some latin/dummy text to English so spellcheck linter passes
|
|
* docs: Add role="switch" to switches
* Tweak/expand explanation about assistive technologies
Co-authored-by: Patrick H. Lauke <redux@splintered.co.uk>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Prepare v5.1.1.
* Dist
|
|
|
|
* 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 <markd.otto@gmail.com>
Co-authored-by: Mark Otto <markd.otto@gmail.com>
Co-authored-by: XhmikosR <xhmikosr@gmail.com>
|
|
(#34910)
* Docs: Add Callout to Stacks Helper page about limited flexbox gap support
Fixes: #34737
* Update stacks.md
* Delete callout-warning-flexbox-gap.md
Co-authored-by: XhmikosR <xhmikosr@gmail.com>
|
|
(#34892)
|
|
|
|
* Remove the font-family-* override vars from Reboot build
* Update Reboot docs to mention CSS variables
|
|
|
|
It's the default.
|
|
|
|
|
|
We don't use the same approach with a button on the Placeholders page.
|
|
|
|
|
|
|
|
(#34701)
|
|
|