Where we stand, with the measurements.

State as of October 30, 2026

What this page covers

The public site (remanso.ca) and the service (app.remanso.ca), in French and in English.

What has been done

On October 12, 2026, we ran the public site (14 pages, in both languages) and the screens of the service, in light and dark themes, through the automated tool axe-core, with the WCAG 2.0 and 2.1 rules at levels A and AA, in three browser engines (Chromium, Firefox, WebKit) and with an emulated Android phone and iPhone. We also checked, by hand or by script:

• keyboard-only navigation: visible focus indicator, no focus trap;
• eight screen widths, from 320 to 2560 pixels, including 200% zoom and reflow at 320 pixels, and text enlarged to 150%;
• the system’s “reduce motion” setting;
• use without JavaScript for the basic screens, and on a slow connection.

That check found contrast defects (sign-up, sign-in and several public pages) and an incorrect accessible name on the account menu. They were fixed and the product’s automated tests guard them.

This check dates from October 12, 2026. The product has changed since; a second check was done on October 30 (see below).

Known defects, as of October 12

• Two controls (the “Close this reminder” button on the dashboard and the person links in the qualifications list) have an accessible name longer than their visible text. To be re-read with a screen reader.
• The palette’s secondary text measures 4.43 to 4.44 to 1 on some backgrounds, just under the 4.5 to 1 threshold of level AA; the person record received a local fix, the palette itself did not.
• The signage screen has no level-1 heading.

What has not been done

• No screen-reader testing (NVDA, JAWS, VoiceOver, TalkBack): we have none to publish.
• The criteria specific to WCAG 2.2 have had a first check only, on October 30, on a development copy of the service and not on the live service (results below). The SGQRI 008 3.0 standard (accessibility of information technology), which binds the public bodies it applies to, requires them: 3.2.6 (consistent help), 3.3.7 (redundant entry), 2.4.11 (focus not obscured), 2.5.7 (dragging movements), 2.5.8 (target size), 3.3.8 (accessible authentication) and 2.4.13 (focus appearance). It also adds three level AAA criteria (2.3.2, 3.1.4, 2.5.6), which have not been checked.
• Safari on a real iPhone, Chrome on a real Android phone and Samsung Internet have not been tried: only equivalent engines and emulated devices have.
• We have no testing with people with disabilities to publish.

An automated tool finds only part of the accessibility defects. This page describes measurements, not conformance.

Findings of October 30, 2026

A second check was done on October 30, 2026 on a development copy of the service (not on the live service), with axe-core 4.14, on 57 screens in French and English, and by reading the code for dragging gestures. It found, in the application (not on the public site), defects that the October 12 check had not seen. They are known; some may be fixed by the time you read this, and this list has not yet been brought up to date with those fixes.

• The button that collapses or expands the side menu has no accessible name: a screen reader announces it simply as “button” (45 screens; critical severity).
• The logo link has no accessible name when the side menu is collapsed (45 screens).
• The dashboard’s “Not now” button has an accessible name that does not contain its visible text, which hampers voice control (criterion 2.5.3).
• At 320 pixels wide (400% zoom), the fixed bottom bar can hide the control that has keyboard focus, on 17 screens (criterion 2.4.11).
• Five administration tools require dragging with no other way to do it: drawing rooms and moving doors on a plan, moving the plan, straightening a plan by its corners, and drawing a rectangle on a pool plan (criterion 2.5.7).
• The PIN of the punch kiosk is a code to memorize, with no other way to identify oneself: we have not yet decided whether that meets criterion 3.3.8.
• The application itself does not yet link to this page; the link is only on the public site.
• The focus indicator is thin or low-contrast in several places (criterion 2.4.13, level AAA; approximate measurement).

This check found no contrast defect (light and dark themes), field label, page landmark or heading problem on these screens, nor any target too small according to the automated tool. Help sits in the same place on the signed-in screens (criterion 3.2.6) and redundant entry was checked at sign-up (criterion 3.3.7). Not covered: the signage screen, the space of an employee linked to a record, Firefox, WebKit and screen readers.

Our commitment

We do not announce a date: we do not want to publish one we are not sure to keep. We will update this page when the state changes, in either direction.

Telling us about a barrier

If something does not work for you — a page, a button, a document — write to bonjour@remanso.ca, telling us the page, the tool or the assistive technology you use. The terms promise an answer from a person within two business days. For content that is not accessible, we will look for an accessible alternative with you. We do not promise a time to fix.