Accessibility - "Unpublished Site" Banner - The current heading level is out of descending sequence

Description

Issue

The “Unpublished Site” banner does not meet accessibility standards due to the heading level falling outside of the descending order. It seems to jump from H2 in the tool menu to H4 in the “Unpublished” Site banner, skipping the H3 level.

Proposal

Review the structural order and adjust the heading level accordingly.

Background

In Google Chrome, on Trunk at (Sakai 23-SNAPSHOT at the time of this writing), scans by both a SiteImprove web browser extension and Google Dev Tools Lighthouse detect this issue.

Looking at the source code, it seems that the heading level immediately preceding the unpublished site banner is the H2 tag at the top of the site menu:

The “Unpublished Site” banner uses an H4:

I leave this to more qualified individuals, but perhaps shift the “Unpublished Site” banner to H3 or maintain the same level (H2) to avoid this issue?

Notes

  1. I selected the component “Site Info” for this ticket but this banner appears at the top of all unpublished sites, no matter the tool selected. If there is a better component (portal?), please advise so that I can update the ticket or kindly edit the ticket directly.

  2. I tested using the desktop web browser. Be sure to verify that the sequence remains the same in both desktop/computer and mobile views. If the mobile presentation varies, modify accordingly so that both views will meet accessibility standards.

Thank you for considering this ticket!

Attachments

6

Activity

Show:

Alan Regan July 31, 2023 at 11:53 PM

I checked Sakai 21.x and the H4 tags are present (as expected).

I checked Sakai 22, 23, and 24. Rather than using H4 tags, there are STRONG tags used instead.

Here is example code (Triunk Sakai 24, using site AFTE_599H_8211):

You can compare that to the code on Sakai 21.x Maintenance (using site QJNQ_305L_8690):

Looks good!

Andrea Schmidt July 31, 2023 at 11:31 PM

Verified on 22x: https://qa22-mysql.nightly.sakaiproject.org/, build: 5ab29521

Will also set 23x to verified, based on comments

Adam Marshall June 11, 2023 at 7:35 PM

saame on sakai 23

Adam Marshall June 11, 2023 at 7:35 PM
Edited

I used axe

 

and got this

I so I’m saying it passed.

 

Alan Regan October 6, 2022 at 8:38 PM
Edited

Thank you so much, Chris! Very glad that your testing went well. And thank you to the developers for addressing this concern!

We look forward to applying this fix in the future. We hope that it can be backported to 21.x and 22.x.

Fixed

Details

Priority

Affects versions

Fix versions

23 Status

QA Verification Pass

22 Status

Verified

Components

Assignee

Reporter

Created April 6, 2022 at 9:32 PM
Updated July 31, 2023 at 11:53 PM
Resolved June 27, 2022 at 5:44 AM