Skip to content
https://signupgenius.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
3 landmarks
FIX
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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.
Info::
No banner (header) landmark
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 (missing!) NAV MAIN (missing!) CONTENTINFO footer

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

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://signupgenius.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://signupgenius.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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
Alt Text Quality
3 of 21 images have issues
REVIEW
3 of 21 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
18 image(s) with good alt text
21 images 18 good alt text 3 missing
IssueCount
missing3 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA
h1 Simplify planning.
2.95:1
#000000
on
#585857
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 Amplify
2.95:1
#000000
on
#585858
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h3 Sign Ups
2.95:1
#000000
on
#585858
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Auctions
2.95:1
#000000
on
#585858
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Tickets
2.95:1
#000000
on
#585858
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Donations
2.95:1
#000000
on
#585858
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Products
2.95:1
#000000
on
#585858
needs 3.0:1 (large text)
19px · bottom of viewport
h3 About
2.95:1
#000000
on
#585858
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Support
2.95:1
#000000
on
#585858
needs 3.0:1 (large text)
19px · bottom of viewport
h3 My Account
2.95:1
#000000
on
#585858
needs 3.0:1 (large text)
19px · bottom of viewport
title SignUpGenius - Free Online Sign Up Forms
2.91:1
#000000
on
#575757
needs 4.5:1 (normal text)
16px · top of page (header area)
span Products
2.91:1
#000000
on
#575757
needs 4.5:1 (normal text)
16px · top of page (header area)
a Pricing
2.52:1
#000000
on
#564C47
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span More
2.87:1
#000000
on
#575655
needs 4.5:1 (normal text)
16px · top of page (header area)
span Create a Sign Up
2.87:1
#000000
on
#575655
needs 4.5:1 (normal text)
16px · above the fold

3 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Simplify planning.2.95:13.0:1
#000000
#585857
Fail
h1 Amplify2.95:13.0:1
#000000
#585858
Fail
h3 Products21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Sign Ups2.95:13.0:1
#000000
#585858
Fail
h3 Auctions2.95:13.0:1
#000000
#585858
Fail
h3 Tickets2.95:13.0:1
#000000
#585858
Fail
h3 Donations2.95:13.0:1
#000000
#585858
Fail
h3 Products2.95:13.0:1
#000000
#585858
Fail
h3 About2.95:13.0:1
#000000
#585858
Fail
h3 Support2.95:13.0:1
#000000
#585858
Fail
h3 My Account2.95:13.0:1
#000000
#585858
Fail
title SignUpGenius - Free …2.91:14.5:1
#000000
#575757
Fail
span Products2.91:14.5:1
#000000
#575757
Fail
a Pricing2.52:14.5:1
#000000
#564C47
Fail
span More2.87:14.5:1
#000000
#575655
Fail
span Create a Sign Up2.87:14.5:1
#000000
#575655
Fail
span Create21.00:14.5:1
#000000
#FFFFFF
Pass
a Sign In21.00:14.5:1
#000000
#FFFFFF
Pass
a Sign In21.00:14.5:1
#000000
#FFFFFF
Pass
span Sign Ups21.00:14.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.

B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 22 passed
REVIEW
83

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
Create nav#basic-navbar-nav > div.header-right > button.sgn-btn > span.d-inline
Get started for free div.hero-content > div.hero-text > div.hero-button-container > a.hero-button
Host an Online Auction div.product-card > div.product-content > div.product-actions > a.product-button
Learn More About Auctions div.product-card > div.product-content > div.product-actions > a.learn-more-link
Read the full story div.active > div.proof-card > div.proof-action > a.full-story-link
Create a Sign Up div.container > div.cta-content > div.cta-button-container > a.cta-button

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Auctions div.product-card > div.product-content > div.product-header > h3.product-title

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.hero-image > section.hero > div.shape > img div.hero-image > section.hero > div.shape > img
div.hero-image > section.hero > div.shape > img div.hero-image > section.hero > div.shape > img
div.hero-image > section.hero > div.shape > img div.hero-image > section.hero > div.shape > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SignUpGenius Logo div.container > div.d-lg-none > div.d-flex > a

These are opportunities to improve the semantics of the controls in your application. This 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
Slide 1 div.product-container > div.new-home-carousel > div.carousel-indicators > button
Slide 2 div.product-container > div.new-home-carousel > div.carousel-indicators > button.active
Slide 3 div.product-container > div.new-home-carousel > div.carousel-indicators > button
Slide 4 div.product-container > div.new-home-carousel > div.carousel-indicators > button
Slide 1 div.container > div.new-home-carousel > div.carousel-indicators > button
Slide 2 div.container > div.new-home-carousel > div.carousel-indicators > button.active
Slide 3 div.container > div.new-home-carousel > div.carousel-indicators > button

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
●`[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
●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
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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.
○`[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
○`<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.
○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.
○Identical links have the same purpose.
○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.
A
Heading Hierarchy
10 headings, 1 skip(s)
PASS
10 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Products
  • H1 Simplify planning.Amplify impact.
  • H3 Sign Ups skipped
  • H3 Auctions
  • H3 Tickets
  • H3 Donations
  • H3 Products
  • H3 About
  • H3 Support
  • H3 My Account

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback