Repository navigation
v0.10.0
Kinora 0.10.0
This release brings accessibility checks to Playwright tests: kinora now records the axe scans of your end-to-end tests, like it does for Storybook stories.
Accessibility
-
@kinora/reporter0.8.0 reads the axe scans attached to a test and uploads their violations: the rules broken, their impact (critical, serious, moderate, minor), the elements they hit and a link to each rule's documentation. Only the violations are sent, not axe's full result. -
New
scanA11yhelper in@kinora/reporter/a11y: it runs the scan with@axe-core/playwrightand attaches the result to the test, so kinora can read it.import { scanA11y } from '@kinora/reporter/a11y' const { violations } = await scanA11y(page) expect(violations).toEqual([])
-
If you already build your scans with
AxeBuilder, attach the result as JSON withtestInfo.attachand kinora picks it up, whatever the attachment name. Without an attachment, kinora only sees the test fail. -
Assert on the violations and the test fails on them. Scan without asserting and kinora records them as warnings, to track a backlog without blocking CI.
-
The Tests page shows how many rules each test breaks, filters on tests with accessibility issues, and ranks your test files by their violations under Accessibility hotspots.
-
@kinora/cli0.8.0 reads the same scans from the JSON report, when they are attached with abody. -
See the Playwright reporter guide.