Skip to content
https://www.titansalerts.sbs

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
7
REVIEW
3
PASS
14
INFO
0
Checks
24
14 PASS 3 REVIEW 7 FIX
F
Heading Hierarchy
Action
43 headings, 5 skip(s)
FIX
43 headings, 5 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.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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 AUTOMATE ALERTS. JOURNAL TRADES. SCALE PROFITS.
  • H2 COMPLETE TRADING WORKSPACE 🛠️
  • H3 Telegram Alerts
  • H3 Trading Journal
  • H3 P&L Calendar
  • H3 Strategy Tracker
  • H3 Free Recharge & UPI
  • H3 Premium Learn Hub
  • H2 AUTOMATED CHANNEL BROADCAST 📢
  • H4 BotFather Setup skipped
  • H4 One-Click Send
  • H4 Multiple Channels
  • H4 Status Dashboard
  • H4 VIP Trading Alert Channel
  • H2 PROFESSIONAL TRADING JOURNAL 📝
  • H4 Detailed Logging skipped
  • H4 Interactive Calendar
  • H4 Strategy Metrics
  • H4 Target Challenges
  • H2 FREE MOBILE RECHARGE & UPI CASH 📱
  • H4 Network Operators skipped
  • H4 Direct UPI Cash Out
  • H4 Spin Wheel & Scratch
  • H4 Educational Missions
  • H4 YOU WON 1,000 POINTS! 🎉
  • H2 GET ACTIVE IN 3 STEPS ⚡
  • H4 Register Account skipped
  • H4 Setup Bots & Journal
  • H4 Optimize Performance
  • H2 LEADERBOARD OF THE MONTH 🏆
  • H4 EliteBull skipped
  • H4 AlphaScalper
  • H4 DeltaTrader
  • H2 JOIN OUR GLOBAL TELEGRAM GROUP! 📢
  • H2 GOT QUESTIONS? ❓
  • H2 LATEST INSIGHTS 📚
  • H3 Health Insurance Comparison: Top Health Plans & Features
  • H3 Best Mutual Funds in India (2026): Top Performing Schemes
  • H3 Best Credit Cards in India (2026): Cashback & Travel Cards
  • H2 READY TO Automate & Journal?
  • H3 Quick Links
  • H3 Legal
  • H4 Install TitansAlerts

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

D
Iframe Accessibility
Action
6/7 iframe(s) missing title; 0 placeholder(s)
FIX
6/7 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="about:blank")
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="about:blank")
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="about:blank")
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://www.google.com/recaptcha/api2/aframe")
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://googleads.g.doubleclick.net/pagead/html/r20261102/r20190131/zrt_lookup.…")
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
Mobile-Readable Font Sizes
Action
38% of visible text renders at >= 12 CSS px (243 below threshold)
FIX
38% of visible text renders at >= 12 CSS px (243 below threshold)
Warning::
243 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("Professional Trading System ⚡"); <div> 8.0px ("+50K"); <p> 10.0px ("Active Traders & Channel Admins"); <span> 10.0px ("Compare Brokers"); <span> 10.0px ("titansalerts_dashboard.app").
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-d21s5g
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #2563eb
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 ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <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.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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 (missing!) NAV 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

C
Favicon & Branding
Action
7 icon(s) detected
REVIEW
7 icon(s) detected
Info::
favicon.ico present at site root
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::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
11 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: 11 all-caps heading(s)
A+
Alt Text Quality
All 5 images OK
PASS
All 5 images OK
Info::
5 image(s) with good alt text
5 images 5 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
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
6 explicit tabindex attribute(s) checked, no anti-patterns
PASS
6 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: TitansAlerts
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name TitansAlerts ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name TitansAlerts Display Mode standalone Theme Color #2563eb Background Color #0f172a Icons 5 icon(s)
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::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 AUTOMATE ALERTS.21.00:13.0:1
#000000
#FFFFFF
Pass
h1 SCALE PROFITS.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 COMPLETE TRADING WOR…19.44:13.0:1
#000000
#F6F6F7
Pass
h2 AUTOMATED CHANNEL BR…19.44:13.0:1
#000000
#F6F6F7
Pass
h2 PROFESSIONAL TRADING…19.44:13.0:1
#000000
#F6F6F7
Pass
h2 FREE MOBILE RECHARGE…19.44:13.0:1
#000000
#F6F6F7
Pass
h2 GET ACTIVE IN 3 STEP…19.44:13.0:1
#000000
#F6F6F7
Pass
h2 LEADERBOARD OF THE M…19.44:13.0:1
#000000
#F6F6F7
Pass
h2 JOIN OUR GLOBAL TELE…19.44:13.0:1
#000000
#F6F6F7
Pass
h2 GOT QUESTIONS? ❓19.44:13.0:1
#000000
#F6F6F7
Pass
h2 LATEST INSIGHTS 📚19.44:13.0:1
#000000
#F6F6F7
Pass
h2 READY TO Automate & …19.44:13.0:1
#000000
#F6F6F7
Pass
h3 Telegram Alerts19.44:13.0:1
#000000
#F6F6F7
Pass
h3 Trading Journal19.44:13.0:1
#000000
#F6F6F7
Pass
h3 P&L Calendar19.44:13.0:1
#000000
#F6F6F7
Pass
h3 Strategy Tracker19.44:13.0:1
#000000
#F6F6F7
Pass
h3 Free Recharge & UPI19.44:13.0:1
#000000
#F6F6F7
Pass
h3 Premium Learn Hub19.44:13.0:1
#000000
#F6F6F7
Pass
h3 Health Insurance Com…19.44:13.0:1
#000000
#F6F6F7
Pass
h3 Best Mutual Funds in…19.44:13.0:1
#000000
#F6F6F7
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.

A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 23 passed
PASS
91

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
ACTIVE TRADERS & CHANNEL ADMINS div.flex > div.text-center > div.pt-6 > p.text-[10px]
TB div.lg:col-span-6 > div.bg-[#17212b] > div.flex > div.w-10
54,200 subscribers • online bot div.bg-[#17212b] > div.flex > div > p.text-[9px]
🚨 NEW TRADING SIGNAL div.bg-[#17212b] > div.space-y-4 > div.bg-[#182533] > p.text-[#5288c1]
CONSISTENCY CALENDAR div.lg:col-span-6 > div.bg-white > div.space-y-2 > p.text-[9px]
12 div.bg-white > div.space-y-2 > div.grid > div.h-7
13 div.bg-white > div.space-y-2 > div.grid > div.h-7
14 div.bg-white > div.space-y-2 > div.grid > div.h-7
STRATEGY ACCURACY div.lg:col-span-6 > div.bg-white > div.space-y-2 > p.text-[9px]
Win Rate: 75% div.space-y-2 > div.p-2.5 > div.space-y-0.5 > p.text-[8px]
₹24,500 div.space-y-2 > div.space-y-2 > div.p-2.5 > span.font-mono
Win Rate: 60% div.space-y-2 > div.p-2.5 > div.space-y-0.5 > p.text-[8px]
₹9,800 div.space-y-2 > div.space-y-2 > div.p-2.5 > span.font-mono
Win Rate: 48% div.space-y-2 > div.p-2.5 > div.space-y-0.5 > p.text-[8px]
-₹2,100 div.space-y-2 > div.space-y-2 > div.p-2.5 > span.font-mono
DATA-DRIVEN DISCIPLINE div.max-w-7xl > div.grid > div.lg:col-span-6 > div.inline-flex
DETAILED LOGGING div.grid > div.p-4 > div.flex > h4.text-xs
INTERACTIVE CALENDAR div.grid > div.p-4 > div.flex > h4.text-xs
STRATEGY METRICS div.grid > div.p-4 > div.flex > h4.text-xs
TARGET CHALLENGES div.grid > div.p-4 > div.flex > h4.text-xs
START YOUR JOURNAL div.grid > div.lg:col-span-6 > div.pt-4 > button.px-6
ECOSYSTEM REWARDS div.max-w-7xl > div.grid > div.lg:col-span-6 > div.inline-flex
NETWORK OPERATORS div.grid > div.p-4 > div.flex > h4.text-xs
DIRECT UPI CASH OUT div.grid > div.p-4 > div.flex > h4.text-xs
SPIN WHEEL & SCRATCH div.grid > div.p-4 > div.flex > h4.text-xs
EDUCATIONAL MISSIONS div.grid > div.p-4 > div.flex > h4.text-xs
MAY 24, 2026 19:44 article.flex > div.flex-1 > div.flex > span.flex
1 MIN READ article.flex > div.flex-1 > div.flex > span.flex
MAY 24, 2026 19:44 article.flex > div.flex-1 > div.flex > span.flex
2 MIN READ article.flex > div.flex-1 > div.flex > span.flex
MAY 24, 2026 19:44 article.flex > div.flex-1 > div.flex > span.flex
2 MIN READ article.flex > div.flex-1 > div.flex > span.flex
Risk Disclaimer: Trading in financial markets involves substantial risk and may… footer.bg-gray-900 > div.max-w-7xl > div.mt-8 > p.text-xs
Risk Disclaimer: div.max-w-7xl > div.mt-8 > p.text-xs > strong

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
BOTFATHER SETUP div.grid > div.p-4 > div.flex > h4.text-xs
DETAILED LOGGING div.grid > div.p-4 > div.flex > h4.text-xs
NETWORK OPERATORS div.grid > div.p-4 > div.flex > h4.text-xs
REGISTER ACCOUNT div.grid > div.relative > div.bg-slate-50 > h4.text-lg
ELITEBULL div.max-w-7xl > div.grid > div.relative > h4.text-lg

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.grid > div.col-span-1 > div.flex > a.text-gray-400 div.grid > div.col-span-1 > div.flex > a.text-gray-400
div.grid > div.col-span-1 > div.flex > a.text-gray-400 div.grid > div.col-span-1 > div.flex > a.text-gray-400
div.grid > div.col-span-1 > div.flex > a.text-gray-400 div.grid > div.col-span-1 > div.flex > a.text-gray-400
div.grid > div.col-span-1 > div.flex > a.text-gray-400 div.grid > div.col-span-1 > div.flex > a.text-gray-400
div.grid > div.col-span-1 > div.flex > a.text-gray-400 div.grid > div.col-span-1 > div.flex > a.text-gray-400

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.

○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
●`[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
●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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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.
○`[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.
○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