Skip to content
https://patreon.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
F
Heading Hierarchy
Action
32 headings, 10 skip(s)
FIX
32 headings, 10 skip(s)
Warning::
Multiple H1 headings (8 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Creators
  • H3 Features
  • H3 Pricing
  • H3 Resources
  • H1 Where podcasts grow
  • H3 Ellis Ever After is building a family podcasting empire skipped
  • H1 Your wildest creative reality duplicate H1
  • H3 Jade Novah is fusing her loves of music, writing, and comedy skipped
  • H1 Your newsletter Your rules duplicate H1
  • H3 Anne Helen Petersen is exploring how we shape — and are shaped by — culture. skipped
  • H1 Make it making art duplicate H1
  • H3 RossDraws is creating, sharing, and teaching the art of worldbuilding skipped
  • H1 From you to your crew duplicate H1
  • H3 Elliott Wilson is building community around hip-hop journalism skipped
  • H1 Your house Your rules duplicate H1
  • H3 Rachel Maksy is creating a space for vlogs, makeup transformations, and whimsy skipped
  • H1 Creator is now a career duplicate H1
  • H3 Tim Chantarangsu is dropping podcast episodes and spitting fire skipped
  • H1 Speak volumes duplicate H1
  • H3 Real Ones is diving deep into the biggest issues of our time skipped
  • H2 Creativity poweredby fandom
  • H4 "Patreon provides a space for artists to sustain ourselves by connecting us directly to our own communities." skipped
  • H3 KAMAUU
  • H2 Complete creative control
  • H2 Creators. Fans. Nothing in between.
  • H2 Turning passions into businesses
  • H4 More ways to earn skipped
  • H4 Unlock growth
  • H4 Your world to create
  • H2 Choose your language
  • H2 Choose your region
  • H2 Choose your currency

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
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.
B
Form Accessibility
2 of 5 controls have issues
REVIEW
2 of 5 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search">; <input type="search">
Info::
3 control(s) properly labeled
5 controls
3 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
selectselectSelect Languagearia-label
selectselectSelect your regionaria-label
selectselectSelect your regionaria-label
inputsearch(Find a Creator)placeholder only
inputsearch(Find a Creator)placeholder only

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

<input type="search">; <input type="search">

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not found | Patreon ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Patreon
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Patreon ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Patreon Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA 1 pass AA only
h2 Choose your language
1.08:1
#000000
on
#0E0C0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Choose your region
1.08:1
#000000
on
#0E0C0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Choose your currency
1.08:1
#000000
on
#0E0C0A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Creators
1.08:1
#000000
on
#0E0C0A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Features
1.08:1
#000000
on
#0E0C0A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Pricing
1.08:1
#000000
on
#0E0C0A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Resources
1.08:1
#000000
on
#0E0C0A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 KAMAUU
1.08:1
#000000
on
#0E0C0A
needs 3.0:1 (large text)
19px · bottom of viewport
title Where Creator Communities Thrive — Pat…
1.87:1
#000000
on
#642820
needs 4.5:1 (normal text)
16px · top of page (header area)
span Skip to content
1.55:1
#000000
on
#591613
needs 4.5:1 (normal text)
16px · top of page (header area)
span Creators
2.39:1
#000000
on
#822F28
needs 4.5:1 (normal text)
16px · top of page (header area)
span Features
3.89:1
#000000
on
#A3543C
needs 4.5:1 (normal text)
16px · top of page (header area)
span Pricing
3.57:1
#000000
on
#835B4D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Resources
2.33:1
#000000
on
#564542
needs 4.5:1 (normal text)
16px · above the fold
label Find a Creator
3.73:1
#000000
on
#6E665F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Close
1.51:1
#000000
on
#312B28
needs 4.5:1 (normal text)
16px · above the fold
span Log in
1.91:1
#000000
on
#423B38
needs 4.5:1 (normal text)
16px · above the fold

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Choose your language1.08:13.0:1
#000000
#0E0C0A
Fail
h2 Choose your region1.08:13.0:1
#000000
#0E0C0A
Fail
h2 Choose your currency1.08:13.0:1
#000000
#0E0C0A
Fail
h3 Creators1.08:13.0:1
#000000
#0E0C0A
Fail
h3 Features1.08:13.0:1
#000000
#0E0C0A
Fail
h3 Pricing1.08:13.0:1
#000000
#0E0C0A
Fail
h3 Resources1.08:13.0:1
#000000
#0E0C0A
Fail
h3 KAMAUU1.08:13.0:1
#000000
#0E0C0A
Fail
title Where Creator Commun…1.87:14.5:1
#000000
#642820
Fail
span Skip to content1.55:14.5:1
#000000
#591613
Fail
span Creators2.39:14.5:1
#000000
#822F28
Fail
span Features3.89:14.5:1
#000000
#A3543C
Fail
span Pricing3.57:14.5:1
#000000
#835B4D
Fail
span Resources2.33:14.5:1
#000000
#564542
Fail
span Updates13.00:14.5:1
#000000
#DEC7BC
Pass
span Open menu7.40:14.5:1
#000000
#E17F5E
Pass
span Patreon6.04:14.5:1
#000000
#97858A
Pass
label Find a Creator3.73:14.5:1
#000000
#6E665F
Fail
span Close1.51:14.5:1
#000000
#312B28
Fail
span Log in1.91:14.5:1
#000000
#423B38
Fail

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.

B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 24 passed
REVIEW
89

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
div.sc-fc3e0d65-0 > div.container-inner > div.sc-135cb999-0 > button.sc-135cb999-11 div.sc-fc3e0d65-0 > div.container-inner > div.sc-135cb999-0 > button.sc-135cb999-11
div.sc-fc3e0d65-0 > div.container-inner > div.sc-135cb999-0 > button.sc-135cb999-12 div.sc-fc3e0d65-0 > div.container-inner > div.sc-135cb999-0 > button.sc-135cb999-12

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
Already have an account? Log in div.sc-3de513f2-2 > div.text-editor > div.sc-13c2a112-0 > p.sc-4dda64df-0

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Jade Novah is fusing her loves of music, writing, and comedy a.sc-b4b575fb-0 > div.sc-135cb999-8 > div.sc-135cb999-9 > h3
"Patreon provides a space for artists to sustain ourselves by connecting us dir… div.container-inner > div > div.sc-a4630065-0 > h4.sc-e8472d59-0
More ways to earn div.sc-13f794b9-6 > div.sc-13f794b9-5 > div.sc-13c2a112-0 > h4.sc-e8472d59-0

These are opportunities to improve keyboard navigation in your application.

○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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[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
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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
○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.
A
Landmark Structure
17 landmarks
PASS
17 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

A+
Alt Text Quality
All 36 images OK
PASS
All 36 images OK
Info::
3 decorative image(s) correctly marked
Info::
33 image(s) with good alt text
36 images 33 good alt text 3 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback