Skip to content Skip to search
My Norwich

Accessibility statement: Technical information about this website’s accessibility

Norwich City Council is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with accessibility regulations

Colour contrast

  • At the top of some pages there is an information text box where there isn't sufficient contrast between the colour of the text and the background.
  • In the A-Z listing there isn’t sufficient contrast between the letter and background for those letters where there are no entries ie K,Q,X,Y,Z

This means that the experience of people using screen readers and other assistive technologies might not be as good as it should be. This fails WCAG 2.1 AA success criterion 1.4.3 Contrast (Minimum).

We are working with our developer to correct this issue. When we publish new content we’ll make sure our use of colour contrast meets accessibility standards.

Images

  • In the banner heading of the website the council logo duplicates alternative text that is the same as adjacent text. This fails WCAG A 1.1.1

We are working with our developer to correct this issue. When we publish new content we’ll make sure our use of images meets accessibility standards.

Links

  • There are some pages where links need to be distinguished by more than just colour in order for users with visual impairments to see these links eg latest news section and forms This fails WCAG A 1.4.1.

We are working with our developer to correct this issue.

  • On some pages, links to the same destination use different link text. This fails WCAG AA success Criterion 3.2.4 (Consistent Identification)
  • In some pages, links to different destinations use the same link text. This fails WCAG A 2.4.4 (Avoid using the same link text for different destinations)
  • On some pages links may not identify the purpose of the link in order to help users decide whether they want to follow the link. This fails WCAG AA success criterion 2.4.4 Link purpose (in context)

Skip to content

On the Food hygiene ratings list, Business merits list and skin piercing establishments there is no skip to content function. This fails WCAG A 2.4.1 Allow users to quickly skip to content.

We are currently working through these pages to correct them and plan to have this done by the end of 2021. When we publish new content we’ll make sure link text meets accessibility standards. Where it is necessary to publish a document that cannot be made fully accessible eg Citizen magazine it will be published alongside accessible HTML web content.

Pop-up windows (dialogs)

Some dialogs may not have accessible labels therefore cannot be read out by screen readers. This fails WCAG A 1.3.1

Controls including links, buttons, and fields

Some links buttons and fields don't change appearance when they are selected on the keyboard. This fails WCAG AA 2.4.7

Embedded maps

Some ID attributes are not unique, This fails WCAG A 4.1.1

Alternative text the same as adjacent text

An  image inside a link must not have the same alt text that as the text link inside or beside it. This fails WCAG A 1.1.1 Avoid alternative text that is the same as adjacent text

Tables

  • Some tables do not have headers. This fails WCAG 2.1 A 1.3.1 success criterion (Info and Relationships).

We are working with our developer to correct this issue. In the meantime any existing tables are being corrected manually which we plan to have done by the end of 2021. When we publish new tables we’ll make sure they meet accessibility standards.

Forms

  • Some form fields do not identify what their purpose is programmatically, which allows browsers to help users fill in forms with known information. This fails WCAG AA 1.3.5
  • Some search functions do not contain a submit button. This fails WCAG A 2.2.2

We are working with our developer to correct this issue.

PDFs and other documents

We have a number of PDFs and other documents that are not compliant for the following reasons:

  • tagging hasn't been carried out correctly (WCAG A 1.3.1)
  • headings have not been specified (WCAG A 1.3.1)
  • headings don't follow a logical order
  • default language is not specified (WCAG A 3.1.1)
  • titles are not defined
  • long  pdfs may not have bookmarks
  • documents have been designed
  • documents have been photocopied and converted to pdfs
  • forms in PDF or Word format
  • documents have been provided by third parties

We are reviewing all of our PDFs or Word documents to ensure they will meet accessibility standards unless we determine that they represent a disproportionate burden within the meaning of the accessibility regulations.

Ultimately we plan to provide an accessible HTML version of the information as the primary source. Where it is necessary to publish a document for customers to print that cannot be made fully accessible, it will be published alongside accessible HTML web content eg Citizen magazine and council policies.

Pdfs and documents can be made available in an alternative format on request.

Content that’s not within the scope of the accessibility regulations

You can find the complete list of content exempt from meeting the accessibility regulations on legislation.gov.uk.

PDFs and other documents

The accessibility regulations don't require us to fix PDFs or other documents published before 23 September 2018 if they're not essential to providing our services.

Live video

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

Similarly, any prerecorded video published before 23 September 2020 is exempt from meeting the regulations.

Maps

Online maps and mapping services are exempt from meeting the accessibility regulations.

Archived content

Some of our content, such as news articles and minutes of meetings is archived and not within scope of the accessibility regulations.

Third party applications

We require that any new system we commission is Web Content Accessibility Guidelines 2.1 AA compliant. However the following third party applications are partly or wholly out of our control and so may not conform to the same levels of accessibility as the rest of the website.  

  • CMIS (councillor information, meetings, agendas and minutes)
  • Idox (planning applications search)
  • Civica (payments)
  • Gateway (parking)
  • Northgate (council tax)
  • iTrent (job applications)
  • Norwich Home options (Housing)

We are working with our suppliers to fix accessibility issues.

How we tested this website

This website was and is currently being tested for compliance with the Web Content Accessibility Guidelines V2.1 level A and level AA, and these tests have been carried out internally by the web team using automated software and manual sampling.

What we’re doing to improve accessibility

We are continuing to fix the accessibility issues listed in this statement both in-house and with our developers and third party suppliers. Product contract renewals and upgrades will be reviewed.

The accessibility of the website is being reviewed on an ongoing basis and we are now using Silktide (automatic software) and Wave (manual sampling) to help us identify any new issues that arise.

This statement was prepared on 23 September 2020. It was last updated 17 August 2021.