Skip to content
https://blackberry.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
6
REVIEW
1
PASS
6
INFO
0
Checks
13
6 PASS 1 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
8 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 8 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA
title BlackBerry | Secure Communications and Q…
4.42:1
#000000
on
#1371DC
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
4.42:1
#000000
on
#1371DC
needs 4.5:1 (normal text)
16px · top of page (header area)
p Download the State of Secure Communicati…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span Close
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Support
1.41:1
#000000
on
#24282C
needs 4.5:1 (normal text)
16px · above the fold
a Contact BlackBerry
1.44:1
#000000
on
#292929
needs 4.5:1 (normal text)
16px · above the fold
a BlackBerry Secure Communications
1.30:1
#000000
on
#212120
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a QNX
1.12:1
#000000
on
#131211
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 BlackBerry: two divi…17.89:13.0:1
#000000
#EAEDF2
Pass
h2 Every call.
Every …17.19:13.0:1
#000000
#E4E9EE
Pass
h2 True sovereign contr…17.53:13.0:1
#000000
#E7EBEF
Pass
h2 High-assurance relia…17.37:13.0:1
#000000
#E6EAEE
Pass
h2 Foundational softwar…16.29:13.0:1
#000000
#DEE3EB
Pass
h2 A secure foundation …16.29:13.0:1
#000000
#DEE3EB
Pass
h2 High-performance emb…16.29:13.0:1
#000000
#DEE3EB
Pass
h2 Company16.29:13.0:1
#000000
#DEE3EB
Pass
h2 Divisions16.29:13.0:1
#000000
#DEE3EB
Pass
h2 Support16.29:13.0:1
#000000
#DEE3EB
Pass
h2 Legal16.29:13.0:1
#000000
#DEE3EB
Pass
h2 Modern Slavery Act S…16.29:13.0:1
#000000
#DEE3EB
Pass
title BlackBerry | Secure …4.42:14.5:1
#000000
#1371DC
Fail
a Skip to main content4.42:14.5:1
#000000
#1371DC
Fail
p Download the State o…1.00:14.5:1
#000000
#000000
Fail
span Close1.00:14.5:1
#000000
#000000
Fail
a Support1.41:14.5:1
#000000
#24282C
Fail
a Contact BlackBerry1.44:14.5:1
#000000
#292929
Fail
a BlackBerry Secure Co…1.30:14.5:1
#000000
#212120
Fail
a QNX1.12:14.5:1
#000000
#131211
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.

A+
Landmark Structure
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Upper Navigation" MAIN CONTENTINFO footer
A+
Heading Hierarchy
12 headings
PASS
12 headings
Info::
Single H1 present
  • H1 BlackBerry: two divisions focused on security, trust, and innovation.
  • H2 Every call.
Every message. Protected.
  • H2 True sovereign control.
  • H2 High-assurance reliability for every device.
  • H2 Foundational software for automotive systems.
  • H2 A secure foundation for mission-critical industries.
  • H2 High-performance embedded solutions.
  • H2 Company
  • H2 Divisions
  • H2 Support
  • H2 Legal
  • H2 Modern Slavery Act Statements
A
Alt Text Quality
6 of 21 images have issues
PASS
6 of 21 images have issues
Warning::
6 image(s) with generic alt text
Info::
12 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
21 images 3 good alt text 12 decorative 6 generic
IssueCount
generic6 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 28 passed
PASS
100

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.

○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
●`[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.
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback