Skip to content
https://nxp.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Landmark Structure
Action
6 landmarks
FIX
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <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 MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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
No navigation patterns
FIX
No navigation patterns
Info::
4 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 4 <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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not available ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Lighthouse Accessibility Audits
Action
Score 72/100 — 8 failing, 21 passed
REVIEW
72

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
DESIGN FRDM for i.MX 95 Family Ideal for advanced AI acceleration and rich mul… div.homepage-content > div.homepage-slider > div#homepage_slider_v4 > div.carousel-inner

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
DESIGN FRDM for i.MX 95 Family Ideal for advanced AI acceleration and rich mul… div.homepage-content > div.homepage-slider > div#homepage_slider_v4 > div.carousel-inner

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LEARN MORE div.hero > div.hero-body > div.btn-container > a.btn
DISCOVER THE BENEFITS div.primary-topic-item > div.primary-topic-content > div.primary-topic-link > a.btn

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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.whats-new-list > div.whats-new-item > figure.whats-new-img > img.img-responsive div.whats-new-list > div.whats-new-item > figure.whats-new-img > img.img-responsive
div.whats-new-list > div.whats-new-item > figure.whats-new-img > img.img-responsive div.whats-new-list > div.whats-new-item > figure.whats-new-img > img.img-responsive
div.whats-new-list > div.whats-new-item > figure.whats-new-img > img.img-responsive div.whats-new-list > div.whats-new-item > figure.whats-new-img > 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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

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
div#search-component > div.Search__searchContainer--1MPk0 > div#search-input > input#parts div#search-component > div.Search__searchContainer--1MPk0 > div#search-input > input#parts

These are opportunities to improve keyboard navigation in your application.

○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]`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
●Form elements have associated labels
●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
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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 a valid value for its `[lang]` attribute
○`<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
○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.
○Uses ARIA roles only on compatible elements
○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.
A
Heading Hierarchy
52 headings
PASS
52 headings
Warning::
Multiple H1 headings (4 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H3 Products
  • H3 Product Finding Tools
  • H3 Sample and Buy
  • H3 Product Resources
  • H3 Automotive
  • H3 Industrial
  • H3 Consumer
  • H3 Technologies
  • H3 Development Boards and Designs
  • H3 Software
  • H3 Documentation
  • H3 Partner Marketplace
  • H3 Training
  • H3 Support
  • H3 NXP Community
  • H3 Training
  • H3 Sample and Buy
  • H3 About NXP
  • H3 Sustainability
  • H3 Newsroom
  • H3 Investor Relations
  • H3 Events
  • H3 Contact Us
  • H1 Automotive, IoT & Industrial Solutions
  • H1 Build with Zephyr Today duplicate H1
  • H1 FRDM for i.MX 95 Family duplicate H1
  • H1 Cyber Resilience Act (CRA) Training Academy duplicate H1
  • H2 Together, we accelerate the breakthroughs that advance our world.
  • H3 Automotive
  • H3 S32M2 for 12V Motor Control
  • H3 Industrial
  • H3 i.MX 94 Applications Processor
  • H3 Consumer
  • H3 i.MX RT700 Crossover MCU
  • H3 Technologies
  • H3 RW612 Wireless MCU
  • H3 Edge AI
  • H3 FRDM i.MX 8M Plus Development Platform
  • H2 Spotlight on Healthcare
  • H2 Secure, Connected Healthcare Starts Here
  • H3 Securing the Internet of Medical Things: Cybersecurity and Compliance
  • H3 AI Controller for Health Insights (AICHI)
  • H3 Transforming Complexity to Efficiency in Healthcare with RAIN RFID and NFC
  • H3 Securing Medical Devices: FDA and EU‑MDR Cybersecurity with EdgeLock®
  • H2 Start Designing Today with NXP
  • H3 Product Finders
  • H3 Design Resources
  • H3 Ready to gain access to everything NXP?
  • H3 Enabling a Better, More Sustainable World
  • H3 Long-Term Success With R&D Investment
  • H3 Decades of Expertise and Innovation
  • H2 Bright Minds. Bright Futures.

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

A
Alt Text Quality
3 of 9 images have issues
PASS
3 of 9 images have issues
Warning::
3 image(s) with filename as alt text
Info::
6 image(s) with good alt text
9 images 6 good alt text 3 generic
IssueCount
filename3 image(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="parts">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#partstext(Search...)placeholder only

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

<input type="text" name="q" id="parts">

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+
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 Automotive, IoT & In…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Build with Zephyr To…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 FRDM for i.MX 95 Fam…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Cyber Resilience Act…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Together, we acceler…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Spotlight on Healthc…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Secure, Connected He…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Start Designing Toda…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Bright Minds. Bright…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 S32M2 for 12V Motor …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 i.MX 94 Applications…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 i.MX RT700 Crossover…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 RW612 Wireless MCU21.00:13.0:1
#000000
#FFFFFF
Pass
h3 FRDM i.MX 8M Plus De…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Securing the Interne…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AI Controller for He…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Transforming Complex…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Securing Medical Dev…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product Finders21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Design Resources21.00:13.0:1
#000000
#FFFFFF
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.

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

Send Feedback