Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureAction5 landmarksFIX
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
Multiple navigations need aria-label to distinguish them for screen readers.
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
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
DPrint StylesheetActionNo print stylesFIX
BHeading Hierarchy10 headingsREVIEW
- H1 (empty)
- H1 Privacy & Terms duplicate H1
- H1 (empty)
- H2 Privacy & Terms
- H1 Privacy Policy duplicate H1
- H1 Terms of Service duplicate H1
- H1 Google Safety Center duplicate H1
- H1 Google Account duplicate H1
- H1 Our Privacy and Security Principles duplicate H1
- H1 Google Product Privacy Guide duplicate H1
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
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
CFavicon & BrandingAction4 icon(s) detectedREVIEW
CWeb ManifestActionValid manifestREVIEW
BDark Mode SupportDark mode detectedREVIEW
Detection limited to meta tags and inline styles.
A+Alt Text QualityAll 6 images OKPASS
A+Form AccessibilityNo form controlsPASS
A+Link & Button Quality34 links, 1 buttons — all OKPASS
A+Color Contrast (Screenshot)20 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 (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Privacy & Terms | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Privacy Policy | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Terms of Service | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Google Safety Center | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Google Account | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Our Privacy and Secu… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Google Product Priva… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Privacy & Terms – … | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Privacy & Terms | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div Privacy & Terms | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Privacy & Terms | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Privacy & Terms | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Skip to main content | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Sign in | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Overview | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Privacy Policy | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Terms of Service | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Technologies | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a FAQ | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Overview | 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 99/100 — 1 failing, 27 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.
Best practices
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.