coreui / coreui-pro / 37295514915

96%

main: 94%

push

github

feat(Calendar): announce a page turn through announce() instead of a live region (#1566)

* feat(Calendar): announce a page turn through announce() instead of a live region

The month and year between the navigation arrows were a polite, atomic live
region, so a key that moved from August 31 to September 1 was read twice in
VoiceOver, as the date that took focus and then as "September 2026". The
navigation is now plain markup, and every update compares the label and the
description of each grid before and after it.

While focus is in the calendar but not on a date, on a navigation button or on
the grid when it holds the tab stop, the pages that changed are announced
through announce() as one message, followed by ariaNothingToPickLabel on a
page where nothing can be picked. From a date only ariaNothingToPickLabel is
announced, since the date already names its month and year, and a pick that
leaves another panel with nothing to pick names that panel's page. A newer
page replaces a message that was not read yet, dispose() cancels it, and
nothing is announced while focus is outside the calendar. The visually hidden
note in the navigation is gone; the grid keeps its aria-describedby.

* chore: raise bundlewatch ceilings for the calendar page announcement

Announcing a page turn through announce() adds, measured with gzip -9 against
v6-dev: coreui.js +95 B (165.25 kB ceiling reached), coreui.esm.js +140 B (60 B
left) and coreui.esm.min.js +93 B (40 B left). Each ceiling goes up by 0.25 kB.

* test(Calendar): cover a page that a key turns to from the grid when a date takes focus

* fix(Calendar): announce every turn the page can see, inside a picker panel too

A date picker panel is a div with role="dialog" and aria-modal="true", and
VoiceOver in Safari and Chrome read nothing from the live region at the start
of the page while it was open, where the old region inside the panel was read.
announce() now treats a shown element with aria-modal="true" like a nat... (continued)

6990 of 7547 branches covered (92.62%)

Branch coverage included in aggregate %.

34 of 34 new or added lines in 2 files covered. (100.0%)

12168 of 12463 relevant lines covered (97.63%)

1503.18 hits per line