• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

coreui / coreui-pro / 39604700298
97%
main: 94%

Build:
Build:
LAST BUILD BRANCH: v6-dev
DEFAULT BRANCH: main
Ran 21 Oct 2026 01:05PM UTC
Jobs 1
Files 88
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

21 Oct 2026 01:03PM UTC coverage: 96.141%. Remained the same
39604700298

push

github

web-flow
docs: give accessibility a section of its own (#1734)

* docs: give accessibility a section of its own

Accessibility moves out of Getting started into its own sidebar group with
six pages: overview, compliance, keyboard, screen readers, color contrast
and reduced motion. The old URL redirects to the overview, and every link
that pointed at an anchor of the old page now points at the page that
carries the section.

The compliance page is generated from build/a11y.config.mjs, the same
configuration the WCAG suite runs on, so the published criteria cannot
drift from what CI checks. The docs build fails when an entry points at a
page that does not exist; the tabs entry still used components/navs-tabs,
which v6 split into nav and tab. The keyboard page lists every component
page with a keyboard table, read from the pages themselves.

The notes in the suite configuration now read as public text and match the
current code: modal and offcanvas are native dialogs without a focus trap,
the stepper panes are no longer live regions, only the first OTP field
carries one-time-code, and so on. Autocomplete 4.1.3 goes to partial,
because its no-results message exists only with searchNoResultsLabel, and
Tooltip 1.4.13 to built-in, because the tip stays open while hovered since
#974.

* docs: correct the accessibility pages where the code says otherwise

The build fails only on criteria axe-core or a scripted step checks, so the
pages say that instead of promising it for every claimed criterion. The
screen reader table lists the browsers the shipping live regions were
measured in, Chrome 154 and Firefox 157, and what each one covered. Menus
are no longer called a single tab stop that takes focus on open, and the
keyboard index also finds key tables kept under Accessibility.

Suite notes corrected after a second read of the code: menu items take
Enter and only button items Space, only day cells carry a date label,
modal and offcanvas return focus to a data API trigger,... (continued)

7745 of 8301 branches covered (93.3%)

Branch coverage included in aggregate %.

13355 of 13646 relevant lines covered (97.87%)

2080.04 hits per line

Jobs
ID Job ID Ran Files Coverage
1 39604700298.1 21 Oct 2026 01:05PM UTC 88
96.14
GitHub Action Run
Source Files on build 39604700298
  • Tree
  • List 88
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #39604700298
  • 830a512e on github
  • Prev Build on v6-dev (#39602442659)
  • Next Build on v6-dev (#39615224630)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc