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 4 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No 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

No contentinfo (footer) 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Link & Button Quality

Action

10 issue(s) across 39 links and 3 buttons

FIX

10 issue(s) across 39 links and 3 buttons

7 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /tour; /join; /join; /tour; https://twitter.com/SlayherJax; https://www.instagram.com/el_gran_jax/; https://onlyfans.com/jaxslayher

3 link(s) open in new tab without warning

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

Got: https://epoch.com/; https://www.rtalabel.org/; https://epoch.com/

3 button(s) with no accessible text

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

Got: button.hamburger (#23 on page); button.choice_theme (#48 on page); button.btn (#55 on page)

29 link(s) with descriptive text

39 links

7 empty

0 generic text

3 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
/tour	(empty)	empty	Add link text or aria-label
/join	(empty)	empty	Add link text or aria-label
/join	(empty)	empty	Add link text or aria-label
/tour	(empty)	empty	Add link text or aria-label
https://epoch.com/	EPOCH	new tab	Add '(opens in new tab)' to text
https://www.rtalabel.org/	RTA Restrict	new tab	Add '(opens in new tab)' to text
https://epoch.com/	EPOCH	new tab	Add '(opens in new tab)' to text
https://twitter.com/SlayherJax	(empty)	empty	Add link text or aria-label
https://www.instagram.com/el_gran_jax/	(empty)	empty	Add link text or aria-label
https://onlyfans.com/jaxslayher	(empty)	empty	Add link 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

29 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/tour; /join; /join; /tour; https://twitter.com/SlayherJax; https://www.instagram.com/el_gran_jax/; https://onlyfans.com/jaxslayher

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://epoch.com/; https://www.rtalabel.org/; https://epoch.com/

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

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

button.hamburger (#23 on page); button.choice_theme (#48 on page); button.btn (#55 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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-sodd0m

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://jaxslayher.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://jaxslayher.com/manifest.json

Manifest contains invalid JSON.

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 ✗

Heading Hierarchy

4 headings

REVIEW

4 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H3 CUSTOMER SERVICE
H3 Info
H3 BILLING
H3 FOLLOW US

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h3 CUSTOMER SERVICE

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

h3 Info

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

h3 BILLING

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 FOLLOW US

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

title SFW Tour | JaxSlayher.com

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Videos

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Models

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Login

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Login

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Get Access

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Get Access

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div All models appearing on this website are…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a EPOCH

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div , our authorized sales agents.

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a 18 U.S.C. 2257 and 2257A Record-Keeping …

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div 2026

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

a CONTACT & SUPPORT

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 CUSTOMER SERVICE	1.00:1	3.0:1	#000000	#000000	Fail
h3 Info	1.00:1	3.0:1	#000000	#000000	Fail
h3 BILLING	1.00:1	3.0:1	#000000	#000000	Fail
h3 FOLLOW US	1.00:1	3.0:1	#000000	#000000	Fail
title SFW Tour \| JaxSlayhe…	1.00:1	4.5:1	#000000	#000000	Fail
a Home	1.00:1	4.5:1	#000000	#000000	Fail
a Videos	1.00:1	4.5:1	#000000	#000000	Fail
a Models	1.00:1	4.5:1	#000000	#000000	Fail
a Login	1.00:1	4.5:1	#000000	#000000	Fail
span Login	1.00:1	4.5:1	#000000	#000000	Fail
span Get Access	1.00:1	4.5:1	#000000	#000000	Fail
span Get Access	1.00:1	4.5:1	#000000	#000000	Fail
div All models appearing…	1.00:1	4.5:1	#000000	#000000	Fail
a EPOCH	1.00:1	4.5:1	#000000	#000000	Fail
div , our authorized sal…	1.00:1	4.5:1	#000000	#000000	Fail
a 18 U.S.C. 2257 and 2…	1.00:1	4.5:1	#000000	#000000	Fail
div Copyright ©	1.00:1	4.5:1	#000000	#000000	Fail
div 2026	1.00:1	4.5:1	#000000	#000000	Fail
div JaxSlayher.com All R…	1.00:1	4.5:1	#000000	#000000	Fail
a CONTACT & SUPPORT	1.00:1	4.5:1	#000000	#000000	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.

Lighthouse Accessibility Audits

Score 84/100 — 4 failing, 20 passed

REVIEW

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.wrapper > div.header > div.holder > button.hamburger `div.wrapper > div.header > div.holder > button.hamburger`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header > div.holder > div.logo > a `div.header > div.holder > div.logo > a`
div.main > div.sfw-tour > div.sfw-item > a `div.main > div.sfw-tour > div.sfw-item > a`
div.main > div.sfw-tour > div.sfw-item > a `div.main > div.sfw-tour > div.sfw-item > a`
div.holder > div.col > div.logo > a `div.holder > div.col > div.logo > a`
div.col > ul.list > li.item > a `div.col > ul.list > li.item > a`
div.col > ul.list > li.item > a `div.col > ul.list > li.item > a`
div.col > ul.list > li.item > a `div.col > ul.list > li.item > a`

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. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
EPOCH `div.col > div.description > div.row > a`
18 U.S.C. 2257 and 2257A Record-Keeping Requirements Compliance Statement `div.col > div.description > div.row > a`

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

●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

●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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○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

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

3 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 3 all-caps heading(s)

A+

Alt Text Quality

All 15 images OK

PASS

All 15 images OK

15 image(s) with good alt text

15 images 15 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	(Search...)	placeholder only

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

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "Search..." should use type="search" (currently type="text")

Field name "Search..." suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

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

PASS

1 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

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 20 visible text node(s) render at >= 12 CSS pixels

PASS

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

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

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.

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