Skip to content
https://ti.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 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::
1 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 1 <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
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
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 (missing!)

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

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error 404 not found | TI.com ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
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 New products
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Our passion
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Join our team
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our commitment to corporate citizenship
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
title Analog | Embedded processing | Semicondu…
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
a Close
2.21:1
#000000
on
#5E3D3D
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Previous menu
1.36:1
#000000
on
#520000
needs 4.5:1 (normal text)
16px · top of page (header area)
span Internet Explorer is not a supported bro…
2.20:1
#000000
on
#49453D
needs 4.5:1 (normal text)
16px · top of page (header area)
ti-svg-icon close
1.66:1
#000000
on
#3C3123
needs 4.5:1 (normal text)
16px · above the fold
span Menu
1.19:1
#000000
on
#191919
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Products
1.43:1
#000000
on
#29282C
needs 4.5:1 (normal text)
16px · above the fold
a Close
1.20:1
#000000
on
#1E1912
needs 4.5:1 (normal text)
16px · above the fold
a Amplifiers
1.13:1
#000000
on
#18120E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Audio, haptics & piezo
1.53:1
#000000
on
#372B1E
needs 4.5:1 (normal text)
16px · above the fold
a Battery management ICs
1.12:1
#000000
on
#121212
needs 4.5:1 (normal text)
16px · above the fold
a Clocks & timing
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · above the fold
a Data converters
1.10:1
#000000
on
#101010
needs 4.5:1 (normal text)
16px · above the fold
a DLP
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · mid-page
a products
1.09:1
#000000
on
#0E0E0E
needs 4.5:1 (normal text)
16px · mid-page
a Interface
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · mid-page

3 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 New products1.32:13.0:1
#000000
#222222
Fail
h2 Our passion1.32:13.0:1
#000000
#222222
Fail
h2 Join our team1.32:13.0:1
#000000
#222222
Fail
h2 Our commitment to co…1.32:13.0:1
#000000
#222222
Fail
title Analog | Embedded pr…3.66:14.5:1
#000000
#666666
Fail
a Close2.21:14.5:1
#000000
#5E3D3D
Fail
a Previous menu1.36:14.5:1
#000000
#520000
Fail
span Internet Explorer is…2.20:14.5:1
#000000
#49453D
Fail
ti-svg-icon close1.66:14.5:1
#000000
#3C3123
Fail
span Menu1.19:14.5:1
#000000
#191919
Fail
a Products1.43:14.5:1
#000000
#29282C
Fail
a Close1.20:14.5:1
#000000
#1E1912
Fail
a Amplifiers1.13:14.5:1
#000000
#18120E
Fail
a Audio, haptics & pie…1.53:14.5:1
#000000
#372B1E
Fail
a Battery management I…1.12:14.5:1
#000000
#121212
Fail
a Clocks & timing1.11:14.5:1
#000000
#111111
Fail
a Data converters1.10:14.5:1
#000000
#101010
Fail
a DLP1.10:14.5:1
#000000
#0F0F0F
Fail
a products1.09:14.5:1
#000000
#0E0E0E
Fail
a Interface1.08:14.5:1
#000000
#0D0D0D
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 82/100 — 4 failing, 22 passed
REVIEW
82

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
Menu Search myTI Language My cart body.ti-homepage > header#tiResponsiveHeader > nav.ti_p-responsiveHeader-nav-bar > ul.ti_p-responsiveHeader-nav-bar-list

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
button.header-llc-sidesheet-side-sheet-holder button.header-llc-sidesheet-side-sheet-holder

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
a.ti-image-action a.ti-image-action

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
COMPANY BLOG div.u-fullHeight > div.u-centered-minHeight > div.u-font-label > a#news_blog

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]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●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
●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
●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 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
○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.
○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
Info::
Single H1 present
  • H4 Amplifiers
  • H4 Audio, haptics & piezo
  • H4 Battery management ICs
  • H4 Clocks & timing
  • H4 Data converters
  • H4 DLP® products
  • H4 Interface
  • H4 Isolation
  • H4 Logic & voltage translation
  • H4 Microcontrollers (MCUs) & processors
  • H4 Motor drivers
  • H4 Passive & discrete
  • H4 Power management
  • H4 RF & microwave
  • H4 Sensors
  • H4 Switches & multiplexers
  • H4 Wireless connectivity
  • H4 Products by applications or technologies
  • H4 Automotive
  • H4 Communications equipment
  • H4 Data center
  • H4 Industrial
  • H4 Personal electronics
  • H4 Reference designs
  • H4 Technologies
  • H4 Design & development
  • H4 TI E2E™ design support forums
  • H4 Embedded development
  • H4 Design & development tools
  • H4 Educational resources
  • H4 Quality
  • H4 Reliability
  • H4 Certifications & standards
  • H4 Environmental information
  • H4 Quality, reliability and packaging FAQs
  • H4 Popular tools
  • H4 Quality, reliability & packaging data download
  • H4 Buying with TI
  • H4 TI API suites
  • H4 Tools & information
  • H4 Ordering support
  • H4 Company
  • H4 Newsroom
  • H4 Investor relations
  • H4 Corporate citizenship
  • H4 Careers
  • H4 Search
  • H4 Regional preferences
  • H1 New products
  • H2 Our passion
  • H2 Join our team
  • H2 Our commitment to corporate citizenship
A+
Alt Text Quality
All 1 images OK
PASS
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback