Short review of on its accessibility and usability for people with disabilities

Disclaimer: This document is a short, follow up review. Its main purpose is to raise awareness for education and training purposes. This document is also meant to help to bring the product to be fully Web Accessible for all users including people with disabilities.

Scope of review

Reviewed on October 8, 2019

General notes:

<input type="hidden" name="language" value="en">


  1. All comments in the document refer to English and French pages unless specified otherwise.

  2. Testing done using: Firefox 67, NVDA, keyboard-only

  3. Pages were tested against WCAG 2.1 level A, AA. (only fixes for WCAG 2.0 AA are strictly required at present)

Table of Contents

WCAG 2.1 accessibility issues levels A, AA and AAA

1.1 Text Alternatives

1.2 Time-based Media

1.3 Adaptable

1.4 Distinguishable

1.4.13 Content on Hover or Focus (WCAG 2.1 Level AA)

Once the focus is removed from any required field without entering any data, additional content is triggered.

For example, if a keyboard user first wants to enter the message and then wants to choose the reason for contacting, there is no way to do it without seeing the screenshot below. This discussion dominates the issues about forms on GitHub and there is an agreement on the approach that validations should not be performed before the submit button is hit.

image 1

2.1 Keyboard Accessible

2.1.4 Character Key Shortcuts (WCAG 2.1 Level A)

Not tested

2.2 Enough Time

2.3 Seizures

2.4 Navigable

2.4.2 Page Titled (Level A)

A debatable issue: The title is almost the same as the h1. Should Titles and h1s not be different? h1 could have been more descriptive.

<title> Feedback form -</title>

<h1 property="name" id="wb-cont">Feedback form</h1>

2.5 Input Modalities

2.5.4 Motion Actuation (WCAG 2.1 Level A)

NOT tested

3.1 Readable

3.2 Predictable

3.2.1 On Focus (Level A)

Please see 1.4.13

3.3 Input Assistance

4.1 Compatible