Skip to content
https://farnell.com

Accessibility

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

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

F
Heading Hierarchy
Action
101 headings, 7 skip(s)
FIX
101 headings, 7 skip(s)
Warning::
Multiple H1 headings (53 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 WELCOME TO FARNELL GLOBAL
  • H2 WELCOME TO FARNELL GLOBAL
  • H4 Select country or region from the list below: skipped
  • H4 Europe & Africa
  • H4 Asia Pacific
  • H4 Americas
  • H3 Can't find the country you're looking for?
  • H3 Visit our Export Store
  • H1 WHO WE ARE duplicate H1
  • H1 AN AVNET COMPANY duplicate H1
  • H1 OUR BRANDS duplicate H1
  • H1 OUR REGIONAL BRANDS duplicate H1
  • H4 Select country or region from the list below: skipped
  • H4 Europe & Africa
  • H4 Asia Pacific
  • H4 Americas
  • H3 Can't find the country you're looking for?
  • H3 Visit our Export Store
  • H1 ELEMENT14 COMMUNITY duplicate H1
  • H1 OUR GLOBAL REACH duplicate H1
  • H3 3,000 skipped
  • H3 80+
  • H3 20
  • H3 10M
  • H3 3,000+
  • H3 48
  • H3 13
  • H3 890,000
  • H1 OUR HERITAGE duplicate H1
  • H1 1934 duplicate H1
  • H1 1939 duplicate H1
  • H1 1990s duplicate H1
  • H1 1996 duplicate H1
  • H1 2006 duplicate H1
  • H1 2009 duplicate H1
  • H1 2010 duplicate H1
  • H1 2011 duplicate H1
  • H1 2012 duplicate H1
  • H1 2013 duplicate H1
  • H1 2014 duplicate H1
  • H1 2016 duplicate H1
  • H1 2019 duplicate H1
  • H1 2022 duplicate H1
  • H1 1934 duplicate H1
  • H1 1939 duplicate H1
  • H1 1990s duplicate H1
  • H1 1996 duplicate H1
  • H1 2006 duplicate H1
  • H1 2009 duplicate H1
  • H1 2010 duplicate H1
  • H1 2011 duplicate H1
  • H1 2012 duplicate H1
  • H1 2013 duplicate H1
  • H1 2014 duplicate H1
  • H1 2016 duplicate H1
  • H1 2019 duplicate H1
  • H1 2022 duplicate H1
  • H1 2019 duplicate H1
  • H1 2022 duplicate H1
  • H1 OUR SOLUTIONS duplicate H1
  • H1 A WIDE RANGE OF PRODUCTS duplicate H1
  • H1 LEADING SUPPLIERS duplicate H1
  • H1 EXTENSIVE RANGE OF INDUSTRIAL PRODUCTS duplicate H1
  • H1 DEDICATED TEAM AND TECHNICAL SUPPORT duplicate H1
  • H1 OUR VALUE-ADDED SERVICES duplicate H1
  • H1 OUR COMPREHENSIVE TECHNICAL RESOURCES duplicate H1
  • H1 WHY CHOOSE US duplicate H1
  • H1 OUR PEOPLE duplicate H1
  • H1 OUR CORE VALUES duplicate H1
  • H6 Integrity skipped
  • H6 Integrity
  • H6 Customer Focus
  • H6 Customer Focus
  • H6 Ownership
  • H6 Ownership
  • H6 Teamwork
  • H6 Teamwork
  • H6 Inclusiveness
  • H6 Inclusiveness
  • H1 WHY FARNELL? duplicate H1
  • H1 OUR OFFER duplicate H1
  • H5 Hybrid working skipped
  • H5 Insurance plans
  • H5 Pension plans
  • H5 A global employee referral programme
  • H5 Company socials
  • H5 A global mentoring programme
  • H5 The option to buy annual leave
  • H5 Education assistance
  • H5 Employee discounts
  • H5 Wellbeing initiatives
  • H1 DIVERSITY, EQUITY, AND INCLUSION duplicate H1
  • H4 Listen and Learn skipped
  • H4 Education and Awareness
  • H4 Policies and Processes
  • H4 Leadership Commitment
  • H6 Meet the Team skipped
  • H6 Work with us
  • H6 Contact us
  • H1 CORPORATE RESPONSIBILITY duplicate H1
  • H1 GLOBAL CHALLENGES CLOSE TO HOME duplicate H1

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

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

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

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

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

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

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

F
Alt Text Quality
Action
57 of 182 images have issues
FIX
57 of 182 images have issues
Critical::
57 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
4 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
125 image(s) with good alt text
182 images 125 good alt text 57 missing
IssueCount
missing57 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
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 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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
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.
D
Lighthouse Accessibility Audits
Action
Score 68/100 — 7 failing, 13 passed
FIX
68

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.

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
Watch full video div.row > div.col-md-12 > div.video-btn > a.btn
Take me to Newark div.container-fluid > div#localeInterMobile > a.col-11 > span
Join element14 Community div.col-md-12 > div.row > div.col-md-6 > a.join-element14
Newark Electronic founded div.cpc-fea-prods-container-slider > div.timeline > div.timeline-odd > p.heri-font
1934 div.cpc-fea-prods-container-slider > div.timeline > div.timeline-odd > h1
Browse all products div.bg-full-width-inner > div.row > div.col-md-6 > a.browse-all-products
Browse all manufacturers div.bg-full-width-inner > div.row > div.col-md-6 > a.browse-all-manufacturers
Discover more div.bg-full-width-inner > div.row > div.col-md-6 > a.discover-more
Chat now div.bg-full-width-inner > div.row > div.col-md-6 > a.chat-now
Explore more div.bg-full-width-inner > div.row > div.col-md-6 > a.explore-more
Explore more div.bg-full-width-inner > div.row > div.col-md-6 > a.explore-more-tech
Discover more div.minibanner > div.row > div.col-md-6 > a.discover-more-us
Teamwork div.flip-card-inner > div.flip-card-back > div.flp-back > h6.text-white
EMEA div.col-9 > ul.m-t-menu > li > a.mtt-emea
Americas div.col-9 > ul.m-t-menu > li > a.mtt-americas
Asia Pacific div.col-9 > ul.m-t-menu > li > a.mtt-asia
Careers div.alt-product-text-fixed-height > ul.m-t-menu > li > a.careers
Discover more div.col-md-12 > div.row > div.col-md-6 > a.discover-more-esg
Privacy div.footer-quick-links-small > ul.nav > li.nav-item > a.nav-link
Terms of Access div.footer-quick-links-small > ul.nav > li.nav-item > a.nav-link
Legal and Copyright Notices div.footer-quick-links-small > ul.nav > li.nav-item > a.nav-link
Cookies Settings div.footer-quick-links-small > ul.nav > li.nav-item > a.nav-link
An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved. Farnell i… div.container > div.row > div.col-12 > div.site-legal-text
An Avnet Company div.row > div.col-12 > div.site-legal-text > a

These are opportunities to improve the legibility of your content.

Navigation

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
3,000 div.bg-full-width-inner > div.row > div.col-6 > h3.brand-slash-glb
Integrity div.flip-card-inner > div.flip-card-front > div.foundation-logos > h6.pt-1
Hybrid working div.bg-full-width-inner > div.row > div.col-xs-4 > h5.padg-top
Listen and Learn div.col-12 > div.row > div.col-xs-7 > h4.our-gen-cont
Meet the Team div.col-12 > div.row > div.col-9 > h6

These are opportunities to improve keyboard navigation in your application.

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.col-md-12 > div.row > div.col-md-6 > img div.col-md-12 > div.row > div.col-md-6 > img
div.col-md-6 > div.row > div.col-md-4 > img div.col-md-6 > div.row > div.col-md-4 > img
div.col-md-6 > div.row > div.col-md-4 > img div.col-md-6 > div.row > div.col-md-4 > img
div.col-md-6 > div.row > div.col-md-4 > img div.col-md-6 > div.row > div.col-md-4 > img
div.col-md-6 > div.row > div.col-md-12 > img div.col-md-6 > div.row > div.col-md-12 > img
div.col-md-12 > div.row > div.col-md-6 > img.w-100 div.col-md-12 > div.row > div.col-md-6 > img.w-100
div.cpc-fea-prods-container-slider > div.timeline > div.timeline-odd-icon > img.icon-sz div.cpc-fea-prods-container-slider > div.timeline > div.timeline-odd-icon > img.icon-sz
div#demo2 > a.carousel-control-prev > span.carousel-control-prev-icon > img.sz-lf-arrow div#demo2 > a.carousel-control-prev > span.carousel-control-prev-icon > img.sz-lf-arrow
div#demo2 > a.carousel-control-next > span.carousel-control-next-icon > img.sz-arrow div#demo2 > a.carousel-control-next > span.carousel-control-next-icon > img.sz-arrow
div.bg-full-width-inner > div.row > div.col-md-6 > img.w-100 div.bg-full-width-inner > div.row > div.col-md-6 > img.w-100
div.bg-full-width-inner > div.row > div.col-md-6 > img.w-100 div.bg-full-width-inner > div.row > div.col-md-6 > img.w-100
div.bg-full-width-inner > div.row > div.col-md-6 > img.w-100 div.bg-full-width-inner > div.row > div.col-md-6 > img.w-100
div.bg-full-width-inner > div.row > div.col-md-6 > img.w-100 div.bg-full-width-inner > div.row > div.col-md-6 > img.w-100
div.bg-full-width-inner > div.row > div.col-md-6 > img.w-100 div.bg-full-width-inner > div.row > div.col-md-6 > img.w-100
div.bg-full-width-inner > div.row > div.col-md-6 > img.w-100 div.bg-full-width-inner > div.row > div.col-md-6 > img.w-100
div.bg-full-width-inner > div.row > div.col-md-12 > img.w-100 div.bg-full-width-inner > div.row > div.col-md-12 > img.w-100
div.flip-card-inner > div.flip-card-front > div.foundation-logos > img.icon-cust div.flip-card-inner > div.flip-card-front > div.foundation-logos > img.icon-cust
div.flip-card-inner > div.flip-card-front > div.foundation-logos > img.icon-cust div.flip-card-inner > div.flip-card-front > div.foundation-logos > img.icon-cust
div.flip-card-inner > div.flip-card-front > div.foundation-logos > img.icon-cust div.flip-card-inner > div.flip-card-front > div.foundation-logos > img.icon-cust
div.flip-card-inner > div.flip-card-front > div.foundation-logos > img.icon-cust div.flip-card-inner > div.flip-card-front > div.foundation-logos > img.icon-cust
div.flip-card-inner > div.flip-card-front > div.foundation-logos > img.icon-cust div.flip-card-inner > div.flip-card-front > div.foundation-logos > img.icon-cust
div.col-md-12 > div.row > div.col-md-6 > img.w-100 div.col-md-12 > div.row > div.col-md-6 > img.w-100
div.row > div.col-xs-4 > div > img.we-offer-icon-ht div.row > div.col-xs-4 > div > img.we-offer-icon-ht
div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht
div.row > div.col-xs-4 > div > img.we-offer-icon-ht div.row > div.col-xs-4 > div > img.we-offer-icon-ht
div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht
div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht
div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht
div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht
div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht
div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht
div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht div.row > div.col-xs-4 > div.we-offer-icon > img.we-offer-icon-ht
div.col-md-6 > div.row > div.col-md-6 > img.w-100 div.col-md-6 > div.row > div.col-md-6 > img.w-100
div.col-md-6 > div.row > div.col-md-6 > img.w-100 div.col-md-6 > div.row > div.col-md-6 > img.w-100
div.col-md-6 > div.row > div.col-md-6 > img.w-100 div.col-md-6 > div.row > div.col-md-6 > img.w-100
div.col-md-6 > div.row > div.col-md-6 > img.w-100 div.col-md-6 > div.row > div.col-md-6 > img.w-100
div.col-12 > div.row > div.col-xs-5 > img.img div.col-12 > div.row > div.col-xs-5 > img.img
div.col-12 > div.row > div.col-xs-5 > img.img div.col-12 > div.row > div.col-xs-5 > img.img
div.col-12 > div.row > div.col-xs-5 > img.img div.col-12 > div.row > div.col-xs-5 > img.img
div.col-12 > div.row > div.col-xs-5 > img.img div.col-12 > div.row > div.col-xs-5 > img.img
div.col-12 > div.row > div.col-3 > img.img div.col-12 > div.row > div.col-3 > img.img
div.col-12 > div.row > div.col-3 > img.img div.col-12 > div.row > div.col-3 > img.img
div.col-12 > div.row > div.col-3 > img.img div.col-12 > div.row > div.col-3 > img.img
div.col-md-6 > div.row > div.col-md-4 > img.w-100 div.col-md-6 > div.row > div.col-md-4 > img.w-100
div.col-md-6 > div.row > div.col-md-4 > img.w-100 div.col-md-6 > div.row > div.col-md-4 > img.w-100
div.col-md-6 > div.row > div.col-md-4 > img.w-100 div.col-md-6 > div.row > div.col-md-4 > img.w-100

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
div.container-fluid > div.container > div#demo2 > a.carousel-control-prev div.container-fluid > div.container > div#demo2 > a.carousel-control-prev
div.container-fluid > div.container > div#demo2 > a.carousel-control-next div.container-fluid > div.container > div#demo2 > a.carousel-control-next

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
WHO WE ARE nav > ul.menu-links > li > a.who-we-are
OUR BRANDS nav > ul.menu-links > li > a.our-brands
OUR GLOBAL REACH nav > ul.menu-links > li > a.our-global-reach
OUR HERITAGE nav > ul.menu-links > li > a.our-Heritage
OUR SOLUTIONS nav > ul.menu-links > li > a.our-solutions
OUR PEOPLE nav > ul.menu-links > li > a.our-people
CORPORATE RESPONSIBILITY nav > ul.menu-links > li > a.esg
Americas: HRNow@Avnet.com div.col-9 > div.alt-product-text-fixed-height > p.contact-us > a
ASIA: HRNow.ASIA@Avnet.com div.col-9 > div.alt-product-text-fixed-height > p.contact-us > a

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.

○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●`[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 use only permitted ARIA attributes
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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
○Buttons have an accessible name
○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
○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
○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.
○No element has a `[tabindex]` value greater than 0
○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+
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
#bypassDesktopcheckboxBypass this page in the futurefor/id
#bypassMobilecheckboxBypass this page in the futurefor/id
#bypassMobilecheckboxBypass this page in the futurefor/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)
ElementRatioRequiredFGBGResult
h1 WELCOME TO FARNELL G…17.79:13.0:1
#000000
#ECECED
Pass
h1 WHO WE ARE21.00:13.0:1
#000000
#FFFFFF
Pass
h1 AN AVNET COMPANY21.00:13.0:1
#000000
#FFFFFF
Pass
h1 OUR BRANDS21.00:13.0:1
#000000
#FFFFFF
Pass
h1 OUR REGIONAL BRANDS21.00:13.0:1
#000000
#FFFFFF
Pass
h1 ELEMENT14 COMMUNITY21.00:13.0:1
#000000
#FFFFFF
Pass
h1 OUR GLOBAL REACH21.00:13.0:1
#000000
#FFFFFF
Pass
h1 OUR HERITAGE21.00:13.0:1
#000000
#FFFFFF
Pass
h1 193421.00:13.0:1
#000000
#FFFFFF
Pass
h1 193921.00:13.0:1
#000000
#FFFFFF
Pass
h1 1990s21.00:13.0:1
#000000
#FFFFFF
Pass
h1 199621.00:13.0:1
#000000
#FFFFFF
Pass
h1 200621.00:13.0:1
#000000
#FFFFFF
Pass
h1 200921.00:13.0:1
#000000
#FFFFFF
Pass
h1 201021.00:13.0:1
#000000
#FFFFFF
Pass
h1 201121.00:13.0:1
#000000
#FFFFFF
Pass
h1 201221.00:13.0:1
#000000
#FFFFFF
Pass
h1 201321.00:13.0:1
#000000
#FFFFFF
Pass
h1 201421.00:13.0:1
#000000
#FFFFFF
Pass
h1 201621.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