Skip to content
https://motorola.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
F
404 Error Page
Action
HTTP 500, bare page
FIX
HTTP 500, bare page
Warning::
Unexpected status code: HTTP 500
Expected HTTP 404 but received 500. This may confuse search engine crawlers.
Got: HTTP 500
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 500 ✗Page Title Internal Server Error ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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::
Search functionality detected
Got: role-search
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
29 headings, 1 skip(s)
REVIEW
29 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H2 (empty)
  • H3 (empty)
  • H2 exclusive moto g stylus bundle
  • H2 the icon unfolds its next chapter
  • H2 classic by design. sporty at the core.
  • H1 Recommendations duplicate H1
  • H3 motorola razr ultra skipped
  • H3 motorola razr - 2025
  • H3 moto g power - 2026
  • H3 moto g - 2026
  • H2 Flip into the game with motorola razrfifa world cup 26™ edition
  • H2 Active pen within reach
  • H2 Make it iconic
  • H2 Exceptional fromevery angle
  • H2 Find your edge
  • H2 Stylish yet durable
  • H2 Complete yourexperience
  • H3 moto watch fit
  • H3 moto buds loop - with Crystals by Swarovski
  • H3 Moto Buds+
  • H3 Moto tag Sage Green - 1 pack
  • H2 Moto Care purchase protection
  • H2 Motorola Videos
  • H2 Find your perfect match
  • H3 motorola razr ultra 2025
  • H3 motorola edge - 2025
  • H3 motorola razr+
  • H3 Engineered to be extraordinary. Coming soon.

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

B
Form Accessibility
2 of 10 controls have issues
REVIEW
2 of 10 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="email" name="moto.newsletter.email">
Info::
8 control(s) properly labeled
10 controls
8 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#termscheckboxI agree to receive product information and special promotional offers by email from Motorola, and I confirm that I am 16 years of age or older.Privacy Policyfor/id
moto.first.nametextFirst Namearia-label
moto.last.nametextLast Namearia-label
moto.email.addresstextEmail aria-label
moto.email.optinradioYesaria-label
moto.email.optinradioNoaria-label
moto.contact.privacycheckbox<p style="font-size: 12px;">I agree to receive product information and special promotional offers by email from Motorola, and I confirm that I am 16 years of age or older. <a href="https://www.motorola.com/us/en/legal/privacy-policy" target="_blank" id="">Privacy Policy</a> </p>aria-label
moto.campaign.nametextmoto.campaign.namearia-label
inputtext(Search)placeholder only
moto.newsletter.emailemail(E-mail address)placeholder only

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

<input type="text">; <input type="email" name="moto.newsletter.email">

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
Landmark Structure
14 landmarks
PASS
14 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Main icons" SEARCH MAIN ASIDE "Feedback dialog" CONTENTINFO footer

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

A
Alt Text Quality
6 of 122 images have issues
PASS
6 of 122 images have issues
Warning::
6 image(s) with generic alt text
Info::
75 decorative image(s) correctly marked
Info::
41 image(s) with good alt text
122 images 41 good alt text 75 decorative 6 generic
IssueCount
generic6 image(s)
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 Recommendations18.05:13.0:1
#000000
#EAEEF5
Pass
h2 the icon unfolds18.05:13.0:1
#000000
#EAEEF5
Pass
h2 its next chapter18.05:13.0:1
#000000
#EAEEF5
Pass
h2 Flip into the game18.05:13.0:1
#000000
#EAEEF5
Pass
h2 with motorola razr18.05:13.0:1
#000000
#EAEEF5
Pass
h2 fifa world cup 26™…18.05:13.0:1
#000000
#EAEEF5
Pass
h2 Active pen within re…18.05:13.0:1
#000000
#EAEEF5
Pass
h2 Make it iconic18.05:13.0:1
#000000
#EAEEF5
Pass
h2 Exceptional from18.05:13.0:1
#000000
#EAEEF5
Pass
h2 every angle18.05:13.0:1
#000000
#EAEEF5
Pass
h2 Find your perfect ma…18.05:13.0:1
#000000
#EAEEF5
Pass
h3 motorola razr ultra18.05:13.0:1
#000000
#EAEEF5
Pass
h3 motorola razr - 202518.05:13.0:1
#000000
#EAEEF5
Pass
h3 moto g power - 202618.05:13.0:1
#000000
#EAEEF5
Pass
h3 moto g - 202618.05:13.0:1
#000000
#EAEEF5
Pass
h3 moto watch fit18.05:13.0:1
#000000
#EAEEF5
Pass
h3 moto buds loop - wit…18.05:13.0:1
#000000
#EAEEF5
Pass
h3 Moto Buds+18.05:13.0:1
#000000
#EAEEF5
Pass
h3 Moto tag Sage Green …18.05:13.0:1
#000000
#EAEEF5
Pass
h3 motorola razr ultra …18.05:13.0:1
#000000
#EAEEF5
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 90/100 — 5 failing, 29 passed
PASS
90

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We use cookies and similar technologies to personalize content and ads and anal… body.pc_httl > div#_evidon_banner

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
motorola razr ultra div.recommendation_content > div.recommendation_content_config > div.recommendation_content_description > h3

These are opportunities to improve keyboard navigation in your application.

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
section.gridLayoulSection > div.grid1 > div.allWrapperDiv > a.imgClass section.gridLayoulSection > div.grid1 > div.allWrapperDiv > a.imgClass
section.gridLayoulSection > div.grid1 > div.allWrapperDiv > a.imgClass section.gridLayoulSection > div.grid1 > div.allWrapperDiv > a.imgClass
section.gridLayoulSection > div.grid2 > div.allWrapperDiv > a.imgClass section.gridLayoulSection > div.grid2 > div.allWrapperDiv > a.imgClass
section.gridLayoulSection > div.grid1 > div.allWrapperDiv > a.imgClass section.gridLayoulSection > div.grid1 > div.allWrapperDiv > a.imgClass
section.gridLayoulSection > div.grid1 > div.allWrapperDiv > a.imgClass section.gridLayoulSection > div.grid1 > div.allWrapperDiv > a.imgClass

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn more The official smartphone partner of FIFA Learn more Make the switc… div.catchallv3-gallery > section.carousel > div.carousel__viewport > ol.carousel__track

These are opportunities to improve the experience of reading tabular or list data using 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
exclusive moto g stylus bundle The new moto g stylus - 2026 comes with up to t… div#c87674bfxc0e5-42b8-982a-688e76f990d0 > div.app > section#home-single-banner > a.banner-wrapper
○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
●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
●`[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
●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.
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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.
○`<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.
○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