Skip to content
Check

Sample report

musterladen.example

This website is invented

Musterladen does not exist. The report was made the same way as a real single audit, with the same rules, explanations and code fixes, so you can see what you get. The owner’s answers in the guided check and the statement are examples too.

Check your own homepage for free

1 · Summary

48 / 100

Significant barriers

Coverage of WCAG 2.2 AA

  • Tested automatically: 26 of 55 criteria
  • Not testable automatically: 29, needs a person
Critical
58 places · 2 issues
Serious
161 places · 3 issues
Moderate
6 places · 1 issue
Minor
0 places · 0 issues

225 places with errors in total

Plus 3 places to check by hand, in 1 finding the automatic check could not decide. Go to the list

The five most important actions

  1. Images without a text alternativeAdd an alt attribute that says what the image shows, or alt="" if it is purely decorative.
  2. Form fields without a labelConnect a visible <label> to each field with for and id.
  3. Text with too little contrastDarken the text or lighten the background until normal text reaches 4.5:1 and large text 3:1.
  4. Links without a nameGive the link visible text, or an aria-label that says where it goes.
  5. Keyboard focus is not visibleGive links, buttons and fields a clear focus style, for example an outline in :focus-visible. Do not remove the outline without a replacement.
Website
https://musterladen.example/
Pages checked
12
Date
November 2, 2026
Keyboard and layout checks
7 pages
Standard
WCAG 2.2 level AA, EN 301 549

2 · Issues (6)

6 issues shown

  • CriticalImages without a text alternativeScreen reader users hear only “image” or a file name, so they miss what the picture shows..product-tile > a > img46 places9 pages

    How to fix it: Add an alt attribute that says what the image shows, or alt="" if it is purely decorative.

    WCAG 1.1.1 Non-text Content · EN 301 549 9.1.1.1

    Suggested code

    A suggestion built from the element's HTML. Check it before you use it.

    Before

    <img src="/media/sofa-oslo-grau.jpg" class="product-tile__image" width="480" height="360">

    After

    <img src="/media/sofa-oslo-grau.jpg" class="product-tile__image" width="480" height="360" alt="Describe what the image shows">

    Examples

    • https://musterladen.example/ · desktop.product-tile > a > img
      <img src="/media/sofa-oslo-grau.jpg" class="product-tile__image" width="480" height="360">
    • https://musterladen.example/sofas · desktop.product-tile > a > img
      <img src="/media/sofa-oslo-grau.jpg" class="product-tile__image" width="480" height="360">
    • https://musterladen.example/sofas/oslo-2-sitzer · desktop.product-tile > a > img
      <img src="/media/sofa-oslo-grau.jpg" class="product-tile__image" width="480" height="360">

    Pages with this issue

    • https://musterladen.example/
    • https://musterladen.example/kontakt
    • https://musterladen.example/leuchten
    • https://musterladen.example/sofas
    • https://musterladen.example/sofas/bergen-ecksofa
    • https://musterladen.example/sofas/oslo-2-sitzer
    • https://musterladen.example/tische
    • https://musterladen.example/tische/esstisch-lund
    • https://musterladen.example/warenkorb
  • CriticalForm fields without a labelScreen reader users don't know what to type, and a placeholder that disappears while typing doesn't help either.footer .newsletter input[type="email"]12 places12 pages

    How to fix it: Connect a visible <label> to each field with for and id.

    WCAG 4.1.2 Name, Role, Value · EN 301 549 9.4.1.2

    Suggested code

    A suggestion built from the element's HTML. Check it before you use it.

    Before

    <input type="email" name="newsletter_email" placeholder="E-Mail-Adresse">

    After

    <label for="field-name">Field name</label>
<input type="email" name="newsletter_email" placeholder="E-Mail-Adresse" id="field-name">

    Examples

    • https://musterladen.example/ · desktopfooter .newsletter input[type="email"]
      <input type="email" name="newsletter_email" placeholder="E-Mail-Adresse">
    • https://musterladen.example/sofas · desktopfooter .newsletter input[type="email"]
      <input type="email" name="newsletter_email" placeholder="E-Mail-Adresse">
    • https://musterladen.example/sofas/oslo-2-sitzer · desktopfooter .newsletter input[type="email"]
      <input type="email" name="newsletter_email" placeholder="E-Mail-Adresse">

    Pages with this issue

    • https://musterladen.example/
    • https://musterladen.example/impressum
    • https://musterladen.example/kontakt
    • https://musterladen.example/leuchten
    • https://musterladen.example/sofas
    • https://musterladen.example/sofas/bergen-ecksofa
    • https://musterladen.example/sofas/oslo-2-sitzer
    • https://musterladen.example/tische
    • https://musterladen.example/tische/esstisch-lund
    • https://musterladen.example/ueber-uns
    • https://musterladen.example/versand
    • https://musterladen.example/warenkorb
  • SeriousText with too little contrastPeople with low vision, and anyone reading on a phone in sunlight, struggle to read pale text on its background..price--old118 places12 pages

    How to fix it: Darken the text or lighten the background until normal text reaches 4.5:1 and large text 3:1.

    WCAG 1.4.3 Contrast (Minimum) · EN 301 549 9.1.4.3

    Suggested code

    A suggestion built from the element's HTML. Check it before you use it.

    Before

    .price--old {
    color: #9a9a9a;
}

    After

    .price--old {
    color: #747474; /* 4.7:1 on #ffffff */
}

    Examples

    • https://musterladen.example/ · desktop.price--old
      <span class="price--old">1.299,00 €</span>
    • https://musterladen.example/sofas · desktop.price--old
      <span class="price--old">1.299,00 €</span>
    • https://musterladen.example/sofas/oslo-2-sitzer · desktop.price--old
      <span class="price--old">1.299,00 €</span>

    Pages with this issue

    • https://musterladen.example/
    • https://musterladen.example/impressum
    • https://musterladen.example/kontakt
    • https://musterladen.example/leuchten
    • https://musterladen.example/sofas
    • https://musterladen.example/sofas/bergen-ecksofa
    • https://musterladen.example/sofas/oslo-2-sitzer
    • https://musterladen.example/tische
    • https://musterladen.example/tische/esstisch-lund
    • https://musterladen.example/ueber-uns
    • https://musterladen.example/versand
    • https://musterladen.example/warenkorb
  • SeriousLinks without a nameA screen reader announces just “link”, so visitors can't tell where it leads. This is common for icon-only links.footer .social > a:nth-child(1)36 places12 pages

    How to fix it: Give the link visible text, or an aria-label that says where it goes.

    WCAG 2.4.4 Link Purpose (In Context) · EN 301 549 9.2.4.4WCAG 4.1.2 Name, Role, Value · EN 301 549 9.4.1.2

    Suggested code

    A suggestion built from the element's HTML. Check it before you use it.

    Before

    <a href="https://instagram.com/musterladen" class="social__link">

    After

    <a href="https://instagram.com/musterladen" class="social__link" aria-label="Where the link goes">

    Examples

    • https://musterladen.example/ · desktopfooter .social > a:nth-child(1)
      <a href="https://instagram.com/musterladen" class="social__link"><svg class="icon" viewBox="0 0 24 24"><circle cx="12" cy="12" r="4"></circle></svg></a>
    • https://musterladen.example/sofas · desktopfooter .social > a:nth-child(1)
      <a href="https://instagram.com/musterladen" class="social__link"><svg class="icon" viewBox="0 0 24 24"><circle cx="12" cy="12" r="4"></circle></svg></a>
    • https://musterladen.example/sofas/oslo-2-sitzer · desktopfooter .social > a:nth-child(1)
      <a href="https://instagram.com/musterladen" class="social__link"><svg class="icon" viewBox="0 0 24 24"><circle cx="12" cy="12" r="4"></circle></svg></a>

    Pages with this issue

    • https://musterladen.example/
    • https://musterladen.example/impressum
    • https://musterladen.example/kontakt
    • https://musterladen.example/leuchten
    • https://musterladen.example/sofas
    • https://musterladen.example/sofas/bergen-ecksofa
    • https://musterladen.example/sofas/oslo-2-sitzer
    • https://musterladen.example/tische
    • https://musterladen.example/tische/esstisch-lund
    • https://musterladen.example/ueber-uns
    • https://musterladen.example/versand
    • https://musterladen.example/warenkorb
  • SeriousScript checkKeyboard focus is not visiblePeople who use a keyboard cannot see where they are, because nothing changes when the element receives focus..main-nav__link7 places7 pages

    How to fix it: Give links, buttons and fields a clear focus style, for example an outline in :focus-visible. Do not remove the outline without a replacement.

    WCAG 2.4.7 Focus Visible · EN 301 549 9.2.4.7

    Suggested code

    A suggestion built from the element's HTML. Check it before you use it.

    CSS

    .main-nav__link:focus-visible {
    outline: 3px solid currentColor;
    outline-offset: 2px;
}

    Examples

    • https://musterladen.example/ · desktop.main-nav__link
      <a href="/sofas" class="main-nav__link">Sofas</a>
    • https://musterladen.example/sofas · desktop.main-nav__link
      <a href="/sofas" class="main-nav__link">Sofas</a>
    • https://musterladen.example/sofas/oslo-2-sitzer · desktop.main-nav__link
      <a href="/sofas" class="main-nav__link">Sofas</a>

    Pages with this issue

    • https://musterladen.example/
    • https://musterladen.example/leuchten
    • https://musterladen.example/sofas
    • https://musterladen.example/sofas/bergen-ecksofa
    • https://musterladen.example/sofas/oslo-2-sitzer
    • https://musterladen.example/tische
    • https://musterladen.example/tische/esstisch-lund
  • ModerateClick targets that are too smallSmall or tightly packed buttons and links are hard to hit for people with tremor and on touch screens..quantity__step6 places3 pages

    How to fix it: Make targets at least 24 × 24 pixels, or leave enough space around them.

    WCAG 2.5.8 Target Size (Minimum)

    Suggested code

    A suggestion built from the element's HTML. Check it before you use it.

    CSS

    .quantity__step {
    min-width: 24px;
    min-height: 24px;
}

    Examples

    • https://musterladen.example/ · desktop.quantity__step
      <button class="quantity__step" type="button">+</button>
    • https://musterladen.example/sofas · desktop.quantity__step
      <button class="quantity__step" type="button">+</button>
    • https://musterladen.example/sofas/oslo-2-sitzer · desktop.quantity__step
      <button class="quantity__step" type="button">+</button>

    Pages with this issue

    • https://musterladen.example/
    • https://musterladen.example/sofas
    • https://musterladen.example/sofas/oslo-2-sitzer

To check by hand

The automatic check could not decide these. They are not counted in the score. Look at each one and decide whether it is an error.

  • Possibly seriousText with too little contrastPeople with low vision, and anyone reading on a phone in sunlight, struggle to read pale text on its background.3 places1 template

    How to fix it: Darken the text or lighten the background until normal text reaches 4.5:1 and large text 3:1.

    WCAG 1.4.3 Contrast (Minimum) · EN 301 549 9.1.4.3

    Where it occurs

    • .hero__title3 places · 1 page

      Examples

      • https://musterladen.example/ · desktop.hero__title
        <h1 class="hero__title">Neu: die Kollektion Herbst</h1>

      Pages with this issue

      • https://musterladen.example/

3 · Documentation

Manual check

These are the answers given by the website owner in the guided manual check, for 4 of 20 questions. They are their own assessment, not a test by Luentis.

  • Everything works with the keyboardWCAG 2.1.1 · WCAG 2.1.2 · Nov 9, 2026No problems found
  • Focus is visible and in a logical orderWCAG 2.4.3 · WCAG 2.4.7 · WCAG 2.4.11 · Nov 9, 2026Problems found
  • Nothing changes unexpectedlyWCAG 3.2.1 · WCAG 3.2.2 · Nov 9, 2026No problems found
  • Images are described meaningfullyWCAG 1.1.1 · WCAG 1.4.5 · Nov 9, 2026Problems found

Every success criterion of WCAG 2.2 at levels A and AA, with the clause in EN 301 549. "No errors found automatically" only means that our automatic rules found nothing. It does not mean that the criterion is met.

WCAG 2.2 success criteria and results
WCAGCriterionEN 301 549Result
1.1.1Non-text Content9.1.1.1Errors found
1.2.1Audio-only and Video-only (Prerecorded)9.1.2.1No errors found automatically
1.2.2Captions (Prerecorded)9.1.2.2No errors found automatically
1.2.3Audio Description or Media Alternative (Prerecorded)9.1.2.3Cannot be tested automatically
1.2.4Captions (Live)9.1.2.4Cannot be tested automatically
1.2.5Audio Description (Prerecorded)9.1.2.5Cannot be tested automatically
1.3.1Info and Relationships9.1.3.1No errors found automatically
1.3.2Meaningful Sequence9.1.3.2Cannot be tested automatically
1.3.3Sensory Characteristics9.1.3.3Cannot be tested automatically
1.3.4Orientation9.1.3.4No errors found automatically
1.3.5Identify Input Purpose9.1.3.5No errors found automatically
1.4.1Use of Color9.1.4.1No errors found automatically
1.4.2Audio Control9.1.4.2No errors found automatically
1.4.3Contrast (Minimum)9.1.4.3Errors found
1.4.4Resize Text9.1.4.4No errors found automatically
1.4.5Images of Text9.1.4.5Checked by you: problems found
1.4.10Reflow9.1.4.10No errors found automatically
1.4.11Non-text Contrast9.1.4.11Cannot be tested automatically
1.4.12Text Spacing9.1.4.12No errors found automatically
1.4.13Content on Hover or Focus9.1.4.13Cannot be tested automatically
2.1.1Keyboard9.2.1.1Checked by you: no problems found
2.1.2No Keyboard Trap9.2.1.2Checked by you: no problems found
2.1.4Character Key Shortcuts9.2.1.4Cannot be tested automatically
2.2.1Timing Adjustable9.2.2.1No errors found automatically
2.2.2Pause, Stop, Hide9.2.2.2No errors found automatically
2.3.1Three Flashes or Below Threshold9.2.3.1Cannot be tested automatically
2.4.1Bypass Blocks9.2.4.1No errors found automatically
2.4.2Page Titled9.2.4.2No errors found automatically
2.4.3Focus Order9.2.4.3Checked by you: problems found
2.4.4Link Purpose (In Context)9.2.4.4Errors found
2.4.5Multiple Ways9.2.4.5Cannot be tested automatically
2.4.6Headings and Labels9.2.4.6Cannot be tested automatically
2.4.7Focus Visible9.2.4.7Errors found
2.4.11Focus Not Obscured (Minimum)–Checked by you: problems found
2.5.1Pointer Gestures9.2.5.1Cannot be tested automatically
2.5.2Pointer Cancellation9.2.5.2Cannot be tested automatically
2.5.3Label in Name9.2.5.3No errors found automatically
2.5.4Motion Actuation9.2.5.4Cannot be tested automatically
2.5.7Dragging Movements–Cannot be tested automatically
2.5.8Target Size (Minimum)–Errors found
3.1.1Language of Page9.3.1.1No errors found automatically
3.1.2Language of Parts9.3.1.2No errors found automatically
3.2.1On Focus9.3.2.1Checked by you: no problems found
3.2.2On Input9.3.2.2Checked by you: no problems found
3.2.3Consistent Navigation9.3.2.3Cannot be tested automatically
3.2.4Consistent Identification9.3.2.4Cannot be tested automatically
3.2.6Consistent Help–Cannot be tested automatically
3.3.1Error Identification9.3.3.1Cannot be tested automatically
3.3.2Labels or Instructions9.3.3.2No errors found automatically
3.3.3Error Suggestion9.3.3.3Cannot be tested automatically
3.3.4Error Prevention (Legal, Financial, Data)9.3.3.4Cannot be tested automatically
3.3.7Redundant Entry–Cannot be tested automatically
3.3.8Accessible Authentication (Minimum)–Cannot be tested automatically
4.1.2Name, Role, Value9.4.1.2Errors found
4.1.3Status Messages9.4.1.3Cannot be tested automatically
Pages checked (12)
  • https://musterladen.example/
  • https://musterladen.example/sofas
  • https://musterladen.example/sofas/oslo-2-sitzer
  • https://musterladen.example/sofas/bergen-ecksofa
  • https://musterladen.example/tische
  • https://musterladen.example/tische/esstisch-lund
  • https://musterladen.example/leuchten
  • https://musterladen.example/warenkorb
  • https://musterladen.example/kontakt
  • https://musterladen.example/ueber-uns
  • https://musterladen.example/versand
  • https://musterladen.example/impressum