[BITV] 9.1.3.1a/3.1 - Although the page has some headings, these only partially help to structure the page content as the main content of the page, the tables/list view, is not structured by the headings.

[AndyScherzinger]

It is recommended to remove the current "h1" heading "Nextcloud's homepage" and replace it e.g. with a visually hidden heading "All files" at the beginning of the main landmark. (1)

Fix:

• Move heading to the main content #37583
• Move heading to the main content photos#1727
• Add placeholder for heading inside of app content nextcloud-libraries/nextcloud-vue#3957

Details

https://report.bitvtest.de/default-en/d63601ac-cb34-4645-8256-66bec78964a0.html#checkpoint-be75bbae42-v3-n1

[JuliaKirschenheuter]

Related (same) issue is here: #35626

[JuliaKirschenheuter]

• Fix: Set <h1> headings for navigation through files app #37174
• Backport NC26: [stable26] Set <h1> headings for navigation through files app #37273
• Fix NC25: Set <h1> headings for navigation through files app #37232

[JuliaKirschenheuter]

https://www.w3.org/TR/WCAG21/#adaptable
https://ergebnis.bitvtest.de/pruefschritt/bitv-20-web/9-1-3-1a-html-strukturelemente-fuer-ueberschriften

[JuliaKirschenheuter]

HI @michaelnissenbaum,

could i ask you about this ticket?
This part:

It is recommended to remove the current "h1" heading "Nextcloud's homepage" and replace it e.g. with a visually hidden heading "All files" at the beginning of the main landmark. (1)

is already solved. I would like to ask you about main content of the page. In this ticket is mentioned "the tables/list view, is not structured by the headings" what should we do in that case?

? Should we place something like "Main content" as <h2> for pages with tables/lists view?

On pages without table/lists view there are already <h2> headings taking place:

"Appearance and accessibility", "Keyboard shortcuts", "Background" ..and so on are already <h2>.

[michaelnissenbaum]

Hi @JuliaKirschenheuter,

as I see it, the current implementation at https://try.nextcloud.com/ltd/a11y/ is not entirely correct or at least not what I proposed. For example, my suggestion was to place the h1 heading for "All Files" not in the header element, but in the main landmark, preferably in the DOM right after the navigation. If implemented this way, a screen reader user would have multiple options - to jump directly to a specific landmark/section or to the h1 heading. By jumping directly to the h1 heading, the user would be able to navigate through the main content of the page immediately.

[JuliaKirschenheuter]

Thank you @michaelnissenbaum!

[JuliaKirschenheuter]

@michaelnissenbaum in current implementation it is really hard to move <h1> heading directly under the navigation. It is possible to do it only in apps which are already using Vue. But in older ones it is really hard. I've put <h1> right after the navigation in Photos App. In all other places I've put it as a first node of the <main>.

Hope it is ok 🙏

[michaelnissenbaum]

Hi @JuliaKirschenheuter screenshots you attached to this tickets are looking good to me.