Skip to content
https://arm.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 1 <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.
B
Form Accessibility
2 of 11 controls have issues
REVIEW
2 of 11 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="range">; <input type="range">
Info::
9 control(s) properly labeled
11 controls
9 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
inputtextSearcharia-label
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting 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
inputrange(none)none
inputrange(none)none

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

<input type="range">; <input type="range">

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

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.

C
Favicon & Branding
Action
17 icon(s) detected
REVIEW
17 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: arm
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name arm ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name arm Display Mode standalone Theme Color #0091BD Background Color #0091BD Icons 2 icon(s)
A+
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "top-navigation" SEARCH MAIN ASIDE CONTENTINFO footer
A+
Heading Hierarchy
41 headings
PASS
41 headings
Info::
Single H1 present
  • H6 Arm Account
  • H1 The future of AI is built on Arm
  • H2 Arm technology is solving some of the greatest challenges for everyone
  • H3 Advancing healthcare
  • H3 Powering innovation
  • H3 Enabling next-gen wearables
  • H2 Latest highlights
  • H3 Build CPUs for AI-driven cloud workloads
  • H3 A new CPU for the age of AI
  • H3 Tech unheard
  • H3 Gemma 4 accelerates on-device AI
  • H3 The story behind the Arm compute platform
  • H3 Advancing healthcare with AI in Ghana
  • H2 Delivering unmatched scale
  • H3 100%
  • H3 350B+
  • H3 22M+
  • H2 Intelligent compute everywhere
  • H3 Cloud & data center High-performance, power-efficient platform for scaling infrastructure.
  • H3 Autonomous machines Performance-driven platform powering safe, real-world autonomy.
  • H3 Mobile & PC AI-first compute platform delivering fast, personalized experiences.
  • H3 Wearables, smart homes & embedded Power-efficient compute bringing always-on intelligence to everyday devices.
  • H2 Powering tomorrow's innovation, today
  • H3 The future of AI infrastructure
  • H3 Intelligence in everyday devices
  • H3 AI in motion
  • H2 High-performance travel
  • H2 Trusted Identification
  • H2 Autonomous Driving
  • H2 Leadership and vision
  • H3 Tech unheard podcasts
  • H3 Shaping the future
  • H3 Arm newsroom
  • H2 Stay connected
  • H2 Personalize Your Experience
  • H3 Manage Consent Preferences
  • H4 Essential Cookies
  • H4 Functional Cookies
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H3 Cookie List
A+
Alt Text Quality
All 109 images OK
PASS
All 109 images OK
Info::
66 decorative image(s) correctly marked
Info::
43 image(s) with good alt text
109 images 43 good alt text 66 decorative
All images have appropriate alt text.
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
h2 Arm technology is so…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Latest highlights18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Delivering unmatched…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Intelligent compute …18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Powering tomorrow's18.10:13.0:1
#000000
#EEEEEE
Pass
h2 innovation, today18.10:13.0:1
#000000
#EEEEEE
Pass
h2 High-performance tra…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Trusted Identificati…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Autonomous Driving18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Leadership and visio…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Stay connected18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Personalize Your Exp…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Advancing healthcare18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Powering innovation18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Enabling next-gen we…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Build CPUs for AI-dr…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 A new CPU for the18.10:13.0:1
#000000
#EEEEEE
Pass
h3 age of AI18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Tech unheard18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Gemma 4 accelerates …18.10:13.0:1
#000000
#EEEEEE
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.

A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 26 passed
PASS
91

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SEARCH div.c-top-navigation-flex > ul.c-top-navigation-tabs > li.c-top-navigation-tab > div.submenu
ARM ACCOUNT Arm Account Log in to access your Arm Account. Login Need an Arm I… div.c-top-navigation-flex > ul.c-top-navigation-tabs > li.c-top-navigation-tab > div.submenu
Products Markets Partners Developers Support & Training Company div.c-top-navigation-flex > ul.c-top-navigation-tabs > li.c-top-navigation-bar > div.submenu

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.

Names and labels

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.c-top-navigation-flex > ul.c-top-navigation-tabs > li.c-top-navigation-bar > a.c-top-navigation-tab-link div.c-top-navigation-flex > ul.c-top-navigation-tabs > li.c-top-navigation-bar > a.c-top-navigation-tab-link

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.

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
Build CPUs for AI-driven cloud workloads   Run AI and cloud workloads effic… div#tns1-iw > div#tns1 > div#tns1-item0 > a.c-carousel-card
A new CPU for the age of AI   Explore how the Arm AGI CPU supports next-gen… div#tns1-iw > div#tns1 > div#tns1-item1 > a.c-carousel-card
○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-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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[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
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` 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
○Links are distinguishable without relying on color.
○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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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