Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
axe-core (WCAG 2.2 A/AA plus best-practice, light and dark) found 30 violations across the website and web UI. Fixed:
--accent-solidtoken for fills behind white text, lighter dark-theme--accentfor text; the hard-codedtext-accentcolour now uses the token. Broker filter selects got aria-labels; History and Action Needed headings no longer skip levels.AccessibilityCI job (part of Required checks passed) runsscripts/a11y/run.sh: builds the site and the web UI, seeds fictional data (scripts/a11y/seed), scans 15 pages in both themes. Entrance animations are disabled during the scan since axe reads mid-fade colours. Dependabot covers the npm deps.Local result: no violations. This only covers what axe can detect automatically; keyboard and screen-reader behaviour still need a manual pass.