https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40283 Bug ID: 40283 Summary: Accessibility of the status message in the OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Accessibility Assignee: koha-bugs@lists.koha-community.org Reporter: nina.martinez@biblibre.com QA Contact: testopia@bugs.koha-community.org CC: martin.renvoize@openfifth.co.uk, matt.blenkinsop@openfifth.co.uk, oleonard@myacpl.org The intent of this success criterion is to make users aware of important changes in content that are not given focus, and to do so in a way that doesn't unnecessarily interrupt their work. https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html To improve this, we can add role=”status” or role=”alert” in the message tag. Using the status role from the ARIA specification to notify Assistive Technologies (AT) when content has been updated with information about the user's or application's status. https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA22 The purpose of the role=”alert” is to notify Assistive Technologies (AT) when an input error occurs. The role=”alert”attribute makes it possible for an AT (such as a screen reader) to be notified when error messages -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.