Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 4 REVIEW 3 FIX

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 ✗

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 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 icon(s) detected

No favicon.ico at site root

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

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

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 #121212 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

h2 The story so far

1.09:1

#000000

#0E0E0E

needs 3.0:1 (large text)

24px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Remix 3 is under act…	18.16:1	3.0:1	#000000	#EBEFF2	Pass
h2 The story so far	1.09:1	3.0:1	#000000	#0E0E0E	Fail
h2 Stay in the loop	20.31:1	3.0:1	#000000	#FBFBFC	Pass
h3 Timeline milestones	20.31:1	3.0:1	#000000	#FBFBFC	Pass
h3 Remix Newsletter	20.31:1	3.0:1	#000000	#FBFBFC	Pass
h3 Remix Community	20.31:1	3.0:1	#000000	#FBFBFC	Pass
title Remix - A Full Stack…	12.87:1	4.5:1	#000000	#C7CBCF	Pass
a Skip to main content	13.41:1	4.5:1	#000000	#CBCFD3	Pass
span Remix home	13.95:1	4.5:1	#000000	#CFD3D7	Pass
a Blog	14.37:1	4.5:1	#000000	#D2D6DA	Pass
a Jam	14.94:1	4.5:1	#000000	#D6DADE	Pass
a Store	15.53:1	4.5:1	#000000	#DADEE2	Pass
a V2 Docs	16.13:1	4.5:1	#000000	#DEE2E6	Pass
span Open menu	16.43:1	4.5:1	#000000	#E0E4E8	Pass
a Blog	16.74:1	4.5:1	#000000	#E2E6EA	Pass
a Jam	17.04:1	4.5:1	#000000	#E4E8EB	Pass
a Store	17.36:1	4.5:1	#000000	#E6EAED	Pass
a V2 Docs	17.68:1	4.5:1	#000000	#E8ECEF	Pass
p A new full stack fra…	18.52:1	4.5:1	#000000	#EEF1F4	Pass
p We are building Remi…	18.84:1	4.5:1	#000000	#F0F3F5	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+

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

6 headings

PASS

6 headings

Single H1 present

H1 Remix 3 is under active development
H2 The story so far
H3 Timeline milestones
H2 Stay in the loop
H3 Remix Newsletter
H3 Remix Community

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

1 decorative image(s) correctly marked

1 image(s) with good alt text

2 images 1 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#newsletter-email	email	Email address	for/id

Link & Button Quality

24 links, 1 buttons — all OK

PASS

24 links, 1 buttons — all OK

7 link(s) open in new tab without warning

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

Got: https://shop.remix.run; https://shop.remix.run; https://v5.reactrouter.com/; https://reactrouter.com/v6; https://v2.remix.run/; https://reactrouter.com/; https://github.com/remix-run/remix

17 link(s) with descriptive text

24 links

0 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://shop.remix.run	Store	new tab	Add '(opens in new tab)' to text
https://shop.remix.run	Store	new tab	Add '(opens in new tab)' to text
https://v5.reactrouter.com/	2019v5	new tab	Add '(opens in new tab)' to text
https://reactrouter.com/v6	2020v6	new tab	Add '(opens in new tab)' to text
https://v2.remix.run/	2023v2	new tab	Add '(opens in new tab)' to text
https://reactrouter.com/	2024v7	new tab	Add '(opens in new tab)' to text
https://github.com/remix-run/remix	2025v3	new tab	Add '(opens in new tab)' to text

18 links and buttons have descriptive text

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

https://shop.remix.run; https://shop.remix.run; https://v5.reactrouter.com/; https://reactrouter.com/v6; https://v2.remix.run/; https://reactrouter.com/; https://github.com/remix-run/remix

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

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 24 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.

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
Watch the repo `section.flex > div.text-rmx-primary > a.rmx-bg-button-primary > span`
v6 `div.mx-auto > div.xl:hidden > div.relative > div.rmx-caption`
v1 `div.mx-auto > div.xl:hidden > div.relative > div.rmx-caption`
Subscribe `div.flex > div.rmx-bg-surface-4 > form.m-0 > button.rmx-bg-button-primary`
DOCS AND EXAMPLES LICENSED UNDER MIT `div.rmx-home-surface-bg > footer.flex > div.text-rmx-muted > p`
©2026 SHOPIFY, INC. `div.rmx-home-surface-bg > footer.flex > div.text-rmx-muted > p`

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

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

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

●Buttons have an accessible name

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

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

○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

○`[role]` values are valid

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

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

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

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