Accessibility issue: Main landmark should not be contained in another landmark on /django-pattern-library/demo/render-pattern/patterns_jinja/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_jinja/pages/search/search.html because main landmark should not be contained in another landmark. Learn more about why this was flagged by visiting https://dequeuniversity.com/rules/axe/4.11/landmark-main-is-top-level?application=playwright.

The following element needs attention:

• <main> (selector: main > main)

To fix this, ensure the main landmark is at top level.

Specifically:

Fix any of the following:

• The main landmark is contained in another landmark.

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 page at the linked URL and trace the template that produces the main > main selector. Re-run the accessibility scan using the referenced axe rule, then confirm the nested main landmark is gone and add a regression test if the repository’s existing test structure supports it.