Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FFavicon & BrandingAction1 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
CLandmark StructureAction1 landmarksREVIEW
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.
Learn more ▾ ▴
WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.
Source: WCAG 2.1 SC 2.4.1
BHeading Hierarchy1 headingsREVIEW
- H2 (empty)
Every page should have one H1 that describes the page content.
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Learn more ▾ ▴
The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.
Source: WCAG 2.4.6 / Google Search Central
Empty headings appear in the document outline but provide no information.
Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.
Source: WCAG 2.4.6
C404 Error PageActionHTTP 404, custom pageREVIEW
AAlt Text Quality1 of 1 images have issuesPASS
| Issue | Count |
|---|---|
| missing | 1 image(s) |
Images without alt text are invisible to screen readers.
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
Learn more ▾ ▴
WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.
Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report
A+Form AccessibilityNo form controlsPASS
A+Link & Button Quality1 links, 0 buttons — all OKPASS
A+Color Contrast (Screenshot)11 text elements analyzed, 0 fail WCAG AAPASS
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (11)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| title Just a moment... | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div Verification success… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Ray ID | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| li : 9e8bafadafec42ba | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Your IP address | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| li : 2001:41d0:ab00::4:… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Detected location | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| li : ES | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p We’re currently ch… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p If you keep getting … | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a problem with Canva | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
A+Lighthouse Accessibility AuditsScore 97/100 — 1 failing, 26 passedPASS
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Source: MDN Permissions-Policy
| Failing Elements |
|---|
Continue in the app
Enjoy more features, share direct to social media and get … body > div.NoN2AA > div#_r_k_ |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.