Accessibility roadmap


We will be fixing the accessibility issues on the site as soon as practicable.

Our approach to this is to categorise & prioritise according to the following matrix:

Priority 2

High impact but low use

  • Remove unnecessary proprietary (.docx, .pptx) documents
  • Fix the timer contrast

Priority 1

High impact and high use

  • Tab order - keyboard access
    (both page links and Umbraco forms)
  • §Reviewing pages for correct heading structure
  • §Review "alt" on all images & provision of alternate content for "infographics"
  • §Creating accessible documents & PDFs
  • "Technical" issues with system-generated code (listed separately)
  • Update forms package & re-check accessibility

Priority 4

Low impact and low use

  • Form label issues (need further investigation to evaluate effect on screen-reader users)
  • <noscript> issues
  • <iframe> issues*

Priority 3

Low impact but high use

  • Theme contrast issues (listed separately) - mitigated by contrast button
  • Top logo link destination "Subsite home"
  • Remove empty link from notices: <a target="_self"></a>
  • Fix missing "alt" on Image map/route templates
  • Label grid in Images grid template on touch devices
  • Review colours on the content section templates
  • Review & convert PDFs (& proprietary files) to HTML where appropriate
  • Home page menu icons & duplicate links

§These issues are training related. We include accessibility training all web and email bulletin sessions but we have problems with:

  • users producing badly structured pages because they think they can produce "better" content, typically ignoring heading consistency and misusing images containing text (typically infographics & posters);
  • poor document preparations skills and a complete lack of understanding of how to structure a document well and check it for accessibility.

*Third party embedded content such as video players, maps and calendars, typically contained in <iframes> will be checked in a second phase and where issues are discovered we will contact the supplier of such content to discuss improvement. Where necessary, we will investigate and switch to more accessible alternatives.



  • Accessibility tested & roadmap developed
  • Constitution translated from PDF to HTML


  • Preparing "training" guidance for all system editors.
  • Checking notice contrast accessibility


  • Open urgent ticket for tab order keyboard access
  • Open ticket with supplier for system generated code issues
  • Confirm theme changes with design
  • Open ticket with supplier for theme issue
  • Accessibility training for all admin authors (Digital Team)
  • Accessibility training for champions
  • Implement workflow for content approval

Other issues (not listed above)

The issues detected will be submitted as tickets to the supplier.

Help us improve Gloucestershire

Don’t include personal or financial information like your National Insurance number or credit card details.