Skip to content
https://brandwatch.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
Alt Text Quality
Action
50 of 60 images have issues
FIX
50 of 60 images have issues
Critical::
50 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
8 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
10 image(s) with good alt text
60 images 10 good alt text 50 missing
IssueCount
missing50 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
5 landmarks
REVIEW
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 header NAV MAIN (missing!) CONTENTINFO footer

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

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
Heading Hierarchy
36 headings, 2 skip(s)
REVIEW
36 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 The most intelligent social suite
  • H2 Consumer Intelligence
  • H2 Social Media Management
  • H2 Influencer Marketing
  • H6 News skipped
  • H5 Big news! Cision has acquired Trajaan. Find out how Brandwatch and Trajaan can help you turn social and search intelligence into action.
  • H4 All-in-one suite for all your social media channels
  • H4 Trusted by thousands of the world’s biggest brands
  • H2 A complementary suite of specialized, best in class tools
  • H4 Conduct deep research skipped
  • H4 Monitor your brand
  • H4 Create winning content
  • H4 Engage with consumers
  • H2 React to the trends that matter
  • H2 Collaborate on data-driven content
  • H2 Shield your brand from threats
  • H2 Manage all channels with ease
  • H2 Get better results and ROI
  • H3 Better audience engagement
  • H3 Take the lead
  • H3 Double the ROI
  • H3 Turn crisis into opportunity
  • H2 “My favourite thing about Brandwatch is the ability to really customize the data. We’re able to customize what we’re looking for and the audiences we’re speaking to.”
  • H2 A solution that fits
  • H3 Use Cases
  • H3 Industries
  • H3 Roles
  • H2 The #1 trusted enterprise solution
  • H2 Book a meetingto get started
  • H2 Cookie consent settings
  • H3 Manage Consent Preferences
  • H4 Advertising Cookies
  • H4 Functionality Cookies
  • H4 Performance Cookies
  • H4 Operationally Necessary 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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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
Lighthouse Accessibility Audits
Score 82/100 — 7 failing, 21 passed
REVIEW
82

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI assistant body.blog > q-focus-sentinel > div
After AI assistant body.blog > q-focus-sentinel > div
AI assistant, start div#qualified-multimodal-host > div
AI assistant, end div#qualified-multimodal-host > div

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
CONTACT ul.df > li.f1 > a.c-tertiary > span.db
SUPPORT ul.df > li.f1 > a.c-tertiary > span.db
Consumer Intelligence li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Social Media Management li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Influencer Marketing li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Media Intelligence & Insights li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Search Intelligence li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
APIs li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Innovation Spotlight li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Blog li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Events li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Webinars li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Reports li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Case Studies li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Guides li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Social Media Glossary li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Brandwatch Academy li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Community li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
About Us li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Careers li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Contact Us li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Press li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Partnerships li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Integrations li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Environmental Commitment li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Awards li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Legal Hub li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
User Privacy Statement li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Author Privacy Statement li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Terms & Conditions li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Information Security li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Gender Pay Gap Report li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Modern Slavery Act Statement li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Do Not Sell My Personal Data li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Cookies Policy li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Customer Support li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Help Center li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Platform Status li.lh-tight > ul.pt1 > li.mb1 > a.c-simple-link-light
Copyright © 2026 Brandwatch. All Rights Reserved. Cision Group Ltd, 7th Floor, … div.l-container > div.l-grid > div.l-grid__item > p.color-text-grey-5
Cookie policy. div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
Manage cookie settings div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-pc-btn-handler

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
Big news! Cision has acquired Trajaan. Find out how Brandwatch and Trajaan can … a.pa5 > div.df-xs > div.ml5-sm > h5.c-heading
Conduct deep research div > div.df > div.df > h4.c-heading

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.c-asset-border-radius > div.w-100 > div > img.w-100 div.c-asset-border-radius > div.w-100 > div > img.w-100
div.color-bg-transparent > div.w-100 > div > img.js-lazy-img div.color-bg-transparent > div.w-100 > div > img.js-lazy-img
div.color-bg-transparent > div.w-100 > div > img.js-lazy-img div.color-bg-transparent > div.w-100 > div > img.js-lazy-img
div.color-bg-transparent > div.w-100 > div > img.js-lazy-img div.color-bg-transparent > div.w-100 > div > img.js-lazy-img
div.relative > div.color-bg-transparent > div.w-100 > img.js-lazy-img div.relative > div.color-bg-transparent > div.w-100 > img.js-lazy-img
div.color-bg-transparent > div.w-100 > div > img.js-lazy-img div.color-bg-transparent > div.w-100 > div > img.js-lazy-img
div.color-bg-grey-2 > div.w-100 > div > img.js-lazy-img div.color-bg-grey-2 > div.w-100 > div > img.js-lazy-img
div.mx-auto > div > div.w-100 > img.w-100 div.mx-auto > div > div.w-100 > img.w-100
div > div.w-100 > div > img.w-100 div > div.w-100 > div > img.w-100
div.absolute--fill > div.color-bg-grey-7 > div.w-100 > img.js-lazy-img div.absolute--fill > div.color-bg-grey-7 > div.w-100 > img.js-lazy-img

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.l-container > div.df > div.df > a.df div.l-container > div.df > div.df > a.df
div.l-grid__item > ul.l-grid > li.l-grid__item > a.color-text-grey-7 div.l-grid__item > ul.l-grid > li.l-grid__item > a.color-text-grey-7
div.l-grid__item > ul.l-grid > li.l-grid__item > a.color-text-grey-7 div.l-grid__item > ul.l-grid > li.l-grid__item > a.color-text-grey-7
div.l-grid__item > ul.l-grid > li.l-grid__item > a.color-text-grey-7 div.l-grid__item > ul.l-grid > li.l-grid__item > a.color-text-grey-7
div.l-grid__item > ul.l-grid > li.l-grid__item > a.color-text-grey-7 div.l-grid__item > ul.l-grid > li.l-grid__item > a.color-text-grey-7
div.l-grid__item > ul.l-grid > li.l-grid__item > a.color-text-grey-7 div.l-grid__item > ul.l-grid > li.l-grid__item > a.color-text-grey-7

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

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
Cookie 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
●`[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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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.
●Deprecated ARIA roles were not used
○`[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
○`<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.
○Identical links have the same purpose.
○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
1 of 9 controls have issues
PASS
1 of 9 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">
Info::
8 control(s) properly labeled
9 controls
8 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0004checkboxAdvertising Cookiesfor/id
#ot-group-id-C0003checkboxFunctionality Cookiesfor/id
#ot-group-id-C0002checkboxPerformance 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
stext(Search...)placeholder only

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

<input type="text" name="s">

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

A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The most21.00:13.0:1
#000000
#FFFFFF
Pass
h1 social suite21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Consumer Intelligenc…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Social Media Managem…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Influencer Marketing21.00:13.0:1
#000000
#FFFFFF
Pass
h2 React to the21.00:13.0:1
#000000
#FFFFFF
Pass
h2 that matter21.00:13.0:1
#000000
#FFFFFF
Pass
h2 on data-driven conte…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Shield your brand fr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 all channels with ea…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get better results a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A solution that21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The21.00:13.0:1
#000000
#FFFFFF
Pass
h2 trusted enterprise s…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Book a meeting21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Cookie consent setti…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Better audience21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Take the21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Double the21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Turn crisis into21.00:13.0: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.

Send Feedback