magnacoda review

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).

Problems found, by severity
SeverityCount
critical2
serious9
moderate1
minor0

Problems found

Failing rules and where they are
Severity Rule WCAG Elements Where
seriouscolor-contrast
Elements must meet minimum color contrast ratio thresholds
1.4.32
  • .hours
  • footer
serioushtml-has-lang
<html> element must have a lang attribute
3.1.11
  • html
criticalimage-alt
Images must have alternative text
1.1.12
  • img[src$="logo.svg"]
  • img[src$="loaves.svg"]
seriousmagnacoda/click-only
It reacts to a mouse click, but Tab can't reach it, so keyboard users can't use it
2.1.11
  • div
seriousmagnacoda/reflow
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
1.4.102
  • nav
  • main > img
seriousmagnacoda/focus-not-visible
With the keyboard focus on it, it looks exactly the same as without: nothing shows where the focus is
2.4.73
  • a:nth-of-type(1)
  • a:nth-of-type(2)
  • a:nth-of-type(3)
moderatemagnacoda/missing-autocomplete
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
1.3.51
  • input

Suggested fixes

Passed checks (9)

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 semantic for 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")

2. main > img ("loaves.svg")

3. p.hours:nth-of-type(1) ("Open Tuesday to Sunday, 7 am to 3 pm.")

5. html ("MenuVisitOrder Fresh bread every morning Open Tue…")

6. div

7. nav

8. Fix these 3 elements, all in the same way

For each of them:

9. input ("Your email")

10. form.order ("Send")

Check on every page (7)

Depends on your site or user flows (7)

Passed automated checks (17)

Ticked items need nothing more; unticked ones have a human follow-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.

Probably not applicable (6)

No trigger was detected on this page - confirm quickly.

Back to top