Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 6 REVIEW 3 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

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.

Homepage link present on 404 page

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✓Search Form ✗

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

Hamburger menu detected (responsive design)

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)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Form Accessibility

2 of 3 controls have issues

REVIEW

2 of 3 controls have issues

2 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="number">; <input type="number">

1 control(s) properly labeled

3 controls

1 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
input	checkbox		none
input	number	(none)	none
input	number	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Mobile-Readable Font Sizes

94% of visible text renders at >= 12 CSS px (6 below threshold)

REVIEW

94% of visible text renders at >= 12 CSS px (6 below threshold)

6 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <div> 10.4px ("eDPI"); <div> 10.4px ("Valorant"); <div> 10.4px ("cm / 360°"); <div> 10.4px ("Valorant"); <div> 10.4px ("in / 360°").

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Sens Converter

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

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

Name Sens Converter Display Mode standalone Theme Color #0B0D10 Background Color #0B0D10 Icons 2 icon(s)

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: dark

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: #0b0d10

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta dark ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Sens Converter

1.08:1

#000000

#0B0D10

needs 3.0:1 (large text)

32px · above the fold

h2 Popular conversions

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Extra calculators

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What is Sens Converter?

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How Sens Converter works

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why use Sens Converter

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sens Converter FAQ

1.07:1

#000000

#0A0C0F

needs 3.0:1 (large text)

24px · bottom of viewport

title Sens Converter — Free Mouse Sensitivit…

1.07:1

#000000

#0B0C10

needs 4.5:1 (normal text)

16px · top of page (header area)

span Sens

1.07:1

#000000

#0B0C10

needs 4.5:1 (normal text)

16px · top of page (header area)

span Converter

1.08:1

#000000

#0B0D10

needs 4.5:1 (normal text)

16px · top of page (header area)

a Converter

1.08:1

#000000

#0B0D10

needs 4.5:1 (normal text)

16px · top of page (header area)

button Calculators

1.08:1

#000000

#0B0D10

needs 4.5:1 (normal text)

16px · above the fold

a Games

1.08:1

#000000

#0B0D10

needs 4.5:1 (normal text)

16px · above the fold

a Guides

1.08:1

#000000

#0B0D10

needs 4.5:1 (normal text)

16px · above the fold

span English

1.08:1

#000000

#0B0D10

needs 4.5:1 (normal text)

16px · above the fold

p Free mouse sensitivity converter for 50+…

1.07:1

#000000

#0A0C0F

needs 4.5:1 (normal text)

16px · above the fold

label From game

1.07:1

#000000

#0A0C0F

needs 4.5:1 (normal text)

16px · above the fold

span Valorant

1.07:1

#000000

#0A0C0F

needs 4.5:1 (normal text)

16px · above the fold

label To game

1.07:1

#000000

#0A0C0F

needs 4.5:1 (normal text)

16px · mid-page

span CS2

1.07:1

#000000

#0A0C0F

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Sens Converter	1.08:1	3.0:1	#000000	#0B0D10	Fail
h2 Popular conversions	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Extra calculators	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 What is Sens Convert…	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 How Sens Converter w…	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Why use Sens Convert…	1.07:1	3.0:1	#000000	#0A0C0F	Fail
h2 Sens Converter FAQ	1.07:1	3.0:1	#000000	#0A0C0F	Fail
title Sens Converter — F…	1.07:1	4.5:1	#000000	#0B0C10	Fail
span Sens	1.07:1	4.5:1	#000000	#0B0C10	Fail
span Converter	1.08:1	4.5:1	#000000	#0B0D10	Fail
a Converter	1.08:1	4.5:1	#000000	#0B0D10	Fail
button Calculators	1.08:1	4.5:1	#000000	#0B0D10	Fail
a Games	1.08:1	4.5:1	#000000	#0B0D10	Fail
a Guides	1.08:1	4.5:1	#000000	#0B0D10	Fail
span English	1.08:1	4.5:1	#000000	#0B0D10	Fail
p Free mouse sensitivi…	1.07:1	4.5:1	#000000	#0A0C0F	Fail
label From game	1.07:1	4.5:1	#000000	#0A0C0F	Fail
span Valorant	1.07:1	4.5:1	#000000	#0A0C0F	Fail
label To game	1.07:1	4.5:1	#000000	#0A0C0F	Fail
span CS2	1.07:1	4.5:1	#000000	#0A0C0F	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.

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 22 passed

REVIEW

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
EDPI `div.card > dl.mt-4 > div.rounded-lg > div.text-[0.65rem]`
Valorant `div.card > dl.mt-4 > div.rounded-lg > div.mt-0.5`
CM / 360° `div.card > dl.mt-4 > div.rounded-lg > div.text-[0.65rem]`
Valorant `div.card > dl.mt-4 > div.rounded-lg > div.mt-0.5`
IN / 360° `div.card > dl.mt-4 > div.rounded-lg > div.text-[0.65rem]`
Valorant `div.card > dl.mt-4 > div.rounded-lg > div.mt-0.5`

These are opportunities to improve the legibility of your content.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
EDPI 320 Valorant CM / 360° 40.82 Valorant IN / 360° 16.07 Valorant `div.mx-auto > section.mx-auto > div.card > dl.mt-4`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.card > div.grid > div > input.input `div.card > div.grid > div > input.input`
div.card > div.grid > div > input.input `div.card > div.grid > div > input.input`

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
V Valorant `div.card > div.grid > div.relative > button.input`
C CS2 `div.card > div.grid > div.relative > button.input`

○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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

●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

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with 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

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

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

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

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) 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

A+

Heading Hierarchy

7 headings

PASS

7 headings

Single H1 present

H1 Sens Converter
H2 Popular conversions
H2 Extra calculators
H2 What is Sens Converter?
H2 How Sens Converter works
H2 Why use Sens Converter
H2 Sens Converter FAQ

A+

Heading Text Quality

All 7 heading(s) have substantive, well-formed text

PASS

All 7 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Link & Button Quality

23 links, 9 buttons — all OK

PASS

23 links, 9 buttons — all OK

23 link(s) with descriptive text

23 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

32 links and buttons have descriptive text

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

Favicon & Branding

5 icon(s) detected

PASS

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.