Skip to content
https://projectamino.io

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
82
GRADE
B
FIX
5
REVIEW
3
PASS
16
INFO
0
Checks
24
16 PASS 3 REVIEW 5 FIX
D
Heading Hierarchy
Action
38 headings, 3 skip(s)
FIX
38 headings, 3 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Science-Backed, 
Premium Research Peptides​
  • H3 Fast & Reliable Shipping skipped
  • H3 99% Purity - Third Party Tested
  • H3 Made in the USA
  • H3 24/7 Customer Support
  • H2 Who We Are
  • H2 Why Choose Us
  • H4 Fast and Reliable Delivery skipped
  • H4 Dedicated Support for Researchers
  • H4 99% Purity - Third Party Tested
  • H4 Transparent Quality Assurance
  • H2 Discover Our Top Research Peptides
  • H5 Bacteriostatic Water skipped
  • H5 RTA-GLP-3R
  • H5 Tesamorelin
  • H5 GHK-Cu
  • H5 KPV
  • H5 TRZ-GLP-2T
  • H5 MOTS-C
  • H5 BPC-157 – Research-Grade Peptide
  • H5 SS-31
  • H5 NAD+
  • H5 KPV
  • H5 GHK-Cu
  • H5 Bacteriostatic Water
  • H5 TRZ-GLP-2T
  • H5 Tesamorelin
  • H5 Semax
  • H5 RTA-GLP-3R
  • H5 MOTS-C
  • H5 KLOW 4X Blend
  • H5 BPC-157 – Research-Grade Peptide
  • H2 Built for Researchers, Backed by Science
  • H3 Guides and Educational Resources
  • H3 Shipping and Delivery
  • H2 Important Notice: Research Use Only
  • H1 Project Amino duplicate H1
  • H2 21+

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 ▾

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 ▾

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

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
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.
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, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA
a About Us
1.28:1
#000000
on
#0D2321
needs 4.5:1 (normal text)
16px · top of page (header area)
a Products
1.30:1
#000000
on
#0C2522
needs 4.5:1 (normal text)
16px · above the fold
a Peptides
1.32:1
#000000
on
#0C2623
needs 4.5:1 (normal text)
16px · above the fold
a Sprays
1.33:1
#000000
on
#0D2724
needs 4.5:1 (normal text)
16px · above the fold
a Liquids
1.36:1
#000000
on
#0D2926
needs 4.5:1 (normal text)
16px · above the fold
a Capsules
1.44:1
#000000
on
#0D2E2B
needs 4.5:1 (normal text)
16px · above the fold
a GLPs
1.48:1
#000000
on
#0E302D
needs 4.5:1 (normal text)
16px · above the fold
a All Products
1.52:1
#000000
on
#103231
needs 4.5:1 (normal text)
16px · above the fold
a Products Certificates
1.73:1
#000000
on
#103C3A
needs 4.5:1 (normal text)
16px · above the fold
a Affiliate Program
1.98:1
#000000
on
#114642
needs 4.5:1 (normal text)
16px · above the fold
a Track My Order
2.44:1
#000000
on
#14554F
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Science-Backed, 
P…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Who We Are21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why Choose Us21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Discover Our Top Res…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Built for Researcher…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Important Notice: Re…21.00:13.0:1
#000000
#FFFFFF
Pass
title Research Peptides On…18.18:14.5:1
#000000
#E5F1F1
Pass
a Skip to content18.18:14.5:1
#000000
#E5F1F1
Pass
a Home7.15:14.5:1
#000000
#899A99
Pass
a About Us1.28:14.5:1
#000000
#0D2321
Fail
a Products1.30:14.5:1
#000000
#0C2522
Fail
a Peptides1.32:14.5:1
#000000
#0C2623
Fail
a Sprays1.33:14.5:1
#000000
#0D2724
Fail
a Liquids1.36:14.5:1
#000000
#0D2926
Fail
a Capsules1.44:14.5:1
#000000
#0D2E2B
Fail
a GLPs1.48:14.5:1
#000000
#0E302D
Fail
a All Products1.52:14.5:1
#000000
#103231
Fail
a Products Certificate…1.73:14.5:1
#000000
#103C3A
Fail
a Affiliate Program1.98:14.5:1
#000000
#114642
Fail
a Track My Order2.44:14.5:1
#000000
#14554F
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+
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Navbar Mobile Menu" MAIN CONTENTINFO footer
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
8 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 8 all-caps heading(s)
A+
Alt Text Quality
All 52 images OK
PASS
All 52 images OK
Info::
22 decorative image(s) correctly marked
Info::
30 image(s) with good alt text
52 images 30 good alt text 22 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#dgwt-wcas-search-input-1searchProducts searchfor/id
#dgwt-wcas-search-input-2searchProducts searchfor/id
#dgwt-wcas-search-input-3searchProducts searchfor/id
age_gate[remember]checkboxnone
A+
Form Input Types
4 form control(s) checked, no type mismatches
PASS
4 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 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
10 explicit tabindex attribute(s) checked, no anti-patterns
PASS
10 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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 73 visible text node(s) render at >= 12 CSS pixels
PASS
All 73 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found - Project Amino ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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.
A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 26 passed
PASS
92

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
21+ Adults Only Please confirm that you’re over 21 or please, leave the websi… body.home > div.age-gate__wrapper > div.age-gate

These are opportunities to improve the usage of ARIA in your application which 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
Fast & Reliable Shipping div.elementor-element > div.elementor-icon-box-wrapper > div.elementor-icon-box-content > h3.elementor-icon-box-title
Fast and Reliable Delivery div.elementor-element > div.elementor-icon-box-wrapper > div.elementor-icon-box-content > h4.elementor-icon-box-title
SS-31 div.pp-woo-product-wrapper > div.pp-woo-products-summary-wrap > a.pp-loop-product__link > h5.woocommerce-loop-product__title

These are opportunities to improve keyboard navigation in your application.

Names and labels

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
Shopper Approved trust metrics: 50+ five-star ratings. div.elementor-element > div.content-box > div.sa-badge-wrapper > 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.

○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●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.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○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
○`<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.
○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.
○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.

Send Feedback