processing / processing/p5.js-website

[Page Structure] Ensure all page content is contained within landmarks

Open
#928 2 comments 0 reactions 1 assignee View on GitHub

@coseeian is already working on this.

Since Aug 4, 2025.

Accessibility: Low Severity
Dominant language
MDX
Stars
96
Forks
322
Avg merge
5d 22h
Merged PRs (30d)
8

Description

Title

[Page Structure] Ensure all page content is contained within landmarks

Description

All page content should be contained within landmark regions using appropriate HTML5 elements (such as <header>, <nav>, <main>, <footer>) and/or ARIA landmark roles (such as role="banner", role="navigation", role="main", role="contentinfo").
Landmarks enable screen reader users and other assistive technology users to quickly navigate between meaningful sections of the page.
When content is placed outside of landmarks, it becomes difficult to locate and may lack a clear purpose or context for users relying on these navigation aids.

Steps to Reproduce
  1. Go to the home page (/).
  2. Locate the "hide banner" button at the bottom of the page.
  3. Observe that this button is not contained within any landmark region (e.g., footer).
Actual Behavior

The "hide banner" button is not contained within any landmark region, making it difficult for screen reader users to locate via landmark navigation.

Expected Behavior

The "hide banner" button should be placed within an appropriate landmark region (such as <footer>).

Environments

No response

Suggested Fix

Move the "hide banner" button into a <footer> landmark region

Reference
What is your operating system?

None

Web browser and version

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.