Skip to content
https://magiceraser.live

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
89
GRADE
B
FIX
2
REVIEW
4
PASS
18
INFO
0
Checks
24
18 PASS 4 REVIEW 2 FIX
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Mobile-Readable Font Sizes
93% of visible text renders at >= 12 CSS px (14 below threshold)
REVIEW
93% of visible text renders at >= 12 CSS px (14 below threshold)
Info::
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: <div> 10.0px ("Before"); <div> 10.0px ("After"); <div> 10.0px ("Before"); <div> 10.0px ("After"); <span> 11.0px ("Remove").
B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found — Magic Eraser ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 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 Present
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 #b0d7e4 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer
A+
Heading Hierarchy
20 headings
PASS
20 headings
Info::
Single H1 present
  • H1 Magic Eraser AI Photo Editor for Effortless Editing
  • H2 Discover The Common Features
  • H3 Remove Objects
  • H3 Remove Background
  • H3 AI Fill
  • H3 AI Enhance
  • H2 Trusted by 10M+ users
  • H2 What is Magic Eraser?
  • H2 AI Photo Editing Tools for Faster Image Cleanup and Creation
  • H3 Remove objects from photos with clean AI retouching
  • H3 Remove and replace backgrounds with an AI background remover
  • H3 Enhance image quality with an AI photo enhancer
  • H3 Other amazing and Innovative AI Tools
  • H3 Expand images and uncrop photos with AI
  • H3 Apply AI photo filters for creative looks in one tap
  • H3 Use AI Fill to replace selected areas and rebuild missing image parts naturally
  • H2 Real people, real results.
  • H2 Explore more
  • H2 Frequently Asked Questions
  • H2 Start Creating Magic Today
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+
Alt Text Quality
All 44 images OK
PASS
All 44 images OK
Info::
17 decorative image(s) correctly marked
Info::
27 image(s) with good alt text
44 images 27 good alt text 17 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
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
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
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
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
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+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Magic Eraser
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Magic Eraser ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Magic Eraser Display Mode standalone Theme Color #B0D7E4 Background Color #ffffff Icons 5 icon(s)
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::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
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)
ElementRatioRequiredFGBGResult
h2 Trusted by 10M+ user…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What is Magic Eraser…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AI Photo Editing Too…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Real people, real re…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore more21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Frequently Asked Que…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Start Creating Magic…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Remove Objects21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Remove Background21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AI Fill21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AI Enhance21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Remove objects from …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Remove and replace b…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Enhance image qualit…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Expand images and un…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Apply AI photo filte…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Use AI Fill to repla…21.00:13.0:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
span Magic Eraser21.00:14.5:1
#000000
#FFFFFF
Pass
span Features20.65:14.5:1
#000000
#FDFDFD
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 96/100 — 1 failing, 24 passed
PASS
96

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
REMOVE div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
REMOVE div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
BLOG div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
BLOG div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
TEMPLATES div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
TEMPLATES div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
ACADEMY div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
INDUSTRIES div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
HOW-TO GUIDES div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
GLOSSARY div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]

These are opportunities to improve the legibility of your content.

○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
●`[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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○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.
○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.
○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.
○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