Fix landmark accessibility violation for progress and clock elements#7
Merged
Fix landmark accessibility violation for progress and clock elements#7
Conversation
…bility - Changed div elements to aside elements with semantic meaning - Added aria-label attributes for unique accessible names - Created test-landmarks.sh to prevent regression - Added test:landmarks to npm test suite - Updated AGENTS.md documentation Fixes the axe/region accessibility violation where page content was not contained by landmarks. Co-authored-by: mgifford <116832+mgifford@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix accessibility issue for page content landmarks
Fix landmark accessibility violation for progress and clock elements
Feb 13, 2026
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.
The
.progressand.clockelements were not contained by landmark regions, violating WCAG 2.1 and triggering axe/region failures.Changes
<div class="progress">and<div class="clock">to<aside>elements with uniquearia-labelattributesImplementation
The
<aside>element provides the implicitcomplementarylandmark role required by WCAG. Existing CSS and JavaScript continue to work unchanged as they reference class selectors, not element types.Screenshot
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
https://storage.googleapis.com/chromium-browser-snapshots/Linux_x64/869685/chrome-linux.zip/home/REDACTED/work/_temp/ghcca-node/node/bin/node node install.js(http block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.