Accessibility

Website accessibility analysis
what’s reviewed and why it matters

An accessible website is one that anyone can use: someone with low vision, someone who navigates with the keyboard or someone who uses a screen reader. Wakaris reviews the most common barriers with 17 checks and explains every finding in plain language.

  • 17 checks
  • 9 possible findings
  • 9 guides
What’s reviewed

What Wakaris checks
in your website’s accessibility

That’s 17 checks grouped into 9 blocks. Each block is a finding that can show up in your report.

Finding01/ 09

Blocks1 check

Visual contrast

Low contrast isn’t a minority problem: it affects anyone using their phone in the sun, with an old screen or simply past forty. It’s the most widespread accessibility barrier and the easiest to measure.

What it checks

  • Text contrastCalculates the contrast between text and its background. No finding at 4.5:1 or more for normal text, or 3:1 for large text (18 pt regular or 14 pt bold). Blocks below the applicable threshold.
Read the guide: Visual contrast 

Finding02/ 09

Blocks1 check

Form labels

A field without a label is a field without a name: a screen reader announces “text box” and nothing more. Whoever uses it has to guess what’s being asked from the order in which it appears.

What it checks

  • Fields with an accessible nameChecks the applicable input, select and textarea elements: they must get a name through <label>, aria-label or aria-labelledby. No finding if all comply; blocks if at least one has no accessible name; inconclusive if there are no fields.
Read the guide: Form labels 

Finding03/ 09

Blocks3 checks

Accessible names for controls

A button without a name is announced as “button” and nothing more. People navigating with a screen reader or by voice can’t know what it does or refer to it to press it.

What it checks

  • Links with an accessible nameCalculates each link’s accessible name. No finding if all have a non-empty name; blocks if at least one doesn’t; inconclusive if there are no links.
  • Buttons with an accessible nameChecks <button> elements, button-type inputs and elements with role="button". No finding if all have a name; blocks if any doesn’t.
  • Frames with an accessible nameChecks that each iframe or frame has a title or accessible name. No finding if all are named; blocks if any isn’t.
Read the guide: Accessible names for controls 

Finding04/ 09

Blocks2 checks

Text alternatives

Alt text is all that’s left of an image when it can’t be seen: because of a screen reader, a connection that cuts it off or a path that broke. Without it, there’s nothing there.

What it checks

  • Images with an alternativeChecks that each <img> has an alt attribute or is correctly declared as decorative. No finding if all comply technically; blocks if at least one has no valid alternative.
  • Image buttons with an alternativeChecks inputs of type "image". No finding if all have an accessible name or alternative; blocks if any doesn’t.
Read the guide: Text alternatives 

Finding05/ 09

Limits2 checks

Document language

It’s a tiny attribute that decides how your website sounds: a screen reader uses the declared language to choose its pronunciation. With the wrong language, Spanish text gets read with English phonetics and nothing makes sense.

What it checks

  • Declared languageChecks that <html> includes a lang attribute with a value. No finding if present and not empty; blocks if missing or empty.
  • Valid language codeSyntactically validates the lang value against accepted language codes. Blocks if the code is invalid.
Read the guide: Document language 

Finding06/ 09

Limits4 checks

Valid ARIA

Bad ARIA is worse than no ARIA. A wrong role makes a screen reader announce the element as something it isn’t, and whoever uses it acts accordingly: they try to press what can’t be pressed, or look for options that don’t exist.

What it checks

  • Valid ARIA rolesChecks that each role value matches a valid, allowed ARIA role. No finding if there are none; blocks if there’s at least one invalid role.
  • Allowed ARIA attributesChecks that each aria-* attribute can be used on the element or role where it appears. Blocks if at least one isn’t allowed.
  • Required ARIA attributesChecks that roles requiring certain attributes include them. Blocks if at least one required attribute is missing.
  • Valid ARIA valuesChecks that each aria-* attribute’s value is one of those accepted for that attribute. Blocks if at least one has a value that doesn’t exist.
Read the guide: Valid ARIA 

Finding07/ 09

Limits1 check

Zoom and scaling

Blocking zoom shuts out anyone who needs to enlarge text to read it, which is a huge number of people once they’re past forty. And it adds nothing: for years it was added so websites would “feel like an app”, copying a line from a tutorial.

What it checks

  • Zoom not blockedChecks the meta viewport settings. No finding if it doesn’t contain user-scalable=no and maximum-scale is absent or 2 or higher. Blocks if it prevents scaling or if the maximum is below 2.
Read the guide: Zoom and scaling 

Finding08/ 09

Affects2 checks

Semantic structure

The main block is what lets people skip the menu. Those navigating with a screen reader use it to jump straight to the content instead of hearing the same navigation on every page they open.

What it checks

  • Main content areaCounts the main blocks declared with <main> or role="main". No finding with exactly one visible; blocks with none or more than one.
  • List structureChecks that each <li> is correctly contained in a ul, ol or menu. No finding if there are none; blocks if there’s at least one badly structured list item.
Read the guide: Semantic structure 

Finding09/ 09

Affects1 check

Touch target size

A button that’s too small isn’t just awkward: it’s a task that fails. You tap the one next to it, close what you didn’t mean to close, and end up abandoning the form on your phone.

What it checks

  • Target size and spacingChecks each pointer target against WCAG 2.2. No finding at 24x24 CSS px or more, or if it meets exactly one of the spacing exceptions provided. Blocks if any meets neither the size nor the exception.
Read the guide: Touch target size 

The label tells you how much each finding weighs: Blocks critical,Limits important,Affects could be better.

Why it matters

Why your website’s accessibility
matters

A barrier on your website doesn’t just annoy the person who meets it: it shuts them out.

  • It’s for more people

    This isn’t only about permanent disability. An arm in a cast, sunlight on the screen or tired eyes put anyone in the same position.

  • It’s also an obligation

    European accessibility rules now reach many digital services. It’s worth knowing where your website stands before someone asks you.

  • Improves the whole website

    Good contrast, buttons with names and properly labelled forms make the website clearer for everyone, and easier for search engines to read too.

To understand it

Accessibility guides
to understand each finding

Each guide explains one finding from this area in plain language: what it is, how it’s measured, why it matters to you and how to fix it. The technical part is kept separate, for whoever looks after your website.

9guides on accessibility

See the 9 guides
Frequently asked questions

Common questions
on accessibility

Will this analysis tell me whether my website meets the standard?

Not entirely. An automated analysis detects the barriers that can be measured, such as contrast or an image with no description, but some criteria can only be assessed by a person. It’s useful for correcting the most frequent problems; it is not a conformance certificate.

What is WCAG?

The international guidelines that describe what a website should be like so that everyone can use it. Regulations usually refer to them, and the checks in this area are based on their criteria.

Is my website required to be accessible?

It depends on your activity and the size of your company, and it varies from case to case. Public bodies have been required to for years, and European rules have extended it to many private services. If you’re unsure about your own case, ask a professional.

Do I have to rebuild my website to make it accessible?

Hardly ever. Most of the barriers the analysis detects are corrected one by one: raising a contrast, giving a button a name, labelling a field. The report sorts them by importance so you can start with what affects people most.

Who has to fix whatever comes up?

Whoever handles your website’s design or development. Every finding comes explained, with the evidence that proves it and a ready-made prompt to fix it with an AI, and you can share it with a link.

How much does the accessibility analysis cost?

Nothing. Analysing a page is free, asks for no sign-up or card and gives you the result in a few seconds. Accessibility is reviewed alongside the other eight areas in the same analysis.