torchbox / torchbox/django-pattern-library

Accessibility issue: Page should contain a level-one heading on /django-pattern-library/demo/render-pattern/patterns_jinja/components/test_extends/extended.html

Open Beginner friendly
#318 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

axe rule: page-has-heading-one axe-scanning-issue best-practice
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/components/test_extends/extended.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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by opening the rendered extended.html page and tracing it to the corresponding pattern template in the repository. Add or adjust the page content so it contains a level-one heading, then rerun the accessibility scan to confirm the reported violation is gone and check whether a regression test can be added.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
accessibility, frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.