I agree with adding the landmark. Not sure about the arialabel. Will check in more detail later but I don't think it's needed or particularly helpful

I would like to have a landmark here and get rid of this ugly "missing landmark" error.
But am not sure if <aside is correct.
Semantic meaning is "content which is relaed to the main content and supports it".
We can define modules - there we know when the module is related to the main content.
But sidebar could be everything.
Would be interesting to know if the <aside helps blind users and has a meaning

Aside means it is complimentary to the main region but I wonder if it can be considered as complimentary as it has the page h1 in it.

The <aside> HTML element represents a portion of a document whose content is only indirectly related to the document's main content. https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/aside

This suggests it's not the correct landmark region to use here

A <div role="complementary" could match.

A <div role="complementary" could match.

that is the exact same thing as aside https://www.w3.org/WAI/ARIA/apg/patterns/landmarks/examples/complementary.html

Not sure about the arialabel. Will check in more detail later but I don't think it's needed or particularly helpful

I was surprised that the label would identify the text as the referred id is to the div and not the individual text. So that arial label is both the h1 and the h2

In general a region only needs a label if there are more than one on the page but i dont suppose it harms having one anyway.

I wonder if this is the real main region on the page and its the login that is either complimentary or region https://www.w3.org/WAI/ARIA/apg/patterns/landmarks/examples/region.html

My 2 cents here.
As the h1and h2 are in the sidebar-wrapper thingy, I think the aside should be for the <div id="sidebar"> .

But, besides getting rid of the error in automatic detection tools. Does this help to anyone? Everytime I investigate about landmarks I end giving up because of the scarce support hey have in browsers and screen readers.

I have tested this item ✅ successfully on a692226

I have tested this item ✅ successfully on a692226

I also looked up https://www.w3schools.com/accessibility/accessibility_landmarks.php
It tells that the

element "aside" is missing in above comment

I just dont see how a region with the h1 inside it can ever be considered to be complimentary

I just dont see how a region with the h1 inside it can ever be considered to be complimentary

fair point.
Any suggestions how to get rid of this ugly "missing landmark" error?

Thank you for the work on this, pushed to 6.1 as not fixing a bug.

The following text was forwarded to me

This PR #45988 does not solve the problem.
Here is a detailed report (English, Markdown format) of my site for the backend:

Accessibility and Usability Analysis

Joomla Administrator Login Page

1. Scope of the analysis

This analysis concerns the accessibility and usability of the Joomla Administrator login page, with particular focus on:

• heading structure,
• landmark usage,
• semantic relationship between headings and main content,
• user orientation, especially for screen reader users.

2. Key accessibility and usability issues

2.1. Heading structure and content identification

Primary issue:

The only heading that correctly describes the purpose of the page (“Joomla Administrator Login”) is marked as an H2 and is located:

• outside the <main> element,
• outside any landmark region,
• within a sidebar-like container that does not represent the main task of the page.

The H1 heading (“Polskie Centrum Joomla”):

• does not describe the main content or task of the page,
• serves as organisational or branding information,
• is also placed outside the main content area.

Impact:

Screen reader users do not receive a clear and immediate answer to the question:
“What is this page for?”

Navigating by headings does not lead users to the login task, and the semantic hierarchy of the page does not reflect its functional purpose.

This affects compliance with:

• WCAG 2.4.6 – Headings and Labels
• WCAG 1.3.1 – Info and Relationships
• indirectly WCAG 2.4.1 – Bypass Blocks

2.2. Landmark structure and user orientation

Current state:

• A <header> landmark is present and contains branding and global links.
• A <main> element exists but does not include a heading that describes the main content.
• The area containing the H1, H2, and several key links:
  • is not marked as <aside>, <nav>, or <main>,
  • is not exposed as a meaningful region in the accessibility tree.

Impact:

Landmark navigation is ineffective.
Headings are not logically associated with page regions, and the accessibility tree does not reflect the functional structure of the page.

2.3. Task-oriented usability

The page serves one primary task: logging in.

Although the form controls are correctly labelled and required attributes are present, the page lacks:

• a clear task-oriented title within the main content,
• a semantic connection between the login form and the purpose of the page.

Impact:

This increases cognitive load and reduces clarity, particularly for:

• screen reader users,
• users with cognitive disabilities,
• less experienced users.

3. Core structural principle

The H1 heading must describe the main purpose of the page and be located within the <main> landmark.

Branding or organisational identification must not replace or override the functional heading of a task-oriented page such as a login screen.

4. Recommended page structure

4.1. Semantic role allocation

4.2. Example of a corrected semantic structure

<body>

  <header role="banner">
    <!-- Branding and global links -->
  </header>

  <main id="main-content">

    <header class="page-header">
      <h1>Joomla Administrator Login</h1>
    </header>

    <section aria-labelledby="login-form-heading">
      <h2 id="login-form-heading" class="visually-hidden">
        Login form
      </h2>

      <!-- Login form -->
    </section>

  </main>

  <aside aria-labelledby="support-heading">
    <h2 id="support-heading">Help and support</h2>

    <nav aria-label="Support links">
      <ul>
        <li><a href="…">Joomla Support Forum</a></li>
        <li><a href="…">Joomla Documentation</a></li>
        <li><a href="…">Joomla News</a></li>
      </ul>
    </nav>
  </aside>

</body>

After that I received a draft of the login page standard that was developed.

Standard: Backend Login Page

Accessibility and Usability Requirements

Version

1.0

Scope

This standard defines the minimum accessibility and usability requirements for login pages to the administrative or backend area of a website, including CMS platforms (e.g. Joomla, WordPress, Drupal).

The login page is treated as a task-oriented page with a single primary purpose: user authentication.

1. Core principle

The structure of the login page must clearly communicate its purpose and allow users to immediately identify:

• where they are,
• what task they can perform,
• how to complete that task.

This must be achieved through correct use of headings, landmarks, and semantic relationships, independent of visual layout.

2. Page purpose and heading structure

2.1. Main heading (H1)

• The page must contain exactly one H1 heading.
• The H1 must describe the primary task of the page, e.g.:
  • “Administrator Login”
  • “Log in to the Management Panel”
• The H1 must be located inside the <main> landmark.
• Branding or organisation names must not be used as the H1 unless they explicitly include the login purpose.

2.2. Secondary headings

• Additional headings (H2+) may be used to:
  • introduce the login form,
  • label complementary content (e.g. help, support).
• Headings must not appear outside any landmark region.

3. Landmark structure

The page must use landmarks to expose its functional structure to assistive technologies.

Required landmarks:

• <header role="banner">
  Contains branding and global links (optional).
• <main>
  Contains the login page’s primary content:
  • page heading (H1),
  • login form.

Optional landmarks:

• <aside>
  Contains complementary content such as:
  • help links,
  • documentation,
  • support resources.
• <nav>
  Used within <header> or <aside> for grouped links.

Content must not be placed outside landmarks unless it is purely decorative.

4. Login form requirements

4.1. Semantic association

• The login form must be programmatically associated with the page purpose.
• The form must be located within <main>.
• If a visible heading is not appropriate, an accessible name must be provided using:
  • a visible heading, or
  • a visually hidden heading referenced via aria-labelledby.

4.2. Form controls

• All form fields must have associated <label> elements.
• Input purposes must be declared using appropriate autocomplete values.
• Required fields must be indicated programmatically.

5. Branding and organisational information

• Organisation or product names:
  • may appear in the banner or footer,
  • may be visually prominent,
  • must not replace the functional page heading.
• Branding elements must not interfere with the logical reading order or heading hierarchy.

6. Support and help content

• Help, documentation, and support links:
  • must not be mixed with the main login task,
  • should be placed in an <aside> landmark,
  • must have a heading describing their purpose (e.g. “Help and support”).

7. Accessibility rationale

This standard ensures:

• clear task identification for screen reader users,
• effective navigation by headings and landmarks,
• reduced cognitive load for all users,
• compliance with:
  • WCAG 2.1 / 2.2 (1.3.1, 2.4.1, 2.4.6),
  • EN 301 549 requirements related to structure and orientation.

8. Non-conformance examples

The following patterns are non-conformant:

• The main login heading placed outside <main>.
• An H1 that contains only the organisation name.
• Headings located outside any landmark.
• Login forms without a clear, programmatic association to the page purpose.

9. Implementation note

This standard can be implemented without visual redesign.
All requirements concern semantic structure and accessibility metadata only.

My question is... do you all agree with the provided information? And if so... I will adjust this PR to meet the requirements setup in the provided draft.

My question is... do you all agree with the provided information? And if so... I will adjust this PR to meet the requirements setup in the provided draft.

Absolutely - I've said the same myself in the past as have others

The PR has been adjusted, based on J6.1-dev
contains a change in language string

With the suggestions as described in #45988 (comment)

I have tested this item ✅ successfully on 52bf793

I have tested this item ✅ successfully on 52bf793

Tested light and dark mode
Tested LTR and RTL

RTC

thanks