Skip to content

Fix landmark violation: Use aside elements for presentation controls#23

Draft
Copilot wants to merge 2 commits intomainfrom
copilot/fix-accessibility-landmarks
Draft

Fix landmark violation: Use aside elements for presentation controls#23
Copilot wants to merge 2 commits intomainfrom
copilot/fix-accessibility-landmarks

Conversation

Copy link

Copilot AI commented Feb 13, 2026

Axe accessibility scanner flagged <div class="clock"> and <div class="progress"> on /presentations/atag-fosdem26.html for not being contained within landmarks (WCAG 2.1 region rule).

Changes

Changed non-landmark divs to semantic aside elements with descriptive labels:

-  <div class="progress"></div>
-  <div class="clock"></div>
+  <aside class="progress" aria-label="Presentation progress"></aside>
+  <aside class="clock" aria-label="Presentation timer"></aside>

Aside elements are complementary content landmarks appropriate for presentation UI controls.

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
    • Triggering command: /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

This section details on the original issue you should resolve

<issue_title>Accessibility issue: All page content should be contained by landmarks on /presentations/atag-fosdem26.html</issue_title>
<issue_description>## What
An accessibility scan flagged the element <div class="clock" aria-label="clock"> on https://ox.ca/presentations/atag-fosdem26.html because all page content should be contained by landmarks. Learn more about why this was flagged by visiting https://dequeuniversity.com/rules/axe/4.11/region?application=playwright.

To fix this, ensure all page content is contained by landmarks.

Specifically:

Fix any of the following:

  • Some page content is not contained by landmarks

Acceptance Criteria

  • The specific axe violation reported in this issue is no longer reproducible.
  • The fix MUST meet WCAG 2.1 guidelines OR the accessibility standards specified by the repository or organization.
  • A test SHOULD be added to ensure this specific axe violation does not regress.
  • This PR MUST NOT introduce any new accessibility issues or regressions.

</issue_description>

Comments on the Issue (you are @copilot in this section)


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: mgifford <116832+mgifford@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix accessibility issue with page content landmarks Fix landmark violation: Use aside elements for presentation controls Feb 13, 2026
Copilot AI requested a review from mgifford February 13, 2026 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Accessibility issue: All page content should be contained by landmarks on /presentations/atag-fosdem26.html

2 participants