Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 6 REVIEW 6 FIX

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" id="ap-email">

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" id="ap-email">

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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 ✗

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.

Landmark Structure

Action

2 landmarks

REVIEW

2 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

Heading Hierarchy

21 headings, 2 skip(s)

REVIEW

21 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Plain English in.A real KiCad file out.
H2 The AI never touches geometry.
H4 You describe it skipped
H4 AI drafts the meaning
H4 Code builds the file
H4 Checked before written
H2 Generation is the start, not the product.
H4 Generate skipped
H4 Edit by hand
H4 Verify on-canvas
H2 Seeing is believing.
H2 Deep where it counts.Honest where it's rough.
H3 Electrical
H3 CAD
H2 Electrical is the first domain. Not the last.
H2 We never mark up a token.
H2 Local-first.
H2 Chat describes. Tools demand. Valatir does both ends.
H2 Applications open.Reviewed personally.
H2 Fair questions.
H2 Describe what you want.Get the real file.

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Form Accessibility

3 of 3 controls have issues

REVIEW

3 of 3 controls have issues

3 control(s) rely on placeholder only

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

Got: <input type="email" id="ap-email">; <textarea id="ap-q1">; <textarea id="ap-q2">

3 controls

0 labeled

3 placeholder only

0 unlabeled

Control	Type	Label	Method
#ap-email	email	(you@example.com)	placeholder only
#ap-q1	textarea	(KiCad, Altium, pen and paper, nothing yet…)	placeholder only
#ap-q2	textarea	(The real circuit or part you’d make first)	placeholder only

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

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

Mobile-Readable Font Sizes

Action

78% of visible text renders at >= 12 CSS px (35 below threshold)

REVIEW

78% of visible text renders at >= 12 CSS px (35 below threshold)

35 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.0px ("valatir — electrical"); <div> 11.0px ("01 · INTENT"); <div> 11.0px ("02 · HELIX"); <div> 11.0px ("03 · ENGINE"); <div> 11.0px ("04 · VERIFY").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Valatir — Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

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 Plain English in.

1.03:1

#000000

#04040A

needs 3.0:1 (large text)

32px · mid-page

h2 The AI never touches geometry.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Generation is the start, not the product…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 Seeing is believing.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Deep where it counts.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Honest where it's rough.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Electrical is the first domain. Not the …

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 We never mark up a token.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 Local-first.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 Chat describes. Tools demand. Valatir do…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Applications open.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Reviewed personally.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Fair questions.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Describe what you want.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h3 Electrical

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 CAD

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

title Valatir — Plain English in. A real KiC…

1.01:1

#000000

#010103

needs 4.5:1 (normal text)

16px · top of page (header area)

a How it works

1.01:1

#000000

#010103

needs 4.5:1 (normal text)

16px · top of page (header area)

a Changelog

1.08:1

#000000

#070E15

needs 4.5:1 (normal text)

16px · top of page (header area)

a Apply for early access

1.09:1

#000000

#070F15

needs 4.5:1 (normal text)

16px · top of page (header area)

4 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 Plain English in.	1.03:1	3.0:1	#000000	#04040A	Fail
h2 The AI never touches…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Generation is the st…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Seeing is believing.	1.00:1	3.0:1	#000000	#000000	Fail
h2 Deep where it counts…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Honest where it's ro…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Electrical is the fi…	1.00:1	3.0:1	#000000	#000000	Fail
h2 We never mark up a t…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Local-first.	1.00:1	3.0:1	#000000	#000000	Fail
h2 Chat describes. Tool…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Applications open.	1.00:1	3.0:1	#000000	#000000	Fail
h2 Reviewed personally.	1.00:1	3.0:1	#000000	#000000	Fail
h2 Fair questions.	1.00:1	3.0:1	#000000	#000000	Fail
h2 Describe what you wa…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Electrical	1.00:1	3.0:1	#000000	#000000	Fail
h3 CAD	1.00:1	3.0:1	#000000	#000000	Fail
title Valatir — Plain En…	1.01:1	4.5:1	#000000	#010103	Fail
a How it works	1.01:1	4.5:1	#000000	#010103	Fail
a Changelog	1.08:1	4.5:1	#000000	#070E15	Fail
a Apply for early acce…	1.09:1	4.5:1	#000000	#070F15	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 Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

5 image(s) with good alt text

5 images 5 good alt text

All images have appropriate alt text.

A+

Link & Button Quality

21 links, 8 buttons — all OK

PASS

21 links, 8 buttons — all OK

21 link(s) with descriptive text

21 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

29 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+

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

No iframes on this page

PASS

No iframes on this page

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

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

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

Lighthouse Accessibility Audits

Score 92/100 — 4 failing, 19 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.

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
valatir — electrical `div > div.term > div.term-bar > div.term-title`
(1.2s) `div.term-body > div.tl > span.t-txt > span.t-dim`
(0.1s · 0 tokens) `div.term-body > div.tl > span.t-txt > span.t-dim`
(14.2 KB) `div.term-body > div.tl > span.t-ok > span.t-dim`
Intent to file. `footer > div.foot > div > span.mono`
Changelog `footer > div.foot > div > a`
Privacy `footer > div.foot > div > a`
Terms `footer > div.foot > div > a`
Contact `footer > div.foot > div > a`
© 2026 Valatir · Ontario, Canada `body > footer > div.foot > div`

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
You describe it `div.wrap > div.spine > div.sp-card > h4`
Generate `div > div.ed-feat > div > h4`

These are opportunities to improve keyboard navigation in your application.

Best practices

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.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Chat AI Native tools alone Valatir Describe it in plain English Output is a… `section > div.wrap > div.comp-wrap > table.comp`

○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

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

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

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

○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

○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

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

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