What level is WCAG 1.3.1?

Level A. It sits under guideline 1.3 Adaptable of the Perceivable principle.

What are common ways pages fail WCAG 1.3.1?

Visual headings styled with ` ` and CSS instead of ` `–` `. Tabular data laid out in nested divs without ` ` semantics. Form inputs with no associated ` ` or `aria-labelledby`. Lists rendered with ` ` instead of ` `/` `.

How do I fix WCAG 1.3.1 issues?

Use the right HTML element for the job (heading, list, table, fieldset). Wire form controls to labels via `for`/`id` or programmatic association. Use ` ` / `scope="row"` for data-table headers. When semantics aren't available, fall back to ARIA roles like `role="list"`.

1.3 Adaptable · Perceivable

WCAG 1.3.1 Info and Relationships

Level A

Information and structural relationships conveyed visually (headings, lists, tables, form labels) must also be exposed in the markup so assistive tech can announce them.

Common failures

Visual headings styled with `<div>` and CSS instead of `<h1>`–`<h6>`.
Tabular data laid out in nested divs without `<table>` semantics.
Form inputs with no associated `<label>` or `aria-labelledby`.
Lists rendered with `<br>` instead of `<ul>`/`<ol>`.

How to fix

Use the right HTML element for the job (heading, list, table, fieldset).
Wire form controls to labels via `for`/`id` or programmatic association.
Use `<th scope="col">` / `scope="row"` for data-table headers.
When semantics aren't available, fall back to ARIA roles like `role="list"`.

Related criteria

WCAG 1.1.1 Non-text Content Level A
WCAG 1.3.2 Meaningful Sequence Level A
WCAG 2.4.6 Headings and Labels Level AA
WCAG 4.1.2 Name, Role, Value Level A