Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 7 REVIEW 6 FIX

Form Accessibility

Action

16 of 19 controls have issues

FIX

16 of 19 controls have issues

2 control(s) without accessible label

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

Got: <select id="variantSelect">; <input type="email" id="profEmail">

14 control(s) rely on placeholder only

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

Got: <input type="text" id="navSearchInput">; <input type="email" id="loginEmail">; <input type="password" id="loginPassword">; <input type="text" id="regName">; <input type="email" id="regEmail">; <input type="tel" id="regPhone">; <input type="password" id="regPassword">; <input type="text" id="couponInput">; <input type="text" id="txnInput">; <input type="text" id="profName"> (+4 more)

3 control(s) properly labeled

19 controls

3 labeled

14 placeholder only

2 unlabeled

Control	Type	Label	Method
#rememberMe	checkbox		none
input	checkbox		none
input	checkbox		none
#navSearchInput	text	(Search for products...)	placeholder only
#regName	text	(Full name)	placeholder only
#regEmail	email	(Email address)	placeholder only
#regPhone	tel	(Phone number)	placeholder only
#regPassword	password	(Password (min 6 chars))	placeholder only
#couponInput	text	(Enter code)	placeholder only
#txnInput	text	(Paste your Transaction ID here...)	placeholder only
#profName	text	(Full name)	placeholder only
#profPhone	tel	(Phone)	placeholder only
#wrCustomerName	text	(Your name)	placeholder only
#wrText	textarea	(Share your experience with this product...)	placeholder only
#loginEmail	email	(Email address)	placeholder only
#loginPassword	password	(Password)	placeholder only
#aiChatInput	text	(Ask about orders, reseller plans, payments...)	placeholder only
#variantSelect	select	(none)	none
#profEmail	email	(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.

<input type="text" id="navSearchInput">; <input type="email" id="loginEmail">; <input type="password" id="loginPassword">; <input type="text" id="regName">; <input type="email" id="regEmail">; <input type="tel" id="regPhone">; <input type="password" id="regPassword">; <input type="text" id="couponInput">; <input type="text" id="txnInput">; <input type="text" id="profName"> (+4 more)

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

Link & Button Quality

Action

21 issue(s) across 31 links and 64 buttons

FIX

21 issue(s) across 31 links and 64 buttons

2 link(s) with no accessible text

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

Got: https://t.me/DripClient0fc; https://discord.gg/MGFtZA2gGE

4 link(s) open in new tab without warning

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

Got: #; https://t.me/DripClient0fc; #; #

19 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.icon-btn (#133 on page); button.hero-arrow (#178 on page); button.hero-arrow (#186 on page); button.pc-cart (#450 on page); button.pc-cart (#481 on page); button.pc-cart (#512 on page); button.pc-cart (#543 on page); button.pc-cart (#574 on page); button.modal-close (#779 on page); button.modal-close (#825 on page) (+9 more)

25 link(s) with descriptive text

31 links

2 empty

0 generic text

4 new tab

19 empty buttons

Element	Text	Issue	Suggested Fix
#	Contact	new tab	Add '(opens in new tab)' to text
https://t.me/DripClient0fc	(empty)	empty	Add link text or aria-label
https://discord.gg/MGFtZA2gGE	(empty)	empty	Add link text or aria-label
https://t.me/DripClient0fc	Telegram Support	new tab	Add '(opens in new tab)' to text
#	Update Files	new tab	Add '(opens in new tab)' to text
#	Contact Support	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

70 links and buttons have descriptive text

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

https://t.me/DripClient0fc; https://discord.gg/MGFtZA2gGE

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://t.me/DripClient0fc; #; #

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.icon-btn (#133 on page); button.hero-arrow (#178 on page); button.hero-arrow (#186 on page); button.pc-cart (#450 on page); button.pc-cart (#481 on page); button.pc-cart (#512 on page); button.pc-cart (#543 on page); button.pc-cart (#574 on page); button.modal-close (#779 on page); button.modal-close (#825 on page) (+9 more)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Mobile Keyboard & Autofill

Action

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

FIX

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

7 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, current-password, tel.

Got: <input type="email" id="loginEmail">, <input type="password" id="loginPassword">, <input type="email" id="regEmail">, <input type="tel" id="regPhone">, <input type="password" id="regPassword">

5 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, tel.

Got: <input type="email" id="loginEmail">, <input type="email" id="regEmail">, <input type="tel" id="regPhone">, <input type="email" id="profEmail">, <input type="tel" id="profPhone">

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #9d3df0

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 ModePartial Dark Mode

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.

Heading Hierarchy

18 headings

REVIEW

18 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Top Ranking
H2 Featured Products
H2 Customer Reviews
H2 Frequently Asked Questions
H3 Welcome Back
H3 Create Account
H3 Product
H4 Order
H4 Steps
H4 Verify Payment
H4 Order
H4 Automatic Payment
H3 My Orders
H3 Profile
H3 All Customer Reviews
H3 Write a Review
H3 Settings
H2 Account Suspended

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Tap Target Adequacy

1 tap target(s) too small or too close together

REVIEW

1 tap target(s) too small or too close together

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.

Mobile-Readable Font Sizes

Action

77% of visible text renders at >= 12 CSS px (59 below threshold)

REVIEW

77% of visible text renders at >= 12 CSS px (59 below threshold)

59 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> 11.0px ("Please wait..."); <span> 8.5px ("Premium Digital Products"); <span> 10.5px ("#1 Digital Product Store"); <div> 10.5px ("LIVE PURCHASE"); <span> 10.5px ("Handpicked For You").

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 ✗

Favicon & Branding

12 icon(s) detected

REVIEW

12 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA

h2 Top

1.03:1

#000000

#0B020F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Featured

1.03:1

#000000

#0B020F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Customer Reviews

1.03:1

#000000

#0B020F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Frequently Asked

1.03:1

#000000

#0B020F

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Welcome Back

1.03:1

#000000

#0B020F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Create Account

1.03:1

#000000

#0B020F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 My Orders

1.03:1

#000000

#0B020F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Profile

1.03:1

#000000

#0B020F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 All Customer Reviews

1.03:1

#000000

#0B020F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Write a Review

1.03:1

#000000

#0B020F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Settings

1.03:1

#000000

#0B020F

needs 3.0:1 (large text)

19px · bottom of viewport

title DRIP CLIENT - Premium Digital Store

1.08:1

#000000

#0F091D

needs 4.5:1 (normal text)

16px · top of page (header area)

div PROCESSING

1.06:1

#000000

#0D0719

needs 4.5:1 (normal text)

16px · top of page (header area)

div Please wait...

1.05:1

#000000

#0A0614

needs 4.5:1 (normal text)

16px · top of page (header area)

span Loading store...

1.04:1

#000000

#080410

needs 4.5:1 (normal text)

16px · top of page (header area)

span DRIP CLIENT

1.03:1

#000000

#07040E

needs 4.5:1 (normal text)

16px · above the fold

span Premium Digital Products

1.04:1

#000000

#080410

needs 4.5:1 (normal text)

16px · above the fold

button All

1.04:1

#000000

#090412

needs 4.5:1 (normal text)

16px · above the fold

button APKMOD

1.05:1

#000000

#0A0515

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Top	1.03:1	3.0:1	#000000	#0B020F	Fail
h2 Featured	1.03:1	3.0:1	#000000	#0B020F	Fail
h2 Customer Reviews	1.03:1	3.0:1	#000000	#0B020F	Fail
h2 Frequently Asked	1.03:1	3.0:1	#000000	#0B020F	Fail
h2 Account Suspended	6.70:1	3.0:1	#FF5B5B	#0B020F	Pass
h3 Welcome Back	1.03:1	3.0:1	#000000	#0B020F	Fail
h3 Create Account	1.03:1	3.0:1	#000000	#0B020F	Fail
h3 My Orders	1.03:1	3.0:1	#000000	#0B020F	Fail
h3 Profile	1.03:1	3.0:1	#000000	#0B020F	Fail
h3 All Customer Reviews	1.03:1	3.0:1	#000000	#0B020F	Fail
h3 Write a Review	1.03:1	3.0:1	#000000	#0B020F	Fail
h3 Settings	1.03:1	3.0:1	#000000	#0B020F	Fail
title DRIP CLIENT - Premiu…	1.08:1	4.5:1	#000000	#0F091D	Fail
div PROCESSING	1.06:1	4.5:1	#000000	#0D0719	Fail
div Please wait...	1.05:1	4.5:1	#000000	#0A0614	Fail
span Loading store...	1.04:1	4.5:1	#000000	#080410	Fail
span DRIP CLIENT	1.03:1	4.5:1	#000000	#07040E	Fail
span Premium Digital Prod…	1.04:1	4.5:1	#000000	#080410	Fail
button All	1.04:1	4.5:1	#000000	#090412	Fail
button APKMOD	1.05:1	4.5:1	#000000	#0A0515	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

Action

Score 73/100 — 6 failing, 15 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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#app > main.main-wrap > section.hero > button.hero-arrow `div#app > main.main-wrap > section.hero > button.hero-arrow`
div#app > main.main-wrap > section.hero > button.hero-arrow `div#app > main.main-wrap > section.hero > button.hero-arrow`

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
div.footer-inner > div.footer-about > div.footer-social > a `div.footer-inner > div.footer-about > div.footer-social > a`
div.footer-inner > div.footer-about > div.footer-social > a `div.footer-inner > div.footer-about > div.footer-social > 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.

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
48 `div.reviews-head > div.rev-stat > span.rev-stat-count > span#reviewCount`

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
body > div#app > a#floatingCartBtn `body > div#app > a#floatingCartBtn`

These items highlight common accessibility best practices.

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
1 `body > div#aiAssistantRoot > button#aiFabBtn`

○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

●Image elements have `[alt]` attributes

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

●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

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

○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

4 landmarks

PASS

4 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 Text Quality

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

PASS

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

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

Alt Text Quality

2 of 8 images have issues

PASS

2 of 8 images have issues

2 image(s) with generic alt text

1 decorative image(s) correctly marked

5 image(s) with good alt text

8 images 5 good alt text 1 decorative 2 generic

Issue	Count
generic	2 image(s)

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "navSearchInput" should use type="search" (currently type="text")

Field name "navSearchInput" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Form Input Quality

1 input-semantic issue(s) across 19 form control(s)

PASS

1 input-semantic issue(s) across 19 form control(s)

2 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" id="loginPassword">, <input type="password" id="regPassword">.

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

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: DRIP CLIENT

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name DRIP CLIENT ✓192×192 icon ✓512×512 icon ✓Start URL /index.php ✓Display Mode standalone ✓

Name DRIP CLIENT Display Mode standalone Theme Color #9d3df0 Background Color #120a1f Icons 4 icon(s)

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.