benivo-ui-library 1.10.13 → 1.10.15

package/benivo-ui-lib.less

@@ -24,6 +24,7 @@
 @import '../components/activityFeed/activityFeed.less';
 @import '../components/notificationCard/notificationCard.less';
 @import '../components/serviceSelectionCard/serviceSelectionCard.less';
+@import '../components/serviceProgressCard/serviceProgressCard.less';
 @import '../components/cardHeader/cardHeader.less';
 @import '../components/alertBanner/alertBanner.less';
 @import '../components/alert/alert.less';
@@ -58,6 +59,7 @@
 @import '../components/asideSummaryCardSection/asideSummaryCardSection.less';
 @import '../components/tab/tabs/tabs.less';
 @import '../components/tab/tabGroup/tabGroup.less';
+@import '../components/tab/verticalTabs/verticalTabs.less';
 @import '../components/accordion/accordion.less';
 @import '../components/countryFlag/countryFlag.less';
 @import '../components/flag/flag.less';

package/datePicker.less

@@ -119,6 +119,28 @@
     }
 }
 
+// react-datepicker renders a `role=alert` live region carrying the month/year announcement, and
+// hides it visually in its OWN stylesheet — which the library cannot assume a consuming app has
+// imported (EPApp does not). Unstyled, the announcement paints as stray text inside the calendar
+// once the month is changed. Hide it here so this stylesheet stands on its own, using the
+// visually-hidden pattern rather than `display: none` so the month change is still announced
+// (WCAG 4.1.3). Deliberately NOT chained to `.react-datepicker` like the rules below:
+// react-datepicker renders TWO spans with this class, and the "Selected date: ..." one sits
+// beside the input, outside the calendar root. Scoping this would leave that one painting.
+// [BPO-15797]
+.react-datepicker__aria-live {
+    position: absolute;
+    width: 1px;
+    height: 1px;
+    margin: -1px;
+    padding: 0;
+    border: 0;
+    overflow: hidden;
+    white-space: nowrap;
+    clip: rect(0 0 0 0);
+    clip-path: inset(50%);
+}
+
 // Chained with `.react-datepicker` (both classes sit on the same element) so every rule here
 // outranks react-datepicker's own stylesheet, which loads after this file at equal specificity.
 // Without this its defaults win — the mid-grey border (read as a dark stroke), the 0.3rem corner