Accessibility

F

Heading Hierarchy

Action

32 headings, 4 skip(s)

FIX

32 headings, 4 skip(s)

Multiple H1 headings (3 found)

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

Heading level skipped: H1 → H5 (missing H2)

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

Heading level skipped: H1 → H5 (missing H2)

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

Heading level skipped: H1 → H5 (missing H2)

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

Heading level skipped: H2 → H5 (missing H3)

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

H1 0
H5 4K/HD XXX Movies skipped
H1 0 + duplicate H1
H5 Hot Models skipped
H1 0 + duplicate H1
H5 Exclusive Updates Per Month skipped
H2 New Updates
H2 Coming Soon
H2 Behind The Scenes
H2 Plans to Suit Everyone
H2 What is Pornworld
H2 Why Should I Join?
H2 Member Benefits
H2 Popular Models
H3 Veronica Leal
H3 Cherry Kiss
H3 Coco Lovelock
H3 Kelly Oliveira
H2 What’s Hot! Always Fresh!
H2 Top Busty Models
H3 Chloe Lamour
H3 Angel Wicky
H3 Jennifer Mendez
H3 Hazel Moore
H2 Martina Smeraldi
H2 Behind The Scenes
H5 PORNWORLD skipped
H5 ABOUT US
H5 MOVIES
H5 HELP
H5 Contact us
H2 Website for adults viewing only!

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

D

404 Error Page

Action

HTTP 400, custom page

FIX

HTTP 400, custom page

Unexpected status code: HTTP 400

Expected HTTP 404 but received 400. This may confuse search engine crawlers.

Got: HTTP 400

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 400 ✗Page Title Page not found - PornWorld ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

F

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #000000

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 ModePartial Dark Mode

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

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

No navigation patterns

FIX

No navigation patterns

1 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

Search

Skip Link

Labeled Navigation 1 <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.

C

Link & Button Quality

Action

28 issue(s) across 160 links and 12 buttons

REVIEW

28 issue(s) across 160 links and 12 buttons

27 link(s) with no accessible text

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

Got: https://pornbox.com/signin; https://pornbox.com/landing/pornworld?aff=d91fc58c8dc4a73cZqLbKe91eqDrq-soNJq…; https://pornbox.com/landing/pornworld?aff=d91fc58c8dc4a73cZqLbKe91eqDrq-soNJq…; https://pornbox.com/landing/pornworld?aff=d91fc58c8dc4a73cZqLbKe91eqDrq-soNJq…; https://pornbox.com/landing/pornworld?aff=d91fc58c8dc4a73cZqLbKe91eqDrq-soNJq…; https://pornbox.com/landing/pornworld?aff=d91fc58c8dc4a73cZqLbKe91eqDrq-soNJq…; https://pornbox.com/landing/pornworld?aff=d91fc58c8dc4a73cZqLbKe91eqDrq-soNJq…; /bts; /bts; /bts (+17 more)

1 link(s) with generic text

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

Got: /notice2257 ("Click here")

2 link(s) open in new tab without warning

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

Got: https://www.pornworld-live.com/in/?tour=grq0&campaign=Eau58&track=pw1_menu; https://pornbox.com/landing/pornworld

130 link(s) with descriptive text

160 links

27 empty

1 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://pornbox.com/signin	(empty)	empty	Add link text or aria-label
https://www.pornworld-live.com/in/?tour=…	Live	new tab	Add '(opens in new tab)' to text
https://pornbox.com/landing/pornworld?af…	(empty)	empty	Add link text or aria-label
https://pornbox.com/landing/pornworld?af…	(empty)	empty	Add link text or aria-label
https://pornbox.com/landing/pornworld?af…	(empty)	empty	Add link text or aria-label
https://pornbox.com/landing/pornworld?af…	(empty)	empty	Add link text or aria-label
https://pornbox.com/landing/pornworld?af…	(empty)	empty	Add link text or aria-label
https://pornbox.com/landing/pornworld?af…	(empty)	empty	Add link text or aria-label
/bts	(empty)	empty	Add link text or aria-label
/bts	(empty)	empty	Add link text or aria-label
/bts	(empty)	empty	Add link text or aria-label
/bts	(empty)	empty	Add link text or aria-label
https://pornbox.com/landing/pornworld?af…	(empty)	empty	Add link text or aria-label
https://pornbox.com/landing/pornworld	GET ACCESS NOW	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://pornbox.com/landing/pornworld?af…	(empty)	empty	Add link text or aria-label
/notice2257	Click here	generic text	Replace with descriptive text
Before: Click here Suggested: Notice2257

142 links and buttons have descriptive text

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

https://pornbox.com/signin; https://pornbox.com/landing/pornworld?aff=d91fc58c8dc4a73cZqLbKe91eqDrq-soNJq…; https://pornbox.com/landing/pornworld?aff=d91fc58c8dc4a73cZqLbKe91eqDrq-soNJq…; https://pornbox.com/landing/pornworld?aff=d91fc58c8dc4a73cZqLbKe91eqDrq-soNJq…; https://pornbox.com/landing/pornworld?aff=d91fc58c8dc4a73cZqLbKe91eqDrq-soNJq…; https://pornbox.com/landing/pornworld?aff=d91fc58c8dc4a73cZqLbKe91eqDrq-soNJq…; https://pornbox.com/landing/pornworld?aff=d91fc58c8dc4a73cZqLbKe91eqDrq-soNJq…; /bts; /bts; /bts (+17 more)

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.

/notice2257 ("Click here")

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.pornworld-live.com/in/?tour=grq0&campaign=Eau58&track=pw1_menu; https://pornbox.com/landing/pornworld

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

B

Iframe Accessibility

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

REVIEW

2/3 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.

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.

C

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

h2 Soon

1.06:1

#000000

on

#090A09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Scenes

1.06:1

#000000

on

#090A09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 to Suit …

1.06:1

#000000

on

#090A09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 is Pornworld

1.06:1

#000000

on

#090A09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Should I …

1.06:1

#000000

on

#090A09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Benefits

1.06:1

#000000

on

#090A09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Models

1.06:1

#000000

on

#090A09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Busty Models

1.06:1

#000000

on

#090A09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Martina Smeraldi

1.06:1

#000000

on

#090A09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Scenes

1.06:1

#000000

on

#090A09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Website for adults viewing only!

1.06:1

#000000

on

#090A09

needs 3.0:1 (large text)

24px · bottom of viewport

title World Class Hardcore Porn - PornWorld

1.16:1

#000000

on

#0B1908

needs 4.5:1 (normal text)

16px · top of page (header area)

a JOIN

1.28:1

#000000

on

#222013

needs 4.5:1 (normal text)

16px · top of page (header area)

a Scenes

1.31:1

#000000

on

#2E1E17

needs 4.5:1 (normal text)

16px · top of page (header area)

a Updates

1.31:1

#000000

on

#2D1E17

needs 4.5:1 (normal text)

16px · top of page (header area)

a Coming Soon

1.61:1

#000000

on

#412C21

needs 4.5:1 (normal text)

16px · above the fold

a Most Popular

1.91:1

#000000

on

#533527

needs 4.5:1 (normal text)

16px · above the fold

a Models

1.93:1

#000000

on

#563527

needs 4.5:1 (normal text)

16px · above the fold

a Tags

1.77:1

#000000

on

#4E3023

needs 4.5:1 (normal text)

16px · above the fold

a Backstage

1.59:1

#000000

on

#45291F

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Soon	1.06:1	3.0:1	#000000	#090A09	Fail
h2 The …	1.06:1	3.0:1	#000000	#090A09	Fail
h2 to …	1.06:1	3.0:1	#000000	#090A09	Fail
h2 is …	1.06:1	3.0:1	#000000	#090A09	Fail
h2 Should …	1.06:1	3.0:1	#000000	#090A09	Fail
h2 Benefits	1.06:1	3.0:1	#000000	#090A09	Fail
h2 Models	1.06:1	3.0:1	#000000	#090A09	Fail
h2 Busty …	1.06:1	3.0:1	#000000	#090A09	Fail
h2 Martina Smeraldi	1.06:1	3.0:1	#000000	#090A09	Fail
h2 The …	1.06:1	3.0:1	#000000	#090A09	Fail
h2 Website for adults v…	1.06:1	3.0:1	#000000	#090A09	Fail
title World Class Hardcore…	1.16:1	4.5:1	#000000	#0B1908	Fail
a JOIN	1.28:1	4.5:1	#000000	#222013	Fail
a Scenes	1.31:1	4.5:1	#000000	#2E1E17	Fail
a Updates	1.31:1	4.5:1	#000000	#2D1E17	Fail
a Coming Soon	1.61:1	4.5:1	#000000	#412C21	Fail
a Most Popular	1.91:1	4.5:1	#000000	#533527	Fail
a Models	1.93:1	4.5:1	#000000	#563527	Fail
a Tags	1.77:1	4.5:1	#000000	#4E3023	Fail
a Backstage	1.59:1	4.5:1	#000000	#45291F	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 87/100 — 4 failing, 23 passed

REVIEW

87

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
JOIN `header > nav.navbar > div.container-fluid > a.btn`
BROWSE MORE VIDEOS `section.gallery > div.pagination-block > div.d-flex > a.btn`
VIEW MORE BTS `section.gallery > div.pagination-block > div.d-flex > a.btn`
CHOOSE PLAN `main.main-container > div.subscription-plans > div.d-flex > a#subscriptionPlanSelector`
SHOW MORE POPULAR MODELS `section.gallery > div.pagination-block > div.d-flex > a.btn`
GET ACCESS NOW `div.row > div.col-lg-6 > div.d-flex > a.btn`
SHOW ALL BUSTY MODELS `section.gallery > div.pagination-block > div.d-flex > a.btn`
SEE ALL MODELS `div.row > div.col-lg-4 > div.d-flex > a.btn`
VIEW MORE BTS `section.gallery > div.pagination-block > div.d-flex > a.btn`
Continue with age verification `div#agego-prompt-actions > button#agego-cta-verify > div.agego-u-left > span#agego-cta-verify-label`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.agego-blur-content > div.row > div.col > iframe `body.agego-blur-content > div.row > div.col > iframe`

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
header > nav.navbar > div.container-fluid > a.login-link `header > nav.navbar > div.container-fluid > a.login-link`
div#homeCarousel > div.carousel-inner > div.carousel-item > a.sexcash-track `div#homeCarousel > div.carousel-inner > div.carousel-item > a.sexcash-track`
body.agego-blur-content > main.main-container > div.responsive-banner > a.sexcash-track `body.agego-blur-content > main.main-container > div.responsive-banner > a.sexcash-track`
section.gallery > div.row > article.card > a.thumbnail `section.gallery > div.row > article.card > a.thumbnail`
section.gallery > div.row > article.card > a.thumbnail `section.gallery > div.row > article.card > a.thumbnail`
section.gallery > div.row > article.card > a.thumbnail `section.gallery > div.row > article.card > a.thumbnail`
section.gallery > div.row > article.card > a.thumbnail `section.gallery > div.row > article.card > a.thumbnail`
body.agego-blur-content > main.main-container > div.responsive-banner > a.sexcash-track `body.agego-blur-content > main.main-container > div.responsive-banner > a.sexcash-track`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi `div.video-embed > div.video-overlay > div.video-overlay-hover > a.bi`
body.agego-blur-content > main.main-container > div.responsive-banner > a.sexcash-track `body.agego-blur-content > main.main-container > div.responsive-banner > a.sexcash-track`

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.

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
4K/HD XXX Movies `main.main-container > div.stats-counter > div.column > h5.title`
Hot Models `main.main-container > div.stats-counter > div.column > h5.title`
Exclusive Updates Per Month `main.main-container > div.stats-counter > div.column > h5.title`
PORNWORLD `footer > div.row > div.col > h5.footer-row-title`

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○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

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

○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

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

A

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H1: "0"

Got: 1 ≤2-char heading(s)

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

1 of 42 images have issues

PASS

1 of 42 images have issues

1 image(s) with generic alt text

1 image(s) with alt text over 125 characters

12 decorative image(s) correctly marked

28 image(s) with good alt text

42 images 28 good alt text 12 decorative 1 generic

Issue	Count
generic	1 image(s)
too long	1 image(s)

A

Form Accessibility

1 of 5 controls have issues

PASS

1 of 5 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">

4 control(s) properly labeled

5 controls

4 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
contact[name]	text	name	aria-label
contact[email]	text	email	aria-label
contact[message]	textarea	message	aria-label
#langSwitcher	select		none
#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

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 "contact[email]" should use type="email" (currently type="text")

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

A+

Form Input Quality

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

PASS

5 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-GB"

PASS

Lang attribute set to "en-GB"

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

Got: en-GB

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+

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

PASS

All 153 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

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.