Accessibility

D

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

F

Heading Hierarchy

Action

32 headings, 10 skip(s)

FIX

32 headings, 10 skip(s)

No H1 heading found

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

H4 Everything you need—included:
H6 Doctor-guided GLP-1 care skipped
H2 Weight loss made easy with personalized care
H3 A smarter approach to weight loss, built around you
H6 Care Designed for Women's Health skipped
H2 Whole-body care for her balance, vitality, and confidence
H3 Support that evolves with your body
H6 METABOLIC NUTRITION skipped
H2 Fuel your transformation, protect your progress
H3 Skip the hassle of meal planning and prepping
H6 Purpose-driven supplementation skipped
H2 Supplements with the power to boost real results
H3 Support that helps you feel better over time
H3 Doctor-formulated blends designed to support how your body works best.
H6 Care for energy, hormones, and performance skipped
H2 Men’s healthcare, built for men who expect more
H3 Care designed to help you feel stronger, sharper, and more in control
H6 ADVANCED Peptide SUPPORT skipped
H2 Targeted support for recovery, performance, and longevity
H3 Support that works below the surface
H6 Targeted hair restoration skipped
H2 Proven care for thinning hair and regrowth
H3 Advanced hair regrowth care to help you look and feel your best
H6 Personalized care for healthier, clearer skin. skipped
H2 Skincare that goes deeper than the surface
H3 Skincare designed to treat the root cause—not just cover it up.
H6 Better is possible—and we built for it. skipped
H2 Modern healthcare, built around you
H3 Personal care coaching and nutrition support
H3 We're creating a better healthcare experience, and the details matterWe're here for those details
H6 Those who chose MEDVi skipped
H2 There’s a reason people are raving about us.

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

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

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

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

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

Link & Button Quality

Action

5 issue(s) across 26 links and 0 buttons

FIX

5 issue(s) across 26 links and 0 buttons

2 link(s) with no accessible text

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

Got: ./; ./

3 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: http://glp.medvi.org/ ("Learn More"); https://meals.medvi.org ("Learn More"); http://quad.medvi.org/ ("Learn More")

4 link(s) open in new tab without warning

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

Got: https://www.triadrx.us/; https://www.redrockhomepharmacy.com/; https://beakerpharmacy.com/beakerpharmacy-compounding; https://www.legitscript.com/websites/?checker_keywords=medvi.org

17 link(s) with descriptive text

26 links

2 empty

3 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
./	(empty)	empty	Add link text or aria-label
./#weight-loss	Weight Loss	img no alt	Add alt attribute to the image
./#peptides	Peptides & Longevity	img no alt	Add alt attribute to the image
./#mens-health	Men's Health	img no alt	Add alt attribute to the image
./#womens-health	Women's Health	img no alt	Add alt attribute to the image
http://glp.medvi.org/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Home page
https://meals.medvi.org	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Meals.Medvi.Org
http://quad.medvi.org/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Home page
./	(empty)	empty	Add link text or aria-label
https://www.triadrx.us/	https://www.triadrx.us	new tab	Add '(opens in new tab)' to text
https://www.redrockhomepharmacy.com/	https://www.redrockhomepharmac…	new tab	Add '(opens in new tab)' to text
https://beakerpharmacy.com/beakerpharmac…	https://beakerpharmacy.com/bea…	new tab	Add '(opens in new tab)' to text
https://www.legitscript.com/websites/?ch…	Verify Approval for www.medvi.…	new tab	Add '(opens in new tab)' to text

17 links and buttons have descriptive text

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

./; ./

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

Generic link text like 'click here' doesn't describe the destination.

http://glp.medvi.org/ ("Learn More"); https://meals.medvi.org ("Learn More"); http://quad.medvi.org/ ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.triadrx.us/; https://www.redrockhomepharmacy.com/; https://beakerpharmacy.com/beakerpharmacy-compounding; https://www.legitscript.com/websites/?checker_keywords=medvi.org

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

D

Favicon & Branding

Action

3 icon(s) detected

FIX

3 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

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Mobile-Readable Font Sizes

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

REVIEW

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

14 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: <p> 10.0px ("Licensed Medical Providers"); <p> 10.0px ("100% Online"); <p> 10.0px ("Clear pricing"); <p> 10.0px ("Shipped to your door"); <h6> 10.0px ("Doctor-guided GLP-1 care").

C

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

B

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.

B

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 20 passed

REVIEW

88

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.

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
DOCTOR-GUIDED GLP-1 CARE `div.framer-ol1qli > div.framer-1h8iae3 > div.framer-1b0cm1f > h6.framer-text`
CARE DESIGNED FOR WOMEN'S HEALTH `div.framer-70ndp4 > div.framer-1rbjezi > div.framer-1tqcm9m > h6.framer-text`
METABOLIC NUTRITION `div.framer-qio70r > div.framer-yq7if2 > div.framer-ovz6x > h6.framer-text`
PURPOSE-DRIVEN SUPPLEMENTATION `div.framer-1277khb > div.framer-1gwzqnc > div.framer-8xeidg > h6.framer-text`
CARE FOR ENERGY, HORMONES, AND PERFORMANCE `div.framer-1lxh8b2 > div.framer-8h8sw3 > div.framer-1o08f22 > h6.framer-text`
ADVANCED PEPTIDE SUPPORT `div.framer-30gyzx > div.framer-16v0z8p > div.framer-mjrn0j > h6.framer-text`
TARGETED HAIR RESTORATION `div.framer-1oujiy1 > div.framer-vwcqgz > div.framer-14804ji > h6.framer-text`
PERSONALIZED CARE FOR HEALTHIER, CLEARER SKIN. `div.framer-1efejek > div.framer-joy6ig > div.framer-1t7811e > h6.framer-text`
BETTER IS POSSIBLE—AND WE BUILT FOR IT. `div.framer-1q960bp > div.framer-181kkv1 > div.framer-2ofegl > h6.framer-text`
THOSE WHO CHOSE MEDVI `div.framer-1vs78ku > div.framer-1mgk3zp > div.framer-1p4rz5m > h6.framer-text`

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
div.framer-Tq2IF > div.framer-ysz1pv > div.framer-14480ss > a.framer-1b33l01 `div.framer-Tq2IF > div.framer-ysz1pv > div.framer-14480ss > a.framer-1b33l01`
div.framer-1kh0292 > div.framer-opm6yw > div.framer-rft0ff > a.framer-1j52qoo `div.framer-1kh0292 > div.framer-opm6yw > div.framer-rft0ff > a.framer-1j52qoo`

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LICENSED MEDICAL PROVIDERS `div#callouts > div.framer-1q40ibv > ul > li.ticker-item`
100% ONLINE `div#callouts > div.framer-1q40ibv > ul > li.ticker-item`
CLEAR PRICING `div#callouts > div.framer-1q40ibv > ul > li.ticker-item`
SHIPPED TO YOUR DOOR `div#callouts > div.framer-1q40ibv > ul > li.ticker-item`
MEDVi Customer Review `div.framer-1b1zwgh > div.framer-1r8i0wi > ul > li.ticker-item`
Billy "Ms. Gonzalez was great! She listened to my needs and provided details o… `div.framer-1b1zwgh > div.framer-1r8i0wi > ul > li.ticker-item`
Terika “The provider was knowledgeable and helpful. She answered all my questi… `div.framer-1b1zwgh > div.framer-1r8i0wi > ul > li.ticker-item`
Review Ranking `div.framer-1b1zwgh > div.framer-1r8i0wi > ul > li.ticker-item`
Jamie "The questions are to the point and easy to navigate. I'm able to voice … `div.framer-1b1zwgh > div.framer-1r8i0wi > ul > li.ticker-item`
Jacqueline "My experience is very positive. I am doing very well. Slowly and s… `div.framer-1b1zwgh > div.framer-1r8i0wi > ul > li.ticker-item`
Diana “The staff has been so friendly and caring. I didn't expect that! If I c… `div.framer-1b1zwgh > div.framer-1r8i0wi > ul > li.ticker-item`
Review Ranking `div.framer-1b1zwgh > div.framer-1r8i0wi > ul > li.ticker-item`
Donna ”The Physician was very knowledgeable and ready to answer all my concern… `div.framer-1b1zwgh > div.framer-1r8i0wi > ul > li.ticker-item`
Terri "Losing weight without a crazy diet, without cardio...it just felt like … `div.framer-1b1zwgh > div.framer-1sgsxo7 > ul > li.ticker-item`
Review Image `div.framer-1b1zwgh > div.framer-1sgsxo7 > ul > li.ticker-item`
Alexandra “Everything was quick and concise. I was treated professionally and … `div.framer-1b1zwgh > div.framer-1sgsxo7 > ul > li.ticker-item`
Greg “I was ready to give up. Wow. I would pay 10x as much if I had to. Dietin… `div.framer-1b1zwgh > div.framer-1sgsxo7 > ul > li.ticker-item`
Review of Service `div.framer-1b1zwgh > div.framer-1sgsxo7 > ul > li.ticker-item`
Lou-Ann “MEDVi Doctors & Staff have been very professional and prompt with any… `div.framer-1b1zwgh > div.framer-1sgsxo7 > ul > li.ticker-item`
Elizabeth “My Clinician was kind, informative, gave a clear understanding of e… `div.framer-1b1zwgh > div.framer-1sgsxo7 > ul > li.ticker-item`
Dan Review Ranking `div.framer-1b1zwgh > div.framer-1sgsxo7 > ul > li.ticker-item`
Dan “Dolores was very knowledgeable and very friendly she answered any questio… `div.framer-1b1zwgh > div.framer-1sgsxo7 > ul > li.ticker-item`

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

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

●Image elements have `[alt]` attributes

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

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

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

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○Buttons have an accessible name

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

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

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

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 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: 1 all-caps heading(s)

A+

Alt Text Quality

All 49 images OK

PASS

All 49 images OK

35 decorative image(s) correctly marked

14 image(s) with good alt text

49 images 14 good alt text 35 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

9 explicit tabindex attribute(s) checked, no anti-patterns

PASS

9 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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
h2 Weight loss	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 with personalized ca…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Whole-body	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 balance, vitality, a…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 your	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Supplements with the	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 real results	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Men’s healthcare, …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 for recovery, perfor…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 for thinning hair an…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 that goes deeper tha…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Modern healthcare,	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 There’s a reason p…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 A smarter approach t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Support that evolves…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Skip the hassle of m…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Support that helps y…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Doctor-formulated bl…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Care designed to hel…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Support that works b…	21.00:1	3.0:1	#000000	#FFFFFF	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.