Skip to content
https://stib-mivb.brussels

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
3
PASS
16
INFO
0
Checks
24
16 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-03qhyl
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://stib-mivb.brussels/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://stib-mivb.brussels/manifest.json

Manifest contains invalid JSON.

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.

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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <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
Favicon & Branding
6 icon(s) detected
REVIEW
6 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
Lighthouse Accessibility Audits
Action
Score 72/100 — 7 failing, 22 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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
All Metro Tram Bus div.col-12 > div#RTLinesAndTimetable > div.realtime-lines-nav > ul.nav-pills

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
All div.realtime-lines-nav > ul.nav-pills > li.nav-item > button#react-aria5690077141-1-tab-a
Metro div.realtime-lines-nav > ul.nav-pills > li.nav-item > button#react-aria5690077141-1-tab-METRO
Tram div.realtime-lines-nav > ul.nav-pills > li.nav-item > button#react-aria5690077141-1-tab-TRAM
Bus div.realtime-lines-nav > ul.nav-pills > li.nav-item > button#react-aria5690077141-1-tab-BUS

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.

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
Today div.form-line > div.input-group > div.dropdown > button#buttonFilterDropdownStartTimeDay

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.col-12 > div.form-line > div.input-group > input#StartTime div.col-12 > div.form-line > div.input-group > input#StartTime

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
body > a body > 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
M5 div#swiper-wrapper-a5c1b6fb7a5105da5 > ul.swiper-slide > li > a.line-number
12 div#swiper-wrapper-a5c1b6fb7a5105da5 > ul.swiper-slide > li > a.line-number
17 div#swiper-wrapper-a5c1b6fb7a5105da5 > ul.swiper-slide > li > a.line-number
19 div#swiper-wrapper-a5c1b6fb7a5105da5 > ul.swiper-slide > li > a.line-number
28 div#swiper-wrapper-a5c1b6fb7a5105da5 > ul.swiper-slide > li > a.line-number
29 div#swiper-wrapper-a5c1b6fb7a5105da5 > ul.swiper-slide > li > a.line-number
38 div#swiper-wrapper-a5c1b6fb7a5105da5 > ul.swiper-slide > li > a.line-number
39 div#swiper-wrapper-a5c1b6fb7a5105da5 > ul.swiper-slide > li > a.line-number
42 div#swiper-wrapper-a5c1b6fb7a5105da5 > ul.swiper-slide > li > a.line-number

These are opportunities to improve the legibility of your content.

Tables and lists

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
All div#RTLinesAndTimetable > div.realtime-lines-nav > ul.nav-pills > li.nav-item
Metro div#RTLinesAndTimetable > div.realtime-lines-nav > ul.nav-pills > li.nav-item
Tram div#RTLinesAndTimetable > div.realtime-lines-nav > ul.nav-pills > li.nav-item
Bus div#RTLinesAndTimetable > div.realtime-lines-nav > ul.nav-pills > li.nav-item

These are opportunities to improve the experience of reading tabular or list data using 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
●Image elements have `[alt]` attributes
●`[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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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 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
○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
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 CONTENTINFO footer

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

A
Heading Hierarchy
21 headings
PASS
21 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Menu
  • H1 nav.modal duplicate H1
  • H1 Let's move Brussels duplicate H1
  • H2 Real-time and timetables
  • H3 Traffic information
  • H2 Purchase your ticket online
  • H3 Season tickets
  • H3 Tickets
  • H3 Pay contactless with your bank card
  • H2 First time with STIB-MIVB? Discover how easy it is to travel with us!
  • H2 In the spotlight
  • H3 About STIB-MIVB
  • H3 About STIB-MIVB
  • H3 Discover Brussels
  • H3 Discover Brussels
  • H3 Our mobile apps
  • H3 Our mobile apps
  • H3 Professionals
  • H3 Professionals
  • H3 Follow us on social media
  • H3 Newsletter

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

A+
Heading Text Quality
All 21 heading(s) have substantive, well-formed text
PASS
All 21 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 13 images OK
PASS
All 13 images OK
Info::
11 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
13 images 2 good alt text 11 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#input-search-globalsearchRechercher dans tout le sitearia-label
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 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 "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
4 explicit tabindex attribute(s) checked, no anti-patterns
PASS
4 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
All 2 iframe(s) have descriptive titles
PASS
All 2 iframe(s) have descriptive titles
Info::
All 2 iframe(s) have title attributes
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 54 visible text node(s) render at >= 12 CSS pixels
PASS
All 54 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::
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 Menu17.69:13.0:1
#000000
#D9EFFB
Pass
h1 nav.modal21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Let's move Brussels13.73:13.0:1
#00304D
#FFFFFF
Pass
h2 Purchase your ticket…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 First time with STIB…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 In the spotlight21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Traffic information21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Season tickets21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Tickets21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pay contactless with…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 About STIB-MIVB21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Discover Brussels21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Our mobile apps21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Professionals21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Follow us on social …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Newsletter21.00:13.0:1
#000000
#FFFFFF
Pass
title Home - STIB - MIVB21.00:14.5:1
#000000
#FFFFFF
Pass
a Buy13.67:14.5:1
#000000
#A1D8F6
Pass
a Travel11.73:14.5:1
#000000
#81CBF0
Pass
a Client support9.36:14.5:1
#000000
#50B8E8
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