WCAG success criterion: "There is a mechanism to bypass content blocks, that are repeated on different web pages."

On websites, there are usually different page areas with content that can be used individually. For sighted users, these areas are indicated by colors, dividing lines or positions. Blind users cannot see these
these markings. Therefore, at least one of the following requirements to navigate and skip these page areas must be met for screen reader users:.

Meaningful area headings of the levels h1 - h6 are used. These can also be visually hidden.

Jump links are provided to jump to the different page areas.

HTML5 elements for area markup (e.g. header, nav, main, aside, footer) or alternatively ARIA document landmarks (e.g. role="navigation", role="main", role="search") make the page structure more page structure in a meaningful way.

There are HTML5 elements for structuring the page areas (example marked blue). However, other area markups are missing, such as nav and header (marked red). Alternative markups with WAI-ARIA document landmarks are not available.

This makes it difficult, especially for screen reader users, to navigate to different parts of the page, e.g. the navigation.

The problem also affects the "Calendar" page from the "Groupware" section.