← Back to all categories
Error heading-1 · WCAG 1.3.1

Skipped heading level

The page goes from h1 directly to h3, skipping h2. Screen reader users navigating by heading level will find the hierarchy confusing and may think content is missing.

Company News

Latest Announcements

We are excited to share our latest product updates...

Upcoming Events

Join us at the annual developer conference...

Error heading-2 · WCAG 1.3.1

No h1 on page

This page section starts with h2 and never provides an h1. The page lacks a top-level heading, making it harder for screen reader users to identify the page topic.

About Our Services

We provide a wide range of professional services.

Consulting

Expert guidance for your business needs.

Development

Custom software solutions built to scale.

Error heading-3 · WCAG 1.3.1

Multiple h1 elements

This section contains two h1 elements. While technically allowed in HTML5, multiple h1s can confuse screen reader users about the primary topic of the page.

Welcome to TechCorp

Your trusted technology partner.

Our Mission

Building the future of accessible technology.

Error heading-4 · WCAG 1.3.1

Styled text used instead of heading element

A div is styled to look like a heading (large, bold text) but uses no heading element. Sighted users see a heading, but screen reader users have no way to identify it as one.

Product Features

Our product includes the following features:

  • Real-time collaboration
  • Cloud storage
  • API integrations