Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 REVIEW 4 FIX

Link & Button Quality

Action

51 issue(s) across 354 links and 62 buttons

FIX

51 issue(s) across 354 links and 62 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: javascript:void(0);

9 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /en/shop/software-portfolio/nigel.html ("Learn more"); /en/perspectives/breaking-out-of-the-testing-silo.html ("Learn more"); /en/perspectives/always-prepared-for-an-uncertain-future.html ("Learn more"); /en/solutions/5g-6g/5g-isnt-for-you.html ("Learn more"); /en/perspectives/engineering-ambitiously-from-anywhere.html ("Learn more"); /en/perspectives/breaking-out-of-the-testing-silo.html ("Learn more"); /en/perspectives/always-prepared-for-an-uncertain-future.html ("Learn more"); /en/solutions/5g-6g/5g-isnt-for-you.html ("Learn more"); /en/perspectives/engineering-ambitiously-from-anywhere.html ("Learn more")

4 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://survey.ni.com/jfe/form/SV_daMuCfO1or7M5HD?Q_Language=EN; https://www.ni.com/privacy; https://www.onetrust.com/products/cookie-consent/; https://www.ni.com/en/forms/sales-inquiry-request.html

41 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.glide__bullet (#834 on page); button.glide__bullet (#835 on page); button.glide__bullet (#836 on page); button.glide__bullet (#1207 on page); button.glide__bullet (#1208 on page); button.glide__bullet (#1209 on page); button.glide__bullet (#1210 on page); button.glide__bullet (#1239 on page); button.glide__bullet (#1240 on page); button.glide__bullet (#1241 on page) (+31 more)

340 link(s) with descriptive text

354 links

1 empty

9 generic text

4 new tab

41 empty buttons

Element	Text	Issue	Suggested Fix
javascript:void(0);	(empty)	empty	Add link text or aria-label
/en/shop/software-portfolio/nigel.html	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Nigel.Html
/en/perspectives/breaking-out-of-the-tes…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Breaking Out Of The Testing Silo.Html
/en/perspectives/always-prepared-for-an-…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Always Prepared For An Uncertain Future.Html
/en/solutions/5g-6g/5g-isnt-for-you.html	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: 5g Isnt For You.Html
/en/perspectives/engineering-ambitiously…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Engineering Ambitiously From Anywhere.Html
/en/perspectives/breaking-out-of-the-tes…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Breaking Out Of The Testing Silo.Html
/en/perspectives/always-prepared-for-an-…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Always Prepared For An Uncertain Future.Html
/en/solutions/5g-6g/5g-isnt-for-you.html	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: 5g Isnt For You.Html
/en/perspectives/engineering-ambitiously…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Engineering Ambitiously From Anywhere.Html
https://survey.ni.com/jfe/form/SV_daMuCf…	Site Feedback	new tab	Add '(opens in new tab)' to text
//www.ni.com/global-gateway/?rtrn=https%…	Brazil (English)	img no alt	Add alt attribute to the image
https://www.ni.com/privacy	NI Privacy Statement, opens in…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
https://www.ni.com/en/forms/sales-inquir…	Contact Sales	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

361 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

javascript:void(0);

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/en/shop/software-portfolio/nigel.html ("Learn more"); /en/perspectives/breaking-out-of-the-testing-silo.html ("Learn more"); /en/perspectives/always-prepared-for-an-uncertain-future.html ("Learn more"); /en/solutions/5g-6g/5g-isnt-for-you.html ("Learn more"); /en/perspectives/engineering-ambitiously-from-anywhere.html ("Learn more"); /en/perspectives/breaking-out-of-the-testing-silo.html ("Learn more"); /en/perspectives/always-prepared-for-an-uncertain-future.html ("Learn more"); /en/solutions/5g-6g/5g-isnt-for-you.html ("Learn more"); /en/perspectives/engineering-ambitiously-from-anywhere.html ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://survey.ni.com/jfe/form/SV_daMuCfO1or7M5HD?Q_Language=EN; https://www.ni.com/privacy; https://www.onetrust.com/products/cookie-consent/; https://www.ni.com/en/forms/sales-inquiry-request.html

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.glide__bullet (#834 on page); button.glide__bullet (#835 on page); button.glide__bullet (#836 on page); button.glide__bullet (#1207 on page); button.glide__bullet (#1208 on page); button.glide__bullet (#1209 on page); button.glide__bullet (#1210 on page); button.glide__bullet (#1239 on page); button.glide__bullet (#1240 on page); button.glide__bullet (#1241 on page) (+31 more)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #f4f4f4

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

Action

4 landmarks

REVIEW

4 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

No banner (header) landmark

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

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

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

Alt Text Quality

2 of 14 images have issues

REVIEW

2 of 14 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 decorative image(s) correctly marked

10 image(s) with good alt text

14 images 10 good alt text 2 decorative 2 missing

Issue	Count
missing	2 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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Error - Page Error - National Instruments ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Favicon & Branding

9 icon(s) detected

REVIEW

9 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #f4f4f4 Background Color #f4f4f4 Icons 2 icon(s)

Heading Hierarchy

26 headings

PASS

26 headings

Multiple H1 headings (2 found)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 Get AI Development Help with Nigel
H2 Featured products
H2 PXI
H2 LabVIEW+ Suite
H2 CompactDAQ Modules
H2 Simplify Test and Measurement
H3 (empty)
H2 Shop by Application Area
H1 Building on Decades of Innovation duplicate H1
H2 NI Events
H2 NI Connect 2026 Fort Worth
H2 Breaking Out of Testing Silos
H2 Be Prepared for an Uncertain Future
H2 5G Isn't for You
H2 Engineering Ambitiously—from Anywhere
H2 Breaking Out of Testing Silos
H2 Be Prepared for an Uncertain Future
H2 5G Isn't for You
H2 Engineering Ambitiously—from Anywhere
H2 NI Cookie Preferences
H3 Manage Consent Preferences
H4 Strictly Necessary and Exempt Cookies
H4 Performance Cookies
H4 Functional Cookies
H4 Targeting Cookies
H3 Cookie List

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

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

A+

Form Accessibility

All 9 controls labeled

PASS

All 9 controls labeled

9 control(s) properly labeled

9 controls

9 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	text	Search terms	aria-label
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id

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)

Element	Ratio	Required	FG	BG	Result
h1 Get AI Development H…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Building on Decades …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Featured products	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 PXI	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 LabVIEW+ Suite	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 CompactDAQ Modules	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Simplify Test and Me…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop by Application …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 NI Events	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 NI Connect 2026 Fort…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Breaking Out of Test…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Be Prepared for an U…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 5G Isn't for You	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Engineering Ambitiou…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Breaking Out of Test…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Be Prepared for an U…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 5G Isn't for You	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Engineering Ambitiou…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 NI Cookie Preference…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Manage Consent Prefe…	21.00:1	3.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.

Lighthouse Accessibility Audits

Score 90/100 — 3 failing, 30 passed

PASS

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.

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.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`

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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn more `div.ni__copy-and-image-button-container > div.button > a.ni-btn > span.ni-notransform`
Get the job done faster with engineering-specific software for measurement, ana… `section > a.ni__carousel-item > div.ni__carousel-content-container > p.ni__body-text--3`
Contact Sales `body > a#tntContactSalesBtn`

These are opportunities to improve the legibility of your content.

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.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`
div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet `div.ni__carousel-grid-right > div.ni__carousel-bullets > div.glide__bullets > button.glide__bullet`

These items highlight common accessibility best practices.

○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

●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.

●`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

●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.

●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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[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

○Form elements have associated labels

○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>`.

○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.