Skip to content
https://mediaroom.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-wo39i0
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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 Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://mediaroom.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://mediaroom.com/manifest.json

Manifest contains invalid JSON.

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::
6 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 6 <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.
B
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
1 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 "primary" MAIN CONTENTINFO footer

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

B
Heading Hierarchy
67 headings, 1 skip(s)
REVIEW
67 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Browse News Releases
  • H2 News Releases Overview
  • H2 Multimedia Gallery
  • H2 Multimedia Gallery Overview
  • H2 Trending Topics
  • H2 Auto & Transportation
  • H2 Auto & Transportation Overview
  • H2 View All Auto & Transportation
  • H2 Business Technology
  • H2 Business Technology Overview
  • H2 View All Business Technology
  • H2 Entertain­ment & Media
  • H2 Entertain­ment & Media Overview
  • H2 View All Entertain­ment & Media
  • H2 Financial Services & Investing
  • H2 Financial Services & Investing Overview
  • H2 View All Financial Services & Investing
  • H2 General Business
  • H2 General Business Overview
  • H2 View All General Business
  • H2 Consumer Technology
  • H2 Consumer Technology Overview
  • H2 View All Consumer Technology
  • H2 Energy & Natural Resources
  • H2 Energy & Natural Resources Overview
  • H2 View All Energy & Natural Resources
  • H2 Environ­ment
  • H2 Environ­ment Overview
  • H2 View All Environ­ment
  • H2 Heavy Industry & Manufacturing
  • H2 Heavy Industry & Manufacturing Overview
  • H2 View All Heavy Industry & Manufacturing
  • H2 Telecomm­unications
  • H2 Telecomm­unications Overview
  • H2 View All Telecomm­unications
  • H2 Consumer Products & Retail
  • H2 Consumer Products & Retail Overview
  • H2 View All Consumer Products & Retail
  • H2 Entertain­ment & Media
  • H2 Entertain­ment & Media Overview
  • H2 View All Entertain­ment & Media
  • H2 Health
  • H2 Health Overview
  • H2 View All Health
  • H2 Sports
  • H2 Sports Overview
  • H2 View All Sports
  • H2 Travel
  • H2 Travel Overview
  • H2 View All Travel
  • H2 Policy & Public Interest
  • H2 Policy & Public Interest Overview
  • H2 View All Policy & Public Interest
  • H2 People & Culture
  • H2 People & Culture Overview
  • H2 View All People & Culture
  • H1 Empower your team and own your narrative with a powerful, scalable online newsroom
  • H3 (empty)
  • H3 "We've always had a news release page on our external site that was managed by PR Newswire. Anytime TD would have a news release, PR Newswire would automatically post that news release on our website.
  • H2 Ready to Get Started?
  • H2 Contact PR Newswire
  • H2 Products
  • H2 About
  • H2 My Services
  • H2 Contact PR Newswire
  • H2 Products
  • H2 About

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

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Empower your team and own your narrative…
1.69:1
#000000
on
#063369
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Ready to Get Started?
1.69:1
#000000
on
#063369
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Contact PR Newswire
1.69:1
#000000
on
#063369
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Products
1.69:1
#000000
on
#063369
needs 3.0:1 (large text)
24px · bottom of viewport
h2 About
1.69:1
#000000
on
#063369
needs 3.0:1 (large text)
24px · bottom of viewport
h2 My Services
1.69:1
#000000
on
#063369
needs 3.0:1 (large text)
24px · bottom of viewport
h3 "We've always had a news release page on…
1.69:1
#000000
on
#063369
needs 3.0:1 (large text)
19px · bottom of viewport
title MediaRoom: Online Newsroom Design | PR N…
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · top of page (header area)
span Close menu
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · top of page (header area)
a News
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · top of page (header area)
a Products
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · top of page (header area)
a Contact
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · above the fold
a Send a Release
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · above the fold
a Client Login
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · above the fold
a Resources
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · above the fold
a Blog
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · above the fold
a Journalists
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · above the fold
a RSS
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · above the fold
span News in Focus
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · above the fold
span Business & Money
1.69:1
#000000
on
#063369
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Empower your team an…1.69:13.0:1
#000000
#063369
Fail
h2 Ready to Get Started…1.69:13.0:1
#000000
#063369
Fail
h2 Contact PR Newswire1.69:13.0:1
#000000
#063369
Fail
h2 Products1.69:13.0:1
#000000
#063369
Fail
h2 About1.69:13.0:1
#000000
#063369
Fail
h2 My Services1.69:13.0:1
#000000
#063369
Fail
h3 "We've always had a …1.69:13.0:1
#000000
#063369
Fail
title MediaRoom: Online Ne…1.69:14.5:1
#000000
#063369
Fail
span Close menu1.69:14.5:1
#000000
#063369
Fail
a News1.69:14.5:1
#000000
#063369
Fail
a Products1.69:14.5:1
#000000
#063369
Fail
a Contact1.69:14.5:1
#000000
#063369
Fail
a Send a Release1.69:14.5:1
#000000
#063369
Fail
a Client Login1.69:14.5:1
#000000
#063369
Fail
a Resources1.69:14.5:1
#000000
#063369
Fail
a Blog1.69:14.5:1
#000000
#063369
Fail
a Journalists1.69:14.5:1
#000000
#063369
Fail
a RSS1.69:14.5:1
#000000
#063369
Fail
span News in Focus1.69:14.5:1
#000000
#063369
Fail
span Business & Money1.69:14.5:1
#000000
#063369
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 89/100 — 4 failing, 29 passed
REVIEW
89

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.prncom > q-focus-sentinel > div
After AI assistant body.prncom > 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
  div.row > div.col-sm-12 > div.text-white > h3

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.row > div.col-xs-12 > div.rightCol > img.img-responsive div.row > div.col-xs-12 > div.rightCol > img.img-responsive

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Notice. div.form-group > div#divTC > p > a

These are opportunities to improve the legibility of your content.

○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.
●Select elements have associated label elements.
●`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
●ARIA input fields have accessible names
●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 have a discernible name
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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>`.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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
Alt Text Quality
1 of 6 images have issues
PASS
1 of 6 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
3 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
6 images 2 good alt text 3 decorative 1 missing
IssueCount
missing1 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

A
Form Accessibility
1 of 15 controls have issues
PASS
1 of 15 controls have issues
Critical::
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">
Info::
14 control(s) properly labeled
15 controls
14 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#sitesearchboxtextSearchfor/id
#mobileSiteSearchboxtextSearch News Releasesaria-label
#firstNametext*First Name:for/id
#lastNametext*Last Name:for/id
#emailAddressemail*Company Email:for/id
#busPhonetel*Business Phone:for/id
#jobroleselect*Job Role:for/id
#jobtitleselect*Job Title:for/id
#countryselect*Country:for/id
#companytext*Company:for/id
#stateselect*State:for/id
#dropdownMenuselectMain Product of Interest:for/id
#gDPROptIn1checkbox* Cision may use your details to contact you with marketing communications (newsletters, webinar invitations, event invitations, product information and educational resources). For more information, please see our Privacy Notice.for/id
#optincheckboxBy submitting your information, 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 our marketing emails. For more information, please see our Privacy Notice.for/id
#g-recaptcha-response-100000textarea(none)none

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

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

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.

Send Feedback