Skip to main content
WCAG 1.3.1 - LogoWCAG 1.3.1 - Logo

Success Criterion 1.3.1 - Level A

Info and Relationships

Ensure that the information and relationships on the screen are not just conveyed visually.

Information on the screen must be conveyed to assistive technologies. For example, make sure that headings are not only bold, but also marked as headings in the code.

Relationships on the screen must be indicated to assistive technologies. Elements in a list must be navigable one by one. Elements in a table must be navigable by rows and columns.


  • It is important for users of assistive technology that titles of rows and columns are conveyed in tables.

  • Make sure paragraphs can be navigated separately by screen reader users.

  • Convey visual indications, such as bullet points in a list, to assistive technologies to let users know they are in a list.


Is the structure of the screen clear when using assistive technologies?”

You can use a screen reader to check the structure of the screen.


Websites often use WAI-ARIA attributes to convey information and relationships. You cannot use these attributes in apps, because apps are not written in HTML. Alternatives are available for some of these attributes, but not for all.

Set accessibility role

Indicate accessibility modal

Group elements