Add main landmark to fix WCAG 2.1 landmark-one-main violation#19
Draft
Add main landmark to fix WCAG 2.1 landmark-one-main violation#19
Conversation
Co-authored-by: mgifford <116832+mgifford@users.noreply.github.com>
Co-authored-by: mgifford <116832+mgifford@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix accessibility issue: Document should have one main landmark
Add main landmark to fix WCAG 2.1 landmark-one-main violation
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 root page was missing a main landmark, failing axe rule
landmark-one-main(WCAG 2.1 Level A).Changes
_layouts/default.html: Replace<section>with<main>for primary content wrapper_layouts/home.html: Change<section class="home">to<div class="home">to avoid nested sectioning elementsassets/css/style.scss: Applymargin-bottom: 2remto bothsectionandmainto preserve stylingBefore/After
Page structure is now:
<header>→<main>→<footer>with proper ARIA landmarks for assistive technology navigation.Screenshot
No visual changes:
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 -I y-3.2.0 -I _64-linux-gnu/ru-I -I ndor/bin/as -I kward -I as -I /x86_64-linux-gn-I /libexec/gcc/x86/usr/include/ruby-3.2.0/ruby/backward by-3.2.0 s-through=-lgcc kward s-through=-lc s-through=-lgcc(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.