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 3 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-lwue6b

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://rs-online.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://rs-online.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

No <nav> landmark found

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

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

Link & Button Quality

Action

9 issue(s) across 129 links and 5 buttons

REVIEW

9 issue(s) across 129 links and 5 buttons

9 link(s) with no accessible text

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

Got: https://www.facebook.com/WeAreRSGroupPLC/; https://twitter.com/WeAreRSGroup; https://www.linkedin.com/company/rs-uk-ireland/; https://www.youtube.com/channel/UCad2C5AV8SYqke58Y5wCuCg/; https://www.instagram.com/wearersgroup/; https://www.tiktok.com/@wearersgroup; javascript:void(0); javascript:void(0); javascript:void(0)

1 link(s) open in new tab without warning

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

Got: https://storefront.distrelec.biz/login

119 link(s) with descriptive text

129 links

9 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://storefront.distrelec.biz/login	Distrelec account	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/WeAreRSGroupPLC…	(empty)	empty	Add link text or aria-label
https://twitter.com/WeAreRSGroup	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/rs-uk-i…	(empty)	empty	Add link text or aria-label
https://www.youtube.com/channel/UCad2C5A…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/wearersgroup/	(empty)	empty	Add link text or aria-label
https://www.tiktok.com/@wearersgroup	(empty)	empty	Add link text or aria-label
javascript:void(0)	(empty)	empty	Add link text or aria-label
javascript:void(0)	(empty)	empty	Add link text or aria-label
javascript:void(0)	(empty)	empty	Add link text or aria-label

124 links and buttons have descriptive text

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

https://www.facebook.com/WeAreRSGroupPLC/; https://twitter.com/WeAreRSGroup; https://www.linkedin.com/company/rs-uk-ireland/; https://www.youtube.com/channel/UCad2C5AV8SYqke58Y5wCuCg/; https://www.instagram.com/wearersgroup/; https://www.tiktok.com/@wearersgroup; javascript:void(0); javascript:void(0); 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

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

https://storefront.distrelec.biz/login

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 9 fail WCAG AA

REVIEW

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

11 pass 9 fail WCAG AA 11 pass AA only

title RS: Industrial Solutions and Product Dis…

2.61:1

#000000

#574E4F

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Welcome to RS

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · top of page (header area)

p Distrelec international website customer…

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · top of page (header area)

p - You still have the option to view your…

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · above the fold

a Distrelec account

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · above the fold

p Across the industrial design, manufactur…

3.60:1

#000000

#656565

needs 4.5:1 (normal text)

16px · above the fold

span Austria

3.44:1

#000000

#626262

needs 4.5:1 (normal text)

16px · above the fold

span Azerbaijan

3.44:1

#000000

#626262

needs 4.5:1 (normal text)

16px · above the fold

span Belgium (FR)

3.44:1

#000000

#626262

needs 4.5:1 (normal text)

16px · mid-page

1 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)

Element	Ratio	Required	FG	BG	Result
h1 Welcome to RS Group	3.66:1	3.0:1	#000000	#666666	Pass
h2 Country List	3.44:1	3.0:1	#000000	#626262	Pass
h3 Europe	3.44:1	3.0:1	#000000	#626262	Pass
h3 North America	3.55:1	3.0:1	#000000	#646464	Pass
h3 North Asia	3.55:1	3.0:1	#000000	#646464	Pass
h3 South Asia	3.55:1	3.0:1	#000000	#646464	Pass
h3 Australasia	3.55:1	3.0:1	#000000	#646464	Pass
h3 South America	3.55:1	3.0:1	#000000	#646464	Pass
h3 Africa	3.55:1	3.0:1	#000000	#646464	Pass
h3 Middle East	3.55:1	3.0:1	#000000	#646464	Pass
title RS: Industrial Solut…	2.61:1	4.5:1	#000000	#574E4F	Fail
span Welcome to RS	3.66:1	4.5:1	#000000	#666666	Fail
p Distrelec internatio…	3.66:1	4.5:1	#000000	#666666	Fail
strong Distrelec order hist…	3.66:1	3.0:1	#000000	#666666	Pass
p - You still have the…	3.66:1	4.5:1	#000000	#666666	Fail
a Distrelec account	3.66:1	4.5:1	#000000	#666666	Fail
p Across the industria…	3.60:1	4.5:1	#000000	#656565	Fail
span Austria	3.44:1	4.5:1	#000000	#626262	Fail
span Azerbaijan	3.44:1	4.5:1	#000000	#626262	Fail
span Belgium (FR)	3.44:1	4.5:1	#000000	#626262	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.

A+

Heading Hierarchy

11 headings

PASS

11 headings

Single H1 present

H6 Welcome to RS
H1 Welcome to RS Group
H2 Country List
H3 Europe
H3 North America
H3 North Asia
H3 South Asia
H3 Australasia
H3 South America
H3 Africa
H3 Middle East

A+

Alt Text Quality

All 8 images OK

PASS

All 8 images OK

7 decorative image(s) correctly marked

1 image(s) with good alt text

8 images 1 good alt text 7 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#AdvertisingSlide	checkbox	Advertising	none
#Recommendations and TestingSlide	checkbox	Recommendations	none
#FunctionalitySlide	checkbox	Functionality	none
#AnalyticsSlide	checkbox	Analytics	none

A+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 24 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

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
section.flex > ul.ml-4 > li > a `section.flex > ul.ml-4 > li > a`
section.flex > ul.ml-4 > li > a `section.flex > ul.ml-4 > li > a`
section.flex > ul.ml-4 > li > a `section.flex > ul.ml-4 > li > a`
section.flex > ul.ml-4 > li > a `section.flex > ul.ml-4 > li > a`
section.flex > ul.ml-4 > li > a `section.flex > ul.ml-4 > li > a`
section.flex > ul.ml-4 > li > a `section.flex > ul.ml-4 > li > a`

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.

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
Accept All `div#ensNotifyBanner > div.ensBannerContainer > div.ensButtons > button#ensCloseBanner`

○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]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

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

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

●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

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

○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

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

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