Accessibility issue: Heading levels should only increase by one on /django-pattern-library/demo/render-pattern/patterns/pages/search/search.html

[!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/search/search.html because heading levels should only increase by one. Learn more about why this was flagged by visiting https://dequeuniversity.com/rules/axe/4.11/heading-order?application=playwright.

The following element needs attention:

• <h4>16</h4> (selector: h4:nth-child(2))

To fix this, ensure the order of headings is semantically correct.

Specifically:

Fix any of the following:

• Heading order invalid

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.

Start with the rendered search.html page at the URL in the issue and trace it to the Django template that produces the h4:nth-child(2) heading. Run the referenced Playwright axe heading-order check after correcting the heading hierarchy; done means the reported violation is gone without introducing new accessibility issues.