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 2 REVIEW 6 FIX

Mobile-Readable Font Sizes

Action

38% of visible text renders at >= 12 CSS px (293 below threshold)

FIX

38% of visible text renders at >= 12 CSS px (293 below threshold)

293 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: <span> 10.0px ("01"); <span> 10.0px ("02"); <span> 10.0px ("03"); <span> 10.0px ("04"); <span> 10.0px ("05").

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-likgvu

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://arklaystudio.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://arklaystudio.com/manifest.json

Manifest contains invalid JSON.

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: #07080a

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.

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.

Mobile Keyboard & Autofill

Action

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

REVIEW

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

2 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: tel, email.

Got: <input type="tel" name="telefono" id=":r0:-telefono">, <input type="email" name="email" id=":r0:-email">

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 Páginas que trabajan

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

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

h1 mientras tú

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

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

h1 Páginas que trabajan

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

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

h1 mientras tú

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

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

h2 Tu negocio lleva años.

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Tu página,

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Una página que genera

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Cada sitio,

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 un giro distinto.

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Del primer mensaje

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 al sitio en vivo.

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Todo incluido,

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 en cada plan.

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Qué cambia cuando tienes

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 un sitio que trabaja.

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Menos mensajes sin respuesta.

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Cómo queda

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 en tu negocio.

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 En marcha

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

h2 en tres pasos.

1.08:1

#000000

#070E09

needs 3.0:1 (large text)

24px · bottom of viewport

4 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 Páginas que trabaja…	1.08:1	3.0:1	#000000	#070E09	Fail
h1 mientras tú	1.08:1	3.0:1	#000000	#070E09	Fail
h1 Páginas que trabaja…	1.08:1	3.0:1	#000000	#070E09	Fail
h1 mientras tú	1.08:1	3.0:1	#000000	#070E09	Fail
h2 Tu negocio lleva añ…	1.08:1	3.0:1	#000000	#070E09	Fail
h2 Tu página,	1.08:1	3.0:1	#000000	#070E09	Fail
h2 Una página que gene…	1.08:1	3.0:1	#000000	#070E09	Fail
h2 Cada sitio,	1.08:1	3.0:1	#000000	#070E09	Fail
h2 un giro distinto.	1.08:1	3.0:1	#000000	#070E09	Fail
h2 Del primer mensaje	1.08:1	3.0:1	#000000	#070E09	Fail
h2 al sitio en vivo.	1.08:1	3.0:1	#000000	#070E09	Fail
h2 Todo incluido,	1.08:1	3.0:1	#000000	#070E09	Fail
h2 en cada plan.	1.08:1	3.0:1	#000000	#070E09	Fail
h2 Qué cambia cuando t…	1.08:1	3.0:1	#000000	#070E09	Fail
h2 un sitio que trabaja…	1.08:1	3.0:1	#000000	#070E09	Fail
h2 Menos mensajes sin r…	1.08:1	3.0:1	#000000	#070E09	Fail
h2 Cómo queda	1.08:1	3.0:1	#000000	#070E09	Fail
h2 en tu negocio.	1.08:1	3.0:1	#000000	#070E09	Fail
h2 En marcha	1.08:1	3.0:1	#000000	#070E09	Fail
h2 en tres pasos.	1.08:1	3.0:1	#000000	#070E09	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.

Landmark Structure

5 landmarks

PASS

5 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

Heading Hierarchy

41 headings

PASS

41 headings

Multiple H1 headings (2 found)

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

H1 Páginas que trabajanmientras tú atiendes.
H1 Páginas que trabajanmientras tú atiendes. duplicate H1
H2 Tu negocio lleva años.Tu página, unos minutos en Google.
H2 Una página que genera contactos reales.
H2 Cada sitio,un giro distinto.
H3 Lumière
H3 Clínica Dental
H3 Despacho Jurídico
H3 ForjaGym
H3 Desarrollo Residencial
H2 Del primer mensajeal sitio en vivo.
H3 Nos escribes
H3 Propuesta en 24 horas
H3 Diseño y construcción
H3 Sale al aire
H2 Todo incluido,en cada plan.
H2 Qué cambia cuando tienesun sitio que trabaja.
H3 Más confianza
H3 Mejor imagen
H3 Más contactos
H3 Ventas en línea
H3 Procesos eficientes
H2 Menos mensajes sin respuesta. Más citas cumplidas.
H3 Respuesta inmediata
H3 Citas que se reservan solas
H3 Cada interesado registrado
H3 Solo ves lo que importa
H2 Cómo quedaen tu negocio.
H3 Consultorio
H2 En marchaen tres pasos.
H3 Diagnóstico gratuito
H3 Flujo a medida
H3 Activo desde el día uno
H2 El sitio correctopara donde estás.
H3 Que te encuentreny te escriban.
H3 Que te conozcanantes de escribirte.
H3 Que reserven, compreny paguen solos.
H3 Que te encuentreny te escriban.
H3 Que te conozcanantes de escribirte.
H3 Que reserven, compreny paguen solos.
H2 Platícanos.

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

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 23 images OK

PASS

All 23 images OK

21 decorative image(s) correctly marked

2 image(s) with good alt text

23 images 2 good alt text 21 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 6 controls labeled

PASS

All 6 controls labeled

6 control(s) properly labeled

6 controls

6 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#:r0:-nombre	text	Tu nombre*	for/id
#:r0:-telefono	tel	Teléfono*	for/id
#:r0:-negocio	text	Nombre del negocio*	for/id
#:r0:-email	email	Email	for/id
#:r0:-servicio	select	¿Qué te interesa?*	for/id
#:r0:-mensaje	textarea	Cuéntanos más	for/id

Link & Button Quality

46 links, 20 buttons — all OK

PASS

46 links, 20 buttons — all OK

8 link(s) open in new tab without warning

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

Got: https://wa.me/525620605414?text=Hola%2C%20quiero%20cotizar%20una%20p%C3%A1gin…; https://wa.me/525620605414?text=Hola%2C%20quiero%20cotizar%20una%20p%C3%A1gin…; https://wa.me/525620605414?text=Hola%2C%20quiero%20cotizar%20una%20p%C3%A1gin…; https://wa.me/525620605414; https://wa.me/525620605414; https://wa.me/525620605414; https://www.instagram.com/arklaystudio?igsh=ZnBhb3EwdGZsaGwy&utm_source=qr; https://wa.me/525620605414?text=Hola%2C%20quiero%20cotizar%20una%20p%C3%A1gin…

38 link(s) with descriptive text

46 links

0 empty

0 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/525620605414?text=Hola%2C%…	Cotizar por WhatsApp	new tab	Add '(opens in new tab)' to text
https://wa.me/525620605414?text=Hola%2C%…	Cotiza por WhatsApp	new tab	Add '(opens in new tab)' to text
https://wa.me/525620605414?text=Hola%2C%…	Cotiza por WhatsApp	new tab	Add '(opens in new tab)' to text
https://wa.me/525620605414	Hablemos por WhatsApp	new tab	Add '(opens in new tab)' to text
https://wa.me/525620605414	WhatsApp directo	new tab	Add '(opens in new tab)' to text
https://wa.me/525620605414	WhatsApp	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/arklaystudio?i…	Instagram	new tab	Add '(opens in new tab)' to text
https://wa.me/525620605414?text=Hola%2C%…	Cotiza por WhatsApp	new tab	Add '(opens in new tab)' to text

58 links and buttons have descriptive text

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

https://wa.me/525620605414?text=Hola%2C%20quiero%20cotizar%20una%20p%C3%A1gin…; https://wa.me/525620605414?text=Hola%2C%20quiero%20cotizar%20una%20p%C3%A1gin…; https://wa.me/525620605414?text=Hola%2C%20quiero%20cotizar%20una%20p%C3%A1gin…; https://wa.me/525620605414; https://wa.me/525620605414; https://wa.me/525620605414; https://www.instagram.com/arklaystudio?igsh=ZnBhb3EwdGZsaGwy&utm_source=qr; https://wa.me/525620605414?text=Hola%2C%20quiero%20cotizar%20una%20p%C3%A1gin…

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

6 form control(s) checked, no type mismatches

PASS

6 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Document Language

Lang attribute set to "es"

PASS

Lang attribute set to "es"

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

Got: es

Tabindex Anti-Patterns

0 positive, 2 -1-on-focusable

PASS

0 positive, 2 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

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+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: https://fonts.googleapis.com/css2?family=Plus+Jakarta+Sans:ital,wght@0,400;0,500;0,600;0,700;0,800;1,400&family=JetBrains+Mono:wght@400&display=swap

Print Stylesheet ✓ Print Optimized

Print stylesheet https://fonts.googleapis.com/css2?family=Plus+Jakarta+Sans:ital,wght@0,400;0,500;0,600;0,700;0,800;1,400&family=JetBrains+Mono:wght@400&display=swap ✓Inline @media print Not detected ✗

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

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

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 30 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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
01 Demos 02 Proceso 03 Automatización 04 Precios 05 Cotizar Cotizar por WhatsAp… `div#root > header.fixed > div.relative > div#nav-dropdown`

These are opportunities to improve the usage of ARIA in your application which 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
Cotiza por WhatsApp `div > div > div > a.btn-primary`
lumiere.mx `div > div > div > div`
lumiere.mx `div > div > div > span`
pacientes `div > div > div > div`
Invisalign · brackets `div > div > div > div`
02 `main#main-content > section#demos > div.max-w-layout > button.tap-highlight-none`
03 `main#main-content > section#demos > div.max-w-layout > button.tap-highlight-none`
04 `main#main-content > section#demos > div.max-w-layout > button.tap-highlight-none`
05 `main#main-content > section#demos > div.max-w-layout > button.tap-highlight-none`
Aguascalientes, México. `div.max-w-layout > div.flex > div > p.text-sm`
Empezar proyecto `div.bg-surface/40 > div.max-w-layout > div.flex > a.inline-flex`
Demos `div.max-w-layout > div.flex > div.flex > a.text-[12px]`
Proceso `div.max-w-layout > div.flex > div.flex > a.text-[12px]`
Automatización `div.max-w-layout > div.flex > div.flex > a.text-[12px]`
Precios `div.max-w-layout > div.flex > div.flex > a.text-[12px]`
Cotizar `div.max-w-layout > div.flex > div.flex > a.text-[12px]`
WhatsApp `div.max-w-layout > div.flex > div.flex > a.text-[12px]`
Instagram `div.max-w-layout > div.flex > div.flex > a.text-[12px]`
Privacidad `div.max-w-layout > div.flex > div.flex > a.text-[12px]`
Cookies `div.max-w-layout > div.flex > div.flex > a.text-[12px]`
Aviso Legal `div.max-w-layout > div.flex > div.flex > a.text-[12px]`
© 2026 Arklay Studio `div.max-w-layout > div.flex > div.flex > span.text-[11px]`
Privacidad `div.fixed > div.max-w-layout > div.flex > a.text-xs`
Entendido `div.fixed > div.max-w-layout > div.flex > button.inline-flex`

These are opportunities to improve the legibility of your content.

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
01 `main#main-content > section#demos > div.max-w-layout > button.tap-highlight-none`
02 `main#main-content > section#demos > div.max-w-layout > button.tap-highlight-none`
03 `main#main-content > section#demos > div.max-w-layout > button.tap-highlight-none`
04 `main#main-content > section#demos > div.max-w-layout > button.tap-highlight-none`
05 `main#main-content > section#demos > div.max-w-layout > button.tap-highlight-none`

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

●Select elements have associated label elements.

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

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Links have a discernible name

●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

●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

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

○`[accesskey]` values are unique

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○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

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