Skip to content
https://ulule.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Landmark Structure
Action
8 landmarks
FIX
8 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <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 (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

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

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

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
No navigation patterns
FIX
No navigation patterns
Info::
5 navigation landmark(s) detected
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 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

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 Page not found - Ulule ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
7 icon(s) detected
REVIEW
7 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Lighthouse Accessibility Audits
Action
Score 72/100 — 9 failing, 21 passed
REVIEW
72

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.yFtv2XoH > section.yFtv2XoQ > nav.yFtv2Xo4 > button.yISLuFS8 div.yFtv2XoH > section.yFtv2XoQ > nav.yFtv2Xo4 > button.yISLuFS8
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J
div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J

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
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English Français Español Italiano Nederlands div.yqWWT5Y1 > div.ybW5ux3 > div.ybhkXym > select
$ (USD) € (EUR) £ (GBP) kr (DKK) kr (NOK) $ (AUD) $ (CAD) fr. (CHF) kr (SEK) $ … div.yqWWT5Y1 > div.ybW5ux3 > div.ybhkXym > select

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.yFtv2Xo7 > div.yFtv2XoH > section.yFtv2XoQ > a.yWlR9E2 nav.yFtv2Xo7 > div.yFtv2XoH > section.yFtv2XoQ > a.yWlR9E2

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.

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
OK! div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_acceptAll
TWINKLE EDITIONS a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
€12,033 div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1 > span.yihFAe4
D-15 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
OUNTRAVELA PUBLISHING a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
200 / 100 div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1
D-34 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
AFTERCLUB.BE a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
561 / 500 div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1
H-23 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
DOROTHÉE PIATEK a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
€4,824 div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1 > span.yihFAe4
D-32 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
SEE ALL PROJECTS div.yJvPGO9 > section.yJvPGO93 > a.yhxEDjC > button.yw80WrDU
SEE ALL CHANNELS div.yJvPGO9 > section.yJvPGO93 > a.yhxEDjC > button.yw80WrDU
SEE ALL CALLS FOR PROPOSALS div.yJvPGO9 > section.yJvPGO93 > a.yhxEDjC > button.yw80WrDU
Language and site currency footer.yFQ85FB1 > div.yqWWT5YE > div.yqWWT5Y1 > p.yNg1KOr9M

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
Help and resources div.yqWWT5YB > section.yfqtpdS1 > label.ysnXvh91 > h3.yNg1KOr9O

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ongoing Lutte contre la précarité alimentaire chez les jeunes de 16 à 25 ans … div#__next > div.yJvPGO9 > section.yJvPGO93 > ul.yqMj87a

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ongoing Lutte contre la précarité alimentaire chez les jeunes de 16 à 25 ans … ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Pour révéler, célébrer et récompenser les talents qui perpétuent l’exc… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Accompagner les porteurs de projet engagés dans la transition énergéti… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Soutien de projets sur les thématiques du bien vieillir, de l’aide aux… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Les hommes et les femmes qui œuvrent pour une société plus inclusive e… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Des projets de nouvelles lignes aériennes élaborées et gérées localeme… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
No, thanks div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_dismiss
I want to choose div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_configure
○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
●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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○Links are distinguishable without relying on color.
○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.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input name="search" id="search">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchinput(Search)placeholder only

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

<input name="search" id="search">

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

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
title Ulule21.00:14.5:1
#000000
#FFFFFF
Pass
strong Warning, our website…21.00:13.0:1
#000000
#FFFFFF
Pass
p We recommend that yo…19.23:14.5:1
#000000
#E7F8FC
Pass
a Update my browser19.30:14.5:1
#000000
#E9F8FC
Pass
a I don't want or I ca…19.49:14.5:1
#000000
#EBF9FC
Pass
span Ulule19.52:14.5:1
#000000
#ECF9FC
Pass
a Launch a project19.72:14.5:1
#000000
#EEFAFC
Pass
a See all projects19.80:14.5:1
#000000
#F0FAFD
Pass
span Ulule19.96:14.5:1
#000000
#F1FBFD
Pass
span Search17.17:14.5:1
#000000
#D1EDF7
Pass
a Search17.86:14.5:1
#000000
#EDECF0
Pass
a Explore all projects17.86:14.5:1
#000000
#EDECF0
Pass
span Sign in17.17:14.5:1
#000000
#D1EDF7
Pass
span Make good18.45:14.5:1
#000000
#FFECEB
Pass
span things happen18.45:14.5:1
#000000
#FFECEB
Pass
div The top service for …21.00:14.5:1
#000000
#FFFFFF
Pass
span Projects21.00:14.5:1
#000000
#FFFFFF
Pass
span in progress21.00:14.5:1
#000000
#FFFFFF
Pass
p Publishing & Media21.00:14.5:1
#000000
#FFFFFF
Pass
p Places & Stores21.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.

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

Send Feedback