Guide Accessibility statement for East Devon District Council

Show all parts of this guide

8. Third-party systems

Accessibility statements from third-party systems used on the East Devon website. 

Granicus Firmstep

Firmstep's products have been developed to meet the UK Government market standards. Forms are compatible with AA accessibility guidelines.

Introduction

Firmstep's products have been developed to meet the UK Government market standards. Forms are AA compliant ref WAI guidelines. The precise level of compliance is dependent on the CSS and branding used to display a form and any javascript/code and HTML elements used locally.

The European Directive came into force for all EU member states by September 23, 2018. All websites created after that date had to be accessible by September 23, 2019, and existing websites will have to comply by September 23, 2020.

All mobile applications will have to be accessible by June 23, 2021. The mandated elements of the directive are given at EN 301 54

Citizen facing products are being updated to ensure they meet all required elements of the accessibility directive that require implementation in the EN 301 549 mandate. Further information will be noted in the Release notes as changes are implemented.

Key Features

  • Relative positioning of all on-screen items. This enables the text size to be adjusted by the client browser gracefully without clipping. This enables Form Fillers who require large text to see all of the form.
  • The tab sequence is set to enable a logical flow from field to field. This assists Form Fillers who cannot use a pointing device to complete the form easily using only a keyboard.
  • Alternative text is set on every image. This ensures that Form Fillers who are blind or partially sighted will be able to understand the meaning of an image and will be able to complete the form without seeing the image.
  • No inline styles are used. This means that a style sheet applied by a Form Filler's software may be used to override the look of the form and display it in a style accessible to that individual. (e.g. using a particular set of high-contrast colours).

Forms incorporate all these elements automatically - no special consideration is required as the form is constructed to build in accessibility features.

Forms are tested with current versions of IBM Home Page Reader 3.0 and JAWS 4 to assist blind and partially sighted users. When used inconjunction with JAWS, Forms will output to most popular refreshable Braille displays in computer or Grade 2 Braille.

MHR

New regulations came into force for public sector bodies on 23 September 2018. They say that public sector bodies must make their websites or mobile apps more accessible by meeting the international WCAG 2.1 AA accessibility standard (unless this change causes a 'disproportionate burden').

The deadline for meeting the standard is:

  • For new websites (published on or after 23 September 2018): 23 September 2019
  • For existing websites: 23 September 2020
  • For apps: 23 June 2021

Please see more details on GOV.UK

MHR will ensure that the web recruitment module which forms part of an organisation's website will meet the WCAG 2.1 AA accessibility standard by 10.33.00 release which is targeted for end of August 2019.

As the regulations focus on their public facing websites, we did make the changes to our Web Recruitment portal to ensure we are WCAG 2.1, and this is documented within the Web Recruitment user guide.

ESS remains WCAG 2.0 compliant, as do elements of the core application.

IDOX

Product: PA

Platform: Web

WCAG 2.1 tested: Yes

Comments: Public Access is our most accessible product. It conforms to the WCAG 2.1 AA standard. We have a standard statement that applies to this product:

Public Access has been built using best practices and standards as defined by the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) and conforms to the relevant success criteria of WCAG 2.1 level AA, at least.

Here is a short list of some of the accessible features presented by Public Access:

  • Clear page titles for better orientation
  • Alternative text detail for images (“alt text”) and other non-text elements
  • Consistent and clear use of headings including a semantic hierarchy (as far as possible)
  • Association of form controls with labels
  • Clear form error messages in proximity to erroneous form fields
  • Association of all data cells in a data table with their headers
  • Meaningful text for hyperlinks (and a title attribute, where applicable)
  • Forms follow a logical order and can be navigated using a keyboard (e.g. Tab key to move between fields)
  • Sufficient foreground and background colour contrast combinations
  • Keyboard navigation for menus and calendar controls

Product: TLC

Platform: Web

WCAG 2.1 tested: No

Comments: Legacy web application where the HTML/CSS has never been fully tested against the WCAG 2.1 standard.

There are WCAG 2.1 failures on all pages.

No product roadmap or plans to revamp this product for accessibility reasons.

Product: DMS

Platform: Web

WCAG 2.1 tested: No

Comments: Legacy web application where the HTML/CSS has never been fully tested against the WCAG 2.1 standard.

There are WCAG 2.1 failures on all pages.

No product roadmap or plans to revamp this product for accessibility reasons.

Product: Mobile Apps

Platform: Mobile

WCAG 2.1 tested: No

Comments: Not applicable. WCAG 2.1 is a standard for web content. Although the line may be blurred if a mobile app embeds a web based component.

Product: Uniform

Platform: Desktop

WCAG 2.1 tested: No

Comments: Not applicable. WCAG 2.1 is a standard for web content. Although the line may be blurred if a mobile app embeds a web based component.

Civica Modern.Gov

Content on our democracy pages are supplied to us by Civica Modern.Gov

Modern.Gov has carried out an accessibility review of our public-facing webpages.

The majority of their pages were compliant for AA standard accessibility under WCAG; however, they have have identified some improvements that could be made, and as such these have been implemented; there is one exception regarding the third-party jQuery-ui date picker, as detailed in Non-accessible content below.

These improvements are available to customers in B1505 and are available as a hotfix for customers who are on B1504. It is their preference that customers upgrade to B1505 as the hotfix for 1504 will not be made available until after a review of current customer versions closer to the statutory deadline of 23 September 2019.

Non-accessible content

Modern.Gov uses the jQuery-ui date picker control for the date boxes across the system. Currently there is not an accessible version of this control but it is detailed on the third-party developer’s future roadmap. This control does not affect the usability of the pages; however, it may show up on accessibility checks.

Their intention is to update this control as soon as a new version is available, as they have already with other third-party libraries they have used.

WSP

East Devon District Council's parking charge notice and parking permits services are supplied by WSP. 

Information from WSP regarding Parking Charge Notice service

https://parking.strata.solutions/EastDevonPCN 

We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • navigate most of the website using speech recognition software
  • listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website are not fully accessible:

  • Within the 'Key Events' page, there is a table which can't be focused via tabbing, or strict keyboard use.
  • The visual presentation of text and images of text do not have a contrast ratio of at least 4.5:1 – some of our ‘buttons’ such as the Pay PCN button and the warning message ‘No mapping data available’ do not pass the contrast success criteria.
  • A blank column header in a table may cause a problem when using a screen reader.
  • There is a ‘SelectedPCNReference’ hidden ID on our Key Events and View Map Location pages that is duplicated, which may cause screen readers to skip some labels, tables etc.
  • There are some personal data fields on the ‘Making a Representation’ screen that do not read out the name of the field whilst using a screen reader (NVDA).
  • There is no error message displayed following the non-upload of file attachments when making a Representation, there is just a coloured border around the Additional Information button.
  • The social media buttons on the bottom right, and the 'Online services', 'Contact us' and 'News & events' buttons are very difficult to see highlighted. All buttons that are primary green are also hard to see when highlighted as the blue matches too closely with the green. Those that rely on keyboard use would have a difficult time seeing what is focused on.
  • Within the 'Images' page on the PayPCN screen, there are two listboxes that do not have an accessible name: videoListView and listView.
  • Website requires a 'skip link' for users that rely on keyboard to skip content such as headers and navigation links.
  • Images and videos are uploaded onto the portal, as part of evidence of a contravention. However, a user that relies on text-to-speech programs will not be able to watch the video. As well - a user that cannot hear audio (if any are present) will have difficulty.

Non-compliance with the accessibility regulations

1.1.1 Non-Text Content
There are some personal data fields on the ‘Making a Representation’ screen that do not read out the name of the field whilst using a screen reader (NVDA).

1.2.1 Audio-only and Video-only (Pre-recorded)

1.2.2 Captions (Pre-recorded)

1.2.3 Audio Description or Media Alternative (Pre-recorded)
Images and videos are uploaded onto the portal, as part of evidence of a contravention. However, a user that relies on text-to-speech programs will not be able to watch the video. As well - a user that cannot hear audio (if any are present) will have difficulty. All videos, images, and audio must be made more accessible via text alternatives.

1.4.3 Contrast
Buttons, such as the 'Pay PCN' buttons, and the red warning text 'No mapping data available.' do not pass the contrast success criteria.

2.4.1 Bypass Blocks
Website requires a 'skip link' for users that rely on keyboard to skip content such as headers and navigation links.

2.4.4 Link Purpose (In Context)
The final column that is to the right of 'Street' in the Pay PCN and Main Display Pages is blank. This is problematic as a user that relies on screen reader technology will not know what that column represents.

2.4.7 Focus Visible
the social media buttons in the website footer and the ‘Online Services’, ‘Contact Us’ and ‘News & Events’ buttons are not being highlighted to indicate their focus when navigating using only the keyboard.

Within the 'Key Events' page, there is a table which can't be focused via tabbing, or strict keyboard use.

3.3.1 Error Identification
There is no error message displayed following the non-upload of file attachments when making a Representation, there is just a coloured border around the Additional Information button.

4.1.1 Parsing
Within the 'Key Events' and 'View Map Location' pages there is a hidden ID titled 'SelectedPCNReference' that is duplicated. This can potentially break accessibility, as screen readers may skip labels, tables etc due to duplicate IDs.

4.1.2 Name, Role, Value
Within the 'Images' page on the PayPCN screen, there are two violations. Two listboxes do not have an accessible name:
videoListView and listView.

We plan to rectify all identified issues by 31st March 2021. When we publish new content, we’ll make sure we continue to meet accessibility standards.

Disproportionate burden

Navigation and accessing information

It’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content.

It’s not possible for users to change text size without some of the content overlapping.

Interactive tools and transactions

Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.

We intend to have rectified this issue with our forms by March 31st 2021.

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

PDFs and other documents

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

Any new PDFs or Word documents we publish will meet accessibility standards.

What we’re doing to improve accessibility

We have identified the areas of accessibility that need to be addressed in order to meet the accessibility guidelines and we will endeavour to rectify all issues by 31st March 2021.

Preparation of this accessibility statement

This statement was prepared on 14/08/2020. It was last reviewed on 14/08/2020. This website was last tested on 02/08/2020. The test was carried out by our testing team.

We completed a full test of every page using a web browser extension in Google Chrome called ‘Accessibility Insights for Web’. We then manually check each page against the WCAG 2.1 guidelines incorporating the NVDA screen reader software.

Information from WSP regarding Parking Permits service

https://parking.strata.solutions/EastDevonPermits/Account/Login

We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • navigate most of the website using speech recognition software
  • listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website are not fully accessible:

  • The visual presentation of text and images of text do not have a contrast ratio of at least 4.5:1 – some of our ‘buttons’ such as the 'Log In' button. The red text when you don't supply proof when applying for a permit. The green text on the 'Buy/Use Vouchers' page showing the available number of vouchers.
  • A ‘skip link’ is required for users that rely on keyboard control to skip content such as headers and navigation links.
  • There are a few tables and grids that cannot be focused on - making it difficult to understand what the content of the table is. A keyboard only user will find it difficult to determine which permit is the one they're viewing, or which one they're applying for.
  • Within the 'Edit Personal Details' and 'Address Details' page, there is an address lookup button next to the post code field - which will look up the addresses in that post code, so the user can select the correct address. However, if using a keyboard you are unable to select any addresses. Users that rely on their keyboard will be unable to select their address here.
  • Also - in the Buy Vouchers screen, within the column 'Number of vouchers you wish to buy', I can't seem to get there with my keyboard either in order to insert the number of vouchers I want.
  • There are two blanks columns on the homepage. One within the 'Permits' area, where the 'View' buttons are, and the other in the 'Permit Applications' area, where the 'Buy' and 'Apply' buttons are listed.
  • Duplicate IDs within each page of the permit application process.
  • When activating a voucher, there is a popup screen which asks for a start and end date. These do not have labels. Screen readers users - due to a lack of label - will not know an input is expected in this area.
  • Any buttons that are green and blue in the permit portal are very difficult to see when it is focused on via keyboard because the ‘blueing’ of the border just blends in with the existing colour scheme of the button.
  • In the following pages, there are incorrectly structured lists:Editing a Permit and edit Customer Details which generates an error in the accessibility tool.

Compliance status

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

Non-compliance with the accessibility regulations

1.3.1 Info and Relationships
In the following pages, there are incorrectly structured lists:
- Editing a Permit
- Edit Customer Details
Which generates an error in the accessibility tool.
When activating a voucher, there is a popup screen which asks for a start and end date. These do not have labels. Screen readers users - due to a lack of label - will not know an input is expected in this area.

1.4.3 Contrast (Minimum)
The visual presentation of text and images of text do not have a contrast ratio of at least 4.5:1 – some of our ‘buttons’ such as the 'Log In' button. The red text when you don't supply proof when applying for a permit. The green text on the 'Buy/Use Vouchers' page showing the available number of vouchers.

2.1.1 Keyboard
Within the 'Edit Personal Details' and 'Address Details' page, there is an address lookup button next to the post code field - which will look up the addresses in that post code, so the user can select the correct address. However, if using a keyboard you are unable to select any addresses. Users that rely on their keyboard will be unable to select their address here.

2.4.1 Bypass Blocks
Requires a 'skip link' for users that rely on keyboard to skip content such as headers and navigation links. A user that strictly 'tabs' using the keyboard would be constantly having to tab past repetitive content areas, which fails the success criteria.

2.4.4 Link Purpose (In Context)
There are two blanks columns on the homepage. One within the 'Permits' area, where the 'View' buttons are, and the other in the 'Permit Applications' area, where the 'Buy' and 'Apply' buttons are listed.

2.4.7 Focus Visible
Any buttons that are green and blue in the permit portal are very difficult to see when it is focused on via keyboard because the ‘blueing’ of the border just blends in with the existing colour scheme of the button.
There are a few tables and grids that cannot be focused on - making it difficult to understand what the content of the table is. A keyboard only user will find it difficult to determine which permit is the one they're viewing, or which one they're applying for.

3.3.2 Labels or Instructions
When activating a voucher, there is a popup screen which asks for a start and end date. These do not have labels. Screen readers users - due to a lack of label - will not know an input is expected in this area.

4.1.1 Parsing
Each page within the permit application process contains the same duplicate ID: #tabstrip-3 > div:nth-child(4)

We plan to rectify all identified issues by 31st March 2021. When we publish new content, we’ll make sure we continue to meet accessibility standards.

Disproportionate burden

Navigation and accessing information

It’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content.
It’s not possible for users to change text size without some of the content overlapping.

Interactive tools and transactions

Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.
We intend to have rectified this issue with our forms by March 31st 2021.

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

PDFs and other documents
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
Any new PDFs or Word documents we publish will meet accessibility standards.

What we’re doing to improve accessibility

We have identified the areas of accessibility that need to be addressed in order to meet the accessibility guidelines and we will endeavour to rectify all issues by 31st March 2021.

Preparation of this accessibility statement

This statement was prepared on 14/08/2020. It was last reviewed on 14/08/2020.This website was last tested on 02/08/2020. The test was carried out by our testing team.
We completed a full test of every page using a web browser extension in Google Chrome called ‘Accessibility Insights for Web’. We then manually check each page against the WCAG 2.1 guidelines incorporating the NVDA screen reader software.