Accessibility

F

Heading Hierarchy

Action

59 headings, 6 skip(s)

FIX

59 headings, 6 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H3 → H5 (missing H4)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H3 → H5 (missing H4)

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

H4 Track your brand’s footprint in AI search
H4 Let your business shine with Listings AI
H4 Access 20 years of data with flexible pricing
H4 Surface actionable competitive intel
H1 Show up in search. Show up in AI. Own the results.
H4 From keyword rankings to AI-generated answers, Moz Pro surfaces every opportunity to win more traffic and revenue. skipped
H2 Trusted by 500,000+ brands and agencies
H2 Your SEO & digital marketing solutions
H3 Get the SEO insights you need to convert more traffic and outrank the competition
H3 Tackle large-scale SEO with accuracy and ease
H3 Become the brand that AI recommends
H5 Measure your brand’s presence in AI answers, benchmark competitors, and lead the next evolution of search. skipped
H3 Improve discovery, user experience, and rankings through content optimization
H3 Craft high-impact PR strategies to get your brand in front of the right audience
H3 Reach more customers online for your local business(es)
H3 Supercharge your own tools and dashboards with leading SEO metrics
H2 Research, refine, and rise in AI search with our complete toolkit
H2 Learn more about Moz tools
H2 Moz Pro: the all-in-one SEO and AI search toolkit
H5 Keyword Research skipped
H5 Competitive Research
H5 Link Research
H5 Rank Tracking
H5 Domain Overview
H5 Site Crawl
H2 STAT: the ultimate large-scale rank tracking platform
H2 Moz Local: the local SEO and reputation management tool
H2 Moz API: powering custom data solutions
H2 Propel your business forward with Moz Data
H5 1.25 billionKeyword suggestions in Keyword Explorer skipped
H5 44.8 trillionLinks indexed by Link Explorer
H5 100,000Local business listings optimized with Moz Local
H5 8 millionSERPs analyzed daily by STAT
H2 Why marketers trust Moz Data & tools
H2 Learn SEO from our experts
H5 Attend MozCon skipped
H5 Attend MozCon
H5 Get Certified with Moz Academy
H5 Get Certified with Moz Academy
H5 New to SEO?
H5 New to SEO?
H5 Get free SEO education
H5 Get free SEO education
H2 Ready to get started with Moz Pro?
H2 The latest from the Moz Blog
H2 LLMs Are Not as Complex as You Think: Here Are 10 Strategies To Improve AI Visibility
H2 The Complete AI Research Workflow: From Prompt Discovery to Content Creation
H2 Travel Marketing: How to Compete and Future-Proof in 2026 — Whiteboard Friday
H3 Get started with Moz Pro!
H5 Products skipped
H5 Moz Solutions
H5 Free SEO Tools
H5 Resources
H5 About Moz
H5 Why Moz
H5 Get Involved
H5 Connect with us
H5 Join our newsletter
H2 Your privacy is important to us.

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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

2 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 2 <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

Alt Text Quality

Action

4 of 55 images have issues

REVIEW

4 of 55 images have issues

4 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

16 decorative image(s) correctly marked

35 image(s) with good alt text

55 images 35 good alt text 16 decorative 4 missing

Issue	Count
missing	4 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

C

Form Accessibility

Action

3 of 5 controls have issues

REVIEW

3 of 5 controls have issues

2 control(s) without accessible label

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

Got: <select id="mobileSelect-tabs-674">; <input type="submit">

1 control(s) rely on placeholder only

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

Got: <input type="text" name="q">

2 control(s) properly labeled

5 controls

2 labeled

1 placeholder only

2 unlabeled

Control	Type	Label	Method
#email-379ffa8c-772e-4b7b-9c22-47d60e0db419	email	Email*	for/id
#LEGAL_CONSENT.subscription_type_4414581-379ffa8c-772e-4b7b-9c22-47d60e0db419	checkbox		none
q	text	(Search...)	placeholder only
#mobileSelect-tabs-674	select	(none)	none
input	submit	(none)	none

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

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.

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

C

Link & Button Quality

Action

11 issue(s) across 207 links and 13 buttons

REVIEW

11 issue(s) across 207 links and 13 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a.link-cta (#755 on page)

10 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /blog/ai-research-workflow-moz-pro ("Learn more"); /try-competitive-research-suite ("Learn More"); /explorer ("Learn more"); /try-competitive-research-suite ("Learn more"); /products/pro/link-research ("Learn more"); /products/pro/rank-tracking ("Learn more"); /help/domain-overview ("Learn more"); /products/pro/site-crawl ("Learn more"); /mozcon ("Learn more"); /mozcon ("Learn more")

14 link(s) open in new tab without warning

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

Got: https://gofishdigital.com/; /case-studies/chesapeake-regional-health; https://intellitonic.com/; https://www.hum.works/; http://zillow.com; https://moz.com/community/users/20754431; https://moz.com/community/users/10757585; https://moz.com/community/users/24685215; https://twitter.com/Moz; https://www.facebook.com/moz/ (+4 more)

182 link(s) with descriptive text

207 links

1 empty

10 generic text

14 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/blog/ai-research-workflow-moz-pro	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai Research Workflow Moz Pro
/try-competitive-research-suite	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Try Competitive Research Suite
	(empty)	empty	Add link text or aria-label
/explorer	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Explorer
/try-competitive-research-suite	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Try Competitive Research Suite
/products/pro/link-research	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Link Research
/products/pro/rank-tracking	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Rank Tracking
/help/domain-overview	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Domain Overview
/products/pro/site-crawl	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Site Crawl
https://gofishdigital.com/	Go Fish Digital	new tab	Add '(opens in new tab)' to text
/case-studies/chesapeake-regional-health	Chesapeake Regional Healthcare	new tab	Add '(opens in new tab)' to text
https://intellitonic.com/	Intellitonic	new tab	Add '(opens in new tab)' to text
https://www.hum.works/	Hum	new tab	Add '(opens in new tab)' to text
http://zillow.com	Zillow	new tab	Add '(opens in new tab)' to text
/mozcon	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Mozcon
/mozcon	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Mozcon
https://moz.com/community/users/20754431	Chima Mmeje	new tab	Add '(opens in new tab)' to text
https://moz.com/community/users/10757585	Meghan Pahinui	new tab	Add '(opens in new tab)' to text
https://moz.com/community/users/24685215	Chloe Osunsami	new tab	Add '(opens in new tab)' to text
https://twitter.com/Moz	link to Twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/moz/	link to Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/moz_hq/	link to Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/moz/	link to Linkedin	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCs26XZB…	link to youtube	new tab	Add '(opens in new tab)' to text
https://www.ziffdavis.com/privacy-policy	More information about your pr…	new tab	Add '(opens in new tab)' to text

195 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a.link-cta (#755 on page)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/blog/ai-research-workflow-moz-pro ("Learn more"); /try-competitive-research-suite ("Learn More"); /explorer ("Learn more"); /try-competitive-research-suite ("Learn more"); /products/pro/link-research ("Learn more"); /products/pro/rank-tracking ("Learn more"); /help/domain-overview ("Learn more"); /products/pro/site-crawl ("Learn more"); /mozcon ("Learn more"); /mozcon ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://gofishdigital.com/; /case-studies/chesapeake-regional-health; https://intellitonic.com/; https://www.hum.works/; http://zillow.com; https://moz.com/community/users/20754431; https://moz.com/community/users/10757585; https://moz.com/community/users/24685215; https://twitter.com/Moz; https://www.facebook.com/moz/ (+4 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

B

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 Moz logo ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

a Products

2.67:1

#000000

on

#304D9D

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Show up in search. S…	9.35:1	3.0:1	#000000	#33B7FE	Pass
h1 Own the results.	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 Trusted by 500,000+ …	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 Your SEO & digital m…	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 Research, refine, an…	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 Learn more about Moz…	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 the all-in-one SEO a…	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 the ultimate large-s…	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 the local SEO and re…	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 powering custom data…	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 Propel your business…	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 Why marketers	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 from our experts	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 Ready to get started…	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 The latest from the	9.35:1	3.0:1	#000000	#33B7FE	Pass
h2 Your privacy is impo…	9.35:1	3.0:1	#000000	#33B7FE	Pass
h3 Get started with Moz…	9.35:1	3.0:1	#000000	#33B7FE	Pass
title Moz - SEO Software f…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	11.28:1	4.5:1	#000000	#ADBFDE	Pass
a Products	2.67:1	4.5:1	#000000	#304D9D	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.

B

Lighthouse Accessibility Audits

Score 80/100 — 8 failing, 25 passed

REVIEW

80

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#wrap > div#mzr-top-nav > nav.mzr-container > a.mzr-home-logo `div#wrap > div#mzr-top-nav > nav.mzr-container > a.mzr-home-logo`
div#wrap > div#mzr-top-nav > nav.mzr-container > a.mzr-mobile-nav-toggle `div#wrap > div#mzr-top-nav > nav.mzr-container > a.mzr-mobile-nav-toggle`

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
From keyword rankings to AI-generated answers, Moz Pro surfaces every opportuni… `div.container > div.row > div.col-md > h4.jumbotron-subtitle`
Keyword Research `div.col-10 > div.card-body > a.card-title-link > h5.card-title`
1.25 billion Keyword suggestions in Keyword Explorer `div.stat > div.card > div.card-body > h5`
Attend MozCon `div.grid-container > div.card > div.flip-card-mobile > h5.card-title`
PRODUCTS `div.mzr-main-footer-column > div.mzr-footer-links > div.mzr-col-6 > h5.h6`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SEO SEO at Scale AI Visibility Content Marketing Digital PR Local Marketing Cus… `div.container > nav.tabs-block > span.select-wrapper > select#mobileSelect-tabs-674`

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.row > div.col > div.d-inline-block > a.link-cta `div.row > div.col > div.d-inline-block > a.link-cta`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Daily analytics at scale Get everything the 100-result SERP has to offer (plu… `div.row > div.col-12 > div.page-section-features-content-wrapper > ul.expandable-list`
Business listings management Seamlessly create and manage your local business … `div.row > div.col-12 > div.page-section-features-content-wrapper > ul.expandable-list`
Domain Authority Predict the ranking power of link signals to a website with t… `div.row > div.col-12 > div.page-section-features-content-wrapper > ul.expandable-list`

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Daily analytics at scale `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.expanded-link`
Get everything the 100-result SERP has to offer (plus its full HTML) in any loc… `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li#expandable-list-answer-325-0`
Market visibility `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.collapsed`
SERP feature insights `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.collapsed`
Customizable segments `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.collapsed`
Flexible reporting `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.collapsed`
Business listings management `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.expanded-link`
Seamlessly create and manage your local business listings on Google, Facebook, … `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li#expandable-list-answer-628-0`
Review management `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.collapsed`
Easily share news and offers `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.collapsed`
Monitor and report on performance `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.collapsed`
Domain Authority `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.expanded-link`
Predict the ranking power of link signals to a website with the original author… `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li#expandable-list-answer-390-0`
Page Authority `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.collapsed`
Brand Authority `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.collapsed`
Spam Score `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.collapsed`
In-depth link data `div.page-section-features-content-wrapper > ul.expandable-list > div.feature-row-as-accordion-wrapper > li.collapsed`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.inputs-list > li.hs-form-booleancheckbox > label.hs-form-booleancheckbox-display > input#LEGAL_CONSENT.subscription_type_4414581-379ffa8c-772e-4b7b-9c22-47d60e0db419 `ul.inputs-list > li.hs-form-booleancheckbox > label.hs-form-booleancheckbox-display > input#LEGAL_CONSENT.subscription_type_4414581-379ffa8c-772e-4b7b-9c22-47d60e0db419`

These items highlight common accessibility best practices.

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
Privacy Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

●Input buttons have discernible text.

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

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

●Links are distinguishable without relying on color.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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 type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

A

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

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

No banner (header) landmark

Skip navigation link present

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