Skip to content
https://securelist.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
44
GRADE
F
FIX
7
REVIEW
6
PASS
0
INFO
0
Checks
13
6 REVIEW 7 FIX
D
Landmark Structure
Action
48 landmarks
FIX
48 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 NAV 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

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

F
Heading Hierarchy
Action
35 headings, 6 skip(s)
FIX
35 headings, 6 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Securelist by Kaspersky
  • H6 Other solutions skipped
  • H6 Other Industries
  • H6 Other Products
  • H6 Other Services
  • H3 Lotus Wiper: a new threat targeting the energy and utilities sector
  • H3 FakeWallet crypto stealer spreading through iOS apps in the App Store
  • H3 Adapt or pay: an analysis of the AdaptixC2 framework
  • H3 CPU-Z / HWMonitor watering hole infection – a copy-pasted attack
  • H3 Threat landscape for industrial automation systems in Q4 2025
  • H3 JanelaRAT: a financial threat targeting users in Latin America
  • H3 The long road to your crypto: ClipBanker and its marathon infection chain
  • H3 Financial cyberthreats in 2025 and the outlook for 2026
  • H5 Threats skipped
  • H5 Latest Posts
  • H3 A laughing RAT: CrystalX combines spyware, stealer, and prankware features
  • H3 An AI gateway designed to steal your data
  • H3 Coruna: the framework used in Operation Triangulation
  • H3 Anatomy of a Cyber World Global Report 2026
  • H5 Webinars skipped
  • H3 SOC: Build, buy, or hybrid?
  • H3 Inside the dark web job market: Their talent, our threat
  • H3 Hunt Hub: Opening the black box of EDR detection
  • H3 Signal in the noise. What 2025 hacktivism reveals about the modern threat landscape
  • H5 Categories skipped
  • H3 The SOC Files: Time to “Sapecar”. Unpacking a new Horabot campaign in Mexico
  • H3 Free real estate: GoPix, the banking Trojan living off your memory
  • H3 BeatBanker: A dual‑mode Android Trojan
  • H3 Kaspersky Security Bulletin 2025. Statistics
  • H5 Reports skipped
  • H3 HoneyMyte updates CoolClient and deploys multiple stealers in recent campaigns
  • H3 The HoneyMyte APT evolves with a kernel-mode rootkit and a ToneShell backdoor
  • H3 Evasive Panda APT poisons DNS requests to deliver MgBot
  • H3 Cloud Atlas activity in the first half of 2025: what changed
  • H5 Subscribe to our weekly e-mails skipped

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

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

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

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

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

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

F
Alt Text Quality
Action
26 of 47 images have issues
FIX
26 of 47 images have issues
Critical::
26 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
26 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
20 decorative image(s) correctly marked
47 images 20 decorative 26 missing
IssueCount
missing26 image(s)
too long1 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

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::
3 navigation landmark(s) detected
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 3 <nav> element(s)
Back to Top
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.
B
Form Accessibility
2 of 5 controls have issues
REVIEW
2 of 5 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">; <input type="text" name="s">
Info::
3 control(s) properly labeled
5 controls
3 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#input_3505043192_1emailEmail(Required)for/id
#choice_3505043192_11_2_1checkboxI agree to provide my email address to “AO Kaspersky Lab” to receive information about new posts on the site. I understand that I can withdraw this consent at any time via e-mail by clicking the “unsubscribe” link that I find at the bottom of any e-mail sent to me for the purposes mentioned above.for/id
ak_hp_textareatextareaΔnone
stext(Search...)placeholder only
stext(Search...)placeholder only

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

<input type="text" name="s">; <input type="text" 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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | Securelist ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
11 icon(s) detected
REVIEW
11 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA 1 pass AA only
a Home Products
1.33:1
#000000
on
#052821
needs 4.5:1 (normal text)
16px · top of page (header area)
a Small Business 1-50 employees
1.36:1
#000000
on
#042A26
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Medium Business 51-999 employees
2.09:1
#000000
on
#134A44
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Enterprise 1000+ employees
1.48:1
#000000
on
#10302C
needs 4.5:1 (normal text)
16px · above the fold

2 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 Securelist by Kasper…3.04:13.0:1
#000000
#3B615A
Pass
title Securelist | Kaspers…21.00:14.5:1
#000000
#FFFFFF
Pass
p Solutions for:10.21:14.5:1
#000000
#A3B9BB
Pass
a Home Products1.33:14.5:1
#000000
#052821
Fail
a Small Business 1-50 …1.36:14.5:1
#000000
#042A26
Fail
a Medium Business 51-9…2.09:14.5:1
#000000
#134A44
Fail
a Enterprise 1000+ emp…1.48:14.5:1
#000000
#10302C
Fail
span by Kaspersky8.78:14.5:1
#000000
#74B2B5
Pass
a CompanyAccount15.76:14.5:1
#000000
#DFDFDF
Pass
a Get In Touch15.76:14.5:1
#000000
#DFDFDF
Pass
a Dark mode15.76:14.5:1
#000000
#DFDFDF
Pass
span off15.76:14.5:1
#000000
#DFDFDF
Pass
a English15.76:14.5:1
#000000
#DFDFDF
Pass
a Russian15.76:14.5:1
#000000
#DFDFDF
Pass
a Spanish15.76:14.5:1
#000000
#DFDFDF
Pass
a Brazil15.76:14.5:1
#000000
#DFDFDF
Pass
a Solutions15.76:14.5:1
#000000
#DFDFDF
Pass
a Internet of Things &…15.76:14.5:1
#000000
#DFDFDF
Pass
a Learn More15.76:14.5:1
#000000
#DFDFDF
Pass
a Industrial Cybersecu…15.76:14.5:1
#000000
#DFDFDF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 22 passed
REVIEW
83

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Show details div#CybotCookiebotDialogBody > div.CybotCookiebotDialogBodyBottomWrapper > div#CybotCookiebotDialogBodyEdgeMoreDetails > a#CybotCookiebotDialogBodyEdgeMoreDetailsLink
Allow all cookies div.CybotCookiebotScrollArea > div#CybotCookiebotDialogBodyButtons > div#CybotCookiebotDialogBodyButtonsWrapper > button#CybotCookiebotDialogBodyLevelButtonLevelOptinAllowAll
Customize div.CybotCookiebotScrollArea > div#CybotCookiebotDialogBodyButtons > div#CybotCookiebotDialogBodyButtonsWrapper > button#CybotCookiebotDialogBodyLevelButtonCustomize
Use necessary cookies only div.CybotCookiebotScrollArea > div#CybotCookiebotDialogBodyButtons > div#CybotCookiebotDialogBodyButtonsWrapper > button#CybotCookiebotDialogBodyButtonDecline
ALEXANDER CHUDNOV ul.c-list-authors > li > a > span
MIKHAIL REZNICHENKO ul.c-list-authors > li > a > span
KASPERSKY ICS CERT ul.c-list-authors > li > a > span
TECHNOLOGIES AND SERVICES div.c-card__body > header.c-card__header > p.c-card__headline > a.c-tag
10 MAR 2026, 5:00PM div.c-card__body > header.c-card__header > div.u-flex > time.c-card__event-date
FERNANDO ANDREAZI ul.c-list-authors > li > a > span
THREAT INTELLIGENCE AND IR div.c-card__body > header.c-card__header > p.c-card__headline > a.c-tag
26 FEB 2026, 5:00PM div.c-card__body > header.c-card__header > div.u-flex > time.c-card__event-date
ALEXANDRA FEDOSIMOVA ul.c-list-authors > li > a > span
View all categories div.o-col-3@md > ul.c-list-categories > li.c-list-categories__more > a
MALWARE DESCRIPTIONS div.c-card__body > header.c-card__header > p.c-card__headline > a.c-tag
DOMENICO CALDARELLA ul.c-list-authors > li > a > span
MATEUS SALGADO ul.c-list-authors > li > a > span

These are opportunities to improve the legibility of your content.

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
THREATS div.o-container-fluid > div.o-row > div.o-col > h5.c-block__title
WEBINARS div.o-container-fluid > div.o-row > div.o-col > h5.c-block__title
CATEGORIES div.o-container-fluid > div.o-row > div.o-col-3@md > h5.c-block__title
REPORTS div.c-page > section.c-block > div.o-container-fluid > h5.c-block__title

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.o-container-fluid > div.c-image > a > img div.o-container-fluid > div.c-image > a > img
div.o-col-4@sm > div.c-image > a > img div.o-col-4@sm > div.c-image > a > img

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
body.home > header#site-header > div.container > a.menu-toggle body.home > header#site-header > div.container > a.menu-toggle
div.container > div.c-site-title > div.c-site-logo__group > a.c-site-logo div.container > div.c-site-title > div.c-site-logo__group > a.c-site-logo
div.o-row > div.o-col-8@md > article.c-card > a.c-card__figure div.o-row > div.o-col-8@md > article.c-card > a.c-card__figure
div.o-row > div.o-col-4@md > article.c-card > a.c-card__figure div.o-row > div.o-col-4@md > article.c-card > a.c-card__figure
div.o-row > div.o-col-4@md > article.c-card > a.c-card__figure div.o-row > div.o-col-4@md > article.c-card > a.c-card__figure
div.o-row > div.o-col-3@md > article.c-card > a.c-card__figure div.o-row > div.o-col-3@md > article.c-card > a.c-card__figure
section.c-block > div.o-container-fluid > div.c-image > a section.c-block > div.o-container-fluid > div.c-image > a
div > div.o-col-6@sm > article.c-card > a.c-card__figure div > div.o-col-6@sm > article.c-card > a.c-card__figure
div.o-col-6@sm > article.c-card > div.c-card__figure > a.c-card__figure-link div.o-col-6@sm > article.c-card > div.c-card__figure > a.c-card__figure-link
div.o-row > div.o-col-8@md > article.c-card > a.c-card__figure div.o-row > div.o-col-8@md > article.c-card > a.c-card__figure
div.o-row > div.o-col-4@md > article.c-card > a.c-card__figure div.o-row > div.o-col-4@md > article.c-card > a.c-card__figure
div.o-row > div.o-col-4@md > article.c-card > a.c-card__figure div.o-row > div.o-col-4@md > article.c-card > a.c-card__figure
div.o-container-fluid > div > article.c-card > a.c-card__figure div.o-container-fluid > div > article.c-card > a.c-card__figure
div.o-row > div.o-col-4@sm > div.c-image > a div.o-row > div.o-col-4@sm > div.c-image > 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
VALERY AKULENKO div.c-card__authors > ul.c-list-authors > li > a
ALEXEY DVORTSOV div.c-card__authors > ul.c-list-authors > li > a
GEORGY KUCHERIN div.c-card__authors > ul.c-list-authors > li > a
MIKHAIL REZNICHENKO div.c-card__authors > ul.c-list-authors > li > a
SERGEY SOLDATOV div.c-card__authors > ul.c-list-authors > li > a
FERNANDO ANDREAZI div.c-card__authors > ul.c-list-authors > li > a
Privacy Policy div.c-page-footer__links > ul > li > a
Cookies div.c-page-footer__links > ul > li > 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
●`[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
●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
●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
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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.
○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.
○`<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.
○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