bytereport
English
DeutschEnglish
Log inCreate account
Accessibility

Can everyone use your website?

We check a page for the technical basics of accessibility per WCAG 2.2: language and headings, text alternatives, labels, link texts and ARIA. With an account also in a real browser for contrast and focus, over several pages.

A domain checks the start page, a full URL exactly that page. Without an account we read the HTML as the server sends it.

Everything in one report, regularly if you like

In a combined report accessibility runs with the other reports, and a schedule tells you when a new barrier appears.

Create account

With an account you check in a real browser

Contrast

Every text against its actual background, also over images and gradients.

Focus and click targets

We press the tab key and look whether the focus is visible.

Several pages

The browser follows your internal links and checks several pages in one run.

Start here

The guide to accessibility

What the findings mean and how to fix them, in the same categories as the report. Or straight to a topic:

Structure and languageImages and mediaOperation and formsARIAPresentationStatement

What does accessibility check?

Without an account: semantics. Does the page have a language and a title, are headings in a sensible order, do images have text alternatives, fields labels and links understandable names, and are the ARIA attributes right? We read that from the HTML your server sends.

With an account: presentation. A real browser renders the page. In it we check contrast and click targets with axe-core, operate the page by tab and narrow it to 320 pixels. The semantic checks then also see what JavaScript adds later.

Automated tests find only part of the barriers. Whether a text alternative fits, a flow is understandable or the page works with a screen reader only a person can check. A bytereport is no proof of conformity with accessibility laws.