Skip to content
https://appsflyer.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
44
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
F
Heading Hierarchy
Action
59 headings, 6 skip(s)
FIX
59 headings, 6 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: H1 → H3 (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 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Products
  • H4 Featured skipped
  • H2 Solutions
  • H4 Featured skipped
  • H2 Resources
  • H1 The measurement foundation your AI actually needs
  • H3 Trusted by 15,000 brands and counting skipped
  • H2 Everything you need to grow. All in one place.
  • H3 Measure every step across mobile, web, CTV and PC & console
  • H3 Connect users to the right in-app experience across every touchpoint
  • H3 Unlock first-party data value through privacy-preserving partnerships
  • H3 Move beyond insights to autonomous execution with AI agents
  • H2 Clarity for every team. Confidence in every decision.
  • H3 Turn data chaos into confident action
  • H3 Deliver experiences your customers can’t resist
  • H3 Transform creative intuition into growth data
  • H3 Grow confidently with clean data
  • H2 Powering measurable growth for the world’s leading brands
  • H2 The trusted standard for smarter marketing
  • H3 Backed by enterprise-grade security and scale
  • H3 Product
  • H3 Solutions
  • H3 Resources
  • H3 Get started
  • H3 Company
  • H5 Submit your request to see AppsFlyer in action skipped
  • H6 Which solutions are you most interested in? Select all that apply
  • H6 Measurement
  • H6 Data Collaboration Platform
  • H6 Deep Linking
  • H6 Creative Optimization
  • H5 Help us customize your experience
  • H6 Select your company type
  • H3 Advertiser
  • H3 Partner
  • H3 Agency
  • H6 Do you have customers already working with AppsFlyer? skipped
  • H6 Are you already an integrated partner with AppsFlyer?
  • H5 Tell us about your business
  • H6 Numbers of employees
  • H6 Annual mobile advertising budget
  • H6 Annual paid downloads
  • H5 Just a few last details
  • H6 What challenges can we help you solve?
  • H6 How did you hear about AppsFlyer?
  • H5 Help us customize your experience
  • H6 Numbers of employees
  • H5 Meet your AppsFlyer expert
  • H3 Thanks for reaching out! 🎉
  • H6 In the meantime, here are two great ways to learn more about AppsFlyer: skipped
  • H5 <p>Trusted by 100,000+<br /> apps worldwide</p>
  • H2 Our Cookies Policy
  • H2 Cookie Preference Center
  • H3 Please select which Cookies you approve, you may choose all options.
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Marketing Cookies
  • H4 Functional Cookies
  • H3 Cookie List

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
Form Accessibility
Action
17 of 57 controls have issues
FIX
17 of 57 controls have issues
Critical::
6 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="country">; <select name="industry">; <select name="Job_Level__c">; <select name="Job_Function__c">; <select name="country">; <select name="industry">
Warning::
11 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="firstName">; <input type="text" name="lastName">; <input type="email" name="email" id="af-request-demo-email">; <textarea name="Message__c">; <input type="text" name="website">; <input type="tel" name="phone">; <input type="text" name="postalCode" id="af-zip-code">; <textarea name="How_did_you_hear_about_AppsFlyer__c">; <input type="text" name="firstName">; <input type="text" name="lastName"> (+1 more)
Info::
40 control(s) properly labeled
57 controls
40 labeled
11 placeholder only
6 unlabeled
ControlTypeLabelMethod
requestedsolutionMKTOForm[]checkboxnone
requestedsolutionMKTOForm[]checkboxnone
requestedsolutionMKTOForm[]checkboxnone
requestedsolutionMKTOForm[]checkboxnone
My_company_is__cradionone
My_company_is__cradionone
My_company_is__cradionone
agency_existingradionone
agency_existingradionone
partner_existingradionone
partner_existingradionone
Company_Size__cradionone
Company_Size__cradionone
Company_Size__cradionone
Company_Size__cradionone
Company_Size__cradionone
Mobile_Ad_Spend_Annual__cradionone
Mobile_Ad_Spend_Annual__cradionone
Mobile_Ad_Spend_Annual__cradionone
Mobile_Ad_Spend_Annual__cradionone
Mobile_Ad_Spend_Annual__cradionone
Mobile_Ad_Spend_Annual__cradionone
Projected_Paid_Downloads__cradionone
Projected_Paid_Downloads__cradionone
Projected_Paid_Downloads__cradionone
Projected_Paid_Downloads__cradionone
Projected_Paid_Downloads__cradionone
Company_Size__cradionone
Company_Size__cradionone
Company_Size__cradionone
Company_Size__cradionone
Company_Size__cradionone
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxMarketing Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
firstNametext(First name*)placeholder only
lastNametext(Last name*)placeholder only
emailemail(Work email*)placeholder only
phonetel(Phone number*)placeholder only
#af-zip-codetext(Zip code)placeholder only
How_did_you_hear_about_AppsFlyer__ctextarea(e.g., LinkedIn/Facebook ad, colleague recommendation, Google search, industry*)placeholder only
#af-request-demo-emailemail(Work email*)placeholder only
firstNametext(First name*)placeholder only
lastNametext(Last name*)placeholder only
Message__ctextarea(Tell us your primary goal or pain point*)placeholder only
websitetext(Company website*)placeholder only
Job_Function__cselect(none)none
countryselect(none)none
countryselect(none)none
industryselect(none)none
industryselect(none)none
Job_Level__cselect(none)none

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

<select name="country">; <select name="industry">; <select name="Job_Level__c">; <select name="Job_Function__c">; <select name="country">; <select name="industry">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" name="firstName">; <input type="text" name="lastName">; <input type="email" name="email" id="af-request-demo-email">; <textarea name="Message__c">; <input type="text" name="website">; <input type="tel" name="phone">; <input type="text" name="postalCode" id="af-zip-code">; <textarea name="How_did_you_hear_about_AppsFlyer__c">; <input type="text" name="firstName">; <input type="text" name="lastName"> (+1 more)

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
6 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 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
Landmark Structure
Action
13 landmarks
REVIEW
13 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
6 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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 ASIDE CONTENTINFO (missing!)

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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - AppsFlyer ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
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
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The measurement foun…5.03:13.0:1
#000000
#7C7C7C
Pass
h2 Products3.47:13.0:1
#000000
#4D657D
Pass
h2 Solutions5.03:13.0:1
#000000
#7C7C7C
Pass
h2 Resources5.03:13.0:1
#000000
#7C7C7C
Pass
h2 Everything you need …5.03:13.0:1
#000000
#7C7C7C
Pass
h2 All in one place.5.03:13.0:1
#000000
#7C7C7C
Pass
h2 Clarity for every te…5.03:13.0:1
#000000
#7C7C7C
Pass
h2 Confidence in every …5.03:13.0:1
#000000
#7C7C7C
Pass
h2 Powering measurable …5.03:13.0:1
#000000
#7C7C7C
Pass
h2 The trusted standard…5.03:13.0:1
#000000
#7C7C7C
Pass
h2 Our Cookies Policy5.03:13.0:1
#000000
#7C7C7C
Pass
h2 Cookie Preference Ce…5.03:13.0:1
#000000
#7C7C7C
Pass
h3 Trusted by 15,000 br…5.03:13.0:1
#000000
#7C7C7C
Pass
h3 Measure every step a…5.03:13.0:1
#000000
#7C7C7C
Pass
h3 Connect users to the…5.03:13.0:1
#000000
#7C7C7C
Pass
h3 Unlock first-party d…5.03:13.0:1
#000000
#7C7C7C
Pass
h3 Move beyond insights…5.03:13.0:1
#000000
#7C7C7C
Pass
h3 Turn data chaos into…5.03:13.0:1
#000000
#7C7C7C
Pass
h3 Deliver experiences …5.03:13.0:1
#000000
#7C7C7C
Pass
h3 Transform creative i…5.03:13.0:1
#000000
#7C7C7C
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 88/100 — 4 failing, 28 passed
REVIEW
88

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.

ARIA

When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label `progressbar` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > nav#main-nav > div.progress-bar-container > div.progress-bar body.home > nav#main-nav > div.progress-bar-container > div.progress-bar

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.global-container-block__content > div.wp-block-appsflyer-blocks-carousel-block > div.wp-block-appsflyer-blocks-carousel-block__navigation > button.wp-block-appsflyer-blocks-carousel-block__navigation-button div.global-container-block__content > div.wp-block-appsflyer-blocks-carousel-block > div.wp-block-appsflyer-blocks-carousel-block__navigation > button.wp-block-appsflyer-blocks-carousel-block__navigation-button
div.global-container-block__content > div.wp-block-appsflyer-blocks-carousel-block > div.wp-block-appsflyer-blocks-carousel-block__navigation > button.wp-block-appsflyer-blocks-carousel-block__navigation-button div.global-container-block__content > div.wp-block-appsflyer-blocks-carousel-block > div.wp-block-appsflyer-blocks-carousel-block__navigation > button.wp-block-appsflyer-blocks-carousel-block__navigation-button

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.container-fluid > div.main-nav__inner-container > div.holder-mobile-brand-back > a.navbar-brand div.container-fluid > div.main-nav__inner-container > div.holder-mobile-brand-back > a.navbar-brand
nav.footer__social > ul.d-flex > li.pl-0 > a nav.footer__social > ul.d-flex > li.pl-0 > a
nav.footer__social > ul.d-flex > li.pl-0 > a nav.footer__social > ul.d-flex > li.pl-0 > a
nav.footer__social > ul.d-flex > li.pl-0 > a nav.footer__social > ul.d-flex > li.pl-0 > a
nav.footer__social > ul.d-flex > li.pl-0 > a nav.footer__social > ul.d-flex > li.pl-0 > a
nav.footer__social > ul.d-flex > li.pl-0 > a nav.footer__social > ul.d-flex > li.pl-0 > a
nav.footer__social > ul.d-flex > li.pl-0 > a nav.footer__social > ul.d-flex > li.pl-0 > 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.

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
Featured div.mega-menu__container > div.mega-menu__content > div.mega-menu__col--featured > h4.mega-menu__col--featured-title
Featured div.mega-menu__container > div.mega-menu__content > div.mega-menu__col--featured > h4.mega-menu__col--featured-title
Trusted by 15,000 brands and counting div.w-100 > div.w-100 > div.global-container-block__content > h3#h-trusted-by-15-000-brands-and-counting

These are opportunities to improve keyboard navigation in your application.

○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
●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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` 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
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.
A+
Alt Text Quality
All 135 images OK
PASS
All 135 images OK
Info::
36 decorative image(s) correctly marked
Info::
99 image(s) with good alt text
135 images 99 good alt text 36 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback