Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 8 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.

Homepage link present on 404 page

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 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

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

6 landmarks

REVIEW

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <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

Form Accessibility

2 of 4 controls have issues

REVIEW

2 of 4 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="file">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <textarea>

2 control(s) properly labeled

4 controls

2 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
input	range	Brush	none
input	range	Compare original and stencil	aria-label
textarea	textarea	(e.g. a small swallow carrying a sprig of lavender, fine line)	placeholder only
input	file	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

Why this matters

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

Link & Button Quality

9 issue(s) across 79 links and 61 buttons

REVIEW

9 issue(s) across 79 links and 61 buttons

9 button(s) with no accessible text

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

Got: button.relative (#472 on page); button.relative (#474 on page); button.relative (#476 on page); button.relative (#478 on page); button.relative (#480 on page); button.relative (#482 on page); button.relative (#484 on page); button.relative (#486 on page); button.relative (#488 on page)

79 link(s) with descriptive text

79 links

0 empty

0 generic text

0 new tab

9 empty buttons

Element	Text	Issue	Suggested Fix
<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
<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
<button>	(empty)	empty	Add button text or aria-label

131 links and buttons have descriptive text

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

button.relative (#472 on page); button.relative (#474 on page); button.relative (#476 on page); button.relative (#478 on page); button.relative (#480 on page); button.relative (#482 on page); button.relative (#484 on page); button.relative (#486 on page); button.relative (#488 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

Tap Target Adequacy

Action

6 tap target(s) too small or too close together

REVIEW

6 tap target(s) too small or too close together

6 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

Action

87% of visible text renders at >= 12 CSS px (42 below threshold)

REVIEW

87% of visible text renders at >= 12 CSS px (42 below threshold)

42 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: <span> 11.0px ("New"); <span> 11.0px ("Free"); <span> 11.0px ("On skin"); <span> 11.0px ("Geometric rose mandala"); <span> 11.0px ("Stencil").

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.

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

title AI Tattoo Generator with Try-On & Real-S…

1.15:1

#000000

#16141A

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 AI Tattoo Generator	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 Generate, try on and…	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 Walk into the consul…	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 How the AI tattoo ge…	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 A tattoo design gene…	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 Made for the decisio…	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 AI tattoo, on skin, …	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 TryStencil vs. scree…	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 Built to make your a…	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 Simple pricing: 1 cr…	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 Frequently asked que…	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 Try on your tattoo b…	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 Related tools	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h2 Related articles	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h3 Choose a design	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h3 Fine line butterfly	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h3 Geometric rose manda…	19.44:1	3.0:1	#000000	#F8F6F1	Pass
h3 Crescent moon & star…	19.44:1	3.0:1	#000000	#F8F6F1	Pass
title AI Tattoo Generator …	1.15:1	4.5:1	#000000	#16141A	Fail
span New	19.44:1	4.5:1	#000000	#F8F6F1	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

18 headings

PASS

18 headings

Single H1 present

H1 AI Tattoo Generator — try it on, print a real-size stencil.
H2 Generate, try on and stencil your tattoo — in one tool
H3 Choose a design
H2 Walk into the consult with the size already decided
H2 How the AI tattoo generator works
H2 A tattoo design generator that ends in a real stencil
H2 Made for the decisions that are hard to undo
H2 AI tattoo, on skin, and real-size stencil
H3 Fine line butterfly
H3 Geometric rose mandala
H3 Crescent moon & stars
H2 TryStencil vs. screenshots and guesswork
H2 Built to make your artist’s job easier, not to replace it
H2 Simple pricing: 1 credit per image
H2 Frequently asked questions
H2 Try on your tattoo before it's permanent
H2 Related tools
H2 Related articles

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 37 images OK

PASS

All 37 images OK

2 decorative image(s) correctly marked

35 image(s) with good alt text

37 images 35 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Input Types

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

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

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: TryStencil

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

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

Name TryStencil 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+

Lighthouse Accessibility Audits

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

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Fine line butterfly `div.relative > div.absolute > div.flex > button.h-1.5`
Geometric rose mandala `div.relative > div.absolute > div.flex > button.h-1.5`
Crescent moon & stars `div.relative > div.absolute > div.flex > button.h-1.5`
Minimal wave & sun `div.relative > div.absolute > div.flex > button.h-1.5`
“amor fati” in script `div.relative > div.absolute > div.flex > button.h-1.5`
Fine line swallow with lavender `div.relative > div.absolute > div.flex > button.h-1.5`

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
TRYSTENCIL SCREENSHOTS + GUESSWORK Size on the body Calibrated in cm against … `div.mx-auto > div.overflow-hidden > div.overflow-x-auto > table.w-full`

○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

●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

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

●Background and foreground colors have a sufficient contrast ratio

●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

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

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