Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

10 PASS 7 REVIEW 7 FIX

Landmark Structure

Action

5 landmarks

FIX

5 landmarks

No <main> landmark found

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

5 <nav> landmark(s) found

5 of 5 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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.

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

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

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" name="email" id="email">

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email" id="email">

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

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

5 navigation landmark(s) detected

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 5 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

1 control(s) rely on placeholder only

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

Got: <input type="email" name="email" id="email">

2 controls

0 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#email	email	(Enter your email)	placeholder only
#g-recaptcha-response-100000	textarea	(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

Action

25 issue(s) across 58 links and 13 buttons

REVIEW

25 issue(s) across 58 links and 13 buttons

1 link(s) with no accessible text

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

Got: /

23 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.mofos.com/legal/tos ("TERMS & CONDITIONS"); https://www.mofos.com/legal/privacy ("PRIVACY NOTICE"); https://support.mofos.com/ ("Support"); https://www.mofos.com/legal/tos#cancel ("CANCELLATION POLICY"); https://support.mofos.com/accessibility ("Accessibility"); https://support.mofos.com/legal/anti-trafficking-statement ("Anti-trafficking statement"); https://www.mofos.com/legal/tos ("TERMS & CONDITIONS"); https://www.mofos.com/legal/privacy ("PRIVACY NOTICE"); https://support.mofos.com/ ("Support"); https://www.mofos.com/legal/tos#cancel ("CANCELLATION POLICY") (+13 more)

1 link(s) open in new tab without warning

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

Got: https://www.mofos.com/legal/privacy

1 button(s) with no accessible text

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

Got: button.sc-hknOHE (#58 on page)

33 link(s) with descriptive text

58 links

1 empty

23 generic text

1 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
https://www.mofos.com/legal/tos	link	generic text	Replace with descriptive text
Before: link Suggested: Tos
https://www.mofos.com/legal/privacy	link	generic text	Replace with descriptive text
Before: link Suggested: Privacy
https://support.mofos.com/	link	generic text	Replace with descriptive text
Before: link Suggested: Home page
https://www.mofos.com/legal/tos#cancel	link	generic text	Replace with descriptive text
Before: link Suggested: Tos#Cancel
https://support.mofos.com/accessibility	link	generic text	Replace with descriptive text
Before: link Suggested: Accessibility
https://support.mofos.com/legal/anti-tra…	link	generic text	Replace with descriptive text
Before: link Suggested: Anti Trafficking Statement
https://www.mofos.com/legal/tos	link	generic text	Replace with descriptive text
Before: link Suggested: Tos
https://www.mofos.com/legal/privacy	link	generic text	Replace with descriptive text
Before: link Suggested: Privacy
https://support.mofos.com/	link	generic text	Replace with descriptive text
Before: link Suggested: Home page
https://www.mofos.com/legal/tos#cancel	link	generic text	Replace with descriptive text
Before: link Suggested: Tos#Cancel
https://support.mofos.com/accessibility	link	generic text	Replace with descriptive text
Before: link Suggested: Accessibility
https://support.mofos.com/legal/anti-tra…	link	generic text	Replace with descriptive text
Before: link Suggested: Anti Trafficking Statement
https://support.mofos.com/accessibility	link	generic text	Replace with descriptive text
Before: link Suggested: Accessibility
https://support.mofos.com/legal/anti-tra…	link	generic text	Replace with descriptive text
Before: link Suggested: Anti Trafficking Statement
https://support.mofos.com/accessibility	link	generic text	Replace with descriptive text
Before: link Suggested: Accessibility
https://support.mofos.com/legal/anti-tra…	link	generic text	Replace with descriptive text
Before: link Suggested: Anti Trafficking Statement
https://www.mofos.com/legal/2257	link	generic text	Replace with descriptive text
Before: link Suggested: 2257
https://secure.vend-o.com/customers/prof…	link	generic text	Replace with descriptive text
Before: link Suggested: Login
https://cs.segpay.com/	link	generic text	Replace with descriptive text
Before: link Suggested: Home page
http://probiller.com	link	generic text	Replace with descriptive text
Before: link Suggested: Probiller.Com
https://site-ma.mofos.com/login	link	generic text	Replace with descriptive text
Before: link Suggested: Login
https://www.mofos.com/legal/tos	link	generic text	Replace with descriptive text
Before: link Suggested: Tos
https://www.google.com/	link	generic text	Replace with descriptive text
Before: link Suggested: Home page
https://www.mofos.com/legal/privacy	Privacy Notice	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

45 links and buttons have descriptive text

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

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

Generic link text like 'click here' doesn't describe the destination.

https://www.mofos.com/legal/tos ("TERMS & CONDITIONS"); https://www.mofos.com/legal/privacy ("PRIVACY NOTICE"); https://support.mofos.com/ ("Support"); https://www.mofos.com/legal/tos#cancel ("CANCELLATION POLICY"); https://support.mofos.com/accessibility ("Accessibility"); https://support.mofos.com/legal/anti-trafficking-statement ("Anti-trafficking statement"); https://www.mofos.com/legal/tos ("TERMS & CONDITIONS"); https://www.mofos.com/legal/privacy ("PRIVACY NOTICE"); https://support.mofos.com/ ("Support"); https://www.mofos.com/legal/tos#cancel ("CANCELLATION POLICY") (+13 more)

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.mofos.com/legal/privacy

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.sc-hknOHE (#58 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

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

REVIEW

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

1 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

82% of visible text renders at >= 12 CSS px (64 below threshold)

REVIEW

82% of visible text renders at >= 12 CSS px (64 below threshold)

64 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: <a> 11.0px ("MEMBER LOGIN"); <a> 11.0px ("JOIN NOW"); <span> 11.2px ("lpi"); <span> 11.2px ("lpi"); <span> 11.2px ("dbm").

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Back To Top ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 9 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 LATEST MOFOS VIDEOS	6.06:1	3.0:1	#000000	#908887	Pass
h2 LET'S POST IT	5.84:1	3.0:1	#000000	#8B8684	Pass
h2 HE'S GOT RIZZ	6.19:1	3.0:1	#000000	#8D8B8A	Pass
h2 I KNOW THAT GIRL	7.92:1	3.0:1	#000000	#9F9F9D	Pass
h2 Don’t Break Me	7.92:1	3.0:1	#000000	#9F9F9D	Pass
h2 Top Rated Videos	7.92:1	3.0:1	#000000	#9F9F9D	Pass
title Mofos.com \| The Worl…	8.32:1	4.5:1	#000000	#A9A29A	Pass
label Hamburger menu open	8.15:1	4.5:1	#000000	#A8A099	Pass
a MEMBER LOGIN	7.77:1	4.5:1	#000000	#A49C96	Pass
a JOIN NOW	7.41:1	4.5:1	#000000	#A09893	Pass
a VIDEOS	7.03:1	4.5:1	#000000	#9B948F	Pass
a GIRLS	6.60:1	4.5:1	#000000	#968F8B	Pass
a CHANNELS	6.27:1	4.5:1	#000000	#928B88	Pass
a CATEGORIES	6.02:1	4.5:1	#000000	#8E8886	Pass
a MEMBER LOGIN	5.94:1	4.5:1	#000000	#8D8785	Pass
span SAVE 69% OFF	5.94:1	4.5:1	#000000	#8D8785	Pass
span THE ENTIRE YEAR	5.96:1	4.5:1	#000000	#8E8786	Pass
a JOIN NOW	5.98:1	4.5:1	#000000	#8F8786	Pass
a View All	5.98:1	4.5:1	#000000	#8F8786	Pass
span MOFOS CHANNELS	5.95:1	4.5:1	#000000	#8E8785	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 80/100 — 6 failing, 23 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#MobileHeader_57188648263 > div#ContainerAlignment_3631450193 > div.sc-bbSZdi > button.sc-hknOHE `div#MobileHeader_57188648263 > div#ContainerAlignment_3631450193 > div.sc-bbSZdi > button.sc-hknOHE`

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.sc-yo7o1v-0 > div#MobileHeader_57188648263 > div#ContainerAlignment_35374005354 > a#Logo_30007000780 `div.sc-yo7o1v-0 > div#MobileHeader_57188648263 > div#ContainerAlignment_35374005354 > a#Logo_30007000780`

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
Join Now `div.sc-y3rqay-0 > div.sc-1dhvf0w-0 > div.sc-1dhvf0w-1 > a.sc-3byr16-0`
Exit `div.sc-y3rqay-0 > div.sc-y3rqay-1 > div.sc-rkkkdv-0 > a.sc-3byr16-0`

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
Previous `div.sc-1deoyo3-0 > div.sc-15y43vd-0 > div.sc-rnnlw8-0 > button.flickity-button`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
TERMS & CONDITIONS `nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3`
PRIVACY NOTICE `nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3`
SUPPORT `nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3`
CANCELLATION POLICY `nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3`
ACCESSIBILITY `nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3`
ANTI-TRAFFICKING STATEMENT `nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3`
ACCESSIBILITY `nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3`
ANTI-TRAFFICKING STATEMENT `nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3`
here `div.sc-c12nx1-0 > div.sc-qq931q-0 > p.sc-hq7nt5-0 > a`
Vendo `div.sc-c12nx1-0 > div.sc-qq931q-0 > p.sc-hq7nt5-0 > a`
Segpay `div.sc-c12nx1-0 > div.sc-qq931q-0 > p.sc-hq7nt5-0 > a`
Probiller `div.sc-1p82nyv-0 > div.sc-1p82nyv-1 > p.sc-hq7nt5-0 > a`
Login `div.sc-y3rqay-0 > div.sc-1dhvf0w-0 > div.sc-1dhvf0w-1 > a.sc-3byr16-0`
Terms and Conditions `div.sc-y3rqay-1 > div.sc-1eyb95j-0 > p.sc-1eyb95j-1 > a`
Exit `div.sc-y3rqay-0 > div.sc-y3rqay-1 > div.sc-rkkkdv-0 > a.sc-3byr16-0`

○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

●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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

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

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

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

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

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

6 headings

PASS

6 headings

Single H1 present

H1 LATEST MOFOS VIDEOS
H2 LET'S POST IT
H2 HE'S GOT RIZZ
H2 I KNOW THAT GIRL
H2 Don’t Break Me
H2 Top Rated Videos

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

4 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: 4 all-caps heading(s)

A+

Alt Text Quality

All 16 images OK

PASS

All 16 images OK

1 decorative image(s) correctly marked

15 image(s) with good alt text

16 images 15 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Input Types

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

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

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

PASS

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

No tabindex anti-patterns detected

Iframe Accessibility

1/2 iframe(s) missing title; 0 placeholder(s)

PASS

1/2 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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.