torchbox / torchbox/django-pattern-library
Accessibility issue: Page should contain a level-one heading on /django-pattern-library/demo/render-pattern/patterns/molecules/button/button.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/molecules/button/button.html because page should contain a level-one heading. Learn more about why this was flagged by visiting https://dequeuniversity.com/rules/axe/4.11/page-has-heading-one?application=playwright.
The following element needs attention:
<html lang="en-GB">(selector:html)
To fix this, ensure that the page, or at least one of its frames contains a level-one heading.
Specifically:
Fix all of the following:
- Page must have a level-one heading
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 loading the reported demo URL and trace the template or entry point that renders the button pattern page. Ensure the rendered page includes a level-one heading, then rerun the accessibility scan and add a regression test if the repository has a relevant test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100