Skip to content
https://square.site

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
8
REVIEW
2
PASS
3
INFO
0
Checks
13
3 PASS 2 REVIEW 8 FIX
D
Heading Hierarchy
Action
29 headings, 3 skip(s)
FIX
29 headings, 3 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Propulsez votreentreprise avec Square.
  • H1 Commencez à vendre où vousvoulez en quelques minutes. duplicate H1
  • H4 Vendez en ligne, partout. skipped
  • H4 Gagnez du temps avec un seul système flexible.
  • H4 Faites-vous payer où que vous soyez.
  • H2 Encaissez des paiements sans contact directement depuis votre iPhone ou votre téléphone Android.
  • H3 Le logiciel de caissemobile tout-en-un
  • H6 Simple d’utilisation skipped
  • H6 Imprimante de caisse intégrée
  • H6 Des paiements rapides et sécurisés
  • H3 Portable et intuitif, il vous permet degérer l‘ensemble de vos activités.
  • H3 Découvrez plus de matériel sans contact.
  • H3 « Avec mon terminal Square, je peux encaisser mes clients directement en boutique. Je peux envoyer des devis, on peut aussi envoyer directement des liens de paiement. Donc honnêtement, c’est super
  • H3 Plus de 4 millions d’entreprises nous font confiance.
  • H3 Gérez tout depuis un seul endroit.
  • H3 Gardez un œil sur tout.
  • H3 Synchronisez vos applications avec Square.
  • H2 Plus d’outils pour tous les défis commerciaux.
  • H3 Liens de paiement
  • H3 Terminal virtuel
  • H3 Outils de développeurs
  • H3 Gestion des employés Square
  • H3 Cartes cadeaux électroniques
  • H2 Commencezà vendreavec Square.
  • H2 Gardons contact.
  • H2 Nous sommes ravis de faire votre connaissance.
  • H2 Ressources
  • H4 Choisissez votre région et votre langue skipped
  • H4 (empty)

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <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
Form Accessibility
2 of 17 controls have issues
REVIEW
2 of 17 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="Email" id="lead-form-1_Email">; <input type="tel">
Info::
15 control(s) properly labeled
17 controls
15 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#lead-form-1_Email_Opt_Out__c_FalsecheckboxEn fournissant vos coordonnées, vous acceptez de recevoir des e-mails et d’autres communications de Square assurant la promotion de produits et de services susceptibles d’intéresser votre entreprise. Vous pouvez vous désabonner à tout moment*.for/id
#lead-form-2_FirstNametextPrénomfor/id
#lead-form-2_LastNametextNomfor/id
#lead-form-2_US-country-code-prefixradioÉtats-Unis +1for/id
#lead-form-2_GB-country-code-prefixradioRoyaume-Uni +44for/id
#lead-form-2_AU-country-code-prefixradioAustralie +61for/id
#lead-form-2_CA-country-code-prefixradioCanada +1for/id
#lead-form-2_JP-country-code-prefixradioJapon +81for/id
#lead-form-2_IE-country-code-prefixradioIrlande +353for/id
#lead-form-2_ES-country-code-prefixradioEspagne +34for/id
#lead-form-2_FR-country-code-prefixradioFrance +33for/id
#lead-form-2_CompanytextNom de l’entreprisefor/id
#lead-form-2_IndustryselectSecteur d’activitéfor/id
#lead-form-2_Revenue_Range__c_accountselectRevenu annuelfor/id
#lead-form-2_Email_Opt_Out__c_FalsecheckboxEn fournissant vos coordonnées, vous consentez à recevoir des e-mails, des appels promotionnels et/ou des SMS de Square au sujet de produits et services susceptibles de vous intéresser ou de profiter à votre entreprise. Vous pouvez vous désinscrire à tout moment.*for/id
#lead-form-1_Emailemail(Entrez votre adresse e-mail)placeholder only
inputtel(00 00 00 00 00)placeholder only

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

<input type="email" name="Email" id="lead-form-1_Email">; <input type="tel">

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

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 25 passed
REVIEW
88

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.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.content > div.carousel > div.carousel-button-nav > div.carousel-button-left div.content > div.carousel > div.carousel-button-nav > div.carousel-button-left
div.content > div.carousel > div.carousel-button-nav > div.carousel-button-right div.content > div.carousel > div.carousel-button-nav > div.carousel-button-right
div.content > div.carousel > div.carousel-button-nav > div.carousel-button-left div.content > div.carousel > div.carousel-button-nav > div.carousel-button-left
div.content > div.carousel > div.carousel-button-nav > div.carousel-button-right div.content > div.carousel > div.carousel-button-nav > div.carousel-button-right
div.content > div.carousel > div.carousel-button-nav > div.carousel-button-left div.content > div.carousel > div.carousel-button-nav > div.carousel-button-left
div.content > div.carousel > div.carousel-button-nav > div.carousel-button-right div.content > div.carousel > div.carousel-button-nav > div.carousel-button-right

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Découvrir tous les produits de paiement div.column > div.headings-compact > p > a
paiement div.headings-compact > p > a > span.arrow
boutique en ligne gratuite div.column > div.headings-compact > p > a
votre site existant div.column > div.headings-compact > p > a
Parcourir les options de vente en ligne div.column > div.headings-compact > p > a
ligne div.headings-compact > p > a > span.arrow
restaurants div.column > div.headings-compact > p > a
détaillants div.column > div.headings-compact > p > a
Tester notre logiciel de caisse personnalisable div.column > div.headings-compact > p > a.display-block
personnalisable div.headings-compact > p > a.display-block > span.arrow
S‘inscrire à Factures Square div.column > div.headings-compact > p > a
Square div.headings-compact > p > a > span.arrow
Nos terminaux de paiement div.column > div.headings-compact > p > a.h5
paiement div.headings-compact > p > a.h5 > span.arrow
En savoir plus sur la sécurité chez Square div.grid > div.column > div.display-inline-block > a
Square div.column > div.display-inline-block > a > span.arrow
En savoir plus div.tile-content > div.grid-space-line > div.column > div.link
Contacter notre équipe commerciale div.intro > ul.reset > li > a
commerciale ul.reset > li > a > span.arrow
*Veuillez consulter la Politique de confidentialité de Square pour plus d’infor… div.single-column-lead-form-section > form > div.align-left > p
Politique de confidentialité form > div.align-left > p > a
Paiements div.column > div.h6 > a > span.caret
Logiciels et services div.grid-2-at-small > div.column > div.h6 > a
services div.column > div.h6 > a > span.caret
Matériel div.column > div.h6 > a > span.caret
Ressources div.column > div.h6 > a > span.caret
Développeurs div.column > div.h6 > a > span.caret
Square div.column > div.h6 > a > span.caret
© 2026 Block, Inc., Squareup Pte. Ltd. div.content > div.grid-flex-at-medium > div.column > p.copyright
Square, nom commercial de Squareup International Limited, est supervisée par la… div.content > div.grid-flex-at-medium > div.column > p

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
Vendez en ligne, partout. div.grid > div.column > div.headings-compact > h4#vendez-en-ligne-partout
Based on your region, we recommend viewing our website in: div.modal-scroll > div.modal-wrapper > div.content > h4#detection-heading

These are opportunities to improve keyboard navigation in your application.

Names and labels

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
div.grid > div.column > div.position-relative > a.display-block div.grid > div.column > div.position-relative > a.display-block
div.grid > div.column > div.position-relative > a.display-block div.grid > div.column > div.position-relative > a.display-block
div.grid > div.column > div.position-relative > a.display-block div.grid > div.column > div.position-relative > a.display-block
div.grid > div.column > div.position-relative > a.display-block div.grid > div.column > div.position-relative > a.display-block
div.grid > div.column > div.position-relative > a.display-block div.grid > div.column > div.position-relative > a.display-block
div.grid > div.column > div.position-relative > a.display-block div.grid > div.column > div.position-relative > a.display-block
div.grid > div.column > div.position-relative > a.display-block div.grid > div.column > div.position-relative > a.display-block
div.grid > div.column > div.position-relative > a.display-block div.grid > div.column > div.position-relative > a.display-block

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
●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.
●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 are distinguishable without relying on color.
●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.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○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
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) 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

A+
Alt Text Quality
All 52 images OK
PASS
All 52 images OK
Info::
51 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
52 images 1 good alt text 51 decorative
All images have appropriate alt text.
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 Propulsez votre21.00:13.0:1
#000000
#FFFFFF
Pass
h1 entreprise avec Squa…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Commencez à vendre …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 voulez en quelques m…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Encaissez des paieme…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Plus d’outils pour…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Commencez21.00:13.0:1
#000000
#FFFFFF
Pass
h2 à vendre21.00:13.0:1
#000000
#FFFFFF
Pass
h2 avec Square.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Gardons contact.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nous sommes ravis de…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ressources21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Le logiciel de caiss…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 mobile tout-en-un21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Portable et intuitif…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 gérer l‘ensemble …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Découvrez plus de m…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 « Avec mon terminal…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Plus de 4 millions …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gérez tout depuis u…21.00:13.0: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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback