Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureActionNo landmarksFIX
No landmarks detected
Screen reader users have no way to navigate by region.
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
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
F404 Error PageActionSoft 404 detectedFIX
The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.
DPrint StylesheetActionNo print stylesFIX
BDark Mode SupportDark mode detectedREVIEW
Detection limited to meta tags and inline styles.
A+Heading Hierarchy1 headingsPASS
- H1 WhatsApp works with Google Chrome 100+
A+Heading Text QualityAll 1 heading(s) have substantive, well-formed textPASS
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
ALink & Button Quality6 links, 0 buttons — all OKPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://support.google.com/chrome/answer… | Chrome | new tab | Add '(opens in new tab)' to text |
| http://www.firefox.com/ | Mozilla Firefox | new tab | Add '(opens in new tab)' to text |
| https://www.apple.com/safari/ | Safari | new tab | Add '(opens in new tab)' to text |
| https://www.microsoft.com/edge | Microsoft Edge | new tab | Add '(opens in new tab)' to text |
| https://www.opera.com/ | Opera | new tab | Add '(opens in new tab)' to text |
| http://www.google.com/chrome/ | Update Google Chrome | new tab | Add '(opens in new tab)' to text |
Add '(opens in new tab)' to link text or aria-label.
https://support.google.com/chrome/answer/95414; http://www.firefox.com/; https://www.apple.com/safari/; https://www.microsoft.com/edge; https://www.opera.com/; http://www.google.com/chrome/
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
A+Form Input TypesNo form controls on this pagePASS
A+Form Input QualityNo form controls on this pagePASS
A+Mobile Keyboard & AutofillNo form controls -- mobile keyboard check is N/APASS
A+Document LanguageLang attribute set to "en"PASS
A+Tabindex Anti-PatternsNo explicit tabindex attributes foundPASS
A+Iframe AccessibilityNo iframes on this pagePASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+Mobile-Readable Font SizesAll 10 visible text node(s) render at >= 12 CSS pixelsPASS
AFavicon & Branding12 icon(s) detectedPASS
A+Web ManifestPWA-readyPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth2 mobile-depth signal(s) detectedPASS
A+Color Contrast (Screenshot)9 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 (9)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 WhatsApp works with … | 19.40:1 | 3.0:1 | #000000 | #FCF5EB | Pass |
| div To use WhatsApp, upd… | 19.40:1 | 4.5:1 | #000000 | #FCF5EB | Pass |
| a Chrome | 19.40:1 | 4.5:1 | #000000 | #FCF5EB | Pass |
| div or use | 19.40:1 | 4.5:1 | #000000 | #FCF5EB | Pass |
| a Mozilla Firefox | 19.40:1 | 4.5:1 | #000000 | #FCF5EB | Pass |
| a Safari | 19.40:1 | 4.5:1 | #000000 | #FCF5EB | Pass |
| a Microsoft Edge | 20.36:1 | 4.5:1 | #000000 | #FEFBF7 | Pass |
| a Opera | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Update Google Chrome | 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 100/100 — 0 failing, 16 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.