Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DFavicon & BrandingAction5 icon(s) detectedFIX
DPrint StylesheetActionNo print stylesFIX
BLandmark Structure2 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 HierarchyNo headingsREVIEW
No headings found
Headings create the document outline for screen reader navigation.
Headings (H1-H6) create the document outline for screen reader navigation.
A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.
Learn more ▾ ▴
Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.
Source: WCAG 1.3.1 / W3C WAI
B404 Error PageHTTP 404, custom pageREVIEW
BDark Mode SupportDark mode detectedREVIEW
Detection limited to meta tags and inline styles.
A+Heading Text QualityNo headings to evaluate -- check is N/APASS
A+Alt Text QualityNo imagesPASS
A+Form AccessibilityNo form controlsPASS
A+Link & Button Quality1 links, 0 buttons — all OKPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://vercel.link/security-checkpoint | Website owner? Click here to f… | new tab | Add '(opens in new tab)' to text |
Add '(opens in new tab)' to link text or aria-label.
https://vercel.link/security-checkpoint
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 3 visible text node(s) render at >= 12 CSS pixelsPASS
A+Web ManifestPWA-readyPASS
A+PWA Depth1 PWA signal(s) surfacedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
A+Color Contrast (Screenshot)5 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 (5)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| title Vercel Security Chec… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p We're verifying your… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Website owner? Click… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p Vercel Security Chec… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p cdg1::1778416070-Kd0… | 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.
ALighthouse Accessibility AuditsScore 92/100 — 3 failing, 24 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
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Swimming Pool Access
Factor
Caretaker
Bins
Fire
Winter Visitors
History main.site-content > main.relative > nav.fixed > div.bg-neutral-900/65 |
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.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
History nav.fixed > div.bg-neutral-900/65 > button.relative > span.block |
These are opportunities to improve the legibility of your content.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
James Square header.site-header > div.flex > div.rounded-xl > a.flex |