Skip to content
https://Bureau-savini.be

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
9
REVIEW
5
PASS
10
INFO
0
Checks
24
10 PASS 5 REVIEW 9 FIX
F
Heading Hierarchy
Action
67 headings, 19 skip(s)
FIX
67 headings, 19 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
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: H3 → H6 (missing H4)
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: H3 → H6 (missing H4)
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: H3 → H6 (missing H4)
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 → H6 (missing H3)
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: H3 → H6 (missing H4)
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: H3 → H6 (missing H4)
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: H3 → H6 (missing H4)
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: 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 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Bienvenue au Bureau Savini
  • H2 Les biens à la une
  • H6 Appartement 3 chambres skipped
  • H3 1 290 €
  • H6 Maison 6 chambres skipped
  • H3 àpd. 135 000 €
  • H6 Garage skipped
  • H3 80 €
  • H6 garage skipped
  • H3 70 €
  • H6 Villa 4 chambres + entrepôt skipped
  • H3 àpd. 349 000 €
  • H6 Appartement une chambre skipped
  • H3 700 €
  • H6 Villa 4 façades avec vaste garage skipped
  • H3 229 000 €
  • H6 colocation skipped
  • H3 450 €
  • H2 Pourquoi choisir notre agence ?
  • H6 Gestion de A à Z skipped
  • H6 Crédit hypothécaire ?
  • H4 26
  • H4 28
  • H4 4
  • H2 Une sélection de biens juste pour vous !
  • H3 appartement
  • H6 Gerpinnes skipped
  • H4 1 290 €
  • H3 maison
  • H6 Monceau-sur-Sambre skipped
  • H4 àpd. 135 000 €
  • H3 garage (ferme)
  • H6 Marchienne-au-Pont skipped
  • H4 80 €
  • H3 garage (ferme)
  • H6 Marchienne-au-Pont skipped
  • H4 70 €
  • H3 villa
  • H6 Jumet skipped
  • H4 àpd. 349 000 €
  • H3 appartement
  • H6 Gosselies skipped
  • H4 700 €
  • H3 villa
  • H6 Anderlues skipped
  • H4 229 000 €
  • H3 chambre
  • H6 Marcinelle skipped
  • H4 450 €
  • H2 Qu'en pensent nos clients ?
  • H6 SalimaBakkouche skipped
  • H6 XeressGaming
  • H6 KrsOne71
  • H6 SylvieH
  • H6 DomiHoebeke
  • H6 JacquelineVANDENBERGHE
  • H6 SalimaBakkouche
  • H6 XeressGaming
  • H6 KrsOne71
  • H6 SylvieH
  • H6 DomiHoebeke
  • H6 JacquelineVANDENBERGHE
  • H2 Un renseignement ? Une estimation ? Contactez-nous !
  • H5 Nos services skipped
  • H5 Qui sommes-nous ?
  • H5 Réseaux sociaux
  • H5 Notre siège social

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

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

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

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

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

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

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

F
Alt Text Quality
Action
38 of 61 images have issues
FIX
38 of 61 images have issues
Critical::
37 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
24 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with generic alt text
Info::
23 image(s) with good alt text
61 images 23 good alt text 1 generic 37 missing
IssueCount
missing37 image(s)
generic1 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
Tap Target Adequacy
Action
17 tap target(s) too small or too close together
FIX
17 tap target(s) too small or too close together
Warning::
17 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
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 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: pollo
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name pollo ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name pollo Icons 6 icon(s)
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 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 1 <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.
D
Lighthouse Accessibility Audits
Action
Score 66/100 — 10 failing, 17 passed
FIX
66

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.container > div#estateCarousel > div.carousel-indicators > button.active div.container > div#estateCarousel > div.carousel-indicators > button.active
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button.active div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button.active
div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button
div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button
div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button
div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button
div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button

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 > div > p > img div > div > p > img
div > p > a > img div > p > a > img
div > p > a > img div > p > a > img

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
FR NL EN div.me-auto > div.d-flex > form > select.form-select

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.row > div.col-6 > iframe div.container > div.row > div.col-6 > iframe
div.row > div.col-md-5 > div > iframe div.row > div.col-md-5 > div > iframe

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.row > div.col-6 > div.d-flex > a.d-flex div.row > div.col-6 > div.d-flex > a.d-flex
div.row > div.col-6 > div.d-flex > a.d-flex div.row > div.col-6 > div.d-flex > a.d-flex
div.row > div.col-6 > div.d-flex > a.p-2 div.row > div.col-6 > div.d-flex > a.p-2
div.row > div.col-6 > div.d-flex > a.p-2 div.row > div.col-6 > div.d-flex > a.p-2
div > div > p > a
div.row > div.col-md-2 > div.social-icons > a.p-2 div.row > div.col-md-2 > div.social-icons > a.p-2
div.row > div.col-md-2 > div.social-icons > a.p-2 div.row > div.col-md-2 > div.social-icons > a.p-2
footer.footer > div.cookieinfo > span > a footer.footer > div.cookieinfo > span > 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.

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
Nouveau div.carousel-wrapper > div#propertyCarousel > div.property-card > span.badge
Monceau-sur-Sambre div#propertyCarousel > div.property-card > div.p-3 > p.text-muted
Nouveau div.carousel-wrapper > div#propertyCarousel > div.property-card > span.badge
Marchienne-au-Pont div#propertyCarousel > div.property-card > div.p-3 > p.text-muted
Nouveau div.carousel-wrapper > div#propertyCarousel > div.property-card > span.badge
Marchienne-au-Pont div#propertyCarousel > div.property-card > div.p-3 > p.text-muted
Nouveau div.carousel-wrapper > div#propertyCarousel > div.property-card > span.badge
Jumet div#propertyCarousel > div.property-card > div.p-3 > p.text-muted
Nouveau div.carousel-wrapper > div#propertyCarousel > div.property-card > span.badge
Gosselies div#propertyCarousel > div.property-card > div.p-3 > p.text-muted
Nouveau div.carousel-wrapper > div#propertyCarousel > div.property-card > span.badge
Anderlues div#propertyCarousel > div.property-card > div.p-3 > p.text-muted
Nouveau div.carousel-wrapper > div#propertyCarousel > div.property-card > span.badge
Marcinelle div#propertyCarousel > div.property-card > div.p-3 > p.text-muted
Nouveau div.estate-card > div.col-md-4 > div.d-flex > span.badge

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
APPARTEMENT 3 CHAMBRES div#propertyCarousel > div.property-card > div.p-3 > h6.mb-1
MAISON 6 CHAMBRES div#propertyCarousel > div.property-card > div.p-3 > h6.mb-1
GARAGE div#propertyCarousel > div.property-card > div.p-3 > h6.mb-1
GARAGE div#propertyCarousel > div.property-card > div.p-3 > h6.mb-1
VILLA 4 CHAMBRES + ENTREPÔT div#propertyCarousel > div.property-card > div.p-3 > h6.mb-1
APPARTEMENT UNE CHAMBRE div#propertyCarousel > div.property-card > div.p-3 > h6.mb-1
VILLA 4 FAÇADES AVEC VASTE GARAGE div#propertyCarousel > div.property-card > div.p-3 > h6.mb-1
COLOCATION div#propertyCarousel > div.property-card > div.p-3 > h6.mb-1
GESTION DE A À Z div.col-md-4 > div.service-item > div > h6
GERPINNES div.carousel-item > div.estate-card > div.col-md-4 > h6
SALIMA BAKKOUCHE div.client-info > div > div > h6
NOS SERVICES div.container > div.row > div.col-md-2 > h5

These are opportunities to improve keyboard navigation in your application.

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
div.row > div.col-6 > div.d-flex > a.p-2 div.row > div.col-6 > div.d-flex > a.p-2
div.row > div.col-6 > div.d-flex > a.p-2 div.row > div.col-6 > div.d-flex > a.p-2
ACCÈS PROPRIÉTAIRE div.me-auto > div.d-flex > div.d-flex > a.btn
div.container > div#estateCarousel > div.carousel-indicators > button.active div.container > div#estateCarousel > div.carousel-indicators > button.active
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#estateCarousel > div.carousel-indicators > button div.container > div#estateCarousel > div.carousel-indicators > button
div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button.active div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button.active
div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button
div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button
div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button
div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button
div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button div.container > div#testimonialsCarouselMobile > div.carousel-indicators > button

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

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
  RECHERCHE div.row > div.col-12 > div.search-bar > button#btnSearch
○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
●`[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 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
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○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.
○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.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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

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

B
Iframe Accessibility
2/2 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://www.opinionsystem.fr/company_rating.php?company_id=13910&professional_a…")
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.youtube.com/embed/oBkhcUJ1aRA")
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.
B
Mobile-Readable Font Sizes
98% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
98% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
1 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("Nouveau").
C
Favicon & Branding
Action
17 icon(s) detected
REVIEW
17 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::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
PWA Depth
3 PWA signal(s) surfaced
REVIEW
3 PWA signal(s) surfaced
Warning::
Manifest is missing `display` -- defaults to browser, no PWA UX
When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
Info::
Manifest is missing `theme_color`
Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.
A
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
3 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H4: "26" - H4: "28" - H4: "4"
Got: 3 ≤2-char heading(s)
A
Form Accessibility
1 of 5 controls have issues
PASS
1 of 5 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="lg">
Info::
4 control(s) properly labeled
5 controls
4 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#filterCategorieselectcategoryaria-label
#filterVilleselectcityaria-label
#filterChambresselectroomaria-label
#filterPrixselectpricearia-label
lgselect(none)none

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

<select name="lg">

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

A+
Form Input Types
5 form control(s) checked, no type mismatches
PASS
5 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "fr"
PASS
Lang attribute set to "fr"
Info::
<html lang="fr"> is set and valid
Got: fr
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /css/print.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /css/print.css ✓Inline @media print Not detected ✗
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 Bienvenue au Bureau …9.04:13.0:1
#000000
#AAAAAA
Pass
h2 Les biens à la une9.04:13.0:1
#000000
#AAAAAA
Pass
h2 Pourquoi choisir not…9.04:13.0:1
#000000
#AAAAAA
Pass
h2 Une sélection de bi…9.04:13.0:1
#000000
#AAAAAA
Pass
h2 Qu'en pensent nos cl…9.04:13.0:1
#000000
#AAAAAA
Pass
h2 Un renseignement ? …9.04:13.0:1
#000000
#AAAAAA
Pass
h3 1 290 €9.04:13.0:1
#000000
#AAAAAA
Pass
h3 àpd. 135 000 €9.04:13.0:1
#000000
#AAAAAA
Pass
h3 80 €9.04:13.0:1
#000000
#AAAAAA
Pass
h3 70 €9.04:13.0:1
#000000
#AAAAAA
Pass
h3 àpd. 349 000 €9.04:13.0:1
#000000
#AAAAAA
Pass
h3 700 €9.04:13.0:1
#000000
#AAAAAA
Pass
h3 229 000 €9.04:13.0:1
#000000
#AAAAAA
Pass
h3 450 €9.04:13.0:1
#000000
#AAAAAA
Pass
h3 appartement9.04:13.0:1
#000000
#AAAAAA
Pass
h3 maison9.04:13.0:1
#000000
#AAAAAA
Pass
h3 garage (ferme)9.04:13.0:1
#000000
#AAAAAA
Pass
h3 garage (ferme)9.04:13.0:1
#000000
#AAAAAA
Pass
h3 villa9.04:13.0:1
#000000
#AAAAAA
Pass
h3 appartement9.04:13.0:1
#000000
#AAAAAA
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