Bug 41934 - Empty table header in course reserves table causes accessibility error
Summary: Empty table header in course reserves table causes accessibility error
Status: Needs Signoff
Alias: None
Product: Koha
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Laura Escamilla
QA Contact: Testopia
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2026-02-25 15:51 UTC by Laura Escamilla
Modified: 2026-02-26 12:14 UTC (History)
3 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments
Bug 41934: Fix empty table header in course reserves table (1.63 KB, patch)
2026-02-25 15:54 UTC, Laura Escamilla
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Laura Escamilla 2026-02-25 15:51:21 UTC
The responsive control column in the OPAC course reserves table contains an empty <th> element. This results in an empty table header and an empty aria-label, which is flagged as an accessibility error by automated testing tools.
Comment 1 Laura Escamilla 2026-02-25 15:54:46 UTC
Created attachment 193914 [details] [review]
Bug 41934: Fix empty table header in course reserves table

To test:
1. Apply the patch.
2. Navigate to the OPAC course reserves page: http://localhost:8080/cgi-bin/koha/opac-course-reserves.pl
3. Inspect the course reserves table header using browser developer tools.
4. Confirm the responsive control column header contains visually hidden text describing the column (e.g. "Details").
5. Confirm the table appearance and responsive expand/collapse behavior remain unchanged.
6. Sign off.
Comment 2 Owen Leonard 2026-02-26 12:14:43 UTC
This is nit-picky but I don't think wrapping the contents of that table header with .sr-only is correct. .sr-only is for things which are hidden from sighted users but readable by screen readers. If we want something hidden from everyone I think we have as-is.

In order to pass the accessibility test maybe we put text in that header cell without any class? I was thinking "Expand," which might help sighted users. In my test with macOS's VoiceOver the cell isn't read at all.