diff --git a/apps/docs/.vitepress/theme/Layout.vue b/apps/docs/.vitepress/theme/Layout.vue index e34fb4e00..ed2fed884 100644 --- a/apps/docs/.vitepress/theme/Layout.vue +++ b/apps/docs/.vitepress/theme/Layout.vue @@ -314,14 +314,6 @@ watch( color: var(--white); } - @mixin hover-focus-active() { - &:hover, - &:focus, - &:active { - @content; - } - } - .doc-content > div > { h2, h3, diff --git a/apps/docs/src/data/components/modal.data.ts b/apps/docs/src/data/components/modal.data.ts index c0a364db7..ab6a548ba 100644 --- a/apps/docs/src/data/components/modal.data.ts +++ b/apps/docs/src/data/components/modal.data.ts @@ -349,10 +349,10 @@ export default { description: 'CSS class (or classes) to apply to the title', }, { - prop: 'titleSrOnly', + prop: 'titleVisibilityHiddenOnly', type: 'boolean', default: false, - description: "Wraps the title in an '.sr-only' wrapper", + description: "Wraps the title in an '.visually-hidden' wrapper", }, { prop: 'titleTag', diff --git a/apps/docs/src/docs/components/form-input.md b/apps/docs/src/docs/components/form-input.md index 7b5eea6aa..2380215a7 100644 --- a/apps/docs/src/docs/components/form-input.md +++ b/apps/docs/src/docs/components/form-input.md @@ -123,7 +123,7 @@ If the `type` prop is set to an input type that is not supported (see above), a ### Range type input -Inputs with type `range` render using Bootstrap v5's `.custom-range` class. The track (the +Inputs with type `range` render using Bootstrap v5's `.form-range` class. The track (the background) and thumb (the value) are both styled to appear the same across browsers. Range inputs have implicit values for `min` and `max` of `0` and `100` respectively. You may specify diff --git a/apps/docs/src/docs/components/form.md b/apps/docs/src/docs/components/form.md index 812c89313..07495f279 100644 --- a/apps/docs/src/docs/components/form.md +++ b/apps/docs/src/docs/components/form.md @@ -280,7 +280,7 @@ Custom form controls and selects are also supported. ### Alternatives to hidden labels Assistive technologies such as screen readers will have trouble with your forms if you do not include -a label for every input. For these inline forms, you can hide the labels using the `.sr-only` class. +a label for every input. For these inline forms, you can hide the labels using the `.visibility-hidden` class. There are further alternative methods of providing a label for assistive technologies, such as the `aria-label`, `aria-labelledby` or `title` attributes. If none of these are present, assistive technologies may resort to using the `placeholder` attribute, if present, but note that use of diff --git a/apps/docs/src/docs/components/input-group.md b/apps/docs/src/docs/components/input-group.md index a54f70342..36be86737 100644 --- a/apps/docs/src/docs/components/input-group.md +++ b/apps/docs/src/docs/components/input-group.md @@ -67,8 +67,6 @@ Easily extend form controls by adding text, buttons, or button groups on either You can attach addons using either props, named slots and/or sub-components. -**Note** Bootstrap 5 dropped `.input-group-append` and `.input-group-prepend`. You can now just add buttons and `.input-group-text` as direct children of the input groups. The sub-components are added for compatibility reasons. - ### Using `prepend` and `append` props Values will be internally wrapped by a `BInputGroupText` to display correctly. @@ -334,23 +332,42 @@ the control and the hidden label. Multiple add-ons are supported and can be mixed with checkbox and radio input versions. +
+ + + + + $ + + +
+
+ + + + + + $ + +
+ - + Link 1 Link 2 Disabled @@ -418,7 +418,7 @@ Note that the expanded scope property only works when supplying the target prop - + Link 1 Link 2 Disabled diff --git a/apps/docs/src/docs/reference/accessibility.md b/apps/docs/src/docs/reference/accessibility.md index 92bfc2890..51eff991a 100644 --- a/apps/docs/src/docs/reference/accessibility.md +++ b/apps/docs/src/docs/reference/accessibility.md @@ -51,7 +51,7 @@ Content which should be visually hidden, but remain accessible to assistive tech -For visually hidden interactive controls, such as traditional “skip” links, use the `.visually-hidden-focusable` class. This will ensure that the control becomes visible once focused (for sighted keyboard users). Watch out, compared to the equivalent `.sr-only` and `.sr-only-focusable` classes in past versions, Bootstrap 5’s `.visually-hidden-focusable` is a standalone class, and must not be used in combination with the `.visually-hidden` class. +For visually hidden interactive controls, such as traditional “skip” links, use the `.visually-hidden-focusable` class. This will ensure that the control becomes visible once focused (for sighted keyboard users). Watch out, compared to the equivalent `.visibility-hidden` and `.visibility-hidden-focusable` classes in past versions, Bootstrap 5’s `.visually-hidden-focusable` is a standalone class, and must not be used in combination with the `.visually-hidden` class. diff --git a/apps/playground/src/components/Comps/TTable.vue b/apps/playground/src/components/Comps/TTable.vue index a012a5030..dbc3f7281 100644 --- a/apps/playground/src/components/Comps/TTable.vue +++ b/apps/playground/src/components/Comps/TTable.vue @@ -314,7 +314,7 @@