Limitations of HiMap's accessibility
We have designed, developed and tested HiMap to be accessible. However, you may find some accessibility limitations which we are working to fix.
Screen reader use in tables, search and filtering tools
Some areas of HiMap that contain tables, search results and filtering controls may provide more information than necessary when used with a screen reader. Some filtering interactions may also be more complex than they will be when optimised.
Maturity Scorecard
The Accessibility Maturity Scorecard currently has some accessibility limitations affecting screen reader and keyboard-only users. Some controls may require more keyboard interaction than desired and some dynamic updates may not always be communicated as clearly as intended. Users may also experience challenges moving between the scorecard and the surrounding page content.
Page display at high zoom levels
At 200% zoom and particularly at 400% zoom, some users may experience navigation and scrolling difficulties when using the Accessibility Maturity Scorecard or some of the more data rich areas of HiMap such as Your Action Plan.
Using the browser Back button during a scorecard assessment
Using the browser Back button while completing the Accessibility Maturity Scorecard may result in previously entered responses being lost. When entering information into the Scorecard, we recommend using the controls provided within the Scorecard itself rather than browser navigation controls.
We are aware of these issues and are continuing to improve accessibility as HiMap develops. Accessibility issues are prioritised according to user impact and are being addressed as part of the ongoing product roadmap.