Skip to content
https://roids4all.ws

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
24
14 PASS 4 REVIEW 6 FIX
D
Tabindex Anti-Patterns
Action
0 positive, 26 -1-on-focusable
FIX
0 positive, 26 -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.)
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 <button id="slick-slide-control01">
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 <button id="slick-slide-control02">
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 <button id="slick-slide-control03">
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 <button id="slick-slide-control04">
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 <button id="slick-slide-control05">
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 <button id="slick-slide-control06">
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 <button id="slick-slide-control07">
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 <button id="slick-slide-control08">
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.)
F
404 Error Page
Action
HTTP 500, custom page
FIX
HTTP 500, custom page
Warning::
Unexpected status code: HTTP 500
Expected HTTP 404 but received 500. This may confuse search engine crawlers.
Got: HTTP 500
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 500 ✗Page Title Datenbankfehler ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
6 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Mobile Keyboard & Autofill
Action
2/3 eligible field(s) missing autocomplete or inputmode
REVIEW
2/3 eligible field(s) missing autocomplete or inputmode
Warning::
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: search, email.
Got: <input type="search" name="s" id="akj-header-search-field">, <input type="email" name="email" id="akj-home-newsletter-email">
B
Mobile-Readable Font Sizes
96% of visible text renders at >= 12 CSS px (12 below threshold)
REVIEW
96% of visible text renders at >= 12 CSS px (12 below threshold)
Info::
12 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: <a> 11.0px ("Anabolika Tabletten"); <a> 11.0px ("Oxandrolon (Anavar)"); <a> 11.0px ("Anabolika Tabletten"); <a> 11.0px ("Stanozolol (Stromba)"); <a> 11.0px ("Anabolika Tabletten").
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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 Missing
✓ Multiple Sizes Present
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 ALLES ÜBERSICHTLICH
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
32px · bottom of viewport
h1 AN EINEM ORT
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Rabattgutscheine für neue Kunden
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Hersteller & Marken
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Unsere Bestseller
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Info Anabolika-Blog
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Newsletter abonnieren
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Produkte Eingetroffen
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Echte Kundenmeinungen
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Kundenservice
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Kundenportal
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sortiment
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Informationen
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Zahlungsmethoden
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Lieferung
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Bewertungen
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Diskreter Versand
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Premium Qualität
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sichere Zahlung
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Kundenservice
1.14:1
#000000
on
#320000
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 ALLES ÜBERSICHTLICH1.14:13.0:1
#000000
#320000
Fail
h1 AN EINEM ORT1.14:13.0:1
#000000
#320000
Fail
h2 Rabattgutscheine fü…1.14:13.0:1
#000000
#320000
Fail
h2 Hersteller & Marken1.14:13.0:1
#000000
#320000
Fail
h2 Unsere Bestseller1.14:13.0:1
#000000
#320000
Fail
h2 Info Anabolika-Blog1.14:13.0:1
#000000
#320000
Fail
h2 Newsletter abonniere…1.14:13.0:1
#000000
#320000
Fail
h2 Produkte Eingetroffe…1.14:13.0:1
#000000
#320000
Fail
h2 Echte Kundenmeinunge…1.14:13.0:1
#000000
#320000
Fail
h2 Kundenservice1.14:13.0:1
#000000
#320000
Fail
h2 Kundenportal1.14:13.0:1
#000000
#320000
Fail
h2 Sortiment1.14:13.0:1
#000000
#320000
Fail
h2 Informationen1.14:13.0:1
#000000
#320000
Fail
h2 Zahlungsmethoden1.14:13.0:1
#000000
#320000
Fail
h2 Lieferung1.14:13.0:1
#000000
#320000
Fail
h2 Bewertungen1.14:13.0:1
#000000
#320000
Fail
h3 Diskreter Versand1.14:13.0:1
#000000
#320000
Fail
h3 Premium Qualität1.14:13.0:1
#000000
#320000
Fail
h3 Sichere Zahlung1.14:13.0:1
#000000
#320000
Fail
h3 Kundenservice1.14:13.0:1
#000000
#320000
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
19 landmarks
PASS
19 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "MAIN MENU 2" SEARCH MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
33 headings
PASS
33 headings
Info::
Single H1 present
  • H1 ALLES ÜBERSICHTLICH AN EINEM ORT
  • H2 Rabattgutscheine für neue Kunden
  • H3 Diskreter Versand
  • H3 Premium Qualität
  • H3 Sichere Zahlung
  • H3 Kundenservice
  • H2 Hersteller & Marken
  • H2 Unsere Bestseller
  • H2 Testosteron-Depot 250mg (EIFELFANGO)
  • H2 Boldaxyl 300 (KALPA PHARMA)
  • H2 Boldenon Undecylenat 250 (GENERAL PHARMA)
  • H2 Testosteron Cypionat 250 (GENERAL PHARMA)
  • H2 Clenbutaxyl 40 mcg (KALPA PHARMA)
  • H2 Info Anabolika-Blog
  • H3 Anabolika für Frauen: Chancen und Risiken
  • H3 Anavar (Oxandrolon)
  • H3 Abnehmen mit Clenbuterol, T3 und Ozempic
  • H3 Post Zyklus Therapie (PCT)
  • H2 Newsletter abonnieren
  • H2 Produkte Eingetroffen
  • H2 Oxandrolon 10 mg (GENERAL PHARMA)
  • H2 Stanozolol 10 mg (HILMA BIOCARE)
  • H2 Dianabol 10 mg (HUMAN LABS)
  • H2 Etho Primobolan (BELIGAS PHARMA)
  • H2 Boldaxyl 300 (KALPA PHARMA)
  • H2 Echte Kundenmeinungen
  • H2 Kundenservice
  • H2 Kundenportal
  • H2 Sortiment
  • H2 Informationen
  • H2 Zahlungsmethoden
  • H2 Lieferung
  • H2 Bewertungen
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Alt Text Quality
All 72 images OK
PASS
All 72 images OK
Info::
72 image(s) with good alt text
72 images 72 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#akj-header-search-fieldsearchSuchefor/id
#akj-home-newsletter-emailemailDeine E-Mail-Adressefor/id
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "de"
PASS
Lang attribute set to "de"
Info::
<html lang="de"> is set and valid
Got: de
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
2 mobile-depth signal(s) detected
PASS
2 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.
Info::
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.
A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 29 passed
PASS
100

Accessibility

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

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MEHR ENTDECKEN › div.akj-premium-hero__shell > div.akj-premium-hero__layout > div.akj-premium-hero__content > a.akj-premium-hero__button
Anabolika für Frauen: Chancen und Risiken 22/09/2025 section.akj-blog-showcase > div.akj-home-blog-compact-grid > article.akj-home-blog-compact-card > a.akj-home-blog-compact-link
Anavar (Oxandrolon) 07/08/2025 section.akj-blog-showcase > div.akj-home-blog-compact-grid > article.akj-home-blog-compact-card > a.akj-home-blog-compact-link
Abnehmen mit Clenbuterol, T3 und Ozempic 04/06/2025 section.akj-blog-showcase > div.akj-home-blog-compact-grid > article.akj-home-blog-compact-card > a.akj-home-blog-compact-link
Post Zyklus Therapie (PCT) 26/05/2025 section.akj-blog-showcase > div.akj-home-blog-compact-grid > article.akj-home-blog-compact-card > a.akj-home-blog-compact-link
JETZT ANSEHEN div.ct-container > section.akj-new-products-section > div.akj-new-products-header > a.akj-new-products-cta
○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links 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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
○`[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 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
○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
○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.
○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