torchbox / torchbox/django-pattern-library
Accessibility issue: Main landmark should not be contained in another landmark on /django-pattern-library/demo/render-pattern/patterns/pages/forms/example_form.html
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 423
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
[!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/pages/forms/example_form.html because main landmark should not be contained in another landmark. Learn more about why this was flagged by visiting https://dequeuniversity.com/rules/axe/4.11/landmark-main-is-top-level?application=playwright.
The following element needs attention:
<main>(selector:main > main)
To fix this, ensure the main landmark is at top level.
Specifically:
Fix any of the following:
- The main landmark is contained in another 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.
Contributor 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.
Research direction
Start with the rendered example_form.html page at the URL in the issue and trace the source responsible for the main > main selector. Run the referenced accessibility scan against the page, then verify that the main landmark is top-level and that the reported violation no longer reproduces; add a regression test if the repository's test setup supports it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, html, python
- Domain
- accessibility, web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100