https://though-threatened-trains-station.trycloudflare.com

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 1 REVIEW 7 FIX

Mobile-Readable Font Sizes

Action

56% of visible text renders at >= 12 CSS px (45 below threshold)

FIX

56% of visible text renders at >= 12 CSS px (45 below threshold)

45 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: <div> 11.0px ("Categories"); <span> 10.0px ("#1"); <span> 9.6px ("ANIME"); <span> 10.0px ("#2"); <span> 9.6px ("ANIME").

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

✗ favicon.ico Missing

✓ 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

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.

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.

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

3 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

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Heading Hierarchy

27 headings

REVIEW

27 headings

No H1 heading found

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

H2 🏆 Top 10 Today
H2 🎬 Latest Releases
H3 LIAR GAME
H3 Grand Blue Dreaming Season 3
H3 Oh Boy, Was I Wrong About Her
H3 A Livid Lady’s Guide to Getting Even: How I Crushed My Homeland with My Mighty Grimoires
H3 The World Is Dancing
H3 Skeleton Knight in Another World Season 2
H3 The Insipid Prince's Furtive Grab for the Throne
H3 Love Unseen Beneath the Clear Night Sky
H3 Attack on Titan
H3 Tomb Raider King
H3 Horimiya: The Missing Pieces
H3 Horimiya
H3 Sparks of Tomorrow
H3 Anime AzurLane: Slow Ahead! Season 2
H3 The Birth of Kitaro: The Mystery of GeGeGe
H3 ONE PIECE HEROINES
H3 Though I Am an Inept Villainess
H3 Goodbye, Lara
H3 Mushoku Tensei: Jobless Reincarnation Season 3
H3 The Classroom of the Black Cat and a Witch
H3 The 100 Girlfriends Who Really, Really, Really, Really, REALLY Love You Season 3
H3 The World's Strongest Rearguard
H3 Iron Wok Jan!
H3 You and I Are Polar Opposites
H3 No results found

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

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

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

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 24 images OK

PASS

All 24 images OK

24 image(s) with good alt text

24 images 24 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#searchInput	search	Search all titles	aria-label

A+

Link & Button Quality

8 links, 13 buttons — all OK

PASS

8 links, 13 buttons — all OK

8 link(s) with descriptive text

8 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

21 links and buttons have descriptive text

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

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

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

PASS

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

No tabindex anti-patterns detected

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+

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.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Top 10 Today	12.10:1	3.0:1	#000000	#A2CFB2	Pass
h2 Latest Releases	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 LIAR GAME	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 Grand Blue Dreaming …	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 Oh Boy, Was I Wrong …	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 A Livid Lady’s Gui…	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 The World Is Dancing	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 Skeleton Knight in A…	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 The Insipid Prince's…	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 Love Unseen Beneath …	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 Attack on Titan	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 Tomb Raider King	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 Horimiya: The Missin…	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 Horimiya	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 Sparks of Tomorrow	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 Anime AzurLane: Slow…	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 The Birth of Kitaro:…	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 ONE PIECE HEROINES	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 Though I Am an Inept…	12.62:1	3.0:1	#000000	#99D6B3	Pass
h3 Goodbye, Lara	12.62:1	3.0:1	#000000	#99D6B3	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.

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 26 passed

PASS

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.

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
anime `main#mainContent > div.category-pills-wrapper > div#categoryPills > div.category-pill`
donghua `main#mainContent > div.category-pills-wrapper > div#categoryPills > div.category-pill`
movie `main#mainContent > div.category-pills-wrapper > div#categoryPills > div.category-pill`
news `main#mainContent > div.category-pills-wrapper > div#categoryPills > div.category-pill`
series `main#mainContent > div.category-pills-wrapper > div#categoryPills > div.category-pill`
🏆 Top 10 Today `main#mainContent > section.content-section > div.row-header > h2.section-title`
#4 `div.top10-card > div.top10-info > div.top10-meta > span.top10-rank`
#5 `div.top10-card > div.top10-info > div.top10-meta > span.top10-rank`
#6 `div.top10-card > div.top10-info > div.top10-meta > span.top10-rank`
#7 `div.top10-card > div.top10-info > div.top10-meta > span.top10-rank`
#8 `div.top10-card > div.top10-info > div.top10-meta > span.top10-rank`
#9 `div.top10-card > div.top10-info > div.top10-meta > span.top10-rank`
#10 `div.top10-card > div.top10-info > div.top10-meta > span.top10-rank`
🎬 Latest Releases `main#mainContent > section#contentSection > div.row-header > h2#sectionTitle`
··· `section#contentSection > div#pagination > div#pageNumbers > button.page-btn`
34 `section#contentSection > div#pagination > div#pageNumbers > button.page-btn`
Showing 1–24 of 800 titles `main#mainContent > section#contentSection > div#pagination > div#paginationInfo`
Contact `body > footer.footer > nav.footer-links > a`
DMCA `body > footer.footer > nav.footer-links > a`
Terms `body > footer.footer > nav.footer-links > a`
© 2026 HORIZON `body > footer.footer > p.footer-copy`

These are opportunities to improve the legibility of your content.

○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

●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

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

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

●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 have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

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

○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

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

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