Skip to content
https://everything.adamnordling.se

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
24
14 PASS 4 REVIEW 6 FIX
F
Form Accessibility
Action
16 of 35 controls have issues
FIX
16 of 35 controls have issues
Critical::
8 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="file" id="backup-file-input">; <select id="tz-source-select">; <input type="date" id="deadline-input-date">; <select id="yt-video-quality">; <input type="range" id="yt-volume-slider">; <input type="number" id="yt-volume-number">; <textarea id="yt-command-output">; <select id="tz-picker-select">
Warning::
8 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="number" id="tz-hour-input">; <input type="number" id="tz-min-input">; <textarea id="scratchpad-textarea">; <input id="deadline-input-title">; <input id="daily-task-input">; <input id="habit-add-input">; <input id="yt-url-input">; <input type="text" id="winopt-spec-paste-input">
Info::
19 control(s) properly labeled
35 controls
19 labeled
8 placeholder only
8 unlabeled
ControlTypeLabelMethod
#yt-mode-singleradionone
#yt-mode-playlistradionone
#yt-media-typeselectMedia Channelfor/id
#yt-audio-formatselectAudio Codec / Filetypefor/id
#yt-video-formatselectContainer & Resolutionfor/id
#yt-trim-togglecheckboxnone
#yt-trim-startinputStart Time (HH:MM:SS):for/id
#yt-trim-endinputEnd Time (HH:MM:SS):for/id
#yt-pl-ignore-errorscheckboxnone
#yt-pl-startnumberStart Index:for/id
#yt-pl-endnumberEnd Index (0 = All):for/id
#winopt-os-selectselectOS TARGETfor/id
#winopt-mobo-selectselectMOTHERBOARD & BIOS PLATFORMfor/id
#winopt-cpu-selectselectCPU ARCHITECTUREfor/id
#winopt-gpu-selectselectGRAPHICS CARDfor/id
#winopt-ram-selectselectMEMORY (RAM) PROFILEfor/id
#coord-lat-inputnumberLatitude:for/id
#coord-lon-inputnumberLongitude:for/id
#coord-name-inputinputLocation Name:for/id
#habit-add-inputinput(Add new morning habit...)placeholder only
#yt-url-inputinput(Paste YouTube video or playlist URL (auto-detects instantly))placeholder only
#tz-hour-inputnumber(00)placeholder only
#tz-min-inputnumber(00)placeholder only
#winopt-spec-paste-inputtext(Paste command output here to auto-detect your exact components...)placeholder only
#scratchpad-textareatextarea(Quickly paste terminal outputs, JSON, API keys, or temporary notes... (Auto-saved))placeholder only
#deadline-input-titleinput(New deadline task...)placeholder only
#daily-task-inputinput(Enter a task and press Enter...)placeholder only
#yt-volume-numbernumber(none)none
#yt-video-qualityselect(none)none
#deadline-input-datedate(none)none
#backup-file-inputfile(none)none
#yt-command-outputtextarea(none)none
#tz-source-selectselect(none)none
#yt-volume-sliderrange(none)none
#tz-picker-selectselect(none)none

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

<input type="file" id="backup-file-input">; <select id="tz-source-select">; <input type="date" id="deadline-input-date">; <select id="yt-video-quality">; <input type="range" id="yt-volume-slider">; <input type="number" id="yt-volume-number">; <textarea id="yt-command-output">; <select id="tz-picker-select">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="number" id="tz-hour-input">; <input type="number" id="tz-min-input">; <textarea id="scratchpad-textarea">; <input id="deadline-input-title">; <input id="daily-task-input">; <input id="habit-add-input">; <input id="yt-url-input">; <input type="text" id="winopt-spec-paste-input">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

D
Mobile-Readable Font Sizes
Action
34% of visible text renders at >= 12 CSS px (130 below threshold)
FIX
34% of visible text renders at >= 12 CSS px (130 below threshold)
Warning::
130 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: <span> 11.2px ("Developer & Utility Suite"); <div> 10.4px ("OVERVIEW"); <div> 10.4px ("UTILITIES & TOOLS"); <span> 9.6px ("Soon"); <span> 9.6px ("Soon").
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-mc8bey
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.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://everything.adamnordling.se/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://everything.adamnordling.se/manifest.json

Manifest contains invalid JSON.

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::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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 header MAIN ASIDE "Main Tool Navigation" CONTENTINFO (missing!)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Lighthouse Accessibility Audits
Action
Score 76/100 — 4 failing, 13 passed
REVIEW
76

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
UNIX EPOCH div.clock-ambient-stack > button#clock-epoch-btn > div.ambient-row-left > span.ambient-label
Copy div.clock-ambient-stack > button#clock-epoch-btn > div.ambient-row-right > span.ambient-action-hint
DAYLIGHT SAVING div.clock-ambient-stack > div#clock-dst-card > div.ambient-row-left > span.ambient-label
SOLAR HORIZON div.clock-ambient-stack > div#clock-sunset-card > div.ambient-row-left > span.ambient-label
Convert Time: div.card > div.converter-stacked-module > div.converter-inputs-bar > span.converter-label
Local: div.converter-stacked-module > div#tz-converted-output > div.converter-result-box > span.converter-result-label
10:49 div.converter-stacked-module > div#tz-converted-output > div.converter-result-box > span.converter-result-value
Same Day div.converter-stacked-module > div#tz-converted-output > div.converter-result-box > span.pill-badge
DAY 281/365 · Q4 · 77.0% div.card > div.year-progress-module > div.year-stats-line > span#year-stats-text
UTC div.year-progress-module > div.year-stats-line > button#active-tz-btn > span#active-tz-display
IP: div.telemetry-top-bar > div.telemetry-network-block > div.ping-pulse-indicator > span.telemetry-label-prefix
ISP: div.telemetry-top-bar > div.telemetry-network-block > div.telemetry-isp-row > span.telemetry-label-prefix
PHYSICAL DISPLAY: div.telemetry-vertical-hud > div.hud-col > div.hud-row > span.hud-k
VIEWPORT: div.telemetry-vertical-hud > div.hud-col > div.hud-row > span.hud-k
REFRESH RATE: div.telemetry-vertical-hud > div.hud-col > div.hud-row > span.hud-k
DISPLAYS SETUP: div.telemetry-vertical-hud > div.hud-col > div.hud-row > span.hud-k
CPU CONCURRENCY: div.telemetry-vertical-hud > div.hud-col > div.hud-row > span.hud-k
CPU BENCHMARK: div.telemetry-vertical-hud > div.hud-col > div.hud-row > span.hud-k
DNS & TLS WATERFALL: div.telemetry-vertical-hud > div.hud-col > div.hud-row > span.hud-k
IPV6 CONNECTIVITY: div.telemetry-vertical-hud > div.hud-col > div.hud-row > span.hud-k
POWER & EFFICIENCY: div.telemetry-vertical-hud > div.hud-col > div.hud-row > span.hud-k
ACTIVE JS HEAP: div.telemetry-vertical-hud > div.hud-col > div.hud-row > span.hud-k
AUDIO SUBSYSTEM: div.telemetry-vertical-hud > div.hud-col > div.hud-row > span.hud-k
GRAPHICS ACCELERATOR: div.telemetry-vertical-hud > div.hud-col > div.hud-row > span.hud-k
LIVE ATMOSPHERE div.card > div.weather-card-header > div.weather-title-group > span.weather-header-label
Stockholm, SE div.card > div.weather-card-header > div.weather-title-group > span#wx-location-pill
°C div.weather-top-split > div.weather-reading-block > div > span
UV INDEX div.card > div.metrics-quad > div.metric-box > div.metric-sub-label
HUMIDITY div.card > div.metrics-quad > div.metric-box > div.metric-sub-label
WIND div.card > div.metrics-quad > div.metric-box > div.metric-sub-label
BAROMETER div.card > div.metrics-quad > div.metric-box > div.metric-sub-label
9° div#five-day-strip > div.day-mini-card > span > small
7° div#five-day-strip > div.day-mini-card > span > small
6° div#five-day-strip > div.day-mini-card > span > small
7° div#five-day-strip > div.day-mini-card > span > small
6° div#five-day-strip > div.day-mini-card > span > small
24-Hour Trajectory div.middle-split-row > div.card > div > span
10:00 div > div#hourly-strip > div.hour-chip > span
11:00 div > div#hourly-strip > div.hour-chip > span
12:00 div > div#hourly-strip > div.hour-chip > span
13:00 div > div#hourly-strip > div.hour-chip > span
14:00 div > div#hourly-strip > div.hour-chip > span
15:00 div > div#hourly-strip > div.hour-chip > span
16:00 div > div#hourly-strip > div.hour-chip > span
0 chars · 0 words div.card > div.card-header-flex > div.scratchpad-actions > span#scratch-counter
Mo div.dash-right-column > div.card > div.calendar-weekdays > span
Tu div.dash-right-column > div.card > div.calendar-weekdays > span
We div.dash-right-column > div.card > div.calendar-weekdays > span
Th div.dash-right-column > div.card > div.calendar-weekdays > span
Fr div.dash-right-column > div.card > div.calendar-weekdays > span
Sa div.dash-right-column > div.card > div.calendar-weekdays > span
Su div.dash-right-column > div.card > div.calendar-weekdays > span
28 div.dash-right-column > div.card > div#cal-days-grid > div.cal-cell
29 div.dash-right-column > div.card > div#cal-days-grid > div.cal-cell
30 div.dash-right-column > div.card > div#cal-days-grid > div.cal-cell
Selected Date: div.dash-right-column > div.card > div.cal-footer-meta > span.cal-info-left
Oct 8, 2026 div.dash-right-column > div.card > div.cal-footer-meta > span#cal-selected-label
Name Day: Nils div.card > div#date-intel-card > div > span#intel-nameday-text
Today div.dash-right-column > div.card > div#date-intel-card > span#intel-countdown-badge
No active deadlines. Select a date on the calendar to auto-fill. div.dash-right-column > div.card > div#deadlines-stream > div#deadlines-empty
No daily tasks logged. Add your first task above. div.dash-right-column > div.card > div#daily-task-stream > div.empty-state-notice
No routines configured yet. Create one above. div.dash-right-column > div.card > div#habits-stream > div.empty-state-notice

These are opportunities to improve the legibility of your content.

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.dash-right-column > div.card > form#deadline-form > input#deadline-input-date div.dash-right-column > div.card > form#deadline-form > input#deadline-input-date

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PT (PST / PDT) MT (MST / MDT) CT (CST / CDT) ET (EST / EDT) UTC / GMT London (G… div.card > div.converter-stacked-module > div.converter-inputs-bar > select#tz-source-select

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
× div.card > div.card-header-flex > div.scratchpad-actions > button#scratch-clear-btn

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
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Document has a main landmark.
○`[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 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
○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
○Heading elements appear in a sequentially-descending order
○`<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.
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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
Heading Hierarchy
2 headings
PASS
2 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 YouTube Extractor
  • H1 Windows Playbook & Hardware Tuning 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

A+
Heading Text Quality
All 2 heading(s) have substantive, well-formed text
PASS
All 2 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 1 images OK
PASS
All 1 images OK
Info::
1 decorative image(s) correctly marked
1 images 1 decorative
All images have appropriate alt text.
A+
Form Input Types
35 form control(s) checked, no type mismatches
PASS
35 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
35 form control(s) checked, no input-semantic issues
PASS
35 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Dark Mode Support
Full dark mode support
PASS
Full dark mode support
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light dark
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 light dark ✓Dark theme-color #0b0e14 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
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 YouTube Extractor19.42:13.0:1
#000000
#F7F6F2
Pass
h1 Windows Playbook & H…19.42:13.0:1
#000000
#F7F6F2
Pass
title Everything: Develope…21.00:14.5:1
#000000
#FFFFFF
Pass
span Everything21.00:14.5:1
#000000
#FFFFFF
Pass
span Everything19.42:14.5:1
#000000
#F7F6F2
Pass
span Developer & Utility …19.42:14.5:1
#000000
#F7F6F2
Pass
div OVERVIEW19.42:14.5:1
#000000
#F7F6F2
Pass
span Dashboard19.42:14.5:1
#000000
#F7F6F2
Pass
div UTILITIES & TOOLS19.42:14.5:1
#000000
#F7F6F2
Pass
span Windows Playbook19.42:14.5:1
#000000
#F7F6F2
Pass
span YouTube Extractor19.42:14.5:1
#000000
#F7F6F2
Pass
span SHA & Hash Calculato…19.42:14.5:1
#000000
#F7F6F2
Pass
span Soon19.42:14.5:1
#000000
#F7F6F2
Pass
span Multi-Translator19.42:14.5:1
#000000
#F7F6F2
Pass
span Soon19.42:14.5:1
#000000
#F7F6F2
Pass
span Media File Converter19.42:14.5:1
#000000
#F7F6F2
Pass
span Soon19.42:14.5:1
#000000
#F7F6F2
Pass
span Subnet & CIDR Engine19.42:14.5:1
#000000
#F7F6F2
Pass
span Soon19.42:14.5:1
#000000
#F7F6F2
Pass
span Validators & Encoder…19.42:14.5:1
#000000
#F7F6F2
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