Skip to main content

Since it’s Friday, the WCAG Academy is sending another dose of knowledge

Firstly, it’s important to note that WCAG Criterion 1.3.2 is significant for people using assistive technologies, such as screen readers, to access website content.

Users who can see the website perceive all its elements arranged by CSS styles. The sequence makes sense to them. The criterion is considered fulfilled if, even with styles disabled, the sequence of elements remains logically meaningful. The sequence of elements on the page should be logical and intuitive. Organizing content in a specific sequence is crucial. Any deviation in sequence might alter the entire meaning of the website.

Apart from the typical error of incorrect reading order, we should also avoid other situations that might hinder comprehension for screen reader users:

  • If a tooltip or modal appears visually while navigating the page, it must be read immediately, not at the end of the page.
  • Avoid using white spaces to “space out” text → W I T A J C I E. It might be read as separate letters, not as a whole word.
  • If there are two language versions of the website differing in text reading direction (Arabic, Japanese), ensure appropriate CSS.

A highly comprehensive tool for checking correct sequence is the Web Developer plugin. It has the capability to disable all styles.


Radosław Stachurski

Radosław Stachurski

Accessibility Specialist & WCAG 2.1 Auditor & Quality Assurance