Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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

2 navigation landmark(s) detected

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 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

No banner (header) landmark

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

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Remory — Some moments deserve to last forever. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA

h2 Three steps to forever.

2.54:1

#000000

#1E5751

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Each one, one of a kind.

2.54:1

#000000

#1E5751

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Stories within stories.

2.54:1

#000000

#1E5751

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Made to last forever.

2.54:1

#000000

#1E5751

needs 3.0:1 (large text)

24px · bottom of viewport

h2 One price. One heirloom.

2.54:1

#000000

#1E5751

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Share your photographs

2.54:1

#000000

#1E5751

needs 3.0:1 (large text)

19px · bottom of viewport

h3 We transform your photos

2.54:1

#000000

#1E5751

needs 3.0:1 (large text)

19px · bottom of viewport

h3 You receive an heirloom

2.54:1

#000000

#1E5751

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Archival paper that lasts centuries.

2.54:1

#000000

#1E5751

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Bound to last generations.

2.54:1

#000000

#1E5751

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Some moments deserve…	18.56:1	3.0:1	#000000	#F7F0E6	Pass
h2 “The photograph fa…	18.56:1	3.0:1	#000000	#F7F0E6	Pass
h2 The moment does not…	18.56:1	3.0:1	#000000	#F7F0E6	Pass
h2 From photograph to	18.56:1	3.0:1	#000000	#F7F0E6	Pass
h2 Three steps to forev…	2.54:1	3.0:1	#000000	#1E5751	Fail
h2 Each one, one of a k…	2.54:1	3.0:1	#000000	#1E5751	Fail
h2 Stories within stori…	2.54:1	3.0:1	#000000	#1E5751	Fail
h2 Made to last forever…	2.54:1	3.0:1	#000000	#1E5751	Fail
h2 One price. One heirl…	2.54:1	3.0:1	#000000	#1E5751	Fail
h3 Share your photograp…	2.54:1	3.0:1	#000000	#1E5751	Fail
h3 We transform your ph…	2.54:1	3.0:1	#000000	#1E5751	Fail
h3 You receive an heirl…	2.54:1	3.0:1	#000000	#1E5751	Fail
h3 Archival paper that …	2.54:1	3.0:1	#000000	#1E5751	Fail
h3 Bound to last genera…	2.54:1	3.0:1	#000000	#1E5751	Fail
title Remory — Some mome…	18.57:1	4.5:1	#000000	#F7F0E7	Pass
a Our Story	18.57:1	4.5:1	#000000	#F7F0E7	Pass
a Process	18.57:1	4.5:1	#000000	#F7F0E7	Pass
a Remory	18.56:1	4.5:1	#000000	#F7F0E6	Pass
a Gallery	18.56:1	4.5:1	#000000	#F7F0E6	Pass
a Materials	18.56:1	4.5:1	#000000	#F7F0E6	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+

Heading Hierarchy

13 headings

PASS

13 headings

Single H1 present

H1 Some moments deserve to last forever.
H2 “The photograph fades.The moment does not.”
H2 From photograph to heirloom.
H2 Three steps to forever.
H3 Share your photographs
H3 We transform your photos
H3 You receive an heirloom
H2 Each one, one of a kind.
H2 Stories within stories.
H2 Made to last forever.
H3 Archival paper that lasts centuries.
H3 Bound to last generations.
H2 One price. One heirloom. Forever.

A+

Alt Text Quality

All 11 images OK

PASS

All 11 images OK

11 image(s) with good alt text

11 images 11 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

16 links, 0 buttons — all OK

PASS

16 links, 0 buttons — all OK

16 link(s) with descriptive text

16 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

16 links and buttons have descriptive text

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 23 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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
5 out of 5 stars `div.max-w-screen-xl > div.grid > div.watercolor-edge > div.flex`
5 out of 5 stars `div.max-w-screen-xl > div.grid > div.watercolor-edge > div.flex`
5 out of 5 stars `div.max-w-screen-xl > div.grid > div.watercolor-edge > div.flex`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
01 `div.max-w-screen-xl > div.grid > div.relative > span.absolute`
02 `div.max-w-screen-xl > div.grid > div.relative > span.absolute`
03 `div.max-w-screen-xl > div.grid > div.relative > span.absolute`

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

●`[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

●ARIA input fields have accessible names

●Document has a `<title>` element

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

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

●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.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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

○Buttons have an accessible name

○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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○`<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.

○Identical links have the same purpose.

○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.

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