Bug 9390 - Accessibility - "Item has been withdrawn" alert box difficult to access for screen-reader users
Summary: Accessibility - "Item has been withdrawn" alert box difficult to access for s...
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Staff interface (show other bugs)
Version: Main
Hardware: All All
: P5 - low trivial (vote)
Assignee: Bart Jorgensen
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-15 01:47 UTC by Bart Jorgensen
Modified: 2014-12-07 20:02 UTC (History)
3 users (show)

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


Attachments
Added header tags to error message to make it more accessible (1.06 KB, patch)
2013-01-15 02:15 UTC, Bart Jorgensen
Details | Diff | Splinter Review
Bug #9390 "Item has been withdrawn" alert box difficult to access for screenreader users (1.14 KB, patch)
2013-01-15 03:16 UTC, Liz Rea
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Bart Jorgensen 2013-01-15 01:47:39 UTC
When you attempt to checkout a book that has already been withdrawn the alert message is difficult to read when using screen reader software and also difficult to navigate to as it is in plain text and in a list which is also very far down the html page in some cases.
Comment 1 Bart Jorgensen 2013-01-15 02:15:47 UTC Comment hidden (obsolete)
Comment 2 Liz Rea 2013-01-15 03:16:49 UTC
Created attachment 14583 [details] [review]
Bug #9390 "Item has been withdrawn" alert box difficult to access for screenreader users

to test:
-checkout a withdrawn book to a patron
-check that text is bold
-if unsure view page source and check that the header tags are in the html

Signed-off-by: Liz Rea <liz@catalyst.net.nz>
Comment 3 Katrin Fischer 2013-01-15 07:35:13 UTC
I am sorry, but this change produces invalid XHTML.

You can test XHTML validity using the W3C validator. If your website is not accessible from the internet, you can copy the whole HTML source code from your browser into the third tab (http://validator.w3.org/#validate_by_input)

I think switching around the tags might make the problem go away, but not completely sure.
Comment 4 Katrin Fischer 2013-01-15 07:39:37 UTC
Could introducing a heading to the dialog box be another solution? Sometimes you will get more than one error/warning message for an item, as it triggers more than one condition at the same time.
Comment 5 Owen Leonard 2013-01-15 14:00:54 UTC
See my comment on Bug 9389 about this issue. Can't we accomplish the goal of highlighting the error by adding the heading to the message box itself, with the messages themselves remaining in a list?