torchbox / torchbox/django-pattern-library
Accessibility issue: Landmarks should have a unique role or role/label/title (i.e. accessible name) combination on /django-pattern-library/demo/render-pattern/patterns_jinja/pages/search/search.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_jinja/pages/search/search.html because landmarks should have a unique role or role/label/title (i.e. accessible name) combination. Learn more about why this was flagged by visiting https://dequeuniversity.com/rules/axe/4.11/landmark-unique?application=playwright.
The following element needs attention:
<main>(selector:body > main)
To fix this, ensure landmarks are unique.
Specifically:
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
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
Open patterns_jinja/pages/search/search.html and inspect the element matched by body > main. Rerun the Playwright accessibility scan for the linked search page, then verify that the reported landmark violation is no longer reproducible and that the fix meets the stated accessibility criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, playwright
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 84/100