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 7, 2019

General notes:

There is overreliance on Aria, there are unnecessarily used role attributes (such as <tr role=”row”>), rowspan/colspan attributes (such as <colspan=”1”>).

Sample th code:

<th class="sorting" tabindex="0" aria-controls="wb-auto-4" rowspan="1" colspan="1" style="width: 227px;" aria-label="Rendering engine: activate for ascending sort">
Rendering engine
<span class="sorting-cnt"><span class="sorting-icons"></span></span>


  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.3.1: Info and Relationships

There are 4 tables and none of their cells is associated with headers, either by using “scope” attribute or by “headers” and “ID”s.

[F91: Failure of Success Criterion 1.3.1 for not correctly marking up table headers] (

1.4 Distinguishable

1.4.10 Reflow (WCAG 2.1 Level AA)

Although the design is somewhat responsive, horizontal scroll bar appears on screens smaller than 1200px.

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>Tables -</title>

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

2.4.4 Link Purpose (In Context) Level A

First hyperlink was provided as below

image 2

whereas the next similar one is provided as below:

image 3

The first one would have been more meaningful, if the word “plugin” were included in the hyperlink text.

2.4.6 Headings and Labels Level AA

<h4 class="wb-inv">Filtering Options</h4>

The code below is sufficient and is read by the screen reader. But what does h4 class=”h4” do and should there be any headings in summary elements?

<summary><h4 class="h4">Filter Options</h4></summary>

image 4

image 5

The existing h1 could be more descriptive, h2 can be removed along with its text, all h3s on the webpage could become h2s, and all h4s as mark-up can be removed as well.

2.5 Input Modalities

2.5.4 Motion Actuation (WCAG 2.1 Level A)

NOT tested

3.1 Readable

3.2 Predictable

3.3 Input Assistance

4.1 Compatible