Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Landmark Structure

Action

3 landmarks

FIX

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

2 <nav> landmark(s) found

2 of 2 <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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 2 <nav> element(s)

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.

Heading Hierarchy

Action

14 headings, 2 skip(s)

REVIEW

14 headings, 2 skip(s)

Multiple H1 headings (8 found)

A page should have only one H1. Multiple H1s dilute the document outline.

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: H1 → H3 (missing H2)

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

H2 Enhance Engagement with Disqus
H1 More publishers trust us than any other audience engagement platform.
H4 With the deprecation of third-party cookies, the rise of the walled gardens, and the era of internet toxicity spurred by mis- and dis-information, it’s a challenging time to be a publisher. skipped
H1 The web's largest conversation platform duplicate H1
H1 Transform your casual, anonymous readers into loyal, authenticated users. duplicate H1
H1 Protect your brand and loyal users with our best-in-class moderation panel and tooling. duplicate H1
H1 Track and understand your audience engagement with robust insights. duplicate H1
H1 Harness the power of your direct user relationships to unlock new revenue streams. duplicate H1
H1 Flexible and optimized for your site’s needs duplicate H1
H1 Turbocharge audience engagement with Disqus. duplicate H1
H3 Disqus skipped
H3 Resources
H3 About Us
H3 Learn

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Alt Text Quality

Action

18 of 20 images have issues

REVIEW

18 of 20 images have issues

18 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image(s) with good alt text

20 images 2 good alt text 18 missing

Issue	Count
missing	18 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

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 (404) - Disqus ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

15 icon(s) detected

REVIEW

15 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 86/100 — 4 failing, 23 passed

REVIEW

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
Cookie Policy `div.osano-cm-window > div#efc1395e-8f06-4392-b2de-b0e9ef84b9c0 > div.osano-cm-dialog__content > a.osano-cm-storage-policy`
Accept `div.osano-cm-window > div#efc1395e-8f06-4392-b2de-b0e9ef84b9c0 > div.osano-cm-dialog__buttons > button.osano-cm-accept`
Deny Non-Essential `div.osano-cm-window > div#efc1395e-8f06-4392-b2de-b0e9ef84b9c0 > div.osano-cm-dialog__buttons > button.osano-cm-deny`
Get started `div.bg--light > div.home__wrapper > section.homepage-hero > a.homepage-hero__button`
50M+ `div.panel__content > ul.list > li > div.number`
2.5B+ `div.panel__content > ul.list > li > div.number`
20M+ `div.panel__content > ul.list > li > div.number`
200+ `div.panel__content > ul.list > li > div.number`
Engage now » `div.home__wrapper > section.panel > div.panel__content > a.link`
Moderate now » `div.home__wrapper > section.panel > div.panel__content > a.link`
Analyze now » `div.home__wrapper > section.panel > div.panel__content > a.link`
Monetize now » `div.home__wrapper > section.panel > div.panel__content > a.link`
Platform Overview `nav.site-footer__nav > ul.nav-list > li > a`
Engagement `nav.site-footer__nav > ul.nav-list > li > a`
Moderation & Safety `nav.site-footer__nav > ul.nav-list > li > a`
Audience `nav.site-footer__nav > ul.nav-list > li > a`
Monetization `nav.site-footer__nav > ul.nav-list > li > a`
Pricing `nav.site-footer__nav > ul.nav-list > li > a`
Disqus Pro `nav.site-footer__nav > ul.nav-list > li > a`
Disqus for Business `nav.site-footer__nav > ul.nav-list > li > a`
Blog `nav.site-footer__nav > ul.nav-list > li > a`
Support `nav.site-footer__nav > ul.nav-list > li > a`
Knowledge Base `nav.site-footer__nav > ul.nav-list > li > a`
Disqus 101 `nav.site-footer__nav > ul.nav-list > li > a`
Discuss Disqus `nav.site-footer__nav > ul.nav-list > li > a`
Case Studies `nav.site-footer__nav > ul.nav-list > li > a`
API `nav.site-footer__nav > ul.nav-list > li > a`
Logos `nav.site-footer__nav > ul.nav-list > li > a`
History `nav.site-footer__nav > ul.nav-list > li > a`
Mission `nav.site-footer__nav > ul.nav-list > li > a`
Culture `nav.site-footer__nav > ul.nav-list > li > a`
How Does Disqus Work? `nav.site-footer__nav > ul.nav-list > li > a`
Community Tips `nav.site-footer__nav > ul.nav-list > li > a`
Increase Engagement & Retention `nav.site-footer__nav > ul.nav-list > li > a`
Moderating 101 `nav.site-footer__nav > ul.nav-list > li > a`
Developers `nav.site-footer__nav > ul.nav-list > li > a`
Other Integrations `nav.site-footer__nav > ul.nav-list > li > a`

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
With the deprecation of third-party cookies, the rise of the walled gardens, an… `section.panel > div.panel__content > div.trust-text > h4.trust-subheader`
Disqus `div.site-footer__container > nav.site-footer__nav > ul.nav-list > h3.list-header`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.home__wrapper > section.panel > div.panel__content > img.action-icon `div.home__wrapper > section.panel > div.panel__content > img.action-icon`
div.home__wrapper > section.panel > div.panel__content > img.action-icon `div.home__wrapper > section.panel > div.panel__content > img.action-icon`
div.home__wrapper > section.panel > div.panel__content > img.action-icon `div.home__wrapper > section.panel > div.panel__content > img.action-icon`
div.home__wrapper > section.panel > div.panel__content > img.action-icon `div.home__wrapper > section.panel > div.panel__content > img.action-icon`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`
div.panel__content > div.logos-container > div.img__container > img.logo `div.panel__content > div.logos-container > div.img__container > img.logo`

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
Disqus Platform Overview Engagement Moderation & Safety Audience Monetization P… `footer.site-footer > div.site-footer__container > nav.site-footer__nav > ul.nav-list`
Resources Blog Support Knowledge Base Disqus 101 Discuss Disqus Case Studies AP… `footer.site-footer > div.site-footer__container > nav.site-footer__nav > ul.nav-list`
About Us History Mission Culture `footer.site-footer > div.site-footer__container > nav.site-footer__nav > ul.nav-list`
Learn How Does Disqus Work? Community Tips Increase Engagement & Retention Mode… `footer.site-footer > div.site-footer__container > nav.site-footer__nav > ul.nav-list`

These are opportunities to improve the experience of reading tabular or list data using 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

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

●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

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

●Links have a discernible name

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

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○Form elements have associated labels

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

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

1 issue(s) across 65 links and 5 buttons

PASS

1 issue(s) across 65 links and 5 buttons

1 link(s) with generic text

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

Got: https://blog.disqus.com/introducing-the-disqus-sdk-bring-your-community-to-mo… ("Learn More")

1 link(s) open in new tab without warning

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

Got: https://help.disqus.com/en/articles/1717155-use-of-cookies

63 link(s) with descriptive text

65 links

0 empty

1 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://help.disqus.com/en/articles/1717…	Cookie Policy	new tab	Add '(opens in new tab)' to text
https://blog.disqus.com/introducing-the-…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Introducing The Disqus Sdk Bring Your Community To Mobile

68 links and buttons have descriptive text

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

https://blog.disqus.com/introducing-the-disqus-sdk-bring-your-community-to-mo… ("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://help.disqus.com/en/articles/1717155-use-of-cookies

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+

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 More publishers trus…	7.52:1	3.0:1	#000000	#2E9FFF	Pass
h1 The web's largest co…	7.52:1	3.0:1	#000000	#2E9FFF	Pass
h1 Transform your casua…	7.52:1	3.0:1	#000000	#2E9FFF	Pass
h1 Protect your brand a…	7.52:1	3.0:1	#000000	#2E9FFF	Pass
h1 Track and understand…	7.52:1	3.0:1	#000000	#2E9FFF	Pass
h1 Harness the power of…	7.52:1	3.0:1	#000000	#2E9FFF	Pass
h1 Flexible and optimiz…	7.52:1	3.0:1	#000000	#2E9FFF	Pass
h1 Turbocharge audience…	7.52:1	3.0:1	#000000	#2E9FFF	Pass
h2 Enhance Engagement w…	7.52:1	3.0:1	#000000	#2E9FFF	Pass
h3 Disqus	7.52:1	3.0:1	#000000	#2E9FFF	Pass
h3 Resources	7.52:1	3.0:1	#000000	#2E9FFF	Pass
h3 About Us	7.52:1	3.0:1	#000000	#2E9FFF	Pass
h3 Learn	7.52:1	3.0:1	#000000	#2E9FFF	Pass
title #1 in audience engag…	16.36:1	4.5:1	#000000	#DAE8C8	Pass
span Opens in a new windo…	17.06:1	4.5:1	#000000	#E6EBC6	Pass
span Opens an external we…	19.42:1	4.5:1	#000000	#F7F7E8	Pass
span Opens an external we…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span This website utilize…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Cookie Policy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Accept	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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.