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 3 REVIEW 5 FIX

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

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

7 landmarks

REVIEW

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

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

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

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

h1 Una página para ver anime en sincronía…

1.04:1

#000000

#060606

needs 3.0:1 (large text)

32px · above the fold

h2 ¿Cómo funciona?

1.04:1

#000000

#060606

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Novedades

1.04:1

#000000

#060606

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Entra en una sala

1.04:1

#000000

#060606

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Disfruta del directo

1.04:1

#000000

#060606

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Personaliza tu experiencia

1.04:1

#000000

#060606

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Chats a tu elección

1.04:1

#000000

#060606

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Puntos y medallas

1.04:1

#000000

#060606

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Perfiles de la comunidad

1.04:1

#000000

#060606

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Información de los animes

1.04:1

#000000

#060606

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Repeticiones y suscripciones

1.04:1

#000000

#060606

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Colores y foto de perfil

1.04:1

#000000

#060606

needs 3.0:1 (large text)

19px · bottom of viewport

title ANIMELIVES — Ver anime en directo con …

1.04:1

#000000

#060606

needs 4.5:1 (normal text)

16px · top of page (header area)

a ANIME

1.04:1

#000000

#060606

needs 4.5:1 (normal text)

16px · top of page (header area)

span LIVES

1.04:1

#000000

#060606

needs 4.5:1 (normal text)

16px · top of page (header area)

a 🏆 Ranking

1.04:1

#000000

#060606

needs 4.5:1 (normal text)

16px · top of page (header area)

a Comparativa

1.04:1

#000000

#060606

needs 4.5:1 (normal text)

16px · above the fold

a Beneficios

1.04:1

#000000

#060606

needs 4.5:1 (normal text)

16px · above the fold

a Login

1.04:1

#000000

#060606

needs 4.5:1 (normal text)

16px · above the fold

a Administrador

1.04:1

#000000

#060606

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Una página para ver…	1.04:1	3.0:1	#000000	#060606	Fail
h2 ¿Cómo funciona?	1.04:1	3.0:1	#000000	#060606	Fail
h2 Novedades	1.04:1	3.0:1	#000000	#060606	Fail
h3 Entra en una sala	1.04:1	3.0:1	#000000	#060606	Fail
h3 Disfruta del directo	1.04:1	3.0:1	#000000	#060606	Fail
h3 Personaliza tu exper…	1.04:1	3.0:1	#000000	#060606	Fail
h3 Chats a tu elección	1.04:1	3.0:1	#000000	#060606	Fail
h3 Puntos y medallas	1.04:1	3.0:1	#000000	#060606	Fail
h3 Perfiles de la comun…	1.04:1	3.0:1	#000000	#060606	Fail
h3 Información de los …	1.04:1	3.0:1	#000000	#060606	Fail
h3 Repeticiones y suscr…	1.04:1	3.0:1	#000000	#060606	Fail
h3 Colores y foto de pe…	1.04:1	3.0:1	#000000	#060606	Fail
title ANIMELIVES — Ver a…	1.04:1	4.5:1	#000000	#060606	Fail
a ANIME	1.04:1	4.5:1	#000000	#060606	Fail
span LIVES	1.04:1	4.5:1	#000000	#060606	Fail
a 🏆 Ranking	1.04:1	4.5:1	#000000	#060606	Fail
a Comparativa	1.04:1	4.5:1	#000000	#060606	Fail
a Beneficios	1.04:1	4.5:1	#000000	#060606	Fail
a Login	1.04:1	4.5:1	#000000	#060606	Fail
a Administrador	1.04:1	4.5:1	#000000	#060606	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

12 headings

PASS

12 headings

Single H1 present

H1 Una página para ver anime en sincronía con tu streamer, con chat y cámara en un mismo lugar.
H2 ¿Cómo funciona?
H3 Entra en una sala
H3 Disfruta del directo
H3 Personaliza tu experiencia
H2 Novedades
H3 Chats a tu elección
H3 Puntos y medallas
H3 Perfiles de la comunidad
H3 Información de los animes
H3 Repeticiones y suscripciones
H3 Colores y foto de perfil

A+

Heading Text Quality

All 12 heading(s) have substantive, well-formed text

PASS

All 12 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	range	Volumen de ejemplo	aria-label
input	input	Mensaje de ejemplo	aria-label

Link & Button Quality

11 links, 12 buttons — all OK

PASS

11 links, 12 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://discord.gg/VxVxzn6Ctd; https://discord.gg/VxVxzn6Ctd

9 link(s) with descriptive text

11 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://discord.gg/VxVxzn6Ctd	Discord	new tab	Add '(opens in new tab)' to text
https://discord.gg/VxVxzn6Ctd	Discord	new tab	Add '(opens in new tab)' to text

21 links and buttons have descriptive text

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

https://discord.gg/VxVxzn6Ctd; https://discord.gg/VxVxzn6Ctd

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+

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+

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 "es"

PASS

Lang attribute set to "es"

<html lang="es"> is set and valid

Got: es

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+

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

PASS

All 88 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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 21 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.

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
ES `div.flex > div.inline-flex > div.inline-flex > button#radix-_R_b5aq_`

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

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

●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

●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

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

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

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

○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

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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