Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

18 PASS 4 REVIEW 2 FIX

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (10 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (10 below threshold)

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> 11.0px ("50% OFF"); <span> 10.0px ("Up to 50%"); <div> 10.0px ("Original Text (Detected)"); <div> 10.0px ("New Text (Replacement)"); <div> 10.0px ("Original Text (Detected)").

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 ReWords AI ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

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

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

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 #d97706 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Landmark Structure

13 landmarks

PASS

13 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

26 headings

PASS

26 headings

Single H1 present

H1 ReWords AI — Edit Existing Text in Images
H2 How It Works
H3 Upload
H3 Select
H3 Replace All Text
H3 Download
H2 What is ReWords AI?
H2 Edit text in images for every scenario
H3 Screenshots & chats
H3 Posters & flyers
H3 Product & e-commerce photos
H3 Memes & social graphics
H3 Creative documents
H3 AI-generated images
H2 Why edit text in image with AI instead of Photoshop?
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 Not a Text Overlay Tool. Built to Replace Existing Text
H3 Edit Text in Screenshots and Creative Images
H3 API for Developers?
H2 What people say after the first edit
H2 Questions About Editing Text in Images
H2 Ready to edit text in your image?

A+

Heading Text Quality

All 26 heading(s) have substantive, well-formed text

PASS

All 26 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 12 images OK

PASS

All 12 images OK

12 image(s) with good alt text

12 images 12 good alt text

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+

Link & Button Quality

50 links, 6 buttons — all OK

PASS

50 links, 6 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://www.adobe.com/products/photoshop.html

49 link(s) with descriptive text

50 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.adobe.com/products/photoshop…	Adobe Photoshop	new tab	Add '(opens in new tab)' to text

55 links and buttons have descriptive text

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

https://www.adobe.com/products/photoshop.html

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

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"

PASS

Lang attribute set to "en"

<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

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+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: ReWords AI

192x192 icon present

512x512 icon present

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

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

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)

Element	Ratio	Required	FG	BG	Result
h1 ReWords AI — Edit …	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 How It Works	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 What is ReWords AI?	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Edit text in images …	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Why edit text in ima…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Text edits on finish…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Not a Text Overlay T…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 What people say afte…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Questions About Edit…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Ready to edit text i…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Upload	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Select	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Replace All Text	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Download	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Screenshots & chats	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Posters & flyers	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Product & e-commerce…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Memes & social graph…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Creative documents	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 AI-generated images	19.14:1	3.0:1	#000000	#F7F4EF	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

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
Get Started `header.w-full > div.mx-auto > div.flex > button.inline-flex`
Edit an Image `div.relative > div.flex > div.mt-8 > a.inline-flex`
New Text (Replacement) `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.