Accessibility checks (axe) in the browser tests, from the 0.7 views on #291
Labels
No labels
area/ci
area/desktop
area/packaging
area/protocol
area/reading
area/ui
area/web
area/writing
kind/bug
kind/feature
kind/infra
kind/request
needs/user
parked
perf
security
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
littlefox/neokom#291
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Approved for 0.7 (D-063). It's a first step toward the 1.0 "Accessible" item.
Run the axe accessibility checker (
@axe-core/playwright) in the browser tests, starting with the views 0.7 builds or changes: the channel thread list, the thread chat, the inbox and the composer. It's cheaper to build them accessible than to fix them later.aria-live), and the list is navigable with the keyboard.Tests: an axe step in the specs for those views.
Verified, merged in #310; main green (run #550).
@axe-core/playwright4.13.0 (pinned) throughe2e/tests/axe.ts: serious and critical findings fail the test, the rest show as annotations.a11y.spec.tsagainstaxe-known.json, which is empty: nothing is known to fail.langon the page from the chosen language, the chat as alogregion read out politely, grouped messages reachable by keyboard, and a profile list that showed texts with no recipients.