Accessibility review: https://unrealbakeshop.example/
This is a sample. It shows the review page from a scan of a made-up bakery page. Here, ticks aren't saved; when magnacoda shows your own scan, they are.
Findings
12 problems on 12 elements (2 critical, 9 serious, 1 moderate)
Summary
Tested on desktop, in light mode (the page looks the same in dark mode).
| Severity | Count |
|---|---|
| critical | 2 |
| serious | 9 |
| moderate | 1 |
| minor | 0 |
Problems found
| Severity | Rule | WCAG | Elements | Where |
|---|---|---|---|---|
| serious | color-contrastElements must meet minimum color contrast ratio thresholds | 1.4.3 | 2 |
|
| serious | html-has-lang<html> element must have a lang attribute | 3.1.1 | 1 |
|
| critical | image-altImages must have alternative text | 1.1.1 | 2 |
|
| serious | magnacoda/click-onlyIt reacts to a mouse click, but Tab can't reach it, so keyboard users can't use it | 2.1.1 | 1 |
|
| serious | magnacoda/reflowAt 320 px wide (what 400% zoom gives on a common screen), it sticks out 65 px past the edge, so the page scrolls sideways | 1.4.10 | 2 |
|
| serious | magnacoda/focus-not-visibleWith the keyboard focus on it, it looks exactly the same as without: nothing shows where the focus is | 2.4.7 | 3 |
|
| moderate | magnacoda/missing-autocompleteIt looks like it asks for the visitor's own email address, but has no autocomplete value, so browsers can't fill it in and assistive tools can't show what it's for | 1.3.5 | 1 |
|
Suggested fixes
color-contrast: Change the text color from #b8a99a to #84705d (4.54:1 on #fffaf3; needs 4.5:1).color-contrast: Change the text color from #c9bdb2 to #85705d (4.52:1 on #fffaf3; needs 4.5:1).html-has-lang: Add alangattribute to<html>identifying the page's primary language.image-alt: Add a concise, descriptivealtattribute (oralt=""if the image is purely decorative). (2 elements)magnacoda/click-only: Use a real<button>(or a link, if it goes somewhere): it can be reached with Tab and works with Enter and Space by itself. A<div>or<span>with a click handler can't.magnacoda/reflow: Let it shrink with the window: usemax-width: 100%instead of a fixed width (andheight: autofor images), let long words break (overflow-wrap: anywhere), and put side-by-side parts under each other on narrow screens with a media query. (2 elements)magnacoda/focus-not-visible: Give it a visible focus style, and don't remove the outline without a replacement: for example an outline of at least 2px in a color with 3:1 contrast against the background. (3 elements)magnacoda/missing-autocomplete: Addautocomplete="email", if the field asks for the visitor's own details (for someone else's, such as a gift's recipient, leave it out).
Passed checks (9)
aria-hidden-body: aria-hidden="true" must not be present on the document bodymeta-viewport: Zooming and scaling must not be disabledbypass: Page must have means to bypass repeated blocksdocument-title: Documents must have <title> element to aid in navigationlink-name: Links must have discernible texttarget-size: All touch targets must be 24px large, or leave sufficient spaceform-field-multiple-labels: Form field must not have multiple label elementslabel: Form elements must have labelsnested-interactive: Interactive controls must not be nested
51 other rules did not apply to this page. Passing means axe-core found no violation; automated checks cover only part of WCAG, so this is not a full audit.
Checklist
8 of 57 checked
Scanned 2026-11-19 15:54 UTC with magnacoda 0.0.1.dev344+g5068df09d.d20261031 (axe-core 4.13.0) - WCAG 2.2 Level AA - tested on desktop, in light mode (the page looks the same in dark mode).
Automated checks can settle only part of WCAG. All 55 criteria in scope are covered below, as checked automatically or as still needing a person, because many depend on judgment (is the alt text meaningful, does the keyboard order make sense). What concerns particular elements is listed under each element; the rest is listed by criterion. Tick items off as you verify them. Links go to the W3C's Understanding pages.
To cover more: scan again with
--ai semanticfor a second look at alt text, headings and link text; scan your other kinds of pages too; and work through the page elements and the checks below with a keyboard and a screen reader.
Page elements (12)
Each element that has a problem or something to check, listed once, with everything about it underneath: Fix failed an automated check (tick it when you've fixed it), Review is something axe-core couldn't decide, Check needs a person; tick the element's box when you've looked at its Review and Check items. Elements with exactly the same items are listed together, each with its own box, and the items once. Elements with the most serious problems come first.
1. header > img ("logo.svg")
(200×40)- alt text: none. Is it purely decorative? Yes: add
alt="". No: addalt="..."saying what it shows (or, in a link or button, where it goes or what it does). - source:
https://unrealbakeshop.example/logo.svg - Fix 1.1.1 Non-text Content (opens in a new tab) (A) - Images must have alternative text (critical; rule image-alt)
- now:
<img src="logo.svg" width="200" height="40"> - fix: Add a concise, descriptive
altattribute (oralt=""if the image is purely decorative). (the same fix applies to 2 elements) - e.g.
<img src="logo.svg" width="200" height="40" alt="Describe the image content here">
- now:
- Checked: tick when you've looked at everything below that needs a person
- Check 1.4.5 Images of Text (opens in a new tab) (AA) - Text should be real text, not text baked into images (logos excepted).
2. main > img ("loaves.svg")
(400×160)- alt text: none. Is it purely decorative? Yes: add
alt="". No: addalt="..."saying what it shows (or, in a link or button, where it goes or what it does). - source:
https://unrealbakeshop.example/loaves.svg - Fix 1.1.1 Non-text Content (opens in a new tab) (A) - Images must have alternative text (critical; rule image-alt)
- now:
<img src="loaves.svg" width="400" height="160"> - fix: Add a concise, descriptive
altattribute (oralt=""if the image is purely decorative). (the same fix applies to 2 elements) - e.g.
<img src="loaves.svg" width="400" height="160" alt="Describe the image content here">
- now:
- Fix 1.4.10 Reflow (opens in a new tab) (AA) - At 320 px wide (what 400% zoom gives on a common screen), it sticks out 96 px past the edge, so the page scrolls sideways (serious; rule magnacoda/reflow)
- now:
<img src="loaves.svg" width="400" height="160"> - fix: Let it shrink with the window: use
max-width: 100%instead of a fixed width (andheight: autofor images), let long words break (overflow-wrap: anywhere), and put side-by-side parts under each other on narrow screens with a media query. (the same fix applies to 2 elements) - e.g.
.banner { width: auto; max-width: 100%; }
- now:
- Checked: tick when you've looked at everything below that needs a person
- Check 1.4.5 Images of Text (opens in a new tab) (AA) - Text should be real text, not text baked into images (logos excepted).
3. p.hours:nth-of-type(1) ("Open Tuesday to Sunday, 7 am to 3 pm.")
- Fix 1.4.3 Contrast (Minimum) (opens in a new tab) (AA) - Elements must meet minimum color contrast ratio thresholds (serious; rule color-contrast)
- now:
<p class="hours">Open Tuesday to Sunday, 7 am to 3 pm.</p> - set by
.hours { color: #b8a99a }in a style element of the page (/, line 12 of its HTML); it's a class on the element itself: if it's a utility class (as in Tailwind), change the element's classes in its HTML instead - fix: Change the text color from #b8a99a to #84705d (4.54:1 on #fffaf3; needs 4.5:1).
- e.g.
/* .hours */ color: #84705d;
- now:
4. footer ("© Unreal Bake Shop")
- Fix 1.4.3 Contrast (Minimum) (opens in a new tab) (AA) - Elements must meet minimum color contrast ratio thresholds (serious; rule color-contrast)
- now:
<footer>© Unreal Bake Shop</footer> - set by
footer { color: #c9bdb2 }in a style element of the page (/, line 16 of its HTML) - fix: Change the text color from #c9bdb2 to #85705d (4.52:1 on #fffaf3; needs 4.5:1).
- e.g.
/* footer */ color: #85705d;
- now:
5. html ("MenuVisitOrder Fresh bread every morning Open Tue…")
- Fix 3.1.1 Language of Page (opens in a new tab) (A) - <html> element must have a lang attribute (serious; rule html-has-lang)
- now:
<html> - fix: Add a
langattribute to<html>identifying the page's primary language. - e.g.
<html lang="en">
- now:
6. div
- Fix 2.1.1 Keyboard (opens in a new tab) (A) - It reacts to a mouse click, but Tab can't reach it, so keyboard users can't use it (serious; rule magnacoda/click-only)
- now:
<div onclick="alert('Thanks!')" data-magnacoda-clickable="0">Send</div> - fix: Use a real
<button>(or a link, if it goes somewhere): it can be reached with Tab and works with Enter and Space by itself. A<div>or<span>with a click handler can't. - e.g.
<button type="button">...</button>
- now:
7. nav
- Fix 1.4.10 Reflow (opens in a new tab) (AA) - At 320 px wide (what 400% zoom gives on a common screen), it sticks out 65 px past the edge, so the page scrolls sideways (serious; rule magnacoda/reflow)
- now:
<nav><a href="#menu">Menu</a><a href="#visit">Visit</a><a href="#order">Order</a></nav> - fix: Let it shrink with the window: use
max-width: 100%instead of a fixed width (andheight: autofor images), let long words break (overflow-wrap: anywhere), and put side-by-side parts under each other on narrow screens with a media query. (the same fix applies to 2 elements) - e.g.
.banner { width: auto; max-width: 100%; }
- now:
8. Fix these 3 elements, all in the same way
a:nth-of-type(1)- now:
<a href="#menu">Menu</a> - set by
a:focus { outline: none }in a style element of the page (/, line 15 of its HTML), with the keyboard focus on it - e.g.
:focus-visible { outline: 3px solid #1a4fd0; outline-offset: 2px; }
- now:
a:nth-of-type(2)- now:
<a href="#visit">Visit</a> - set by
a:focus { outline: none }in a style element of the page (/, line 15 of its HTML), with the keyboard focus on it - e.g.
:focus-visible { outline: 3px solid #1a4fd0; outline-offset: 2px; }
- now:
a:nth-of-type(3)- now:
<a href="#order">Order</a> - set by
a:focus { outline: none }in a style element of the page (/, line 15 of its HTML), with the keyboard focus on it - e.g.
:focus-visible { outline: 3px solid #1a4fd0; outline-offset: 2px; }
- now:
For each of them:
- Fix 2.4.7 Focus Visible (opens in a new tab) (AA) - With the keyboard focus on it, it looks exactly the same as without: nothing shows where the focus is (serious; rule magnacoda/focus-not-visible)
- fix: Give it a visible focus style, and don't remove the outline without a replacement: for example an outline of at least 2px in a color with 3:1 contrast against the background. (the same fix applies to 3 elements)
9. input ("Your email")
- Fix 1.3.5 Identify Input Purpose (opens in a new tab) (AA) - It looks like it asks for the visitor's own email address, but has no autocomplete value, so browsers can't fill it in and assistive tools can't show what it's for (moderate; rule magnacoda/missing-autocomplete)
- now:
<input type="email" placeholder="Your email"> - fix: Add
autocomplete="email", if the field asks for the visitor's own details (for someone else's, such as a gift's recipient, leave it out). - e.g.
<input type="email" placeholder="Your email" autocomplete="email">
- now:
- Checked: tick when you've looked at everything below that needs a person
- Check 3.3.1 Error Identification (opens in a new tab) (A) - Submit invalid or empty input: errors must be shown in text and identify the field in error.
- Check 3.3.3 Error Suggestion (opens in a new tab) (AA) - When an input error is detected and a fix is known, the message should suggest it.
- Check 4.1.3 Status Messages (opens in a new tab) (AA) - Status messages (success, errors, result counts) must be announced via role=status/alert or live regions without moving focus.
10. form.order ("Send")
- Checked: tick when you've looked at everything below that needs a person
- Check 3.3.1 Error Identification (opens in a new tab) (A) - Submit invalid or empty input: errors must be shown in text and identify the field in error.
- Check 3.3.3 Error Suggestion (opens in a new tab) (AA) - When an input error is detected and a fix is known, the message should suggest it.
- Check 3.3.4 Error Prevention (Legal, Financial, Data) (opens in a new tab) (AA) - Submissions that are legal, financial or change user data must be reversible, checked or confirmed.
- Check 4.1.3 Status Messages (opens in a new tab) (AA) - Status messages (success, errors, result counts) must be announced via role=status/alert or live regions without moving focus.
Check on every page (7)
- 1.3.2 Meaningful Sequence (opens in a new tab) (A) - Check the reading order makes sense with CSS off or in a screen reader (DOM order matches visual order).
- 1.3.3 Sensory Characteristics (opens in a new tab) (A) - Check instructions don't rely only on shape, size, position or sound ("click the round button").
- 1.3.4 Orientation (opens in a new tab) (AA) - Rotate the device or resize the viewport: content must not be locked to one orientation.
- 1.4.11 Non-text Contrast (opens in a new tab) (AA) - UI components (input borders, icons, focus rings) and meaningful graphics need 3:1 contrast.
- 2.4.3 Focus Order (opens in a new tab) (A) - Tab through the page: focus order must follow a logical, meaningful sequence. Tab went through all 4 elements, always moving on down the page; check that the order also makes sense.
- 2.4.6 Headings and Labels (opens in a new tab) (AA) - Headings and labels must describe their topic or purpose.
- 2.5.2 Pointer Cancellation (opens in a new tab) (A) - Actions should fire on pointer release, and be cancellable by moving the pointer away first.
Depends on your site or user flows (7)
- 2.1.4 Character Key Shortcuts (opens in a new tab) (A) - If the page defines single-key shortcuts, users must be able to turn them off or remap them. (only applies if the page defines single-character keyboard shortcuts, which can't be detected automatically) Pressing single keys (
/,?,s,j,k,n,g,h) with nothing focused did nothing; check any shortcuts the page lists. - 2.4.5 Multiple Ways (opens in a new tab) (AA) - Users should have more than one way to find pages (navigation, search, sitemap). (a site-level check - it needs more than one page)
- 2.5.4 Motion Actuation (opens in a new tab) (A) - Actions triggered by shaking or tilting the device also need a normal control, and motion must be switch-off-able. (only applies if the page responds to device motion, which can't be detected automatically)
- 3.2.3 Consistent Navigation (opens in a new tab) (AA) - Navigation should appear in the same order on every page. (a site-level check - compare several pages)
- 3.2.4 Consistent Identification (opens in a new tab) (AA) - Components with the same function must be labelled the same way across pages. (a site-level check - compare several pages)
- 3.2.6 Consistent Help (opens in a new tab) (A) - Where help is offered (contact link, chat, FAQ) it must appear in the same relative place on every page. (a site-level check - compare several pages)
- 3.3.7 Redundant Entry (opens in a new tab) (A) - In a multi-step process, information already entered must not have to be entered again. (a flow-level check - walk through the multi-step process)
Passed automated checks (17)
Ticked items need nothing more; unticked ones have a human follow-up.
- 1.3.1 Info and Relationships (opens in a new tab) (A) - passed automated checks. Still worth a look: axe checks markup validity, not whether the structure matches what is shown.
- 1.4.4 Resize Text (opens in a new tab) (AA) - passed automated checks. Still worth a look: no text is cut off at 200% zoom; check in a browser that everything still works there.
- 1.4.12 Text Spacing (opens in a new tab) (AA) - passed automated checks. Still worth a look: with WCAG's text spacing no text is cut off or spills out of its box; check that nothing overlaps.
- 2.1.2 No Keyboard Trap (opens in a new tab) (A) - passed automated checks. Still worth a look: Tab went through all 4 elements without a problem; check things that open, such as menus and dialogs, and embedded players: Tab must get out of each.
- 2.4.1 Bypass Blocks (opens in a new tab) (A) - passed automated checks. Still worth a look: axe checks a bypass mechanism exists; confirm the skip link works and is reachable by keyboard.
- 2.4.2 Page Titled (opens in a new tab) (A) - passed automated checks. Still worth a look: axe checks a title exists; confirm it is descriptive.
- 2.4.4 Link Purpose (In Context) (opens in a new tab) (A) - passed automated checks. Still worth a look: axe checks links have text, not that the text is meaningful.
- 2.4.11 Focus Not Obscured (Minimum) (opens in a new tab) (AA) - passed automated checks. Still worth a look: Tab went through all 4 elements without a problem; check things that open, such as menus and dialogs, and the page with any banner shown.
- 2.5.8 Target Size (Minimum) (opens in a new tab) (AA) - passed automated checks. Still worth a look: axe checks target size for the rendered layout; confirm at other viewport sizes.
- 3.2.1 On Focus (opens in a new tab) (A) - passed automated checks. Still worth a look: Tab went through all 4 elements without a problem; check things that open, such as menus and dialogs.
- 3.2.2 On Input (opens in a new tab) (A) - passed automated checks. Still worth a look: if changing a field is meant to do something at once, make sure the page says so beforehand.
- 3.3.2 Labels or Instructions (opens in a new tab) (A) - passed automated checks. Still worth a look: axe checks fields have accessible names; confirm the visible labels and instructions are clear.
- 4.1.2 Name, Role, Value (opens in a new tab) (A) - passed automated checks. Still worth a look: axe checks ARIA validity; test custom widgets with a screen reader.
- 1.4.1 Use of Color (opens in a new tab) (A) (axe-core found nothing to check here) - passed automated checks. Still worth a look: axe checks links inside text blocks, not other color-only cues.
- 2.2.1 Timing Adjustable (opens in a new tab) (A) (axe-core found nothing to check here) - passed automated checks.
- 2.2.2 Pause, Stop, Hide (opens in a new tab) (A) (axe-core found nothing to check here) - passed automated checks.
- 3.1.2 Language of Parts (opens in a new tab) (AA) (axe-core found nothing to check here) - passed automated checks. Still worth a look: axe checks lang values are valid, not that foreign passages are marked up.
Not applicable to this page (6)
No audio, video or embedded player (iframe, object, embed) was found on this page, so these don't apply; they come ticked.
- 1.2.1 Audio-only and Video-only (Prerecorded) (opens in a new tab) (A) - untick if the page shows audio or video after you click something.
- 1.2.2 Captions (Prerecorded) (opens in a new tab) (A) - untick if the page shows audio or video after you click something.
- 1.2.3 Audio Description or Media Alternative (Prerecorded) (opens in a new tab) (A) - untick if the page shows audio or video after you click something.
- 1.2.4 Captions (Live) (opens in a new tab) (AA) - untick if the page shows audio or video after you click something.
- 1.2.5 Audio Description (Prerecorded) (opens in a new tab) (AA) - untick if the page shows audio or video after you click something.
- 1.4.2 Audio Control (opens in a new tab) (A) - untick if the page shows audio or video after you click something.
Probably not applicable (6)
No trigger was detected on this page - confirm quickly.
- 1.4.13 Content on Hover or Focus (opens in a new tab) (AA) - no tooltip or popup triggers detected. If it does apply: Content shown on hover or focus (tooltips, menus) must be dismissible, hoverable and persistent.
- 2.3.1 Three Flashes or Below Threshold (opens in a new tab) (A) - no animation, video, canvas or embeds detected. If it does apply: Nothing should flash more than three times in any one second.
- 2.5.1 Pointer Gestures (opens in a new tab) (A) - no canvas, custom widgets, draggable items or embeds detected. If it does apply: Anything done with multi-finger or path-based gestures (pinch, swipe, drawing) also needs a single-pointer alternative.
- 2.5.3 Label in Name (opens in a new tab) (A) - no controls with an aria-label detected. If it does apply: A control's accessible name must contain its visible label text.
- 2.5.7 Dragging Movements (opens in a new tab) (AA) - no draggable elements or custom widgets detected. If it does apply: Anything done by dragging needs a single-pointer alternative (click or tap).
- 3.3.8 Accessible Authentication (Minimum) (opens in a new tab) (AA) - no password field or CAPTCHA detected. If it does apply: Logging in must not require a cognitive test (memorising, transcribing, puzzles); allow paste and password managers.