Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 7 REVIEW 4 FIX

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

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

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ Apple Touch Missing

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

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

3 landmarks

REVIEW

3 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

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

Form Accessibility

Action

3 of 3 controls have issues

REVIEW

3 of 3 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

2 control(s) rely on placeholder only

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

Got: <input type="email" id="login-email-input">; <input type="text" id="login-code-input">

3 controls

0 labeled

2 placeholder only

1 unlabeled

Control	Type	Label	Method
#login-email-input	email	(you@yourcompany.com)	placeholder only
#login-code-input	text	(000000)	placeholder only
input	submit	(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

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 Keyboard & Autofill

Action

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

REVIEW

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

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="login-email-input">

Mobile-Readable Font Sizes

97% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

97% of visible text renders at >= 12 CSS px (3 below threshold)

3 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.0px ("42 objects"); <span> 11.0px ("118 objects"); <span> 11.0px ("verified").

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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 Not set ✗Dark theme-color Not set ✗CSS indicators 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 Active Directory administration,

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Everything a helpdesk-to-sysadmin team t…

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Real screenshots. Nothing dressed up for…

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Nothing leaves your domain that isn't su…

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A real manual, not just a FAQ page.

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Try it, or just get the real thing.

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Log in

1.53:1

#000000

#152E4C

needs 3.0:1 (large text)

19px · top of page (header area)

h3 Enter your code

1.37:1

#000000

#0B2546

needs 3.0:1 (large text)

19px · above the fold

h3 Users & groups

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Computers & LAPS

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Bulk operations

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Scoped by design

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Every action logged

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Activate once, done

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Built for the phone queue

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Onboard a new hire in one form

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Groups, without the guesswork

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 QuietAD User Guide

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 14-Day Trial

1.44:1

#000000

#0D294C

needs 3.0:1 (large text)

19px · bottom of viewport

title QuietAD — Active Directory Users & Com…

1.53:1

#000000

#152E4C

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Active Directory adm…	1.44:1	3.0:1	#000000	#0D294C	Fail
h2 Everything a helpdes…	1.44:1	3.0:1	#000000	#0D294C	Fail
h2 Real screenshots. No…	1.44:1	3.0:1	#000000	#0D294C	Fail
h2 Nothing leaves your …	1.44:1	3.0:1	#000000	#0D294C	Fail
h2 A real manual, not j…	1.44:1	3.0:1	#000000	#0D294C	Fail
h2 Try it, or just get …	1.44:1	3.0:1	#000000	#0D294C	Fail
h3 Log in	1.53:1	3.0:1	#000000	#152E4C	Fail
h3 Enter your code	1.37:1	3.0:1	#000000	#0B2546	Fail
h3 Users & groups	1.44:1	3.0:1	#000000	#0D294C	Fail
h3 Computers & LAPS	1.44:1	3.0:1	#000000	#0D294C	Fail
h3 Bulk operations	1.44:1	3.0:1	#000000	#0D294C	Fail
h3 Scoped by design	1.44:1	3.0:1	#000000	#0D294C	Fail
h3 Every action logged	1.44:1	3.0:1	#000000	#0D294C	Fail
h3 Activate once, done	1.44:1	3.0:1	#000000	#0D294C	Fail
h3 Built for the phone …	1.44:1	3.0:1	#000000	#0D294C	Fail
h3 Onboard a new hire i…	1.44:1	3.0:1	#000000	#0D294C	Fail
h3 Groups, without the …	1.44:1	3.0:1	#000000	#0D294C	Fail
h3 QuietAD User Guide	1.44:1	3.0:1	#000000	#0D294C	Fail
h3 14-Day Trial	1.44:1	3.0:1	#000000	#0D294C	Fail
title QuietAD — Active D…	1.53:1	4.5:1	#000000	#152E4C	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.

Heading Hierarchy

24 headings, 1 skip(s)

PASS

24 headings, 1 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.

H3 Log in
H3 Enter your code
H1 Active Directory administration, without leaving your domain.
H2 Everything a helpdesk-to-sysadmin team touches in AD, in one window.
H3 Users & groups
H3 Computers & LAPS
H3 Bulk operations
H3 Scoped by design
H3 Every action logged
H3 Activate once, done
H3 Built for the phone queue
H3 Onboard a new hire in one form
H3 Groups, without the guesswork
H2 Real screenshots. Nothing dressed up for the website.
H2 Nothing leaves your domain that isn't supposed to.
H4 Fully offline activation skipped
H4 Encrypted local credentials
H4 Confidential attributes over LDAPS
H4 Idle session timeout
H4 No permissions granted or bypassed
H2 A real manual, not just a FAQ page.
H3 QuietAD User Guide
H2 Try it, or just get the real thing.
H3 14-Day Trial

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

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 6 images OK

PASS

All 6 images OK

1 image(s) with alt text over 125 characters

5 image(s) with good alt text

6 images 5 good alt text

Issue	Count
too long	1 image(s)

A+

Link & Button Quality

29 links, 8 buttons — all OK

PASS

29 links, 8 buttons — all OK

29 link(s) with descriptive text

29 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

37 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 93/100 — 3 failing, 23 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
42 objects `div.tree-card > div.tree > div.row > span.ok`
118 objects `div.tree-card > div.tree > div.row > span.ok`
verified `div.tree-card > div.tree > div.row > span.ok`
/ 14 days `div#trial > div.trial-top > div.trial-price > span`
At checkout, add your organization name in PayPal's "special instructions to se… `div.wrap > div.plans-grid > div#trial > p.trial-note`
organization name `div.plans-grid > div#trial > p.trial-note > strong`
support@quietad.online `div.plans-grid > div#trial > p.trial-note > a`
Get QuietAD from the Microsoft Store → (or download the .zip directly) — the ap… `div.wrap > div.plans-grid > div#trial > p.trial-note`
Microsoft Store → `div.plans-grid > div#trial > p.trial-note > a`
download the .zip directly `div.plans-grid > div#trial > p.trial-note > a`
All sales are final. Refund Policy `div.wrap > div.plans-grid > div#trial > p.trial-note`
Refund Policy `div.plans-grid > div#trial > p.trial-note > a`
Perpetual license `div.wrap > div.plans-grid > div.price-card > span.tag`
one-time `div.plans-grid > div.price-card > div.amount > span`
Priced per organization, not per machine or per admin. `div.wrap > div.plans-grid > div.price-card > p.sub`

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
Fully offline activation `div.trust-list > div.trust-item > 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.

○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

●Input buttons have discernible text.

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

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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

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

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

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

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

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