Information and Relationships (Structuring Pages and Content)

(A)

1.3.1 Information and Relationships

1.3.1 Information and Relationships

Information, structure, and relationships conveyed through the representation can be determined by software or are available in text form.

Description

The layout and structure of a portal or application page are very helpful in understanding its functionality and how to use it. Using headings to structure portal and application pages helps users get a sense of how the page is organized.

It's also helpful to group content or fields.

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 include markup that makes this structure accessible to screen readers. This ensures that the page is accessible to people with visual impairments.

By adding headings and structuring the page, people with visual impairments can use the headings of the individual sections to get a good overview of the content and understand the relationships between the different parts of the content.

It is crucial that headings are actually marked up with the correct HTML tags, since screen readers analyze the 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 using the headings, listen to a list of all headings, and jump to a specific heading to begin reading from that point. Screen readers can use headings to skip repetitive blocks of content, such as headers, menus, and sidebars.

Relevance and Applicability

This guideline is relevant when implementing accessibility for your portal. It is considered one of the best practices (How to Make Your Web Pages Accessible - Best Practices).

General Implementation

  • Arrange the headings from <h1> to <h6>. Use headings hierarchically, with the <h1> representing the main idea of the page and the subsections organized using headings at the <h2> level. These subsections can, in turn, be organized using <h3>-level headings, and so on.

  • Do not choose heading levels based on their appearance. Select the appropriate heading level in the hierarchy.

  • Do not use bold type in place of a heading. One of the most common accessibility mistakes is using bold text instead of proper heading formatting. Although the text looks like a heading, the underlying HTML code is not properly marked up, so users of screen readers cannot benefit from it.

Implementation in Detail - Headings

9.1.3.1a HTML Structural Elements for Headings

Implementation in Detail - Lists

9.1.3.1b HTML Structural Elements for Lists

Lists are another element that helps with structuring pages. To ensure that screen readers can handle lists effectively, it is essential to use the correct HTML structural elements (ul, ol, and so on).

Below are some tips on the elements you can use to create lists in Intrexx.

Implementation in Detail - Tables

Another way to structure a page is to use tables. Here, too, proper markup using HTML structural elements is crucial to ensure that assistive technologies can handle tables effectively.

Implementation in Detail - Additional Information

9.1.3.1d Structured Content

To ensure that text is accessible, it must be marked up with appropriate structural elements (HTML tags). This includes, for example, marking paragraphs as <p> tags. Do not use blank paragraphs to create spacing, such as by pressing the Return key multiple times. Screen readers also read out empty paragraphs.

Intrexx automatically applies the correct formatting. This applies both in Intrexx Portal Manager—for example, when you use the "Static Text Field" element—and in the portal itself, for example, when you use the "Content Editor" or "Text Field" elements (with TinyMCE enabled).