In August 2018, a new law was passed that means that public sector websites will need to meet accessibility standards so that people who use assistive technology or have additional needs can easily access services and information.
It is extremely important to ensure that your website is as accessible as possible for all users of your website.
With this in mind, we have reviewed the guidelines that have been produced to work towards to ensure that all Haiku sites are compliant with the guidelines, giving the best user experience for all visitors to the sites.
The web team in the Medical Sciences Division at Oxford have also carried out a lot of analysis work and information gathering and dissemination for website editors. The information that they have collated can be found from the links below:
Provide information about the new regulations for public sector websites.
Link to the WCAG 2.1.
Provide an area for the Haiku Community to share experiences and know-how about accessibility and carrying out accessibility audits.
The information on these pages are suggestions, ideas and links to resources and guidance.
The WCAG success criteria are open to interpretation.
This is a work in progress.
We have carried out an extensive investigation into the ways that Haiku currently supports the accessibility guidelines, and we have identified some areas where there is either a change in the guidance, or there is new guidance. We have laid out the areas where we need to carry out some changes to Haiku, in order to meet the guidelines. We have noted the action that we will take, and we will update the status of each of these actions using this table. We aim to complete all the improvements by the deadline in September 2020. If you have any questions about the accessibility of your Haiku website, please get in touch with the team through the helpdesk.
Currently, this ‘Extra’ content is limited to pop-ups in editing, as well as image pop-ups, and publication information pop-ups.
Ensure that users can easily dismiss and interact with ‘extra’ content in a manageable way. Ensure that the correct information is in the system to let software identify what the content is and how to deal with it.
Currently only applicable to the carousel functionality. The carousel pauses if you hover your mouse over it.
Add information in the code for a screen reader to be aware that to stop the carousel from moving, the user will need to move their mouse over it. Consider providing additional control for visually impaired users, to stop the carousel from updating.
If there are any buttons etc. where there is Read more type of link text that can’t be edited this should be reported to Fry via the helpdesk.
Locate and review all hardcoded button names, make sure they are done so for a reason, that would not renaming. Need button/icon labels for screen readers with this added functionality. Look into providing context for visually impaired users on all buttons/controls.
Editors have the ability to place the navigation in multiple locations, dependant on the type of content and or listing.
The look and behaviour of the navigation is always the same if using the system tools. Editors should be careful when manually compiling navigation, to ensure they function in the same way as the automated options available in the system
When a user has filled a form, they are able to review it on the screen, until they select to submit or reset the form. This is much more applicable to shops etc. where further confirmation is required
Investigate the possibility of providing a page where users can double-check the information that they have entered before submitting the form.
This functionality is not required. It can be provided with development work.