Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ 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

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

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) 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

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA

h2 🔒 LEAVENWORTH NET ปลอดภั�…

1.32:1

#1F2937

#323C4C

needs 3.0:1 (large text)

24px · mid-page

h2 🛡️ ระบบความปล�…

1.38:1

#1F2937

#353F4F

needs 3.0:1 (large text)

24px · mid-page · over background image/gradient

h2 🔓 ปลดล็อครางว�…

1.10:1

#FFFFFF

#F3F4F6

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h3 ล็อคข้อมูล

1.11:1

#FFFFFF

#F2F3F5

needs 3.0:1 (large text)

19px · bottom of viewport · over background image/gradient

h3 Firewall

1.10:1

#FFFFFF

#F3F4F6

needs 3.0:1 (large text)

19px · bottom of viewport · over background image/gradient

h3 🔒 โปรวันนี้

1.10:1

#FFFFFF

#F3F4F6

needs 3.0:1 (large text)

19px · bottom of viewport · over background image/gradient

h3 LEAVENWORTH NET

1.00:1

#F3F4F6

needs 3.0:1 (large text)

19px · bottom of viewport · over background image/gradient

title LEAVENWORTH NET คาสิโนออ…

2.78:1

#000000

#4B5563

needs 4.5:1 (normal text)

16px · top of page (header area)

a 🏠 หน้าแรก

2.78:1

#000000

#4B5563

needs 4.5:1 (normal text)

16px · top of page (header area)

a 🔓 สมัคร

2.78:1

#000000

#4B5563

needs 4.5:1 (normal text)

16px · top of page (header area)

6 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)

Element	Ratio	Required	FG	BG	Result
h1 🔒 LEAVENWORTH NET…	11.25:1	3.0:1	#F3F4F6	#2B3544	Pass
h2 🔒 LEAVENWORTH NET…	1.32:1	3.0:1	#1F2937	#323C4C	Fail
h2 🛡️ ระบบ…	1.38:1	3.0:1	#1F2937	#353F4F	Fail
h2 🎰 สล็อต…	13.34:1	3.0:1	#1F2937	#F3F4F6	Pass
h2 🃏 บาคาร…	13.34:1	3.0:1	#1F2937	#F3F4F6	Pass
h2 ⚽ แทงบอ�…	13.34:1	3.0:1	#1F2937	#F3F4F6	Pass
h2 🔓 ปลดล็…	1.10:1	3.0:1	#FFFFFF	#F3F4F6	Fail
h3 SSL 256 bit	10.32:1	3.0:1	#FFFFFF	#374150	Pass
h3 ล็อคข้�…	1.11:1	3.0:1	#FFFFFF	#F2F3F5	Fail
h3 Firewall	1.10:1	3.0:1	#FFFFFF	#F3F4F6	Fail
h3 🎲 หวยปล…	13.34:1	3.0:1	#1F2937	#F3F4F6	Pass
h3 🎯 โป๊กเ…	13.34:1	3.0:1	#1F2937	#F3F4F6	Pass
h3 🔒 โปรวั…	1.10:1	3.0:1	#FFFFFF	#F3F4F6	Fail
h3 🔐 ระดับ…	13.34:1	3.0:1	#1F2937	#F3F4F6	Pass
h3 🔗 พาร์ท…	13.34:1	3.0:1	#1F2937	#F3F4F6	Pass
h3 ⭐ จุดเด�…	13.34:1	3.0:1	#1F2937	#F3F4F6	Pass
h3 LEAVENWORTH NET	1.00:1	3.0:1	#F3F4F6	#F3F4F6	Fail
title LEAVENWORTH NET ค�…	2.78:1	4.5:1	#000000	#4B5563	Fail
a 🏠 หน้าแ…	2.78:1	4.5:1	#000000	#4B5563	Fail
a 🔓 สมัคร	2.78:1	4.5:1	#000000	#4B5563	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.

A+

Heading Hierarchy

20 headings

PASS

20 headings

Single H1 present

H1 🔒 LEAVENWORTH NET 🔐
H2 🔒 LEAVENWORTH NET ปลอดภัยที่สุด
H2 🛡️ ระบบความปลอดภัย
H3 SSL 256 bit
H3 ล็อคข้อมูล
H3 Firewall
H2 🎰 สล็อตปลอดภัย
H2 🃏 บาคาร่าปลอดภัย
H2 ⚽ แทงบอลปลอดภัย
H3 🎲 หวยปลอดภัย
H3 🎯 โป๊กเกอร์ปลอดภัย
H3 🔒 โปรวันนี้
H4 ระบบล็อค
H4 กำแพงเหล็ก
H4 ทางออก
H3 🔐 ระดับความปลอดภัย
H3 🔗 พาร์ทเนอร์
H3 ⭐ จุดเด่น
H2 🔓 ปลดล็อครางวัล! 🔑
H3 LEAVENWORTH NET

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

10 links, 0 buttons — all OK

PASS

10 links, 0 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://hilo641.com; https://slot888x.com

8 link(s) with descriptive text

10 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://hilo641.com	ไฮโลไทย	new tab	Add '(opens in new tab)' to text
https://slot888x.com	สล็อต888	new tab	Add '(opens in new tab)' to text

8 links and buttons have descriptive text

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

https://hilo641.com; https://slot888x.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

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 11 passed

PASS

100

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.

○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-hidden="true"]` is not present on the document `<body>`

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○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 use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

○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

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

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

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