Accessibility issue: Page should contain a level-one heading on /django-pattern-library/demo/render-pattern/patterns/atoms/icons/icon.html
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- accessibility
Research direction
Reproduce the accessibility scan at the linked icon pattern page and trace it to the Django template or entry point that renders the page. Ensure the rendered page has a level-one heading, then rerun the relevant accessibility check and add a regression test if the repository provides an appropriate test location.
Written by the indexing model from the issue text.
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/atoms/icons/icon.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.
- Dominant language
- Python
- Stars
- 423
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
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.
More from torchbox/django-pattern-library
-
axe rule: landmark-unique axe-scanning-issue best-practice
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
axe rule: landmark-no-duplicate-main axe-scanning-issue best-practice
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
axe rule: landmark-main-is-top-level axe-scanning-issue best-practice
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
axe rule: heading-order axe-scanning-issue best-practice
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
axe rule: landmark-unique axe-scanning-issue best-practice
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
All issues in torchbox/django-pattern-library
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100