WCAG 2.2 Accessibility Report · Complete with Seal
Accessibility Report (Complete)
Muster-Boutique · 23 July 2026 · Standard applied: WCAG 2.2 A/AA (based on EN 301 549)
Website checked: muster-boutique.ch
Seal status: Not yet awarded – The seal will be issued once the defects listed below have been fixed and the free retest has been completed.
60/100Automated score
Overall result
Your website is well on its way. A number of individual barriers remain that should be addressed specifically – the detail section shows each one with its location and solution.
2high (automated)
1medium
0low
7Instances (automated)
The score assesses only the automated scan. There is no scoring system for the manually checked criteria – they are listed and must be free of defects for the seal. Currently 5 defect(s) found through manual checking (see list below).
Overview
| Pages checked | 3 |
|---|
| Automated scan | 3 rule(s) violated at 7 instance(s) |
|---|
| Automated score | 60 / 100 (automated scan only) |
|---|
| Manually checked criteria (WCAG 2.2 AA) | 37 — 28 met, 4 n/a, 5 with defect |
|---|
| Broken links (quality note) | 1 |
|---|
On the score: The score from 0–100 assesses only the automated scan (severity and number of affected instances; our own model, not an official standard). There is no scoring system for the manually checked criteria – they are listed individually and must be free of defects for the seal (0 defects).
3 content pages were checked – both automatically and manually. Embedded files (PDF/Office) and third-party content are not checked.
Important note: This report is a technical assessment against WCAG 2.2 (Level AA) / EN 301 549 and does not constitute legal advice, official certification, or complete proof of conformance. Only the listed criteria and pages are checked; a passed report does not guarantee legal compliance. For a legally binding assessment, please contact a recognised specialist body.
An automated scan covers the criteria that can be tested by machine (including colour contrast, labelling, page titles); the manual review covers the points a machine cannot detect (including keyboard operation, focus, error messages).
About the numbers: "WCAG 2.2" is the version of the standard. Numbers such as 1.1.1, 2.4.7 or 4.1.3 are the individual success criteria within it – not version numbers. The first digit represents one of the four principles: 1 Perceivable, 2 Operable, 3 Understandable, 4 Robust.
Defects found (8)
Each box is a task: the problem and why it matters at the top, the affected locations and the solution below. If an item shows only example locations, it has the same cause throughout – fix it once centrally (template/theme) and all instances are resolved. The complete list of locations for your webmaster is included as a CSV.
01
Visible focus
high priority
The problem: Anyone navigating by keyboard needs to see where they currently are. A focus outline that has been styled away makes the page unusable.
Affected locations: 3 ·
WCAG: 2.4.7 ·
Check type: 🔎 Manual check
Found on: 3 pages — / /produkte /kontakt
Specific finding: Auf allen Seiten ist der Tastatur-Fokus unsichtbar (outline:none im Stylesheet).
How to fix this: Ensure a clearly visible focus indicator (an outline or border with good contrast); do not remove the default focus style via CSS.
Before*:focus { outline: none; }
After:focus-visible {
outline: 2px solid #1a5276;
outline-offset: 2px;
}
02
Images without alternative text
high priority
The problem: Product images do not have descriptive text. Blind and visually impaired customers using a screen reader cannot see what is in the image.
Affected locations: 3 ·
WCAG: 1.1.1 ·
Check type: 🤖 Automated scan
Found on: 2 pages — /produkte /
Specific finding:<img src="/p/sommerkleid.jpg" class="pimg"><img src="/p/tasche.jpg" class="pimg">
How to fix this: Enter a short alternative text for each image in the shop system that describes the image content (e.g. 'Blue drinking bottle 750 ml'). Purely decorative images should be marked as decorative.
Before<img src="produkt.jpg">
After<img src="produkt.jpg" alt="Trinkflasche, 750 ml">
Rule reference: image-alt
03
Links without meaningful text
high priority
The problem: Links have only generic text such as 'Here', 'Click me' or 'More'. Users with screen readers or motor impairments do not understand where the link leads or cannot select it precisely.
Affected locations: 2 ·
WCAG: 2.4.4, 4.1.2 ·
Check type: 🤖 Automated scan
Found on: 1 page — /
Specific finding:<a href="/agb">hier</a><a href="/produkte">mehr</a>
How to fix this: Label all links with meaningful text (e.g. instead of 'More' rather 'Read privacy policy'). The link text should also be understandable in isolation.
Before<a href="/x"><img src="icon.png"></a>
After<a href="/x" aria-label="Home">
<img src="icon.png" alt="Home">
</a>
Rule reference: link-name
04
Keyboard operation
high priority
The problem: Many people with motor impairments, or who use a screen reader, do not use a mouse. Anything that only works with a mouse is inaccessible to them.
Affected locations: 1 ·
WCAG: 2.1.1/2.1.4 ·
Check type: 🔎 Manual check
Found on: 1 page — /produkte
Specific finding: Filter „Grösse / Farbe“ öffnet sich nur per Mausklick; per Tab/Enter nicht erreichbar.
How to fix this: Make all functions (menu, filters, shopping cart, checkout) reachable and operable via Tab/Enter/arrow keys. Provide keyboard support for custom widgets.
Before<div class="filter"
onclick="open()">Size</div>
After<button type="button" class="filter">
Size
</button>
05
Clear error messages
high priority
The problem: If a form error is indicated only by red colouring, blind users do not know what is wrong – the order fails.
Affected locations: 1 ·
WCAG: 3.3.1/3.3.3 ·
Check type: 🔎 Manual check
Found on: 1 page — /kontakt
Specific finding: Pflichtfelder werden bei Fehleingabe nur rot umrandet, ohne Text.
How to fix this: State errors in text, associate them with the relevant field, and give a concrete instruction for correcting them (not colour alone).
Before<input class="is-error">
After<input aria-invalid="true"
aria-describedby="e-mail">
<span id="e-mail">Enter a valid
e-mail address</span>
06
Status messages are announced
high priority
The problem: Messages such as "Added to cart" are often shown only visually. Screen reader users do not notice them and are left uncertain.
Affected locations: 1 ·
WCAG: 4.1.3 ·
Check type: 🔎 Manual check
Found on: 1 page — /produkte
Specific finding: Nach dem Klick erscheint kurz ein grüner Hinweis, der vom Screenreader nicht vorgelesen wird.
How to fix this: Output status/success/error messages in an aria-live region so the screen reader announces them automatically.
Before<div class="toast">Added to cart</div>
After<div class="toast" role="status"
aria-live="polite">Added to cart</div>
07
Content on hover/focus
medium priority
The problem: Drop-down menus and tooltips that disappear immediately or cannot be dismissed lock out users who rely on magnification or the keyboard.
Affected locations: 2 ·
WCAG: 1.4.13 ·
Check type: 🔎 Manual check
Found on: 2 pages — / /produkte
Specific finding: Das Aufklapp-Menü schliesst, sobald die Maus den Rand berührt; mit Vergrösserung nicht bedienbar.
How to fix this: Content shown on hover/focus must remain operable (the mouse pointer must be able to move onto it), must be dismissible with Esc, and must not permanently obscure the underlying content.
Before.menu:hover .sub {
display: block;
}
After.menu:hover .sub,
.menu:focus-within .sub {
display: block; /* + Esc closes */
}
08
Headings in wrong order
medium priority
The problem: Headings skip levels (e.g. H1 directly to H3). Screen reader users do not understand the structure and cannot navigate efficiently. The page appears disorganised.
Affected locations: 2 ·
WCAG: Best Practice ·
Check type: 🤖 Automated scan
Found on: 2 pages — / /kontakt
Specific finding:<h3>Neu eingetroffen</h3><h4>Öffnungszeiten</h4>
How to fix this: Correct the heading hierarchy: H1 (page title), then H2, H3 etc. without skips. Set tags consistently in the editor or HTML.
Before<h1>…</h1>
<h4>…</h4>
After<h1>…</h1>
<h2>…</h2>
Rule reference: heading-order
Checked items with no issues (32)
These criteria were checked – both automatically and manually – and are in order. "n/a" (not applicable) means: this feature does not exist on your website, so there is nothing to check – the reason is given alongside each one.
Perceivable
✓
Alt text for images Criterion 1.1.1
met
✓
Heading structure Criterion 1.3.1
met
✓
Logical reading order Criterion 1.3.2
met
✓
Not relying on sensory characteristics alone Criterion 1.3.3
met
✓
Information not conveyed by colour alone Criterion 1.4.1
met
✓
Zoom and reflow up to 400% Criterion 1.4.10
met
–
Captions and audio description Criterion 1.2.1–1.2.5Keine Audio- oder Video-Inhalte auf der Website.
n/a
✓
Contrast of user interface components and graphics Criterion 1.4.11
met
✓
Text resizable to 200% Criterion 1.4.4
met
✓
Text spacing adjustable Criterion 1.4.12
met
✓
No text in images Criterion 1.4.5
met
✓
Input purpose identifiable (autofill) Criterion 1.3.5
met
✓
Usable in portrait and landscape Criterion 1.3.4
met
Operable
✓
No keyboard trap Criterion 2.1.2
met
✓
Skip link to content Criterion 2.4.1
met
✓
Logical focus order Criterion 2.4.3
met
✓
Recognisable link purpose Criterion 2.4.4
met
✓
Focus not obscured Criterion 2.4.11
met
–
Alternative to dragging Criterion 2.5.7Keine Zieh-/Schiebe-Bedienung (z. B. Slider) vorhanden.
n/a
✓
Sufficiently large target size Criterion 2.5.8
met
✓
Multiple ways to reach content Criterion 2.4.5
met
✓
Visible name matches accessible name Criterion 2.5.3
met
✓
Time limits and moving content Criterion 2.2.1/2.2.2/2.3.1/1.4.2
met
✓
Descriptive headings and labels Criterion 2.4.6
met
✓
Pointer input: gestures, cancellation, motion Criterion 2.5.1/2.5.2/2.5.4
met
Understandable
✓
No unexpected changes Criterion 3.2.1/3.2.2
met
✓
Order reviewable before submission Criterion 3.3.4
met
–
Accessible sign-in Criterion 3.3.8Kein Kundenkonto / keine Anmeldung – nur Gast-Bestellung.
n/a
–
Language of individual sections Criterion 3.1.2Keine fremdsprachigen Abschnitte im Inhalt.
n/a
✓
Consistent navigation and labelling Criterion 3.2.3/3.2.4
met
✓
No redundant entry Criterion 3.3.7
met
✓
Help placed consistently Criterion 3.2.6
met
Technical notes – broken links (1)
These links lead nowhere. This is not an accessibility criterion and does not block the seal – but it is a quality issue worth fixing. (External links are not checked.)
·
https://muster-boutique.ch/lookbook-2024
Status 404
Links to: /
How to get the seal
1. Work through the defects – starting with those of high priority. The enclosed CSV of locations lists every individual instance for your webmaster.
2. Start the free retest in the portal. We check automatically testable defects monthly, and the manually assessed items once a year at renewal.
3. Receive the seal: Once all items are resolved, we issue the seal "Checked against WCAG 2.2 AA" (valid for 12 months) and you embed it in your footer using a ready-made snippet.
Part of the proceeds from every report supports organisations for people with disabilities.
Basis: WCAG 2.2 (Level AA) / EN 301 549. "High priority" refers to functions that completely prevent access for some groups of users. This report documents the result as at the date stated and does not constitute official certification or complete proof of conformance.
Greenlight Check · greenlight-check.ch · Report against WCAG 2.2 AA