Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.F404 Error PageActionHTTP 404, bare pageFIX
DPrint StylesheetActionNo print stylesFIX
BLandmark Structure5 landmarksREVIEW
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
BLink & Button Quality4 issue(s) across 23 links and 8 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| /use-cases | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: Use Cases | |||
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
Generic link text like 'click here' doesn't describe the destination.
/use-cases ("Learn more")
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Icon-only buttons need an aria-label so screen readers can announce them.
button.w-10 (#256 on page); button.absolute (#267 on page); button.w-16 (#273 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
BMobile-Readable Font Sizes93% of visible text renders at >= 12 CSS px (5 below threshold)REVIEW
BDark Mode SupportDark mode detectedREVIEW
Detection limited to meta tags and inline styles.
A+Heading Hierarchy14 headingsPASS
- H1 Find your potential spouse anonymously.
- H2 Three steps. Quietly.
- H3 Set up your card
- H3 Browse your wall
- H3 Trade three answers
- H2 So your aunt won't recognise you scrolling.
- H2 Block, report, walk away.
- H3 Block
- H3 Report
- H3 Leave
- H2 What people usually want to know first.
- H2 Ready to take a quiet look?
- H3 Support
- H4 How can we help?
A+Heading Text QualityAll 14 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityAll 1 images OKPASS
AForm Accessibility1 of 1 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #support-textarea | textarea | (Type your message...) | placeholder only |
Placeholder text disappears on focus and is not a reliable label.
<textarea name="content" id="support-textarea">
Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.
Learn more ▾ ▴
Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).
Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman
A+Form Input Types1 form control(s) checked, no type mismatchesPASS
A+Form Input Quality1 form control(s) checked, no input-semantic issuesPASS
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
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
AFavicon & Branding8 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)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 Find your potential … | 14.87:1 | 3.0:1 | #000000 | #DAD9D5 | Pass |
| h2 Three steps. Quietly… | 15.17:1 | 3.0:1 | #000000 | #DCDBD8 | Pass |
| h2 So your aunt won't r… | 15.17:1 | 3.0:1 | #000000 | #DCDBD8 | Pass |
| h2 Block, report, walk … | 15.17:1 | 3.0:1 | #000000 | #DCDBD8 | Pass |
| h2 What people usually … | 15.17:1 | 3.0:1 | #000000 | #DCDBD8 | Pass |
| h2 Ready to take a quie… | 15.17:1 | 3.0:1 | #000000 | #DCDBD8 | Pass |
| h3 Set up your card | 15.17:1 | 3.0:1 | #000000 | #DCDBD8 | Pass |
| h3 Browse your wall | 15.17:1 | 3.0:1 | #000000 | #DCDBD8 | Pass |
| h3 Trade three answers | 15.17:1 | 3.0:1 | #000000 | #DCDBD8 | Pass |
| h3 Block | 15.17:1 | 3.0:1 | #000000 | #DCDBD8 | Pass |
| h3 Report | 15.17:1 | 3.0:1 | #000000 | #DCDBD8 | Pass |
| h3 Leave | 15.17:1 | 3.0:1 | #000000 | #DCDBD8 | Pass |
| h3 Support | 15.17:1 | 3.0:1 | #000000 | #DCDBD8 | Pass |
| title Find your potential … | 20.31:1 | 4.5:1 | #000000 | #FDFBF6 | Pass |
| span Potential | 20.31:1 | 4.5:1 | #000000 | #FDFBF6 | Pass |
| span Spouse | 13.99:1 | 4.5:1 | #000000 | #D2D3D2 | Pass |
| a Who it's for | 14.20:1 | 4.5:1 | #000000 | #D2D5D3 | Pass |
| a About | 13.96:1 | 4.5:1 | #000000 | #D1D3D2 | Pass |
| a Essays | 13.96:1 | 4.5:1 | #000000 | #D1D3D2 | Pass |
| a Support | 13.95:1 | 4.5:1 | #000000 | #D1D3D1 | 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 90/100 — 2 failing, 20 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.
Names and labels
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#support-widget > div.absolute > div.relative > button.w-10 div#support-widget > div.absolute > div.relative > button.w-10 |
div.absolute > div.p-5 > form.relative > button.absolute div.absolute > div.p-5 > form.relative > button.absolute |
div#phx-GK6Njpnj9JcuonQR > div#support-widget > div.relative > button.w-16 div#phx-GK6Njpnj9JcuonQR > div#support-widget > div.relative > button.w-16 |
These are opportunities to improve the semantics of the controls in your application. This 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 |
|---|
Spouse div.mx-auto > a.flex > span.font-display > span.text-primary-sky |
Sign in header.sticky > div.mx-auto > div.flex > a.inline-flex |
Start setup — 6 questions → section.hero-section > div.hero-content > div.reveal > button.inline-flex |
Spouse div.mx-auto > div.flex > span.font-display > span.text-primary-sky |
These are opportunities to improve the legibility of your content.