Skip to content
https://poechallenges.cc

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
24
14 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Warning::
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
BANNER header MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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'>.
Info::
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
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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
Info::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
3 of 86 controls have issues
REVIEW
3 of 86 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <select>
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
Info::
83 control(s) properly labeled
86 controls
83 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#subtask-allflame-6-1numberChart Areas progressaria-label
#challenge-allflame-8numberAtlas Accomplishment progressaria-label
#subtask-allflame-9-1numberDefeat Monsters with Essence progressaria-label
#subtask-allflame-9-2numberOpen Strongboxes progressaria-label
#subtask-allflame-9-3numberActivate Shrines progressaria-label
#subtask-allflame-9-4numberDefeat Possessed Monsters progressaria-label
#subtask-allflame-9-5numberDefeat Rogue Exiles progressaria-label
#subtask-allflame-9-6numberDefeat Rare Beyond Monsters progressaria-label
#subtask-allflame-10-1numberComplete Abysses progressaria-label
#subtask-allflame-10-2numberComplete Expeditions progressaria-label
#subtask-allflame-10-3numberHarvest Plots progressaria-label
#subtask-allflame-10-4numberComplete Legion Encounters progressaria-label
#subtask-allflame-10-5numberOpen Smuggler's Caches progressaria-label
#subtask-allflame-10-6numberPass through Mirrors of Delirium progressaria-label
#subtask-allflame-10-7numberComplete Ultimatum Waves progressaria-label
#subtask-allflame-10-8numberComplete Blights progressaria-label
#subtask-allflame-10-9numberComplete Rituals progressaria-label
#subtask-allflame-10-10numberComplete Ore Deposit Encounters progressaria-label
#subtask-allflame-10-11numberComplete Unstable Breaches or Hives progressaria-label
#subtask-allflame-10-12numberDefeat Mercenaries progressaria-label
#subtask-allflame-11-1numberNiko Missions progressaria-label
#subtask-allflame-11-2numberEinhar Missions progressaria-label
#subtask-allflame-11-3numberJun Missions progressaria-label
#subtask-allflame-11-4numberAlva Missions progressaria-label
#subtask-allflame-12-1numberComplete Voyages progressaria-label
#subtask-allflame-12-2numberDefeat Rare Monsters in Voyages progressaria-label
#subtask-allflame-12-3numberUse Dead Man's Sulphur to craft equipment progressaria-label
#subtask-allflame-13-1numberDefeat Rare or Unique Monsters in level 68 or higher areas while you have an Allied Mercenary progressaria-label
#subtask-allflame-13-2numberClaim items with Infamous Modifiers progressaria-label
#subtask-allflame-13-3numberComplete Maps with Mercenary Scarabs or Warrants applied progressaria-label
#subtask-allflame-13-4numberDefeat Infamous Mercenaries in level 68 or higher areas progressaria-label
#subtask-allflame-14-1numberUse Chromatic Orbs progressaria-label
#challenge-allflame-15numberVanquished Villains progressaria-label
#subtask-allflame-16-1numberAbyssal Depths progressaria-label
#subtask-allflame-16-2numberLogbooks with at least 10 Remnants active progressaria-label
#subtask-allflame-16-3numberTier 4 Harvest Seeds progressaria-label
#subtask-allflame-16-4numberDomains of Timeless Conflict with at least 25 rewards progressaria-label
#subtask-allflame-16-5numberBlueprints with 4 revealed wings progressaria-label
#subtask-allflame-16-6numberSimulacrum Waves progressaria-label
#subtask-allflame-16-7numberFully Completed Ultimatums progressaria-label
#subtask-allflame-16-8numberBlighted or Blight Ravaged Maps progressaria-label
#subtask-allflame-16-9numberAll Rituals in Maps with at least one Blood-filled Vessel applied progressaria-label
#subtask-allflame-16-10numberClaim rewards from Rare Maps successfully completed by your Atlas Runners progressaria-label
#subtask-allflame-16-11numberComplete Hive Fortresses or Defeat Breach Marshals progressaria-label
#subtask-allflame-19-1numberOpen Stacked Decks progressaria-label
#subtask-allflame-19-2numberHand in Divination Card sets progressaria-label
#subtask-allflame-19-3numberComplete Red Tier Maps with at least one Divination Scarab applied progressaria-label
#subtask-allflame-20-1numberUnique Item progressaria-label
#subtask-allflame-20-2numberScarab progressaria-label
#subtask-allflame-20-3numberTier 16 Map progressaria-label
#challenge-allflame-24numberStacked Scarabs progressaria-label
#subtask-allflame-25-1numberLevel Gems to level 20 progressaria-label
#challenge-allflame-27numberSuperior Sovereign progressaria-label
#subtask-allflame-29-1numberTemplar Astrolabe progressaria-label
#subtask-allflame-29-2numberFruiting Astrolabe progressaria-label
#subtask-allflame-29-3numberLightless Astrolabe progressaria-label
#subtask-allflame-29-4numberGrasping Astrolabe progressaria-label
#subtask-allflame-29-5numberNameless Astrolabe progressaria-label
#subtask-allflame-29-6numberFungal Astrolabe progressaria-label
#subtask-allflame-29-7numberChaotic Astrolabe progressaria-label
#subtask-allflame-29-8numberDeceptive Astrolabe progressaria-label
#subtask-allflame-29-9numberTimeless Astrolabe progressaria-label
#subtask-allflame-29-10numberRunic Astrolabe progressaria-label
#challenge-allflame-30numberModified Maps progressaria-label
#subtask-allflame-31-1numberOriginator Influenced Maps progressaria-label
#subtask-allflame-31-2numberCourtyard of Wasting progressaria-label
#subtask-allflame-31-3numberChambers of Impunity progressaria-label
#subtask-allflame-31-4numberTheatre of Lies progressaria-label
#subtask-allflame-33-1numberDefeat Map Bosses after having activated at least 4 Eater of Worlds Altars which have modifiers that affect the Map Boss with Eldritch Gaze allocated progressaria-label
#subtask-allflame-33-2numberDefeat Map Bosses after having activated at least 4 Searing Exarch Altars which have modifiers that affect the Map Boss with Wrath of the Cosmos allocated progressaria-label
#subtask-allflame-33-3numberComplete Maps with at least 150% Item Quantity while they are being witnessed by the Maven while having Destructive Play allocated progressaria-label
#subtask-allflame-34-6numberTainted Currency progressaria-label
#subtask-allflame-34-15numberRunegraft or Tattoo progressaria-label
#subtask-allflame-34-16numberEnshrouding Crystal progressaria-label
#subtask-allflame-34-17numberCatalyst progressaria-label
#subtask-allflame-34-18numberCorrupted Essence progressaria-label
#subtask-allflame-34-19numberBlight Oil progressaria-label
#challenge-allflame-35numberSuccinct Summons progressaria-label
#subtask-allflame-40-2numberCleanse Darkshrines in the Endgame Labyrinth progressaria-label
#subtask-allflame-40-3numberDefeat Pinnacle bosses while the area is level 85 progressaria-label
#subtask-allflame-40-4numberComplete Tier 16 Maps that are Rare and Corrupted with 8 Modifiers progressaria-label
#subtask-allflame-40-5numberComplete Nightmare Maps progressaria-label
#subtask-allflame-40-6numberDefeat Rare Monsters in Voyages that are area level 83 progressaria-label
inputtext(Search...)placeholder only
selectselect(none)none
selectselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select>; <select>

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

Placeholder text disappears on focus and is not a reliable label.

<input type="text">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
Mobile-Readable Font Sizes
99% of visible text renders at >= 12 CSS px (2 below threshold)
REVIEW
99% of visible text renders at >= 12 CSS px (2 below threshold)
Info::
2 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: <button> 10.0px ("Max"); <button> 10.0px ("Max").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title PoE Challenge Tracker Custom Styling Navigation Homepage Link Search Form
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
h1 Challenge Tracker
1.03:1
#000000
on
#050404
needs 3.0:1 (large text)
32px · top of page (header area)
h2 Challenges Completed
1.03:1
#000000
on
#060405
needs 3.0:1 (large text)
24px · above the fold
title PoE Challenge Tracker
1.03:1
#000000
on
#050504
needs 4.5:1 (normal text)
16px · top of page (header area)
option Affliction
1.03:1
#000000
on
#050504
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
option Curse of the Allflame
1.03:1
#000000
on
#050605
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
option Keepers of the Flame
1.03:1
#000000
on
#050504
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
option Mirage
1.04:1
#000000
on
#070604
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
option Necropolis
1.04:1
#000000
on
#070604
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
option Settlers of Kalguur
1.03:1
#000000
on
#060505
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
button Sign in
1.04:1
#000000
on
#070706
needs 4.5:1 (normal text)
16px · above the fold
span / 40
1.04:1
#000000
on
#070606
needs 4.5:1 (normal text)
16px · above the fold
p Next reward at
1.04:1
#000000
on
#070606
needs 4.5:1 (normal text)
16px · above the fold
span Oceanic Weapon Effect
1.03:1
#000000
on
#060505
needs 4.5:1 (normal text)
16px · mid-page
span (12 to go)
1.04:1
#000000
on
#080606
needs 4.5:1 (normal text)
16px · mid-page
span Challenge 1
1.04:1
#000000
on
#070605
needs 4.5:1 (normal text)
16px · mid-page
span Challenge 2
1.04:1
#000000
on
#070605
needs 4.5:1 (normal text)
16px · mid-page
span Challenge 3
1.04:1
#000000
on
#070605
needs 4.5:1 (normal text)
16px · mid-page
span Challenge 4
1.03:1
#000000
on
#060504
needs 4.5:1 (normal text)
16px · mid-page
span Challenge 5
1.04:1
#000000
on
#070605
needs 4.5:1 (normal text)
16px · mid-page
span Challenge 6
1.04:1
#000000
on
#060605
needs 4.5:1 (normal text)
16px · mid-page

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)
ElementRatioRequiredFGBGResult
h1 Challenge Tracker1.03:13.0:1
#000000
#050404
Fail
h2 Challenges Completed1.03:13.0:1
#000000
#060405
Fail
title PoE Challenge Tracke…1.03:14.5:1
#000000
#050504
Fail
option Affliction1.03:14.5:1
#000000
#050504
Fail
option Curse of the Allflam…1.03:14.5:1
#000000
#050605
Fail
option Keepers of the Flame1.03:14.5:1
#000000
#050504
Fail
option Mirage1.04:14.5:1
#000000
#070604
Fail
option Necropolis1.04:14.5:1
#000000
#070604
Fail
option Settlers of Kalguur1.03:14.5:1
#000000
#060505
Fail
button Sign in1.04:14.5:1
#000000
#070706
Fail
span / 401.04:14.5:1
#000000
#070606
Fail
p Next reward at1.04:14.5:1
#000000
#070606
Fail
span Oceanic Weapon Effec…1.03:14.5:1
#000000
#060505
Fail
span (12 to go)1.04:14.5:1
#000000
#080606
Fail
span Challenge 11.04:14.5:1
#000000
#070605
Fail
span Challenge 21.04:14.5:1
#000000
#070605
Fail
span Challenge 31.04:14.5:1
#000000
#070605
Fail
span Challenge 41.03:14.5:1
#000000
#060504
Fail
span Challenge 51.04:14.5:1
#000000
#070605
Fail
span Challenge 61.04:14.5:1
#000000
#060605
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
76 headings, 1 skip(s)
PASS
76 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Challenge Tracker
  • H2 Challenges Completed
  • H4 Subtasks (0/3) skipped
  • H4 Guide
  • H4 Subtasks (0/3)
  • H4 Guide
  • H4 Subtasks (0/4)
  • H4 Guide
  • H4 Subtasks (0/5)
  • H4 Guide
  • H4 Subtasks (0/8)
  • H4 Guide
  • H4 Subtasks (0/3)
  • H4 Guide
  • H4 Subtasks (0/5)
  • H4 Guide
  • H4 Guide
  • H4 Subtasks (0/3)
  • H4 Guide
  • H4 Subtasks (0/5)
  • H4 Guide
  • H4 Subtasks (0/2)
  • H4 Guide
  • H4 Subtasks (0/3)
  • H4 Guide
  • H4 Subtasks (0/3)
  • H4 Guide
  • H4 Subtasks (0/3)
  • H4 Guide
  • H4 Guide
  • H4 Subtasks (0/5)
  • H4 Guide
  • H4 Subtasks (0/9)
  • H4 Guide
  • H4 Subtasks (0/5)
  • H4 Guide
  • H4 Subtasks (0/3)
  • H4 Guide
  • H4 Subtasks (0/3)
  • H4 Guide
  • H4 Subtasks (0/6)
  • H4 Guide
  • H4 Subtasks (0/5)
  • H4 Guide
  • H4 Subtasks (0/15)
  • H4 Guide
  • H4 Guide
  • H4 Subtasks (0/3)
  • H4 Guide
  • H4 Subtasks (0/4)
  • H4 Guide
  • H4 Guide
  • H4 Subtasks (0/7)
  • H4 Guide
  • H4 Subtasks (0/6)
  • H4 Guide
  • H4 Guide
  • H4 Subtasks (0/2)
  • H4 Guide
  • H4 Subtasks (0/9)
  • H4 Guide
  • H4 Subtasks (0/2)
  • H4 Guide
  • H4 Subtasks (0/10)
  • H4 Guide
  • H4 Guide
  • H4 Subtasks (0/6)
  • H4 Guide
  • H4 Subtasks (0/3)
  • H4 Guide
  • H4 Subtasks (0/2)
  • H4 Guide
  • H4 Subtasks (0/5)
  • H4 Guide
  • H4 Subtasks (0/4)
  • H4 Guide

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

A+
Heading Text Quality
All 76 heading(s) have substantive, well-formed text
PASS
All 76 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
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
Info::
Input "Search..." should use type="search" (currently type="text")
Field name "Search..." suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
86 form control(s) checked, no input-semantic issues
PASS
86 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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 92/100 — 3 failing, 22 passed
PASS
92

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.

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
SUBTASKS (0/3) div > div.px-4 > div > h4.text-xs

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Affliction Curse of the Allflame Keepers of the Flame Mirage Necropolis Settler… header.Header-module__hBw1pG__header > div.flex > div.flex > select.appearance-none
Default Difficulty Progress div.ChallengeTracker-module__-SbYza__panel > div.px-4 > div.flex > select.appearance-none

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.cinzel_b99a2233-module__Zreyla__variable html.cinzel_b99a2233-module__Zreyla__variable

These items highlight common accessibility best practices.

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
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
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.
Deprecated ARIA roles were not used
`[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
`<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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.

Send Feedback