Accessibility issue: Document should not have more than one main landmark on /django-pattern-library/demo/render-pattern/patterns_jinja/pages/test_page/test_page.html

Open Beginner friendly

#328 opened on Aug 26, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 74/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Active
Tech stack: django, html
Domain: accessibility

Research direction

Start with patterns_jinja/pages/test_page/test_page.html, or the source that generates the reported demo page, and inspect the body > main element alongside the accessibility guidance in the issue. Run the repository's accessibility scan or Playwright check against the page; done means the duplicate-main violation is gone and no new accessibility issues are reported.

Written by the indexing model from the issue text.

Description

axe rule: landmark-no-duplicate-main axe-scanning-issue best-practice

[!NOTE]
This is a best-practice recommendation, not a definite WCAG failure.

What

An accessibility scan flagged an element on https://torchbox.github.io/django-pattern-library/demo/render-pattern/patterns_jinja/pages/test_page/test_page.html because document should not have more than one main landmark. Learn more about why this was flagged by visiting https://dequeuniversity.com/rules/axe/4.11/landmark-no-duplicate-main?application=playwright.

The following element needs attention:

<main> (selector: body > main)

To fix this, ensure the document has at most one main landmark.

Specifically:

Fix any of the following:

Document has more than one main landmark

Acceptance Criteria

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

Dominant language: Python
Stars: 423
Forks: 53
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

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