https://dosebuddy-frontend.dosebuddy-health.workers.dev

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 5 REVIEW 7 FIX

Mobile Keyboard & Autofill

Action

24/34 eligible field(s) missing autocomplete or inputmode

FIX

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

Got: <input type="email" id="su-patient-email">, <input type="email" id="ps-email">, <input type="tel" id="ps-phone">, <input type="tel" id="ps-emergency">, <input type="password" id="sec-current-pw">

17 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, numeric.

Got: <input type="email" id="auth-email">, <input type="email" id="fp-email">, <input type="email" id="su-email">, <input type="tel" id="su-phone">, <input type="tel" id="su-emergency">

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

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

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

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

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

Heading Hierarchy

Action

61 headings, 2 skip(s)

REVIEW

61 headings, 2 skip(s)

Multiple H1 headings (4 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

H1 DoseBuddy
H2 Welcome back
H2 Create your account
H2 Verify Your Email
H2 Reset Password
H3 Terms & Conditions
H4 Reminder Disclaimer
H4 Medical Responsibility
H4 User Responsibility
H4 Notification Disclaimer
H4 Emergency Disclaimer
H4 Acceptance of Terms
H3 Privacy Policy
H4 Data Privacy & Storage
H4 Data We Collect
H4 AI Features & Data Usage
H4 Data Security
H4 Your Rights
H1 Good Morning duplicate H1
H2 0
H2 0
H2 0
H2 0%
H3 Today's Medicines
H3 Weekly Adherence
H3 Milestone Progress
H3 Achievements
H3 Recent Activity
H2 Add Medicine
H3 Upload Prescription
H3 Medicine Details
H2 Dose History
H3 Activity Log
H2 Analytics & Reports
H3 Overall Health Score
H3 Medicine Consumption
H3 Medication Adherence Trend
H3 Missed Doses Summary
H3 BMI Trend
H3 Vitals Analytics
H3 AI Health Insights
H2 BMI Calculator
H3 Calculate BMI
H3 Health Insights
H3 BMI Reference Scale
H1 Vitals Log duplicate H1
H3 Log Vitals skipped
H3 Trends
H3 Health Insights
H3 Recent Records
H1 Health Assistant duplicate H1
H3 Hello! I'm your AI Health Assistant skipped
H4 Important Medical Disclaimer
H3 Past Conversations
H3 Profile Settings
H3 Notification Preferences
H3 Help & Support
H3 Privacy & Security
H3 Sign Out
H4 Welcome to DoseBuddy
H2 Prescription Analysed

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

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

Action

4 of 46 controls have issues

REVIEW

4 of 46 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="file" id="prescription-file-input">

3 control(s) rely on placeholder only

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

Got: <input type="text">; <input type="text">; <textarea id="ai-chat-input">

42 control(s) properly labeled

46 controls

42 labeled

3 placeholder only

1 unlabeled

Control	Type	Label	Method
#auth-email	email	Email Address	for/id
#auth-password	password	Password	for/id
#otp-input	text	Verification Code	for/id
#fp-email	email	Email Address	for/id
#fp-otp	text	Verification Code	for/id
#fp-new-password	password	New Password	for/id
#fp-confirm-password	password	Confirm Password	for/id
#su-name	text	Full Name *	for/id
#su-email	email	Email Address *	for/id
#su-password	password	Password *	for/id
#su-confirm-password	password	Confirm Password *	for/id
#su-phone	tel	Phone Number	for/id
#su-dob	date	Date of Birth	for/id
#su-emergency	tel	Emergency Contact For caregiver alerts	for/id
#su-patient-email	email	Patient's Email *	for/id
#su-terms	checkbox		none
#med-name	text	Medicine Name *	for/id
#med-dosage	text	Dosage *	for/id
#med-instructions	text	Instructions	for/id
#med-start-date	date	Start Date *	for/id
#med-end-date	date	End Date *	for/id
#time-1	time	Morning	for/id
#time-2	time	Afternoon	for/id
#time-3	time	Evening	for/id
#bmi-height-view	number	Height (cm)	for/id
#bmi-weight-view	number	Weight (kg)	for/id
#vf-bp-sys	number	Systolic mmHg	for/id
#vf-bp-dia	number	Diastolic mmHg	for/id
#vf-sugar	number	Level mg/dL	for/id
#vf-weight	number	Weight kg	for/id
#vf-hr	number	Pulse bpm	for/id
#vf-temp	number	Temp °C	for/id
#vf-notes	textarea	Notes (optional)	for/id
#ps-name	text	Full Name	for/id
#ps-email	email	Email Address	for/id
#ps-phone	tel	Phone Number	for/id
#ps-dob	date	Date of Birth	for/id
#ps-gender	select	Gender	for/id
#ps-emergency	tel	Emergency Contact	for/id
#sec-current-pw	password	Current Password	for/id
#sec-new-pw	password	New Password	for/id
#sec-confirm-pw	password	Confirm New Password	for/id
input	text	(Search country or code...)	placeholder only
input	text	(Search country or code...)	placeholder only
#ai-chat-input	textarea	(Ask me anything about your health or medications...)	placeholder only
#prescription-file-input	file	(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

Link & Button Quality

7 issue(s) across 2 links and 113 buttons

REVIEW

7 issue(s) across 2 links and 113 buttons

7 button(s) with no accessible text

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

Got: button#ai-chat-send; button#notif-health-action-btn; button.toggle-switch (#1502 on page); button.toggle-switch (#1508 on page); button.toggle-switch (#1514 on page); button.toggle-switch (#1522 on page); button#help-copy-email

2 link(s) with descriptive text

2 links

0 empty

0 generic text

0 new tab

7 empty buttons

Element	Text	Issue	Suggested Fix
<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

108 links and buttons have descriptive text

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

button#ai-chat-send; button#notif-health-action-btn; button.toggle-switch (#1502 on page); button.toggle-switch (#1508 on page); button.toggle-switch (#1514 on page); button.toggle-switch (#1522 on page); button#help-copy-email

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

Form Input Quality

2 input-semantic issue(s) across 46 form control(s)

REVIEW

2 input-semantic issue(s) across 46 form control(s)

3 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="sec-current-pw">, <input type="password" id="sec-new-pw">, <input type="password" id="sec-confirm-pw">.

2 login form field(s) missing `autocomplete=username` (or `email`)

On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" id="su-patient-email">, <input type="email" id="ps-email">.

Mobile-Readable Font Sizes

92% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

92% of visible text renders at >= 12 CSS px (1 below threshold)

1 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.5px ("DoseBuddy is a reminder tool only. Alway...").

A+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

3 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H2: "0" - H2: "0" - H2: "0"

Got: 3 ≤2-char heading(s)

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

Form Input Types

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

PASS

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

Input "Search country or code..." should use type="search" (currently type="text")

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

Input "Search country or code..." should use type="search" (currently type="text")

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

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.

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)

Element	Ratio	Required	FG	BG	Result
h1 DoseBuddy	19.76:1	3.0:1	#000000	#F7F8FA	Pass
h1 Good Morning	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h1 Vitals Log	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h1 Health Assistant	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h2 Welcome back	19.12:1	3.0:1	#000000	#F4F4F6	Pass
h2 Create your account	19.12:1	3.0:1	#000000	#F4F4F6	Pass
h2 Verify Your Email	13.77:1	3.0:1	#1E293B	#F7F8FA	Pass
h2 Reset Password	13.89:1	3.0:1	#1E293B	#F8F9FB	Pass
h2 Add Medicine	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h2 Dose History	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h2 Analytics & Reports	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h2 BMI Calculator	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h2 Prescription Analyse…	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h3 Terms & Conditions	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h3 Privacy Policy	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h3 Today's Medicines	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h3 Weekly Adherence	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h3 Milestone Progress	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h3 Achievements	19.93:1	3.0:1	#000000	#F8F9FB	Pass
h3 Recent Activity	19.93:1	3.0:1	#000000	#F8F9FB	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.

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 22 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
Your personal medicine reminder & health companion `section#auth-view > div.auth-page > div.auth-brand > p.auth-tagline`
Login `div.auth-page > div.auth-card > div.tabs > button.tab-btn`
Sign Up `div.auth-page > div.auth-card > div.tabs > button.tab-btn`
Sign In `div.auth-page > div.auth-card > form#login-form > button#auth-submit-btn`

These are opportunities to improve the legibility of your content.

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

●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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○Image elements have `[alt]` attributes

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

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

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