Skip to content
https://appeal.org.uk

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
8
REVIEW
5
PASS
11
INFO
0
Checks
24
11 PASS 5 REVIEW 8 FIX
D
Tabindex Anti-Patterns
Action
0 positive, 17 -1-on-focusable
FIX
0 positive, 17 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
D
Iframe Accessibility
Action
6/6 iframe(s) missing title; 0 placeholder(s)
FIX
6/6 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://open.spotify.com/embed/episode/4loCp94eQ3gibzk0e8kS4Q?utm_source=genera…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://cdn.yoshki.com/iframe/55849r.html")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://cdn.yoshki.com/iframe/55849r.html")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
D
Tap Target Adequacy
Action
11 tap target(s) too small or too close together
FIX
11 tap target(s) too small or too close together
Warning::
11 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-8y2ndy
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.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://appeal.org.uk/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://appeal.org.uk/manifest.json

Manifest contains invalid JSON.

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 ✗
B
Alt Text Quality
1 of 13 images have issues
REVIEW
1 of 13 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
8 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
13 images 4 good alt text 8 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

C
Mobile-Readable Font Sizes
Action
86% of visible text renders at >= 12 CSS px (14 below threshold)
REVIEW
86% of visible text renders at >= 12 CSS px (14 below threshold)
Warning::
14 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: <p> 10.0px ("APPEAL is the working name of the Centre..."); <strong> 10.0px ("Registered Charity Number:"); <p> 10.0px ("1144162 |"); <strong> 10.0px ("SRA Authorisation Number:"); <p> 10.0px ("621184 |").
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Navigation UX
Action
3 navigation pattern(s)
REVIEW
3 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 8 pass AA only
a Partners & Funding
1.29:1
#000000
on
#231F20
needs 4.5:1 (normal text)
16px · above the fold
a Careers
1.29:1
#000000
on
#231F20
needs 4.5:1 (normal text)
16px · above the fold
a What We Do
1.29:1
#000000
on
#231F20
needs 4.5:1 (normal text)
16px · above the fold
a Wrongful Convictions
1.29:1
#000000
on
#231F20
needs 4.5:1 (normal text)
16px · above the fold
a Racial Justice
1.29:1
#000000
on
#231F20
needs 4.5:1 (normal text)
16px · above the fold
a Women’s Justice
1.29:1
#000000
on
#231F20
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Archives4.27:13.0:1
#000000
#E20613
Pass
h2 Categories4.27:13.0:1
#000000
#E20613
Pass
h3 Surviving Injustice4.27:13.0:1
#000000
#E20613
Pass
h3 Seventeen Years: The…4.27:13.0:1
#000000
#E20613
Pass
h3 Shadow Worlds - Stol…4.27:13.0:1
#000000
#E20613
Pass
h3 Surviving Injustice4.27:13.0:1
#000000
#E20613
Pass
h3 Seventeen Years: The…4.27:13.0:1
#000000
#E20613
Pass
title Home Page • APPEAL21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
span Menu21.00:14.5:1
#000000
#FFFFFF
Pass
a Who We Are21.00:14.5:1
#000000
#FFFFFF
Pass
a About Us21.00:14.5:1
#000000
#FFFFFF
Pass
a Our Team21.00:14.5:1
#000000
#FFFFFF
Pass
a Reports, Briefings &…4.85:14.5:1
#000000
#7B7979
Pass
a Partners & Funding1.29:14.5:1
#000000
#231F20
Fail
a Careers1.29:14.5:1
#000000
#231F20
Fail
a What We Do1.29:14.5:1
#000000
#231F20
Fail
a Wrongful Convictions1.29:14.5:1
#000000
#231F20
Fail
a Racial Justice1.29:14.5:1
#000000
#231F20
Fail
a Women’s Justice1.29:14.5:1
#000000
#231F20
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+
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Header Menu" SEARCH MAIN ASIDE CONTENTINFO footer
A+
Heading Hierarchy
19 headings
PASS
19 headings
Info::
Single H1 present
  • H2 ✍️ Add your name to support fair compensation for the wrongfully convicted.
  • H2 ✍️ Add your name to support fair compensation for the wrongfully convicted.
  • H1 We fight wrongful convictions and demand a fair justice system
  • H2 Three More Ridgewell Cases Under Review
  • H2 Trew’s Law Event
  • H2 The Accused: Eddie Gilfoyle
  • H2 Desert Island Judgments: R v Hayes; R v Palombo
  • H2 CALA/APPEAL Conference – November 2026
  • H2 Seeking Justice: A guide to criminal appeals for women
  • H2 Get Help
  • H2 The Wrong Man
  • H2 Listen
  • H3 Surviving Injustice
  • H3 Seventeen Years: The Andrew Malkinson Story
  • H3 Shadow Worlds - Stolen Years
  • H3 Surviving Injustice
  • H3 Seventeen Years: The Andrew Malkinson Story
  • H2 Archives
  • H2 Categories
A+
Heading Text Quality
All 19 heading(s) have substantive, well-formed text
PASS
All 19 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">
Info::
2 control(s) properly labeled
3 controls
2 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
ssearchSearch inputaria-label
ssearchSearch inputaria-label
ssearch(Search)placeholder only

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

<input type="search" name="s">

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

A+
Form Input Types
3 form control(s) checked, no type mismatches
PASS
3 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 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+
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 90/100 — 3 failing, 25 passed
PASS
90

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.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.fl-slide-content > div.fl-slide-text > p > iframe div.fl-slide-content > div.fl-slide-text > p > iframe
div.fl-html > div > div > iframe div.fl-html > div > div > iframe
div.fl-html > div > div > iframe div.fl-html > div > div > iframe

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a
div.fl-module-content > div.fl-icon-group > span.fl-icon > a div.fl-module-content > div.fl-icon-group > span.fl-icon > a

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Seventeen Years: The Andrew Malkinson StoryListen below to the incredible story… div.bx-controls > div.bx-pager > div.bx-pager-item > button.bx-pager-link
Shadow Worlds - Stolen YearsHow can a victim of a traumatic crime appear to be … div.bx-controls > div.bx-pager > div.bx-pager-item > button.bx-pager-link
Surviving InjusticeUntold stories from the wrongfully convicted. A podcast from… div.bx-controls > div.bx-pager > div.bx-pager-item > button.bx-pager-link
Media Enquiries div.fl-module-content > div.fl-rich-text > p > a
Subscribe to Newsletter div.fl-module-content > div.fl-rich-text > p > a
Get Legal Help  div.fl-module-content > div.fl-rich-text > p > a
Complaints Policy div.fl-module-content > div.fl-rich-text > p > a
Media Enquiries div.fl-module-content > div.fl-rich-text > p > a
Subscribe to Newsletter div.fl-module-content > div.fl-rich-text > p > a
Get Legal Help  div.fl-module-content > div.fl-rich-text > p > a
Complaints Policy div.fl-module-content > div.fl-rich-text > p > a

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
●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
●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
●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
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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 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
○`<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.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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