Skip to content
https://analog.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
4
REVIEW
8
PASS
1
INFO
0
Checks
13
1 PASS 8 REVIEW 4 FIX
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 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
Warning::
No <nav> landmark found
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 MAIN 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

B
Heading Hierarchy
19 headings, 1 skip(s)
REVIEW
19 headings, 1 skip(s)
Warning::
Multiple H1 headings (6 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.
  • H1 Samana: Simplifying 5G/6G Radio Design
  • H1 Samana: Simplifying 5G/6G Radio Design duplicate H1
  • H1 Quad‑Apollo MxFE™ for X‑Band Beamforming duplicate H1
  • H1 Quad‑Apollo MxFE™ for X‑Band Beamforming duplicate H1
  • H1 Aerospace and Defense Solutions duplicate H1
  • H1 Aerospace and Defense Solutions duplicate H1
  • H3 eShop skipped
  • H3 What We Do (Signals+)
  • H3 ContentZone
  • H2 eShop
  • H2 What We Do (Signals+)
  • H2 ContentZone
  • H2 Featured Resources
  • H3 Newsroom
  • H3 EngineerZone
  • H3 Analog Dialogue
  • H2 {{modalTitle}}
  • H2 {{dropdownTitle}}
  • H3 {{newProjectTitle}}

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

B
Alt Text Quality
1 of 168 images have issues
REVIEW
1 of 168 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
4 image(s) with alt text over 125 characters
Info::
97 decorative image(s) correctly marked
Info::
66 image(s) with good alt text
168 images 66 good alt text 97 decorative 1 missing
IssueCount
missing1 image(s)
too long4 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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
6 icon(s) detected
REVIEW
6 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
h1 Samana: Simplifying 5G/6G Radio Design
2.29:1
#000000
on
#014985
needs 3.0:1 (large text)
32px · top of page (header area) · over background image/gradient
h1 Quad‑Apollo MxFE™ for X‑Band Beamf…
2.29:1
#000000
on
#014985
needs 3.0:1 (large text)
32px · 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 Samana: Simplifying …2.29:13.0:1
#000000
#014985
Fail
h1 Samana: Simplifying …4.50:13.0:1
#000000
#4278AA
Pass
h1 Quad‑Apollo MxFE…6.78:13.0:1
#000000
#8C92A6
Pass
h1 Quad‑Apollo MxFE…2.29:13.0:1
#000000
#014985
Fail
h1 Aerospace and Defens…13.80:13.0:1
#000000
#D3D1D0
Pass
h1 Aerospace and Defens…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 eShop21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What We Do (Signals+…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ContentZone21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured Resources21.00:13.0:1
#000000
#FFFFFF
Pass
h2 {{modalTitle}}21.00:13.0:1
#000000
#FFFFFF
Pass
h2 {{dropdownTitle}}21.00:13.0:1
#000000
#FFFFFF
Pass
h3 eShop21.00:13.0:1
#000000
#FFFFFF
Pass
h3 What We Do (Signals+…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ContentZone21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Newsroom21.00:13.0:1
#000000
#FFFFFF
Pass
h3 EngineerZone21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Analog Dialogue21.00:13.0:1
#000000
#FFFFFF
Pass
h3 {{newProjectTitle}}21.00:13.0:1
#000000
#FFFFFF
Pass
title Mixed-signal and dig…9.94:14.5:1
#000000
#99B6CE
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.

B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 23 passed
REVIEW
86

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 roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Get to Know Us div.image-resource-card__header > div.image-resource-card__header__main > div.image-resource-card__header__main__title > p.title-Large

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
div.image-resource-card__carousel > div#carousel > div.owl-dots > button.owl-dot div.image-resource-card__carousel > div#carousel > div.owl-dots > button.owl-dot
div.image-resource-card__carousel > div#carousel > div.owl-dots > button.owl-dot div.image-resource-card__carousel > div#carousel > div.owl-dots > button.owl-dot
div.image-resource-card__carousel > div#carousel > div.owl-dots > button.owl-dot div.image-resource-card__carousel > div#carousel > div.owl-dots > button.owl-dot

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.image-resource-card__carousel > div#carousel > div.owl-dots > button.owl-dot div.image-resource-card__carousel > div#carousel > div.owl-dots > button.owl-dot
div.image-resource-card__carousel > div#carousel > div.owl-dots > button.owl-dot div.image-resource-card__carousel > div#carousel > div.owl-dots > button.owl-dot
div.image-resource-card__carousel > div#carousel > div.owl-dots > button.owl-dot div.image-resource-card__carousel > div#carousel > div.owl-dots > button.owl-dot

These items highlight common accessibility best practices.

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
Go to myAnalog footer > div#long > div > a#signUpNow
Log In | Sign Up div.acct > div > button#login
沪ICP备09046653号-1 div#short > ul > li > a
○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]` 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
●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 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
●No element has a `[tabindex]` value greater than 0
●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
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○Form elements have associated labels
○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
○`<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.
○Identical links have the same purpose.
○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+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext{{dropdownTitle}}aria-label
inputtext{{newProjectNameText}}aria-label
inputtext{{newProjectDescriptionText}}aria-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback