Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Landmark Structure

Action

6 landmarks

FIX

6 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

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

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

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title MyFitnessPal | Challenge ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Favicon & Branding

7 icon(s) detected

REVIEW

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

Name present: MyFitnessPal

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name MyFitnessPal ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode browser ✗

Name MyFitnessPal Display Mode browser Theme Color #0066ee Background Color #0066ee Icons 2 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA

h2 Sync steps, weight, workouts & more

1.68:1

#000000

#013171

needs 3.0:1 (large text)

24px · bottom of viewport

h2 If it’s edible, it’s in here

1.68:1

#000000

#013171

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Nutrition tracking works, here's the pro…

1.68:1

#000000

#013171

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Starting is the hard part.

1.68:1

#000000

#013171

needs 3.0:1 (large text)

24px · bottom of viewport

h2 As seen in...

1.68:1

#000000

#013171

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Q&A

1.68:1

#000000

#013171

needs 3.0:1 (large text)

24px · bottom of viewport

h2 From our experts

1.68:1

#000000

#013171

needs 3.0:1 (large text)

24px · bottom of viewport

h2 About MyFitnessPal

1.68:1

#000000

#013171

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Essential Guide to Food Logging

1.68:1

#000000

#013171

needs 3.0:1 (large text)

19px · bottom of viewport

h3 11 Things You’ll Learn Using MyFitness…

1.68:1

#000000

#013171

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Essential Guide to Healthy Eating

1.68:1

#000000

#013171

needs 3.0:1 (large text)

19px · bottom of viewport

title Calorie Tracker & BMR Calculator to Reac…

1.74:1

#000000

#003377

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 3.5 Million	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 5-Star Ratings	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Hit your health goal…	9.07:1	3.0:1	#000000	#99ACC6	Pass
h2 Sync steps, weight, …	1.68:1	3.0:1	#000000	#013171	Fail
h2 If it’s edible, it…	1.68:1	3.0:1	#000000	#013171	Fail
h2 Nutrition tracking w…	1.68:1	3.0:1	#000000	#013171	Fail
h2 Starting is the hard…	1.68:1	3.0:1	#000000	#013171	Fail
h2 As seen in...	1.68:1	3.0:1	#000000	#013171	Fail
h2 Q&A	1.68:1	3.0:1	#000000	#013171	Fail
h2 From our experts	1.68:1	3.0:1	#000000	#013171	Fail
h2 About MyFitnessPal	1.68:1	3.0:1	#000000	#013171	Fail
h3 Essential Guide to F…	1.68:1	3.0:1	#000000	#013171	Fail
h3 11 Things You’ll L…	1.68:1	3.0:1	#000000	#013171	Fail
h3 Essential Guide to H…	1.68:1	3.0:1	#000000	#013171	Fail
title Calorie Tracker & BM…	1.74:1	4.5:1	#000000	#003377	Fail
p Reviews	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p How It Works	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Apps	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Advertise With Us	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span #1 nutrition trackin…	21.00:1	4.5: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.

A+

Heading Hierarchy

19 headings

PASS

19 headings

Single H1 present

H1 #1 nutrition tracking appNutrition tracking forreal life
H2 3.5 Million 5-Star Ratings
H2 Hit your health goals in 1-2-3
H2 Sync steps, weight, workouts & more
H2 If it’s edible, it’s in here
H2 Nutrition tracking works, here's the proof
H2 Starting is the hard part. We make it easy...
H2 As seen in...
H2 Q&A
H3 Is MyFitnessPal a free calorie tracker app?
H3 How to track calories with a calorie counter app like MyFitnessPal?
H3 What nutrition data can I track besides calories?
H3 Does MyFitnessPal use a BMI calculator or BMR calculator to set goals?
H3 Can I track weight, workouts, water, or intermittent fasting?
H2 From our experts
H3 Essential Guide to Food Logging
H3 11 Things You’ll Learn Using MyFitnessPal
H3 Essential Guide to Healthy Eating
H2 About MyFitnessPal

Alt Text Quality

All 36 images OK

PASS

All 36 images OK

5 image(s) with alt text over 125 characters

18 decorative image(s) correctly marked

13 image(s) with good alt text

36 images 13 good alt text 18 decorative

Issue	Count
too long	5 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

41 links, 19 buttons — all OK

PASS

41 links, 19 buttons — all OK

41 link(s) with descriptive text

41 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

60 links and buttons have descriptive text

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 25 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.

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
App Review 1 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
App Review 2 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
App Review 3 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
App Review 4 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
App Review 5 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
App Review 6 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
User Testimonial 1 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
User Testimonial 2 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
User Testimonial 3 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
User Testimonial 4 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
User Testimonial 5 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
User Testimonial 6 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
App Review 1 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
App Review 2 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
App Review 3 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
App Review 4 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
App Review 5 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
App Review 6 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
User Testimonial 1 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
User Testimonial 2 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
User Testimonial 3 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
User Testimonial 4 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
User Testimonial 5 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
User Testimonial 6 of 6 `div.MuiContainer-root > div.MuiBox-root > div.MuiBox-root > button.MuiButtonBase-root`
Cookie Preferences `div.MuiBox-root > div.MuiStack-root > div.MuiStack-root > button.MuiButtonBase-root`

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

●Buttons have an accessible name

●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

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

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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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.

○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

○No form fields have multiple labels

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

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

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

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