Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

18 PASS 2 REVIEW 4 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

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

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

7 icon(s) detected

REVIEW

7 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

A+

Heading Hierarchy

20 headings

PASS

20 headings

Single H1 present

H1 A pomodoro timer for focus, study sessions, and virtual coworking
H2 See who else is focusing in real-time
H2 Why FocusLive works well for repeatable focus
H2 Use FocusLive when starting is the hardest part
H3 Pomodoro timer for deep work
H3 Online study timer
H3 Body doubling for accountability
H2 Frequently asked questions
H3 What is FocusLive?
H3 Is FocusLive good for studying?
H3 Do I need an account to use the timer?
H2 Explore more FocusLive pages
H3 Pomodoro Timer
H3 Study Timer
H3 Body Doubling
H3 Virtual Coworking
H2 Recent writing on focus, study, and productivity
H3 What Is Virtual Body Doubling? (And Why It Works Better Than You Think)
H3 Product
H3 Legal

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 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.

Link & Button Quality

1 issue(s) across 16 links and 2 buttons

PASS

1 issue(s) across 16 links and 2 buttons

1 button(s) with no accessible text

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

Got: button.btn (#70 on page)

16 link(s) with descriptive text

16 links

0 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label

17 links and buttons have descriptive text

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

button.btn (#70 on page)

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

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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+

Mobile-Readable Font Sizes

All 80 visible text node(s) render at >= 12 CSS pixels

PASS

All 80 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: FocusLive

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name FocusLive ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name FocusLive Display Mode standalone Theme Color #0f172a Background Color #0f172a 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 A pomodoro timer for…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 See who else is focu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Why	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 works well for repea…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Use	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 when starting is the…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Frequently asked que…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore more	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 pages	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Recent writing on fo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Pomodoro timer for d…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Online study timer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Body doubling for ac…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 What is FocusLive?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Is FocusLive good fo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Do I need an account…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Pomodoro Timer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Study Timer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Body Doubling	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Virtual Coworking	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 94/100 — 2 failing, 21 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
Live `div.flex > a.flex > span.text-base-content > span.text-primary`
Focus Time `section.mx-auto > div.flex > div.flex > button.px-3`
POMODORO TIMER `div.w-full > section.bg-base-100 > div.mx-auto > p.mb-3`
Live `div > h2.text-3xl > span.text-base-content > span.text-primary`
Live `div.max-w-2xl > h2.text-3xl > span.text-base-content > span.text-primary`
Live `div.mx-auto > h2.text-3xl > span.text-base-content > span.text-primary`
FROM THE BLOG `div.mx-auto > div.flex > div > p.text-sm`
NEUROSCIENCE & PRODUCTIVITY `section > div.mx-auto > a.mt-8 > p.text-xs`
Read the article `section > div.mx-auto > a.mt-8 > p.mt-6`
Live `div.flex-1 > a.flex > span.text-base-content > span.text-primary`
Copyright © 2026 - All rights reserved. `div.max-w-7xl > div.flex > div.flex-1 > p.mt-6`

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○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

●Buttons have an accessible name

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

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

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

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

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

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