Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 6 REVIEW 3 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

12 landmarks

REVIEW

12 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

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.

Why this matters

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

Link & Button Quality

4 issue(s) across 90 links and 37 buttons

REVIEW

4 issue(s) across 90 links and 37 buttons

3 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.openstreetmap.org/copyright; /terms; /privacy

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button#birth-year-unknown; button#show-opening; button.inline-flex (#385 on page); button#send-terms

87 link(s) with descriptive text

90 links

0 empty

0 generic text

3 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
/	Birthday Website Maker	img no alt	Add alt attribute to the image
/	Birthday Website Maker	img no alt	Add alt attribute to the image
https://www.openstreetmap.org/copyright	OpenStreetMap	new tab	Add '(opens in new tab)' to text
/terms	Terms of Service	new tab	Add '(opens in new tab)' to text
/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
/birthday-website-for-girlfriend	GirlfriendRomantic, specific, …	img no alt	Add alt attribute to the image
/birthday-website-for-boyfriend	BoyfriendThe things you mean b…	img no alt	Add alt attribute to the image
/birthday-website-for-wife	WifeA look back over the years…	img no alt	Add alt attribute to the image
/birthday-website-for-husband	HusbandShort and honest beats …	img no alt	Add alt attribute to the image
/birthday-website-for-best-friend	Best friendInside jokes first,…	img no alt	Add alt attribute to the image
/birthday-website-for-mom	MomA thank-you she will reread…	img no alt	Add alt attribute to the image
/birthday-website-for-dad	DadFor the dad who “doesn’…	img no alt	Add alt attribute to the image
/long-distance-birthday-surprise	Long distanceArrives at midnig…	img no alt	Add alt attribute to the image
/birthday-website-for-girlfriend	Birthday website for girlfrien…	img no alt	Add alt attribute to the image
/birthday-website-for-boyfriend	Birthday website for boyfriend…	img no alt	Add alt attribute to the image
/birthday-website-for-wife	Birthday website for wifeYears…	img no alt	Add alt attribute to the image
/birthday-website-for-husband	Birthday website for husbandA …	img no alt	Add alt attribute to the image
/birthday-website-for-best-friend	Birthday website for best frie…	img no alt	Add alt attribute to the image
/birthday-website-for-mom	Birthday website for momA than…	img no alt	Add alt attribute to the image
/long-distance-birthday-surprise	Long distance birthday surpris…	img no alt	Add alt attribute to the image
/birthday-surprise-website	Birthday surprise websiteA cak…	img no alt	Add alt attribute to the image
/	Birthday Website Maker	img no alt	Add alt attribute to the image
<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
<button>	(empty)	empty	Add button text or aria-label

120 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://www.openstreetmap.org/copyright; /terms; /privacy

Why this matters

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

Icon-only buttons need an aria-label so screen readers can announce them.

button#birth-year-unknown; button#show-opening; button.inline-flex (#385 on page); button#send-terms

Why this matters

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

Mobile Keyboard & Autofill

Action

3/6 eligible field(s) missing autocomplete or inputmode

REVIEW

3/6 eligible field(s) missing autocomplete or inputmode

3 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: url, email, tel.

Got: <input type="url">, <input type="email" id="send-email">, <input type="tel" id="send-phone">

Mobile-Readable Font Sizes

93% of visible text renders at >= 12 CSS px (30 below threshold)

REVIEW

93% of visible text renders at >= 12 CSS px (30 below threshold)

30 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <p> 11.0px ("Saturday, June 14"); <p> 10.0px ("The letter"); <p> 10.0px ("Moments"); <span> 10.0px ("Empty — hidden"); <span> 10.0px ("Empty — hidden").

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Heading Hierarchy

72 headings

PASS

72 headings

Single H1 present

H1 Birthday Website Maker
H2 Make their birthday page right here
H3 Whose birthday is it?
H3 Fill the party with surprises
H3 All set for the party
H2 What is a birthday website?
H2 How Birthday Website Maker works
H3 Write it
H3 Preview it
H3 Unlock and send
H2 Eight surprises. All of them yours.
H3 A cake that counts down
H3 Your letter — or a template
H3 Moments: up to 10 photos
H3 Little surprises + your song
H3 One link, $5.99 to unlock
H2 This is what they open
H2 For every kind of birthday
H3 Girlfriend
H3 Boyfriend
H3 Wife
H3 Husband
H3 Best friend
H3 Mom
H3 Dad
H3 Long distance
H2 One page, many moods
H3 Soft & sweet
H3 Film & cream
H3 Cake & cheer
H3 Quiet love
H3 Daylight
H2 Example pages
H3 “Happy birthday, love”
H3 “Ten years of bad decisions”
H3 “Thank you for the small things”
H3 “It’s midnight where you are”
H2 Birthday website vs card, video, or party invite
H2 What a birthday website can feel like
H2 Priced like a gift
H3 Preview
H3 Birthday party gift
H2 Questions before you make one
H3 What is Birthday Website Maker?
H3 Is it a party invitation or RSVP site?
H3 Is it free?
H3 Do I need an account?
H3 Does the person I send it to need an app or an account?
H3 What can I put on the page?
H3 Do I need design or coding skills?
H3 Who can see the page?
H3 Can they open it before their birthday?
H3 Can I edit the page after I share it?
H3 Does it write the letter for me?
H3 Will it look right on their phone?
H2 Their birthday, in your words
H2 More birthday website ideas
H3 Birthday website for girlfriend
H3 Birthday website for boyfriend
H3 Birthday website for wife
H3 Birthday website for husband
H3 Birthday website for best friend
H3 Birthday website for mom
H3 Long distance birthday surprise
H3 Birthday surprise website
H2 Birthday guides
H3 How to Make a Birthday Website (No Coding, in One Evening)
H3 What Is a Birthday Website? And When It Beats a Card
H3 How to Choose Photos for a Birthday Surprise Page
H3 When and How to Send a Birthday Surprise Link (Midnight, Morning, or In Person)
H3 Best Birthday Website Makers in 2026: An Honest Comparison
H3 Best Songs for a Birthday Surprise (for Partners, Friends, and Parents)

A+

Heading Text Quality

All 72 heading(s) have substantive, well-formed text

PASS

All 72 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 63 images OK

PASS

All 63 images OK

50 decorative image(s) correctly marked

13 image(s) with good alt text

63 images 13 good alt text 50 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 17 controls labeled

PASS

All 17 controls labeled

17 control(s) properly labeled

17 controls

17 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#recipient-name	input	Who is celebrating?	for/id
#birthday-date	date	Birthday date (optional)	for/id
#sender-name	input	Who is throwing the party?	for/id
textarea	textarea	The letter	aria-label
textarea	textarea	What I love	aria-label
textarea	textarea	Our story	aria-label
textarea	textarea	Wishes	aria-label
#photos	file	Add photosJPG, PNG, WebP, HEIC	for/id
input	input	Search for a place	aria-label
input	date	Our date	aria-label
input	input	What happened that day?	aria-label
input	url	Our song	aria-label
input	input	Song title (optional)	aria-label
#send-email	email	Your email	for/id
#send-phone	tel	Phone (optional)	for/id
#send-password	password	Password (optional)	for/id
#send-promo	input	Promo code	for/id

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "Search for a place" should use type="search" (currently type="text")

Field name "Search for a place" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

17 form control(s) checked, no input-semantic issues

PASS

17 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

Tabindex Anti-Patterns

0 positive, 3 -1-on-focusable

PASS

0 positive, 3 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <input>

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Birthday Website Maker

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Birthday Website Maker ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Birthday Website Maker Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Birthday Website Mak…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Make their birthday …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What is a birthday w…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 How Birthday Website…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Eight surprises. All…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 This is what they op…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 For every kind of bi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 One page, many moods	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Example pages	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Birthday website vs …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What a birthday webs…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Priced like a gift	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Questions before you…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Their birthday, in y…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 More birthday websit…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Birthday guides	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Whose birthday is it…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Fill the party with …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 All set for the part…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Write it	21.00:1	3.0: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.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 29 passed

PASS

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section#chapter-surprises > div.space-y-3 > div.flex > button.inline-flex `section#chapter-surprises > div.space-y-3 > div.flex > button.inline-flex`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SATURDAY, JUNE 14 `div.w-full > div.px-6 > div.text-center > p.text-[11px]`
THE LETTER `div.w-full > div.px-6 > div.mt-5 > p.text-[10px]`
MOMENTS `div.relative > div.w-full > div.px-6 > p.mt-5`
Empty — hidden `div.flex > div.min-w-0 > p.flex > span.rounded-full`
Empty — hidden `div.flex > div.min-w-0 > p.flex > span.rounded-full`
Empty — hidden `div.flex > div.min-w-0 > p.flex > span.rounded-full`
Empty — hidden `div.flex > div.min-w-0 > p.flex > span.rounded-full`
Empty — hidden `div.flex > div.min-w-0 > p.flex > span.rounded-full`
JPG, PNG, WebP, HEIC `div.space-y-3 > div.grid > label.flex > span.text-[10px]`
We read the date and location from your photos to suggest Our date and Places. … `form.min-w-0 > section#chapter-surprises > div.space-y-3 > p.text-[11px]`
Empty — hidden `div.flex > div.min-w-0 > p.flex > span.rounded-full`
Empty — hidden `div.flex > div.min-w-0 > p.flex > span.rounded-full`
The letter `section#chapter-send > div.rounded-xl > ul.mt-2 > li.rounded-full`
What I love `section#chapter-send > div.rounded-xl > ul.mt-2 > li.rounded-full`
Our story `section#chapter-send > div.rounded-xl > ul.mt-2 > li.rounded-full`
Wishes `section#chapter-send > div.rounded-xl > ul.mt-2 > li.rounded-full`
Moments `section#chapter-send > div.rounded-xl > ul.mt-2 > li.rounded-full`
Places `section#chapter-send > div.rounded-xl > ul.mt-2 > li.rounded-full`
Our date `section#chapter-send > div.rounded-xl > ul.mt-2 > li.rounded-full`
Our song `section#chapter-send > div.rounded-xl > ul.mt-2 > li.rounded-full`
FRIDAY, APRIL 5 `div.relative > div.px-6 > div.text-center > p.text-[11px]`
THE LETTER `div.relative > div.px-6 > div.mt-5 > p.text-[10px]`
MOMENTS `div.flex > div.relative > div.px-6 > p.mt-5`
Swipe the table sideways to see every column → `section#compare > div.mx-auto > div.mt-10 > p.mb-2`
Illustrative examples written by our team. We will only publish real reviews wi… `div.flex > section#stories > div.mx-auto > p.mt-6`

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

●`<td>` elements in a large `<table>` have one or more table headers.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.