Info and Relationships (structure pages and content)

(A)

1.3.1 Info and Relationships

1.3.1 Info and Relationships

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Description

The design and structure of a portal or application page helps people to understand its functionality and operation. Organizing portal and application pages by headings helps users get a feel for how the page is organized.

Grouping content or fields is also helpful.

Just as with images and other non-textual elements, the page structure is not visually perceptible to blind people. Therefore, it is necessary for a page to have markers that make this structure accessible to screen readers. This ensures that the site is accessible to people with visual impairments.

By adding headings and structuring the page, people with visual impairments can get a good overview of the content and understand the relationships between the content based on the section headings.

It is crucial that headings are actually tagged with the correct HTML tags, as screen readers analyze source code to determine the structure of a page and then make it accessible.

If the underlying code for a page's headings is correct, screen reader users can also benefit from the headings. Screen reader users can navigate a page based on headings, listen to a list of all headings, and jump to any heading they want, to begin reading at that point. Screen readers can use headers to skip repetitive blocks of content such as headers, menus, and sidebars.

Relevance and applicability

This guideline is relevant when making your portal accessible. It is one of the best practices How to make your pages accessible - Best practices).

General implementation

  • Order the headings from <h1> to <h6. Use headings hierarchically, with <h1> representing the main idea on the page and subsections organized with <h2> level headings. These subsections can in turn be structured with <h3> level headings etc.

  • Do not select heading layers according to their appearance. Select the appropriate heading rank in the hierarchy.

  • Do not use a bold font instead of a heading. One of the most common accessibility mistakes is using bold text instead of proper heading formatting. Although, visually the text looks like a heading, the underlying HTML code is not properly tagged, so screen reader users cannot benefit from it.

Detailed implementation - Headings

9.1.3.1a HTML structural elements for headings

Detailed implementation - Lists

9.1.3.1b HTML structural elements for lists

Lists are another element that helps to structure pages. For screen readers to handle lists properly, proper markup with HTML structural elements (ul, ol, and so on) is crucial.

Below, you will find some notes on elements used to create lists in Intrexx.

Detailed implementation - Tables

Tables are another way to structure a page. Again, proper markup with HTML structural elements is critical for assistive technologies to handle tables properly.

Detailed implementation - Other

9.1.3.1d Structured content

To ensure the accessibility of texts, they must be marked with suitable structural elements (HTML tags). This includes, for example, labeling paragraphs as paragraph <p>. Do not use empty paragraphs to create spacing, such as by using the Return key several times. Blank paragraphs are also output by screen readers.

In Intrexx, the correct formatting is automatically applied. This applies both in the Intrexx Portal Manager, if you use the " static text field" element, for example, but also in the actual portal, if you use the "Content Editor" or "text field" elements (with TinyMCE activated), for example.