Accessibility issue: Landmarks should have a unique role or role/label/title (i.e. accessible name) combination on /django-pattern-library/demo/render-pattern/patterns/pages/forms/example_form.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/forms/example_form.html because landmarks should have a unique role or role/label/title (i.e. accessible name) combination. Learn more about why this was flagged by visiting https://dequeuniversity.com/rules/axe/4.11/landmark-unique?application=playwright.

The following element needs attention:

• <main> (selector: body > main)

To fix this, ensure landmarks are unique.

Specifically:

Fix any of the following:

• The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable

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 by inspecting the rendered example form page at /django-pattern-library/demo/render-pattern/patterns/pages/forms/example_form.html and tracing the body > main element to its Django template source. Verify the landmark has a unique accessible name, then rerun the reported Playwright accessibility scan and add a regression test if the repository’s existing test structure supports it.