Bug 25243 - Accessibility: 2.4.6 Headings and Labels
Summary: Accessibility: 2.4.6 Headings and Labels
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords: accessibility
Depends on: 25244 26655
Blocks: 23003
  Show dependency treegraph
 
Reported: 2020-04-22 06:51 UTC by Martin Renvoize
Modified: 2021-04-14 13:56 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Renvoize 2020-04-22 06:51:21 UTC
There are a few cases where we are not adhering to the 'Headings and labels describe topic or purpose' guidelines for a AA accessibility rating.

This bug serves as a collector bug for cases where this guideline is not being adhered to.
Comment 1 Hayley Pelham 2021-02-03 02:34:01 UTC
The main heading <h1> of each page in Koha should describe the topic or purpose of the page. At the moment, the <h1> of each page looks like:

<h1 id="logo">
 <a class="navbar-brand" href="/cgi-bin/koha/opac-main.pl">
  Library Name</a>
</h1>

It makes more sense and would be more helpful to ensure the heading has a descriptor of the page that they're on, rather than no description surrounding a link containing the name of the library.

The following WCAG2.1 page explains this further:
https://www.w3.org/WAI/WCAG21/Techniques/general/G130

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25155#c12
raises a question of what navigation items should be if h1 is move to the main content, and here is a page which shows that it is acceptable to have h2 that come before the h1 in the content, see example 2:
https://www.w3.org/WAI/tutorials/page-structure/headings/
Comment 2 Martin Renvoize 2021-02-03 10:27:56 UTC
(In reply to Hayley Mapley from comment #1)
> The main heading <h1> of each page in Koha should describe the topic or
> purpose of the page. At the moment, the <h1> of each page looks like:
> 
> <h1 id="logo">
>  <a class="navbar-brand" href="/cgi-bin/koha/opac-main.pl">
>   Library Name</a>
> </h1>
> 
> It makes more sense and would be more helpful to ensure the heading has a
> descriptor of the page that they're on, rather than no description
> surrounding a link containing the name of the library.
> 
> The following WCAG2.1 page explains this further:
> https://www.w3.org/WAI/WCAG21/Techniques/general/G130
> 
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25155#c12
> raises a question of what navigation items should be if h1 is move to the
> main content, and here is a page which shows that it is acceptable to have
> h2 that come before the h1 in the content, see example 2:
> https://www.w3.org/WAI/tutorials/page-structure/headings/

I wholeheartedly agree here.. and had a similar conversation with Owen at the time that I fixed all the nested headings.  At the time, we didn't come up with a solution; but I reckon it's time to revisit this.

Do you have someone willing to work through the system for this Hayley?  Perhaps we could involve our accessibility advocate if we need some help working out suitable H1's for various pages.
Comment 3 Hayley Pelham 2021-02-03 20:28:44 UTC
Hi Martin,

We now have a couple of accessibility advocates in our Koha team at Catalyst, and I think we may have the time to start working through this.

I'm not sure of the best approach that will make sense in Bugzilla, I guess we can make some child tickets to this ticket for changing the navbar with the <h1> logo and then for every other page updating the headings?

Should staff side and OPAC be done separately? Probably would help to keep things managable.
Comment 4 Martin Renvoize 2021-02-05 17:01:34 UTC
That's great news Hayley, 

Accessibility is becoming more and more of a priority and close to my heart :)

I think it's good to split OPAC and Staff to keep things moving. As for splitting down further by page, I did that when I first worked through the OPAC simply to try and keep them trickling through and make sure people could think about them one at a time.. sometimes it can be difficult to spot which heading should be treated as the 'main heading'..  I'd say to an extent play it by ear.. if it feels like a patchset it getting a bit unmanageable then split it into multiple bugs.

I'm more than happy to lend a hand with testing and QA for these.. we have lots of customers especially interested too who are getting up to speed on testing who I can direct at things :)