Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 5 REVIEW 6 FIX

Alt Text Quality

Action

11 of 54 images have issues

FIX

11 of 54 images have issues

8 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image(s) with generic alt text

3 decorative image(s) correctly marked

40 image(s) with good alt text

54 images 40 good alt text 3 decorative 3 generic 8 missing

Issue	Count
missing	8 image(s)
generic	3 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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://cision.com/site.webmanifest contains invalid JSON. Browsers cannot parse it.

Got: https://cision.com/site.webmanifest

Manifest contains invalid JSON.

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 ✗

Heading Hierarchy

Action

13 headings, 2 skip(s)

REVIEW

13 headings, 2 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H2 → H4 (missing H3)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 CisionOne
H3 Media Monitoring skipped
H3 Instant Insights & Reporting
H3 Journalist Outreach
H3 Social Listening
H2 The leading platform for media professionals
H2 Resources
H2 Ready to see CisionOne in action?
H4 Speak to an expert skipped
H4 Speak to an expert
H4 Speak to an expert
H3 (empty)
H3 Do not sell or share my personal information

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Link & Button Quality

Action

36 issue(s) across 174 links and 12 buttons

REVIEW

36 issue(s) across 174 links and 12 buttons

36 link(s) with no accessible text

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

Got: javascript:;; /media-monitoring/; /instant-insights-and-reporting/; /journalist-outreach/; /social-listening-and-management/; a (#562 on page); a (#565 on page); a (#568 on page); a (#571 on page); a (#574 on page) (+26 more)

7 link(s) open in new tab without warning

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

Got: https://www.brandwatch.com; https://www.brandwatch.com/; https://gdpr.cision.com/dataprivacynotice_customersprospects; https://www.linkedin.com/company/cision; https://twitter.com/cision; https://www.instagram.com/cisionglobal; https://www.facebook.com/CisionGlobal

131 link(s) with descriptive text

174 links

36 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.brandwatch.com	Brandwatch	new tab	Add '(opens in new tab)' to text
https://www.brandwatch.com/	Brandwatch	new tab	Add '(opens in new tab)' to text
javascript:;	(empty)	empty	Add link text or aria-label
/media-monitoring/	(empty)	empty	Add link text or aria-label
/instant-insights-and-reporting/	(empty)	empty	Add link text or aria-label
/journalist-outreach/	(empty)	empty	Add link text or aria-label
/social-listening-and-management/	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
/resources/guides-and-reports/complete-g…	(empty)	empty	Add link text or aria-label
/resources/guides-and-reports/complete-g…	(empty)	empty	Add link text or aria-label
/resources/guides-and-reports/complete-g…	(empty)	empty	Add link text or aria-label
/resources/guides-and-reports/public-aff…	(empty)	empty	Add link text or aria-label
https://gdpr.cision.com/dataprivacynotic…	Privacy Notice.	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/cision	linkedin	new tab	Add '(opens in new tab)' to text
https://twitter.com/cision	twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/cisionglobal	instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/CisionGlobal	facebook	new tab	Add '(opens in new tab)' to text

143 links and buttons have descriptive text

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

javascript:;; /media-monitoring/; /instant-insights-and-reporting/; /journalist-outreach/; /social-listening-and-management/; a (#562 on page); a (#565 on page); a (#568 on page); a (#571 on page); a (#574 on page) (+26 more)

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

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

https://www.brandwatch.com; https://www.brandwatch.com/; https://gdpr.cision.com/dataprivacynotice_customersprospects; https://www.linkedin.com/company/cision; https://twitter.com/cision; https://www.instagram.com/cisionglobal; https://www.facebook.com/CisionGlobal

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

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 13 fail WCAG AA

REVIEW

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

7 pass 13 fail WCAG AA 1 pass AA only

h1 CisionOne

1.40:1

#000000

#16215B

needs 3.0:1 (large text)

32px · bottom of viewport

h2 The leading platform for media professio…

1.40:1

#000000

#16215B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Resources

1.40:1

#000000

#16215B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to see CisionOne in action?

1.40:1

#000000

#16215B

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Media Monitoring

1.40:1

#000000

#16215B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Instant Insights & Reporting

1.40:1

#000000

#16215B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Journalist Outreach

1.40:1

#000000

#16215B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Social Listening

1.40:1

#000000

#16215B

needs 3.0:1 (large text)

19px · bottom of viewport

a Platform

1.40:1

#000000

#16215B

needs 4.5:1 (normal text)

16px · above the fold

a CisionOne

1.40:1

#000000

#16215B

needs 4.5:1 (normal text)

16px · above the fold

span All in one, real time communications pla…

1.40:1

#000000

#16215B

needs 4.5:1 (normal text)

16px · above the fold

a Media Monitoring

1.40:1

#000000

#16215B

needs 4.5:1 (normal text)

16px · above the fold

a Instant Insights & Reporting

1.40:1

#000000

#16215B

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 CisionOne	1.40:1	3.0:1	#000000	#16215B	Fail
h2 The leading platform…	1.40:1	3.0:1	#000000	#16215B	Fail
h2 Resources	1.40:1	3.0:1	#000000	#16215B	Fail
h2 Ready to see CisionO…	1.40:1	3.0:1	#000000	#16215B	Fail
h3 Media Monitoring	1.40:1	3.0:1	#000000	#16215B	Fail
h3 Instant Insights & R…	1.40:1	3.0:1	#000000	#16215B	Fail
h3 Journalist Outreach	1.40:1	3.0:1	#000000	#16215B	Fail
h3 Social Listening	1.40:1	3.0:1	#000000	#16215B	Fail
title Cision: AI-Powered M…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a ___	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip Navigation	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Accessibility Statem…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
strong Inside PR 2026 Repor…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
div 500+ PR pros reveale…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Get the Report	5.00:1	4.5:1	#000000	#737A9D	Pass
a Platform	1.40:1	4.5:1	#000000	#16215B	Fail
a CisionOne	1.40:1	4.5:1	#000000	#16215B	Fail
span All in one, real tim…	1.40:1	4.5:1	#000000	#16215B	Fail
a Media Monitoring	1.40:1	4.5:1	#000000	#16215B	Fail
a Instant Insights & R…	1.40:1	4.5:1	#000000	#16215B	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.

Lighthouse Accessibility Audits

Score 86/100 — 4 failing, 26 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.

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#basepage-d474595ca0 > q-focus-sentinel > div`
After AI assistant `body#basepage-d474595ca0 > 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.

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
Media Monitoring `div.hero-card-container > div.hero-card > div.hero-card-content > h3`
Speak to an expert `div#multipartfirst > div.elq-field-style > div.flex-container > h4.elq-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.hero-card-container > div.hero-card > div.DAMimage > img `div.hero-card-container > div.hero-card > div.DAMimage > img`
div.hero-card-container > div.hero-card > div.DAMimage > img `div.hero-card-container > div.hero-card > div.DAMimage > img`
div.hero-card-container > div.hero-card > div.DAMimage > img `div.hero-card-container > div.hero-card > div.DAMimage > img`
div.hero-card-container > div.hero-card > div.DAMimage > img `div.hero-card-container > div.hero-card > div.DAMimage > img`
div.carousel-slide > div.card > div.logo-image > img `div.carousel-slide > div.card > div.logo-image > 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.wrapper > div.column > div.logo > a.first-focusable-element `div.wrapper > div.column > div.logo > a.first-focusable-element`
div.wrapper > div.hero-card-container > div.hero-card > a `div.wrapper > div.hero-card-container > div.hero-card > a`
div.wrapper > div.hero-card-container > div.hero-card > a `div.wrapper > div.hero-card-container > div.hero-card > a`
div.wrapper > div.hero-card-container > div.hero-card > a `div.wrapper > div.hero-card-container > div.hero-card > a`
div.wrapper > div.hero-card-container > div.hero-card > a `div.wrapper > div.hero-card-container > div.hero-card > a`
div.owl-stage > div.owl-item > div.carousel-slide > a `div.owl-stage > div.owl-item > div.carousel-slide > a`
div.wrapper > div.top > div.logo > a `div.wrapper > div.top > div.logo > 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

●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

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Background and foreground colors have a sufficient contrast ratio

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

●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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○Tables have different content in the summary attribute and `<caption>`.

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

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

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

Form Accessibility

1 of 12 controls have issues

PASS

1 of 12 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

11 control(s) properly labeled

12 controls

11 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#emailAddress	email	Email Address*	for/id
#company	text	Company *	for/id
#jobtitle	select	Job Title *	for/id
#jobrole	select	Job Role *	for/id
#firstName	text	First Name *	for/id
#lastName	text	Last Name *	for/id
#country	select	Country *	for/id
#busPhone	tel	Phone Number *	for/id
#contentDemoRequest	select	Yes, I Would like a Free Demo. Please Contact Me.	none
#gDPROptIn1	checkbox	* By clicking here, you agree that Cision may use your information to contact you with marketing communications (newsletters, webinar invitations, event invitations, product information and educational resources). You can unsubscribe via a link in the footer of all marketing emails. By submitting your information to Cision, you are verifying that you have read and agree to our Privacy Notice.	for/id
#optin	checkbox	By clicking here, you agree that Cision may use your information to contact you with marketing communications (newsletters, webinar invitations, event invitations, product information and educational resources). You can unsubscribe via a link in the footer of all marketing emails. By submitting your information to Cision, you are verifying that you have read and agree to our Privacy Notice.	for/id
#g-recaptcha-response-100000	textarea	(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

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