[Koha-bugs] [Bug 27740] Accessibility: OPAC - Headings should have correct tags and hierarchy

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27740

--- Comment #10 from wainuiwitikapark at catalyst.net.nz ---
Hi Owen,

I have contacted our Accessibility team at Catalyst and have received the
following message:

-------------------------------------------------------------------------

"First, I would make sure you're using the proper HTML. According to MDN,
<h#> is a permitted child of <legend> and <caption>, but not of <label>.
Instead, the <h#> would be the parent of <label>.

Second, consider the context of the headings.

According to W3C, "Headings communicate the organization of the content
on the page" so yes I do think that headings can help screen reader
users to have an overview of the website
(https://www.w3.org/WAI/tutorials/page-structure/headings/). However,
headings should be used to identify sections of the page instead of
providing name or specify title of an element.

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/label
"Placing heading elements within a <label> interferes with many kinds of
assistive technology, because headings are commonly used as a navigation
aid. If the label's text needs to be adjusted visually, use CSS classes
applied to the <label> element instead."

You can look at this link to see examples of "Making labels and legends
headings"
https://design-system.service.gov.uk/get-started/labels-legends-headings/"

-------------------------------------------------------------------------

Therefore, I am going to have another look at everything and keep headings
where they are specific sections of the page, as this helps screen-readers
navigate a webpage. However, if the element of the page doesn't seem to be a
stand alone section, I will amend this to put it back to a legend, caption or
label.

-- 
You are receiving this mail because:
You are watching all bug changes.