Skip to content
https://rasterbator.org

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
82
GRADE
B
FIX
3
REVIEW
6
PASS
15
INFO
0
Checks
24
15 PASS 6 REVIEW 3 FIX
D
Iframe Accessibility
Action
6/7 iframe(s) missing title; 0 placeholder(s)
FIX
6/7 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://www.google.com/recaptcha/api2/aframe")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://googleads.g.doubleclick.net/pagead/html/r20261028/r20190131/zrt_lookup.…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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::
2 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 2 <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
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

C
Form Accessibility
Action
3 of 12 controls have issues
REVIEW
3 of 12 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="file">; <input type="file">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="url">
Info::
9 control(s) properly labeled
12 controls
9 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
selectselectLanguagearia-label
selectselectTypenone
textareatextareaYour feedbacknone
inputemailEmail (optional, if you want a reply)none
inputfileScreenshot (optional)none
selectselectTypenone
textareatextareaYour feedbacknone
inputemailEmail (optional, if you want a reply)none
inputfileScreenshot (optional)none
inputurl(http://)placeholder only
inputfile(none)none
inputfile(none)none

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

<input type="file">; <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

Placeholder text disappears on focus and is not a reliable label.

<input type="url">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
Mobile Keyboard & Autofill
Action
3/5 eligible field(s) missing autocomplete or inputmode
REVIEW
3/5 eligible field(s) missing autocomplete or inputmode
Warning::
3 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: url, email.
Got: <input type="url">, <input type="email">, <input type="email">
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404: This page could not be found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 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 #3b82f6 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+
Heading Hierarchy
39 headings
PASS
39 headings
Info::
Single H1 present
  • H1 Free Online Rasterbator Poster Maker
  • H2 Source image
  • H2 Made with Rasterbator
  • H3 Image Upscaler
  • H3 Image Resizer
  • H3 Wall Planner
  • H3 Wall Art Generator
  • H3 Browse Templates
  • H3 Printing Tips
  • H2 What is Rasterbation?
  • H3 Halftone Poster Effect Explained
  • H2 How Rasterbator Works
  • H3 Upload
  • H3 Configure
  • H3 Print & Assemble
  • H2 Why Choose Rasterbator as Your Poster Generator?
  • H3 100% Free
  • H3 Complete Privacy
  • H3 Easy to Use
  • H3 Multiple Effects
  • H2 How to Make a Large Wall Poster at Home with Rasterbator
  • H3 Step 1: Upload Your Image
  • H3 Step 2: Configure and Generate
  • H3 Step 3: Print and Assemble
  • H3 Tips for Best Rasterbator Results
  • H4 Use the Right Paper
  • H4 Print at 100% Scale
  • H4 Lay Out Before Taping
  • H4 View from a Distance
  • H2 Rasterbator vs Other Wall Poster Makers
  • H2 Rasterbator — Frequently Asked Questions
  • H2 Supported Paper Sizes
  • H3 Create
  • H3 Image Tools
  • H3 Print Tools
  • H3 Resources
  • H2 Send feedback
  • H3 Legal
  • H2 Send feedback
A+
Heading Text Quality
All 39 heading(s) have substantive, well-formed text
PASS
All 39 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 34 images OK
PASS
All 34 images OK
Info::
15 decorative image(s) correctly marked
Info::
19 image(s) with good alt text
34 images 19 good alt text 15 decorative
All images have appropriate alt text.
A+
Form Input Types
12 form control(s) checked, no type mismatches
PASS
12 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
12 form control(s) checked, no input-semantic issues
PASS
12 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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
5 explicit tabindex attribute(s) checked, no anti-patterns
PASS
5 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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+
Mobile-Readable Font Sizes
All 152 visible text node(s) render at >= 12 CSS pixels
PASS
All 152 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Rasterbator - Image to Poster Converter
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Rasterbator - Image to Poster Converter ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Rasterbator - Image to Poster Converter Display Mode standalone Theme Color #3b82f6 Background Color #ffffff Icons 4 icon(s)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Service worker registration detected
The page calls `navigator.serviceWorker.register(...)` -- the prerequisite for any real PWA capability (offline support, push notifications, background sync, Cache API). This is a positive signal; whether the registered worker actually does what you want is a separate question (check DevTools > Application > Service Workers).
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 Free Online Rasterba…18.58:13.0:1
#000000
#F1F1F0
Pass
h2 Source image18.55:13.0:1
#000000
#F0F1F0
Pass
h2 Made with Rasterbato…18.55:13.0:1
#000000
#F0F1F0
Pass
h2 What is Rasterbation…18.55:13.0:1
#000000
#F0F1F0
Pass
h2 How Rasterbator Work…18.55:13.0:1
#000000
#F0F1F0
Pass
h2 Why Choose Rasterbat…18.55:13.0:1
#000000
#F0F1F0
Pass
h2 How to Make a Large …18.55:13.0:1
#000000
#F0F1F0
Pass
h2 Rasterbator vs Other…18.55:13.0:1
#000000
#F0F1F0
Pass
h2 Rasterbator — Freq…18.55:13.0:1
#000000
#F0F1F0
Pass
h2 Supported Paper Size…18.55:13.0:1
#000000
#F0F1F0
Pass
h2 Send feedback18.55:13.0:1
#000000
#F0F1F0
Pass
h2 Send feedback18.55:13.0:1
#000000
#F0F1F0
Pass
h3 Image Upscaler18.55:13.0:1
#000000
#F0F1F0
Pass
h3 Image Resizer18.55:13.0:1
#000000
#F0F1F0
Pass
h3 Wall Planner18.55:13.0:1
#000000
#F0F1F0
Pass
h3 Wall Art Generator18.55:13.0:1
#000000
#F0F1F0
Pass
h3 Browse Templates18.55:13.0:1
#000000
#F0F1F0
Pass
h3 Printing Tips18.55:13.0:1
#000000
#F0F1F0
Pass
h3 Halftone Poster Effe…18.55:13.0:1
#000000
#F0F1F0
Pass
h3 Upload18.55:13.0:1
#000000
#F0F1F0
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 100/100 — 0 failing, 29 passed
PASS
100

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.

○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
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Links are distinguishable without relying on color.
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○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
○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
○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.
○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