Skip to content
https://rewordsai.app

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
87
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Mobile-Readable Font Sizes
97% of visible text renders at >= 12 CSS px (10 below threshold)
REVIEW
97% of visible text renders at >= 12 CSS px (10 below threshold)
Info::
10 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: <span> 10.0px ("Up to 50%"); <div> 10.0px ("Detected Text"); <div> 10.0px ("Replacement Text"); <div> 10.0px ("Detected Text"); <div> 10.0px ("Replacement Text").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title ReWords AI ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Favicon & Branding
7 icon(s) detected
REVIEW
7 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 #d97706 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A
Landmark Structure
14 landmarks
PASS
14 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
29 headings
PASS
29 headings
Info::
Single H1 present
  • H1 ReWords AI — Edit Text in Image with Matching Fonts and Styles
  • H2 Change the words. Keep the photo.
  • H2 How It Works
  • H3 Upload
  • H3 Select
  • H3 Replace All Text
  • H3 Download
  • H2 What is ReWords AI?
  • H2 Practical Editing Scenarios
  • H3 Fix AI Image Text
  • H3 Marketing Banners & Promos
  • H3 Social Media Graphics
  • H3 E-Commerce Product Imagery
  • H3 Visual Translation & Localization
  • H3 App & Web Mockup Updates
  • H2 Why Choose ReWords AI
  • H2 Text edits on finished images
  • H3 Update the sale without reprinting
  • H3 Shift the showtime on the marquee
  • H3 Reschedule without rewriting the page
  • H3 Rename the blend on the same cup
  • H2 How ReWords AI Compares
  • H3 Direct Screenshot Refinements
  • H3 Need Assistance or High-Volume Help?
  • H2 What people say after the first edit
  • H2 Frequently Asked Questions
  • H2 Ready to edit text in image with ReWords AI?
  • H2 Related tools
  • H2 Related articles
A+
Heading Text Quality
All 29 heading(s) have substantive, well-formed text
PASS
All 29 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 13 images OK
PASS
All 13 images OK
Info::
13 image(s) with good alt text
13 images 13 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="file">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputfile(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="file">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 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+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: ReWords AI
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name ReWords AI ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=pwa&utm_medium=install ✓Display Mode standalone ✓
Name ReWords AI Display Mode standalone Theme Color #D97706 Background Color #fafaf9 Icons 2 icon(s)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
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
h1 ReWords AI — Edit …6.29:13.0:1
#000000
#908C88
Pass
h2 Change the words. Ke…6.52:13.0:1
#000000
#928F8B
Pass
h2 How It Works6.52:13.0:1
#000000
#928F8B
Pass
h2 What is ReWords AI?6.52:13.0:1
#000000
#928F8B
Pass
h2 Practical Editing Sc…6.52:13.0:1
#000000
#928F8B
Pass
h2 Why Choose ReWords A…6.52:13.0:1
#000000
#928F8B
Pass
h2 Text edits on finish…6.52:13.0:1
#000000
#928F8B
Pass
h2 How ReWords AI Compa…6.52:13.0:1
#000000
#928F8B
Pass
h2 What people say afte…6.52:13.0:1
#000000
#928F8B
Pass
h2 Frequently Asked Que…6.52:13.0:1
#000000
#928F8B
Pass
h2 Ready to edit text i…6.52:13.0:1
#000000
#928F8B
Pass
h2 Related tools6.52:13.0:1
#000000
#928F8B
Pass
h2 Related articles6.52:13.0:1
#000000
#928F8B
Pass
h3 Upload6.52:13.0:1
#000000
#928F8B
Pass
h3 Select6.52:13.0:1
#000000
#928F8B
Pass
h3 Replace All Text6.52:13.0:1
#000000
#928F8B
Pass
h3 Download6.52:13.0:1
#000000
#928F8B
Pass
h3 Fix AI Image Text6.52:13.0:1
#000000
#928F8B
Pass
h3 Marketing Banners & …6.52:13.0:1
#000000
#928F8B
Pass
h3 Social Media Graphic…6.52:13.0:1
#000000
#928F8B
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 — 2 failing, 23 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
Start for Free header.w-full > div.mx-auto > div.flex > button.inline-flex
Start Editing Free div.relative > div.flex > div.relative > button.flex
Replacement Text div.overflow-hidden > div.mt-3 > div.rounded-lg > div.text-[10px]
div.overflow-hidden > div.mt-3 > div.rounded-lg > div.text-[10px] div.overflow-hidden > div.mt-3 > div.rounded-lg > div.text-[10px]
article.grid > div.flex > p.mt-5 > span.rounded-md article.grid > div.flex > p.mt-5 > span.rounded-md
article.grid > div.flex > p.mt-5 > span.rounded-md article.grid > div.flex > p.mt-5 > span.rounded-md
table.w-full > thead > tr.border-b > th.px-5 table.w-full > thead > tr.border-b > th.px-5

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Install App div.paper-grid > div.fixed > div.group > button.inline-flex
○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
●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
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●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.
○`[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 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
○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.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback