We are currently doing some work in response to the new Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 that came into place in September.
One of the main things we are doing is looking at the accessibility of our current Moodle theme [Adaptable 1.7] – specifically we are trying to ensure that the basic Heading structure on Course pages makes sense to anyone using a screen reader. We wondered if you were able to advise.
We have been using a tool called Wave to investigate the basic Heading structure of the current Moodle Theme. The following screen shot of WAVE is annotated to show the issues we have found.
Based on our current understanding and some experimentation with both WAVE and the NVDA screen reader we believe we should aiming to implement the following heading structure.
The above seems to have a sensible and logical structure that would be easy to follow using appropriate keyboard short cuts in a screen reader.
However, we are finding it really difficult to implement <h2> tags for Section headings. These seems to be “hard” coded to <h3>. Furthermore, we don’t not seems to be able to detect a <h2> tag on the course page using WAVE or NVDA screen reader. Given that the ATTO text editor formats lagre headings at <h3> it is difficult to understand why week/topic section headings should also be <h3>.
We be really grateful if someone could advise us on either
- How to change section headings to <h2>
- Why section headings should be <h3> from an accessibility perspective and what headings structure we should actually be aiming to implement
We would be very gratefully.