Skip to content
https://edgepharma.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title 403 Forbidden ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Alt Text Quality
Action
5 of 15 images have issues
REVIEW
5 of 15 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
7 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
15 images 3 good alt text 7 decorative 5 missing
IssueCount
missing5 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
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 Mexican Pharmacy: Reasons to Choose, Med…
2.12:1
#000000
on
#154B45
needs 3.0:1 (large text)
32px · above the fold
h2 Exceeding Expectations for Every Custome…
2.26:1
#000000
on
#1A4F49
needs 3.0:1 (large text)
24px · mid-page
h2 Reasons To Choose Us? Special Approach t…
2.33:1
#000000
on
#1C514B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why Are We Popular with American Custome…
2.33:1
#000000
on
#1C514B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ask the Pharmacist: Common Questions and…
2.33:1
#000000
on
#1C514B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Overview of Featured Medications and Pri…
2.33:1
#000000
on
#1C514B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mexican Online Pharmacy is Your Reliable…
2.33:1
#000000
on
#1C514B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Reputation Among International Clients
2.33:1
#000000
on
#1C514B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How Does The Ordering Process Work?
2.33:1
#000000
on
#1C514B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How is Customer Privacy Protected?
2.33:1
#000000
on
#1C514B
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Bestsellers from Mexico
2.33:1
#000000
on
#1C514B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Search Medication
2.33:1
#000000
on
#1C514B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Latest Updates
2.33:1
#000000
on
#1C514B
needs 3.0:1 (large text)
19px · bottom of viewport
title Mexican Online Pharmacy: Direct Access t…
2.09:1
#000000
on
#134A43
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
2.09:1
#000000
on
#134A43
needs 4.5:1 (normal text)
16px · top of page (header area)
a About
2.09:1
#000000
on
#134A43
needs 4.5:1 (normal text)
16px · top of page (header area)
a Quality
2.09:1
#000000
on
#134A43
needs 4.5:1 (normal text)
16px · top of page (header area)
a Quality Compounding
2.09:1
#000000
on
#134A44
needs 4.5:1 (normal text)
16px · above the fold
a Products
2.09:1
#000000
on
#134A44
needs 4.5:1 (normal text)
16px · above the fold
a Services
2.09:1
#000000
on
#134A44
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Mexican Pharmacy: Re…2.12:13.0:1
#000000
#154B45
Fail
h2 Exceeding Expectatio…2.26:13.0:1
#000000
#1A4F49
Fail
h2 Reasons To Choose Us…2.33:13.0:1
#000000
#1C514B
Fail
h2 Why Are We Popular w…2.33:13.0:1
#000000
#1C514B
Fail
h2 Ask the Pharmacist: …2.33:13.0:1
#000000
#1C514B
Fail
h2 Overview of Featured…2.33:13.0:1
#000000
#1C514B
Fail
h2 Mexican Online Pharm…2.33:13.0:1
#000000
#1C514B
Fail
h2 Reputation Among Int…2.33:13.0:1
#000000
#1C514B
Fail
h2 How Does The Orderin…2.33:13.0:1
#000000
#1C514B
Fail
h2 How is Customer Priv…2.33:13.0:1
#000000
#1C514B
Fail
h3 Bestsellers from Mex…2.33:13.0:1
#000000
#1C514B
Fail
h3 Search Medication2.33:13.0:1
#000000
#1C514B
Fail
h3 Latest Updates2.33:13.0:1
#000000
#1C514B
Fail
title Mexican Online Pharm…2.09:14.5:1
#000000
#134A43
Fail
a Home2.09:14.5:1
#000000
#134A43
Fail
a About2.09:14.5:1
#000000
#134A43
Fail
a Quality2.09:14.5:1
#000000
#134A43
Fail
a Quality Compounding2.09:14.5:1
#000000
#134A44
Fail
a Products2.09:14.5:1
#000000
#134A44
Fail
a Services2.09:14.5:1
#000000
#134A44
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 4 failing, 16 passed
REVIEW
81

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 > header.header > div.header__container > button.burger div.app > header.header > div.header__container > button.burger
div.catalog-search > div.catalog-search__actions > form.search-form > button.search-form__btn div.catalog-search > div.catalog-search__actions > form.search-form > button.search-form__btn

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.benefits__items > div.benefits__item > div.benefits__item-rect > img div.benefits__items > div.benefits__item > div.benefits__item-rect > img
div.benefits__items > div.benefits__item > div.benefits__item-rect > img div.benefits__items > div.benefits__item > div.benefits__item-rect > img
div.benefits__items > div.benefits__item > div.benefits__item-rect > img div.benefits__items > div.benefits__item > div.benefits__item-rect > img
div.benefits__items > div.benefits__item > div.benefits__item-rect > img div.benefits__items > div.benefits__item > div.benefits__item-rect > img
div.benefits__items > div.benefits__item > div.benefits__item-rect > img div.benefits__items > div.benefits__item > div.benefits__item-rect > img

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.

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
Is It Safe to Order Medications from Mexico to the U.S.? div.faq__accordions > div.accordion > button.accordion__toggle > h6

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We believe that medication availability and accessibility are two of the most i… div.accordion__inner > div.accordion__wrapper > div.text-wrapper > ol

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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
●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
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●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-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
○`[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.
○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.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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 Hierarchy
20 headings, 1 skip(s)
PASS
20 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Mexican Pharmacy: Reasons to Choose, Medications and Services
  • H2 Exceeding Expectations for Every Customer
  • H3 Bestsellers from Mexico
  • H3 Search Medication
  • H2 Reasons To Choose Us? Special Approach to Your Order
  • H2 Why Are We Popular with American Customers?
  • H2 Ask the Pharmacist: Common Questions and Answers
  • H6 Is It Safe to Order Medications from Mexico to the U.S.? skipped
  • H6 How Long Will It Take You to Deliver My Order?
  • H6 Can I Return the Drugs That Didn’t Work for Me?
  • H6 Do You Want Bonuses and Promotions? Here They Are
  • H2 Overview of Featured Medications and Prices
  • H2 Mexican Online Pharmacy is Your Reliable Healthcare Partner
  • H2 Reputation Among International Clients
  • H2 How Does The Ordering Process Work?
  • H2 How is Customer Privacy Protected?
  • H3 Latest Updates
  • H4 Does This Cut Need Stitches?
  • H4 Eating Right For Sight
  • H4 Women’s Urological Health

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 20 heading(s) have substantive, well-formed text
PASS
All 20 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="key" id="s">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#stext(Product name...)placeholder only

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

<input type="text" name="key" id="s">

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

A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 159 visible text node(s) render at >= 12 CSS pixels
PASS
All 159 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback