torchbox / torchbox/django-pattern-library
Accessibility issue: All page content should be contained by landmarks on /django-pattern-library/demo/render-pattern/patterns/pages/people/person_page.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/people/person_page.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.
The following element needs attention:
<ul>(selector:ul)
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 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 by inspecting the rendered demo URL and tracing the reported ul selector to the template that produces it. The work is done when all page content is contained by landmarks, the accessibility scan no longer reports this violation, and a regression test covers it if the repository's test setup supports one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100