Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 5 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

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

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

Form Accessibility

11 of 17 controls have issues

REVIEW

11 of 17 controls have issues

11 control(s) rely on placeholder only

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

Got: <input type="text" name="form_fields[name]" id="form-field-name">; <input type="email" name="form_fields[email]" id="form-field-email">; <input type="text" name="form_fields[first_name]" id="form-field-first_name">; <input type="text" name="form_fields[last_name]" id="form-field-last_name">; <input type="email" name="form_fields[email]" id="form-field-email">; <input type="tel" name="form_fields[phone_number]" id="form-field-phone_number">; <input type="text" name="form_fields[company]" id="form-field-company">; <input type="number" name="form_fields[employees]" id="form-field-employees">; <input type="text" name="form_fields[website]" id="form-field-website">; <input type="text" name="form_fields[role_company]" id="form-field-role_company"> (+1 more)

6 control(s) properly labeled

17 controls

6 labeled

11 placeholder only

0 unlabeled

Control	Type	Label	Method
#wt-cli-checkbox-necessary	checkbox	Necessary	for/id
#wt-cli-checkbox-functional	checkbox	Functional	for/id
#wt-cli-checkbox-performance	checkbox	Performance	for/id
#wt-cli-checkbox-analytics	checkbox	Analytics	for/id
#wt-cli-checkbox-advertisement	checkbox	Advertisement	for/id
#wt-cli-checkbox-others	checkbox	Others	for/id
#form-field-company	text	(Company)	placeholder only
#form-field-employees	number	(Number of employees)	placeholder only
#form-field-website	text	(Website)	placeholder only
#form-field-role_company	text	(Role in company)	placeholder only
#form-field-message	textarea	(Message)	placeholder only
#form-field-name	text	(Name)	placeholder only
#form-field-email	email	(Email)	placeholder only
#form-field-first_name	text	(First Name)	placeholder only
#form-field-last_name	text	(Last Name)	placeholder only
#form-field-email	email	(Email)	placeholder only
#form-field-phone_number	tel	(Phone)	placeholder only

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

<input type="text" name="form_fields[name]" id="form-field-name">; <input type="email" name="form_fields[email]" id="form-field-email">; <input type="text" name="form_fields[first_name]" id="form-field-first_name">; <input type="text" name="form_fields[last_name]" id="form-field-last_name">; <input type="email" name="form_fields[email]" id="form-field-email">; <input type="tel" name="form_fields[phone_number]" id="form-field-phone_number">; <input type="text" name="form_fields[company]" id="form-field-company">; <input type="number" name="form_fields[employees]" id="form-field-employees">; <input type="text" name="form_fields[website]" id="form-field-website">; <input type="text" name="form_fields[role_company]" id="form-field-role_company"> (+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

Tabindex Anti-Patterns

0 positive, 5 -1-on-focusable

REVIEW

0 positive, 5 -1-on-focusable

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.)

tabindex="-1" on naturally-focusable <a>

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found - Conversion ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Heading Hierarchy

32 headings, 1 skip(s)

PASS

32 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Dominate Brazilian market and crush the competition, partnering with the Largest SEO Agency in Brazil.
H2 Our Clients
H2 Our Services
H2 Link Building 4.0
H2 Data-Driven PR
H2 SEO Services
H2 E-commerce SEO
H2 On-Page & Technical SEO
H2 Content Creation
H2 SEO Newsletter
H2 Receive our most recent content and news. Content in English.
H2 Latest Content
H3 Top 10 Apps in Brazil: A Comparison with U.S. Trends and Future Insights
H3 Standing Out in the Brazilian App Market: Tips for Differentiating Your App
H3 Organic Marketing: The Future is Not Paying for Ads
H3 Top 10 Apps in Brazil: A Comparison with U.S. Trends and Future Insights
H3 Standing Out in the Brazilian App Market: Tips for Differentiating Your App
H3 Organic Marketing: The Future is Not Paying for Ads
H3 How to Discover Website Keywords and Maximize SEO Performance
H3 How to Find the Backlinks of Any Website?
H3 Duplicate Content Fixing: A Step-by-Step Guide
H3 Number of TikTok users in Brazil: monthly active users and time per user
H3 Number of Facebook users in Brazil: monthly active users and time per user
H3 Number of Instagram users in Brazil: monthly active users and time per user
H3 Most popular apps for online food and market ordering in Brazil in 2023
H2 Testimonials from our clients
H2 AS SEEN ON
H2 AND OVER 400 NEWS SITES
H2 Talk to Our Consultants
H2 Tell us your challenges and how we can help you dominate the Brazilian market.
H2 Organic marketing crushes the competition.
H4 Privacy Overview 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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 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: 2 all-caps heading(s)

A+

Alt Text Quality

All 60 images OK

PASS

All 60 images OK

28 decorative image(s) correctly marked

32 image(s) with good alt text

60 images 32 good alt text 28 decorative

All images have appropriate alt text.

Link & Button Quality

67 links, 3 buttons — all OK

PASS

67 links, 3 buttons — all OK

13 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://conversion.ag/blog/top-10-apps-in-brazil/; https://conversion.ag/blog/brazilian-app-market/; https://conversion.ag/blog/organic-marketing/; http://www.wicz.com/story/47257059/new-brazil-ecommerce-report-analyzes-the-b…; http://digitaljournal.com/pr/new-brazil-e-commerce-report-analyzes-the-brazil…; https://www.newschannelnebraska.com/story/47257059/new-brazil-ecommerce-repor…; https://www.marketwatch.com/press-release/new-brazil-e-commerce-report-analyz…; https://www.benzinga.com/pressreleases/22/09/ab28820891/new-brazil-e-commerce…; https://www.instagram.com/agenciaconversion; https://www.linkedin.com/company/agenciaconversion/ (+3 more)

54 link(s) with descriptive text

67 links

0 empty

0 generic text

13 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://conversion.ag	<img width="150" height="23" s…	img no alt	Add alt attribute to the image
https://conversion.ag/blog/top-10-apps-i…	<img width="800" height="534" …	new tab	Add '(opens in new tab)' to text
https://conversion.ag/blog/brazilian-app…	<img width="701" height="498" …	new tab	Add '(opens in new tab)' to text
https://conversion.ag/blog/organic-marke…	<img width="800" height="450" …	new tab	Add '(opens in new tab)' to text
https://conversion.ag/blog/top-10-apps-i…	<img width="2120" height="1414…	img no alt	Add alt attribute to the image
https://conversion.ag/blog/brazilian-app…	<img width="701" height="498" …	img no alt	Add alt attribute to the image
https://conversion.ag/blog/organic-marke…	<img width="1280" height="720"…	img no alt	Add alt attribute to the image
https://conversion.ag/blog/how-to-discov…	<img width="1254" height="836"…	img no alt	Add alt attribute to the image
https://conversion.ag/blog/how-to-find-t…	<img width="1224" height="857"…	img no alt	Add alt attribute to the image
https://conversion.ag/blog/duplicate-con…	<img width="1254" height="836"…	img no alt	Add alt attribute to the image
https://conversion.ag/blog/tiktok-users-…	<img width="1280" height="720"…	img no alt	Add alt attribute to the image
https://conversion.ag/blog/facebook-braz…	<img width="1280" height="720"…	img no alt	Add alt attribute to the image
https://conversion.ag/blog/instagram-use…	<img width="1280" height="720"…	img no alt	Add alt attribute to the image
https://conversion.ag/blog/apps-food-and…	<img width="1280" height="720"…	img no alt	Add alt attribute to the image
http://www.wicz.com/story/47257059/new-b…	<img width="150" height="63" s…	new tab	Add '(opens in new tab)' to text
http://digitaljournal.com/pr/new-brazil-…	<img width="150" height="61" s…	new tab	Add '(opens in new tab)' to text
https://www.newschannelnebraska.com/stor…	<img width="150" height="89" s…	new tab	Add '(opens in new tab)' to text
https://www.marketwatch.com/press-releas…	<img width="150" height="71" s…	new tab	Add '(opens in new tab)' to text
https://www.benzinga.com/pressreleases/2…	<img width="150" height="20" s…	new tab	Add '(opens in new tab)' to text
https://conversion.ag	<img width="199" height="30" s…	img no alt	Add alt attribute to the image
https://www.instagram.com/agenciaconvers…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/agencia…	Linkedin	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/agenciaconversi…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.conversion.com.br/politica-d…	Privacy Policies	new tab	Add '(opens in new tab)' to text
https://www.conversion.com.br/politica-d…	Cookie Policies.	new tab	Add '(opens in new tab)' to text

57 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://conversion.ag/blog/top-10-apps-in-brazil/; https://conversion.ag/blog/brazilian-app-market/; https://conversion.ag/blog/organic-marketing/; http://www.wicz.com/story/47257059/new-brazil-ecommerce-report-analyzes-the-b…; http://digitaljournal.com/pr/new-brazil-e-commerce-report-analyzes-the-brazil…; https://www.newschannelnebraska.com/story/47257059/new-brazil-ecommerce-repor…; https://www.marketwatch.com/press-release/new-brazil-e-commerce-report-analyz…; https://www.benzinga.com/pressreleases/22/09/ab28820891/new-brazil-e-commerce…; https://www.instagram.com/agenciaconversion; https://www.linkedin.com/company/agenciaconversion/ (+3 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "form_fields[website]" should use type="url" (currently type="text")

Field name "form_fields[website]" suggests type="url". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="url">.

A+

Form Input Quality

17 form control(s) checked, no input-semantic issues

PASS

17 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 73 visible text node(s) render at >= 12 CSS pixels

PASS

All 73 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

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.

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+

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)

Element	Ratio	Required	FG	BG	Result
h1 Dominate Brazilian m…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our Clients	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 Our Services	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Link Building 4.0	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Data-Driven PR	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SEO Services	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 E-commerce SEO	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 On-Page & Technical …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Content Creation	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SEO Newsletter	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Receive our most rec…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Content	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 from our clients	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 AS SEEN ON	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 AND OVER 400 NEWS SI…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Talk to Our Consulta…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Tell us your challen…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Organic marketing cr…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title SEO Agency in Brazil…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Link Building 4.0	21.00:1	4.5:1	#000000	#FFFFFF	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.

Lighthouse Accessibility Audits

Score 90/100 — 3 failing, 25 passed

PASS

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 an 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 make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.elementor-element > div.elementor-widget-container > div.elementor-image-carousel-wrapper > div.elementor-swiper-button `div.elementor-element > div.elementor-widget-container > div.elementor-image-carousel-wrapper > div.elementor-swiper-button`
div.elementor-element > div.elementor-widget-container > div.elementor-image-carousel-wrapper > div.elementor-swiper-button `div.elementor-element > div.elementor-widget-container > div.elementor-image-carousel-wrapper > div.elementor-swiper-button`

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.

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
We are excited to announce the results of our latest research conducted trough … `div.elementor-post__card > div.elementor-post__text > div.elementor-post__excerpt > p`
A breakdown and contrast of major US vs. Brazil market and user characteristics… `div.elementor-post__card > div.elementor-post__text > div.elementor-post__excerpt > p`
Marketing departments in companies have been known to be the ones that spend th… `div.elementor-post__card > div.elementor-post__text > div.elementor-post__excerpt > p`
AND OVER 400 NEWS SITES `div.elementor-element > div.elementor-element > div.elementor-widget-container > h2.elementor-heading-title`

These are opportunities to improve the legibility of your content.

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.elementor-element > div.elementor-widget-container > div.elementor-image > a `div.elementor-element > div.elementor-widget-container > div.elementor-image > a`
div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link `div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link`
div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link `div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link`
div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link `div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link`
div.elementor-element > div.elementor-widget-container > div.elementor-image > a `div.elementor-element > div.elementor-widget-container > div.elementor-image > a`
div.elementor-element > div.elementor-widget-container > div.elementor-image > a `div.elementor-element > div.elementor-widget-container > div.elementor-image > a`
div.elementor-element > div.elementor-widget-container > div.elementor-image > a `div.elementor-element > div.elementor-widget-container > div.elementor-image > a`
div.elementor-element > div.elementor-widget-container > div.elementor-image > a `div.elementor-element > div.elementor-widget-container > div.elementor-image > a`
div.elementor-element > div.elementor-widget-container > div.elementor-image > a `div.elementor-element > div.elementor-widget-container > div.elementor-image > a`
div.elementor-element > div.elementor-widget-container > div.elementor-image > a `div.elementor-element > div.elementor-widget-container > div.elementor-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.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<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

○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.

○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.