torchbox / torchbox/django-pattern-library

Accessibility issue: Headings should not be empty on /django-pattern-library/demo/render-pattern/patterns/pages/test_page/test_page.html

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

Nobody has claimed this yet.

axe rule: empty-heading 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/pages/test_page/test_page.html because headings should not be empty. Learn more about why this was flagged by visiting https://dequeuniversity.com/rules/axe/4.11/empty-heading?application=playwright.

The following element needs attention:

  • <h1></h1> (selector: h1)

To fix this, ensure headings have discernible text.

Specifically:

Fix any of the following:

  • Element does not have text that is visible to screen readers
  • aria-label attribute does not exist or is empty
  • aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  • Element has no title attribute

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 inspecting the rendered demo page at the reported URL and tracing the empty h1 selector back to the template that produces it. Confirm the heading has discernible text, then rerun the accessibility scan and add a regression test if the repository's test setup supports it.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.