Skip to content
https://flyingsolo.nyc

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
5
REVIEW
9
PASS
10
INFO
0
Checks
24
10 PASS 9 REVIEW 5 FIX
F
Form Accessibility
Action
12 of 15 controls have issues
FIX
12 of 15 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="SMS__COUNTRY_CODE">; <input type="text" name="SMS__COUNTRY_CODE">; <input type="text" name="email_address_check">; <select name="footer-help" id="footer-help">
Warning::
8 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="FIRSTNAME" id="FIRSTNAME">; <input type="text" name="LASTNAME" id="LASTNAME">; <input type="text" name="EMAIL" id="EMAIL">; <input type="tel" name="SMS">; <input type="text" name="FIRSTNAME" id="FIRSTNAME">; <input type="text" name="LASTNAME" id="LASTNAME">; <input type="text" name="EMAIL" id="EMAIL">; <input type="tel" name="SMS">
Info::
3 control(s) properly labeled
15 controls
3 labeled
8 placeholder only
4 unlabeled
ControlTypeLabelMethod
selectselectSelect Languagearia-label
phrasesearchSearch inputaria-label
phrasesearchSearch inputaria-label
#FIRSTNAMEtext(FIRSTNAME)placeholder only
#LASTNAMEtext(LASTNAME)placeholder only
#EMAILtext(EMAIL)placeholder only
SMStel(Phone Number)placeholder only
#FIRSTNAMEtext(FIRST NAME)placeholder only
#LASTNAMEtext(LAST NAME)placeholder only
#EMAILtext(EMAIL)placeholder only
SMStel(PHONE NUMBER)placeholder only
SMS__COUNTRY_CODEtext(none)none
SMS__COUNTRY_CODEtext(none)none
email_address_checktext(none)none
#footer-helpselect(none)none

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

<input type="text" name="SMS__COUNTRY_CODE">; <input type="text" name="SMS__COUNTRY_CODE">; <input type="text" name="email_address_check">; <select name="footer-help" id="footer-help">

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="text" name="FIRSTNAME" id="FIRSTNAME">; <input type="text" name="LASTNAME" id="LASTNAME">; <input type="text" name="EMAIL" id="EMAIL">; <input type="tel" name="SMS">; <input type="text" name="FIRSTNAME" id="FIRSTNAME">; <input type="text" name="LASTNAME" id="LASTNAME">; <input type="text" name="EMAIL" id="EMAIL">; <input type="tel" name="SMS">

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 3 <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
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
2 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #content
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN CONTENTINFO (missing!)

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

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

C
Heading Hierarchy
Action
16 headings, 1 skip(s)
REVIEW
16 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 To add items to your wishlist, login or create an account!
  • H2 Come Fly With Us
  • H3 This is your all-access boarding pass to designer edits, events & exclusive drops
  • H4 Join now and get 10% off your first order
  • H3 City Sizzle
  • H3 Summer in the City
  • H3 Hottest Style
  • H2 Stock at Flying Solo
  • H5 Gabriel Daudt skipped
  • H5 Christian Petrovich
  • H5 FRAQAIR
  • H3 Newsletter Subscription
  • H4 Flying Solo Shopping
  • H3 Our Stores
  • H3 Help and Information
  • H3 Discover

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

C
Alt Text Quality
Action
2 of 28 images have issues
REVIEW
2 of 28 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
20 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
28 images 6 good alt text 20 decorative 2 missing
IssueCount
missing2 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

C
Mobile Keyboard & Autofill
Action
4/6 eligible field(s) missing autocomplete or inputmode
REVIEW
4/6 eligible field(s) missing autocomplete or inputmode
Warning::
4 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: search, tel.
Got: <input type="search" name="phrase">, <input type="search" name="phrase">, <input type="tel" name="SMS">, <input type="tel" name="SMS">
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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – Flying Solo NYC ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✓
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA 5 pass AA only
title Flying Solo NYC – Fashion Retail Space…
4.21:1
#000000
on
#7F6A73
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
4.21:1
#000000
on
#7F6A73
needs 4.5:1 (normal text)
16px · top of page (header area)
div Free shipping & free returns on all dome…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
option Select Language
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

1 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
h2 Come Fly With Us5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Stock at Flying Solo5.24:13.0:1
#000000
#7F7F7F
Pass
h3 To add items to your…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 This is your all-acc…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 City Sizzle5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Summer in the City5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Hottest Style5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Newsletter Subscript…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Our Stores5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Help and Information5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Discover5.24:13.0:1
#000000
#7F7F7F
Pass
title Flying Solo NYC – …4.21:14.5:1
#000000
#7F6A73
Fail
a Skip to content4.21:14.5:1
#000000
#7F6A73
Fail
div Free shipping & free…1.00:14.5:1
#000000
#000000
Fail
option Select Language1.66:14.5:1
#000000
#333333
Fail
option Arabic5.24:14.5:1
#000000
#7F7F7F
Pass
option Chinese (Simplified)5.24:14.5:1
#000000
#7F7F7F
Pass
option Dutch5.24:14.5:1
#000000
#7F7F7F
Pass
option English5.24:14.5:1
#000000
#7F7F7F
Pass
option French5.24:14.5:1
#000000
#7F7F7F
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 85/100 — 4 failing, 23 passed
REVIEW
85

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.

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
Gabriel Daudt section#testimonials > div#swiper-wrapper-734c32372d6231a2 > div.swiper-slide > h5

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.footer-newsletter > div.whatsapp-qr > a > img div.footer-newsletter > div.whatsapp-qr > a > img
div.woo-sidebar > div.woo-sidebar-section > div.woo-sidebar-toggle > img div.woo-sidebar > div.woo-sidebar-section > div.woo-sidebar-toggle > img
div.woo-sidebar > div.woo-sidebar-section > div.woo-sidebar-toggle > img div.woo-sidebar > div.woo-sidebar-section > div.woo-sidebar-toggle > img
div.woo-sidebar > div.woo-sidebar-section > div.woo-sidebar-toggle > img div.woo-sidebar > div.woo-sidebar-section > div.woo-sidebar-toggle > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.sib-sms-input-wrapper > div.sib-sms-select > div.sib-sms-select__number-input > input.sib-sms-select__calling-code div.sib-sms-input-wrapper > div.sib-sms-select > div.sib-sms-select__number-input > input.sib-sms-select__calling-code
div.sib-sms-input-wrapper > div.sib-sms-select > div.sib-sms-select__number-input > input.sib-sms-select__calling-code div.sib-sms-input-wrapper > div.sib-sms-select > div.sib-sms-select__number-input > input.sib-sms-select__calling-code

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
nav#mobile-header > div.inside-navigation > div.mobile-nav-bar-left > a nav#mobile-header > div.inside-navigation > div.mobile-nav-bar-left > a
section.inline-banner > div > div > a.light section.inline-banner > div > div > a.light
section.inline-banner > div > div > a.dark section.inline-banner > div > div > a.dark
section.select-products > div#swiper-wrapper-fc1079d28432aa531 > div.swiper-slide > a section.select-products > div#swiper-wrapper-fc1079d28432aa531 > div.swiper-slide > a
section.select-products > div#swiper-wrapper-fc1079d28432aa531 > div.swiper-slide > a section.select-products > div#swiper-wrapper-fc1079d28432aa531 > div.swiper-slide > a
section.select-products > div#swiper-wrapper-fc1079d28432aa531 > div.swiper-slide > a section.select-products > div#swiper-wrapper-fc1079d28432aa531 > div.swiper-slide > a
section.select-products > div#swiper-wrapper-fc1079d28432aa531 > div.swiper-slide > a section.select-products > div#swiper-wrapper-fc1079d28432aa531 > div.swiper-slide > a
section.select-products > div#swiper-wrapper-fc1079d28432aa531 > div.swiper-slide > a section.select-products > div#swiper-wrapper-fc1079d28432aa531 > div.swiper-slide > a
section.sbs-banner > div > div > a.light section.sbs-banner > div > div > a.light
section.select-products > div#swiper-wrapper-264910aef8286e9610 > div.swiper-slide > a section.select-products > div#swiper-wrapper-264910aef8286e9610 > div.swiper-slide > a
section.select-products > div#swiper-wrapper-264910aef8286e9610 > div.swiper-slide > a section.select-products > div#swiper-wrapper-264910aef8286e9610 > div.swiper-slide > a
section.select-products > div#swiper-wrapper-264910aef8286e9610 > div.swiper-slide > a section.select-products > div#swiper-wrapper-264910aef8286e9610 > div.swiper-slide > a
section.select-products > div#swiper-wrapper-264910aef8286e9610 > div.swiper-slide > a section.select-products > div#swiper-wrapper-264910aef8286e9610 > div.swiper-slide > a
section.select-products > div#swiper-wrapper-264910aef8286e9610 > div.swiper-slide > a section.select-products > div#swiper-wrapper-264910aef8286e9610 > div.swiper-slide > a
section.inline-banner > div > div > a.dark section.inline-banner > div > div > a.dark
section.select-products > div#swiper-wrapper-65262bc98c571021b > div.swiper-slide > a section.select-products > div#swiper-wrapper-65262bc98c571021b > div.swiper-slide > a
section.select-products > div#swiper-wrapper-65262bc98c571021b > div.swiper-slide > a section.select-products > div#swiper-wrapper-65262bc98c571021b > div.swiper-slide > a
section.select-products > div#swiper-wrapper-65262bc98c571021b > div.swiper-slide > a section.select-products > div#swiper-wrapper-65262bc98c571021b > div.swiper-slide > a
section.select-products > div#swiper-wrapper-65262bc98c571021b > div.swiper-slide > a section.select-products > div#swiper-wrapper-65262bc98c571021b > div.swiper-slide > a
section.select-products > div#swiper-wrapper-65262bc98c571021b > div.swiper-slide > a section.select-products > div#swiper-wrapper-65262bc98c571021b > div.swiper-slide > a
section.inline-banner > div > div > a.dark section.inline-banner > div > div > a.dark
section.select-products > div#swiper-wrapper-f20e62dd2d31043e4 > div.swiper-slide > a section.select-products > div#swiper-wrapper-f20e62dd2d31043e4 > div.swiper-slide > a
section.select-products > div#swiper-wrapper-f20e62dd2d31043e4 > div.swiper-slide > a section.select-products > div#swiper-wrapper-f20e62dd2d31043e4 > div.swiper-slide > a
section.select-products > div#swiper-wrapper-f20e62dd2d31043e4 > div.swiper-slide > a section.select-products > div#swiper-wrapper-f20e62dd2d31043e4 > div.swiper-slide > a
section.select-products > div#swiper-wrapper-f20e62dd2d31043e4 > div.swiper-slide > a section.select-products > div#swiper-wrapper-f20e62dd2d31043e4 > div.swiper-slide > a
section.select-products > div#swiper-wrapper-f20e62dd2d31043e4 > div.swiper-slide > a section.select-products > div#swiper-wrapper-f20e62dd2d31043e4 > div.swiper-slide > a
div.new-footer-content > div.footer-newsletter > div.whatsapp-qr > a div.new-footer-content > div.footer-newsletter > div.whatsapp-qr > a
div.new-footer-content > div.footer-social > div > a div.new-footer-content > div.footer-social > div > a
div.new-footer-content > div.footer-social > div > a div.new-footer-content > div.footer-social > div > a
div.new-footer-content > div.footer-social > div > a div.new-footer-content > div.footer-social > div > 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.

○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.
●Select elements have associated label elements.
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
○`[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
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○No element has a `[tabindex]` value greater than 0
○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.
○Elements with visible text labels have matching accessible names.
○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 Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A
Form Input Types
3 input(s) using type=text where a specific type would help
PASS
3 input(s) using type=text where a specific type would help
Info::
Input "EMAIL" should use type="email" (currently type="text")
Field name "EMAIL" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "EMAIL" should use type="email" (currently type="text")
Field name "EMAIL" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "email_address_check" should use type="email" (currently type="text")
Field name "email_address_check" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+
Form Input Quality
15 form control(s) checked, no input-semantic issues
PASS
15 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A
Tabindex Anti-Patterns
0 positive, 2 -1-on-focusable
PASS
0 positive, 2 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 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.
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 88 visible text node(s) render at >= 12 CSS pixels
PASS
All 88 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback