| Age | Commit message (Collapse) | Author | Files | Lines |
|
* Rename `sr-only`/`sr-only-focusable`
To be more representative of the fact that these are not necessarily "screen reader" specific, but actually apply to assistive technologies in general (and also things like Alexa/Siri/etc). Goes hand-in-hand with #31133
Co-authored-by: XhmikosR <[email protected]>
|
|
* Docs: improve/expand button documentation
- since we're not doing the disabled cursor thing anymore anyway, remove confusing/unnecessary mention for link-based disabled buttons
- make the disabled toggle example using a link actually follow the preceding advice of also having `tabindex="-1"` and `aria-disabled="true"`
- tweak the link functionality callout to also still mention `aria-disabled` to reinforce the idea
- tweak toggle state description (not just `<button>`s, but also links etc...so just remove mention of `<button>` there; also reinforce accessibility aspect once more)
- add a new callout that cross-references checkbox-based toggles, and what the similarity/difference between them is
- add a matching cross-reference callout to the checkbox-based toggle buttons page
* Update link to now renamed checks-radios.md
|
|
(#31134)
* Docs: clarify that pointer events classes don't affect keyboard interaction
* Neutralise example links that are `pe-none`
|
|
Co-authored-by: Martijn Cuppens <[email protected]>
|
|
* Add a new v5.0.0-alpha2 section
* Add missing Browser versions from v5.0.0-alpha1
|
|
|
|
Co-authored-by: Alex Mohr <[email protected]>
|
|
* Docs: rename form checks page to "Checks / radios"
it's not immediately obvious that "checks" includes information about both checkboxes and radio buttons. while "checks / radios" is also still not perfect (as honestly even I didn't quite grok that "checks" meant checkboxes), it should make it slightly more obvious nonetheless
|
|
Co-authored-by: XhmikosR <[email protected]>
|
|
* docs(example): floating-labels' better Edge fallback
* docs(example): refactor floating-labels' CSS
|
|
* Move color utility callouts to start of page
Hierarchically/structurally, in the position they are currently at, the two callouts seem like they "belong" just to the "background color" section. Moving them to the start makes it clearer that those two callouts relate to everything in the page (both "Color" and "Background color" classes.
* Change heading level
otherwise the assistive technology callout looks like it's hierarchically under the "Dealing with specificity" heading
|
|
Fixes #31089.
Co-authored-by: XhmikosR <[email protected]>
|
|
* updated yarn command to install latest version
* Update README.md
Co-authored-by: XhmikosR <[email protected]>
|
|
|
|
Co-authored-by: XhmikosR <[email protected]>
Co-authored-by: Mark Otto <[email protected]>
|
|
* Fixes a typo so it displays the correct px's.
* Update gutters.md
Co-authored-by: XhmikosR <[email protected]>
|
|
|
|
* Add two new toasts examples
- Adds a new custom content example that removes the toast header and adds a custom close icon
- Adds docs for how to create your own color schemes
- Adds example of additional buttons
* Update toasts examples
- Remove span and place aria on SVG element
- Add .border-0 to color scheme example for crisper edges
* Update toasts.md
Co-authored-by: XhmikosR <[email protected]>
|
|
|
|
Co-authored-by: XhmikosR <[email protected]>
|
|
|
|
- point to WCAG 2.1 rather than 2.0
- soften/expand the language around color contrast, since the situation has definitely improved in v5 but we still can't guarantee all possible permutations of colors/opacities/etc
- minor language/stylistic tweaks
- add further resources
|
|
|
|
|
|
|
|
* Typo fix : thesse ⮞ these
* Several typo fixes
verical ⮞ vertical
availble ⮞ available
thesse ⮞ these
|
|
|
|
* Docs: fix old/broken example capture and typo
* Make example less broken-looking
don't want to give impression that now it's ok to just sprinkle `role="button"` around. this at least makes the `span` keyboard-focusable, similar to at least the start of a custom control
Co-authored-by: XhmikosR <[email protected]>
|
|
* use v5.getbootstrap.com as the site URL/CNAME
* block robots from crawling
* specify next npm tag
|
|
* v5: Add role=button cursor in Reboot
Ports the changes from #30562 made in v4.5 and adds them to v5. This replaces #30563 which sought to add this to the utility API, but the v4 PR shifted to implement an accessible solution vs a lone utility.
* Update reboot.md
Co-authored-by: XhmikosR <[email protected]>
|
|
Co-authored-by: XhmikosR <[email protected]>
|
|
|
|
|
|
|
|
|
|
Hyphen to minus for amount.
Hyphen to dash for ranges.
|
|
- The `media-breakpoint-down()` uses the breakpoint itself instead of the next breakpoint. Use `media-breakpoint-down(lg)` instead of `media-breakpoint-down(md)` to target viewports smaller than the `lg` breakpoint.
- The `media-breakpoint-between()` mixin's second parameter also uses the breakpoint itself instead of the next breakpoint. Use `media-between(sm, lg)` instead of `media-breakpoint-between(sm, md)` to target viewports between the `sm` and `lg` breakpoints.
|
|
|
|
|
|
|
|
|
|
* v5: Redo blockquote attributions
- Renames -small-* variables to -footer-*
- Updates blockquote demos with attribution to place it outside the blockquote with a figure wrapper
* Updated class name
* docs(examples): refactor blockquotes in masonry example
Co-authored-by: Gaël Poupard <[email protected]>
Co-authored-by: XhmikosR <[email protected]>
|
|
|
|
Co-authored-by: Mark Otto <[email protected]>
|
|
- Closes #28423
|
|
|
|
|
|
|
|
containers (#30932)
|
|
|