Skip to main content

Accessibility Report

Table of Contents

Report for North East Lincs Council

  • Report Creator: North East Lincs Council’s Web Team
  • Evaluation Commissioner: North East Lincs Council
  • Evaluation date 29 October 2020

Summary of the evaluation findings

The new nelincs.gov.uk site went live on 23 September 2020 and as there were some delays that were beyond the Council’s control, the site was not 100% complete and there was a few remaining issues. After the launch date, both the Development Team and the Web Team worked through the remaining accessibility issues and a more thorough test was conducted, against the full Web Content Accessibility Guidelines (WCAG) 2.1 Level AAA. The conformance level that all public sector bodies are required to meet is WCAG 2.1 AA and it was the commitment of the Council to launch a product that exceeded the minimum required standard and many best practices and AAA criteria were met during the development of this site. We tested this site against the AAA specification, but with a conformance target of Level AA. The site meets and in many instances exceeds the minimum required standard and therefore, complies with The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (PSBAR).

18 pages were tested using the Web Content Accessibility Guidelines – Evaluation Method (WCAG-EM) and the pages selected for evaluation included main template pages (Home, Search, Bin Schedule (3 steps), Accessibility, Coronavirus, News, Pay it and Contact), 6 pages were identified during random selection, using a random number generator and the additional pages were added to the test methodology, such as those related to Blue Badge and Special Educational Needs, as these were deemed to be pages that were likely to be accessed by users that would most benefit from the accessible features within the application.

The evaluator has a related degree in computer science (where user experience and digital accessibility were studied as part of a self-led project) and experience working as a front-end software developer in the private sector. The results of this test are, to the best of the evaluator’s skills and beliefs an accurate reflection of the overall accessibility of nelincs.gov.uk. The opinion of the evaluator is that the code and content of nelincs.gov.uk exceeds the minimum requirements set forth in WCAG 2.1 AA and is therefore compliant. There are third party tools that are hosted on external sites that the Council is working with suppliers with, to obtain accessibility statements and remediate any identified issues.


Scope of the evaluation

Website nameNorth East Lincs Council
Scope of the website18 pages were identified for evaluation, which included:
A selection of primary pages that included all of the layouts, widgets and tools used throughout the application (Home, Search, Bin Schedule (3 steps), Accessibility, Coronavirus, News, Pay it and Contact).
6 pages were selected at random, using a spreadsheet and a random number generator.
4 additional pages were selected such as Blue Badge and 3 from the Special Educational Needs pages, as these were deemed to be pages that were likely to be accessed by users that would most benefit from the accessible features within the application.
WCAG VersionWCAG 2.1
Conformance targetLevel AA
Additional evaluation requirementsThe report will test all pages that were selected by the evaluator against the full Level AAA criteria, but with a conformance target of Level AA, using all listed devices, browsers and tools.
There are presently in excess of 2,500 documents, including .docx (Word), .xslx (Excel) and PDF (Adobe). The documents were not tested at this stage. the Web Team have reduced the number of documents from over 12,000 to 2,500 and all documents submitted for publication are only published if they meet accessibility checks, unless they are exempt (such as plans or maps) and where a document is exempt, a text alternative exists.
There are some documents that do not pass accessibility checks, as initially we were unable to meet the demand, whilst providing training to the entire organisation and reviewing the content across all pages. We estimate that about 10 – 20% of documents uploaded after 23 September 2018 may have accessibility issues. The Council aims to resolve all of these documents by 31 March 2021, subject to capacity and resources.
There are a number of third-party tools used across this site, such as forms, payment portals and maps. We have been working with external suppliers, pushing for the necessary enhancements to be made, we will test a number of user-journeys, that rely on these third-party tools and provide a report and an update to the statement, as soon as practicably possible.
Accessibility support baselineFirefox (latest version) on a Windows device with NVDA (primary screen reader combination)
Chrome (latest version) on a Windows device (primary non-screen reader testing browser)
Mobile Safari (latest version) on an iPad, with Voiceover (Primary tablet testing device, including screen reader, zoom and usability)
Mobile Chrome (latest version) on an Android phone (Primary mobile testing device, including screen reader, zoom and usability)
Internet Explorer 11 on a Windows device (Voice input testing and basic presentation checks)
Relied upon technologiesHTML5
ECMAScript 5
DOM
CSS
WAI-ARIA

Overview of audit results

PrincipleLevel ALevel AALevel AAA
1. Perceivable9/911/116/9
2. Operable12/123/311/12
3. Understandable5/55/51/7
4. Robust2/21/10/0
Total28/2820/2018/28

Detailed audit results

Principle 1 Perceivable

1.1 Text Alternatives

Results for the entire sample:

Outcome: Passed

Findings: Where non-text content is used, each instance has appropriate labels or good use of ARIA attributes, alternative text was used on images that add context or information to the web page and those that are decorative have an empty alt attribute, so would be ignored by screen readers, so as not to provide unnecessary noise to the webpages.

Inputs were also correctly labelled and where a visible text label did not exist (search button), suitable ARIA was used.

1.2 Time-based Media

Results for the entire sample:

Outcome: Not present

Findings: No video or audio content detected in inspection

Results for the entire sample:

Outcome: Not present

Findings: No video or audio content detected in inspection

Results for the entire sample:

Outcome: Not present

Findings: No video or audio content detected in inspection

Results for the entire sample:

Outcome: Not present

Findings: No video or audio content detected in inspection

Results for the entire sample:

Outcome: Not present

Findings: No video or audio content detected in inspection

Results for the entire sample:

Outcome: Not present

Findings: No video or audio content detected in inspection

Results for the entire sample:

Outcome: Not present

Findings: No video or audio content detected in inspection

Results for the entire sample:

Outcome: Not present

Findings: No video or audio content detected in inspection

Results for the entire sample:

Outcome: Not present

Findings: No video or audio content detected in inspection

1.3 Adaptable

Results for the entire sample:

Outcome: Passed

Findings: All content follows best practices and is structured using the correct HTML, which conveys the correct relationships in the page’s sections and the content within. All headings are used correctly, as well as appropriate landmarks, text formatting and indication of link purpose are used to good effect.
ARIA is used, as a last resort, where HTML has no semantic alternative, such as providing an accessible name or value, where necessary.

 

Results for the entire sample:

Outcome: Passed

Findings: The sequence of content and controls across all tested pages across all tested viewports flows in a logical and meaningful manner. No incorrect use of markup or styles that could create a mismatch between structure and style was detected.

Results for the entire sample:

Outcome: Passed

Findings: Content does not rely on any sensory characteristics, except for on the postcode look up, which uses the word ‘below’, but this instruction always indicates the next item in the DOM and tab order and this was true when tested against all viewports.

Results for the entire sample:

Outcome: Passed

Findings: No functionality of any of the sample pages required a specific device orientation and the whole sample could be used in either landscape or portrait orientation, across all 3 test devices.

Results for the entire sample:

Outcome: Passed

Findings: Search input has autocomplete set to off, as this is not a field that has an autocomplete value.
No other pages have any inputs, other than the bin collection drop down, which is pre-populated.
There are a number of third-party forms, that are not a part of this website’s source code. The council are working with third party suppliers, to bring their content and systems up to the required standard, as they often form a core part of a user journey.

Results for the entire sample:

Outcome: Passed

Findings: Icons such as the paperclip and the external link sign were selected to identify where a document is an attachment or the link points to an external resource, respectively.
The icons are marked up with hidden text, which affords those accessing the site in a non-visual way the same information.
Appropriate use of landmarks and interface components have a name, role and value

1.4 Distinguishable

Results for the entire sample:

Outcome: Passed

Findings: Links have been developed to include an enhanced focus indicator, which use size, background and a thick underline, which replaces the text’s underline.
In page links are underlined, and do not rely on colour alone.
Buttons and controls change shape or size on focus

Results for the entire sample:

Outcome: Not present

Findings: No audio present of the sample of pages

Results for the entire sample:

Outcome: Passed

Findings: All text has a minimum contrast level of 4.5:1, this often significantly higher, with a slightly subdued black text on white forming the main content, which has a contrast ratio of 15.42:1
Links use a blue colour, which has a contrast ratio of 5:1
Links within the navigation bar have a contrast ratio of 8.45:1
Contrast always meets the minimum requirement and in many cases, substantially exceeds it

Results for the entire sample:

Outcome: Passed

Findings: All text resizes using standard operating system controls in Windows (‘ctrl’ and ‘+’)
All text scales when changing the system preferences in Windows
Adjusting the text size in Chrome and Firefox, within the accessibility settings adjusts the text size, as per user preferences
Reverse pinching zooms all text on Android and iOS

Results for the entire sample:

Outcome: Passed

Findings: There is a logo in both the header and footer, which has the correct alt text (NELC logo),
The news page contains a number of images, the alt text is mostly sufficient, although sometimes a little too verbose and often correctly the alt text is left blank for decorative images.
Recommendation for Web Team to continue to provide training to all staff with access, regarding optimal use of alt text

Results for the entire sample:

Outcome: Failed

Findings: Not all text meets the AAA criteria (inline links have a contrast ratio of 5:1)

Results for the entire sample:

Outcome: Not present

Findings: No background audio present

Results for the entire sample:

Outcome: Failed

Findings: No controls for changing the colour of background and fonts are present

Results for the entire sample:

Outcome: Failed

Findings: There are images of text present on some pages, such as on the News page and it’s articles

Results for the entire sample:

Outcome: Passed

Findings: Browser window set to a width of 1280 pixels and zoom set to 400% replicates a device width of 320 pixels (320 x 4 = 1280).
No loss of content or any obscured elements were detected. All content reflows into a single column

Results for the entire sample:

Outcome: Passed

Findings: Buttons and controls, such as inputs typically provide strong visual affordance with cues such as utilising icons or position with sufficient contrast, as well as strong visual focus indication

Results for the entire sample:

Outcome: Passed

Findings: Tested with Bookmarklet, all text increased, using the override mechanism.
Paragraph spacing was in excess of double the text height and text spacing, and word spacing met the criteria, which was set via the bookmarklet.
This also worked well and met the requirements on a simulated mobile viewport

Results for the entire sample:Outcome: Passed

Findings: Fly-out menu can be dismissed with the ‘esc’ key, by tabbing out of the navigation list and by an ‘onblur’ event (clicking outside of the container)
The drop down on the Bin collection pages can be dismissed with the ‘tab’ key, the ‘esc’ key and an ‘onblur’ event.
No content appears on hover or focus without a user initiating the action, by clicking/touching, pressing ‘space’ or ‘enter’ or by using any other input modality.


Principle 2 Operable

2.1 Keyboard Accessible

Results for the entire sample:

Outcome: Passed

Findings: All content can be accessed via a keyboard and no functionality is operable by a particular input modality.
ARIA authoring practices are followed for widgets such as accordions, drop downs and fly-out navigation

Results for the entire sample:Outcome: Passed

Findings: Focus never becomes trapped within any element when using any input modalities

Results for the entire sample:

Outcome: Passed

Findings: No content or controls require a specific input modality and all functionality is available via a keyboard

Results for the entire sample:

Outcome: Passed

Findings: No character key shortcuts have been implemented

2.2 Enough Time

Results for the entire sample:

Outcome: Not present

Findings: There are no elements or functionality on this application that are restricted by any time-based mechanism

Results for the entire sample:

Outcome: Not present

Findings: No animations, slide shows or auto playing videos are present within application

Results for the entire sample:

Outcome: Not present

Findings: There are no elements or function on this site that are restricted by any time-based mechanism

Results for the entire sample:

Outcome: Not present

Findings: Not present in application

Results for the entire sample:

Outcome: Not present

Findings: Not present in application

Results for the entire sample:

Outcome: Not present

Findings: Not present in application

2.3 Seizures and Physical Reactions

Results for the entire sample:

Outcome: Passed

Findings: The only evidence of flashing detected throughout the sample pages was the insert text icon, which uses browser defaults and is below the threshold

Results for the entire sample:

Outcome: Passed

Findings: The only evidence of flashing detected throughout the sample pages was the insert text icon, which uses browser defaults and is below the threshold

Results for the entire sample:

Outcome: Passed

Findings: No non-essential motion is included

2.4 Navigable

Results for the entire sample:

Outcome: Passed

Findings: Application has a Skip to Main Content link, as the first actionable element, which appears on keyboard focus
Application makes good use of landmarks and headings practices which results in multiple ways to bypass or access content, for users of assistive technologies

Results for the entire sample:

Outcome: Passed

Findings: Each page has a unique title.
The unique information comes first, as a best practice eg. “Council tax discount | NELC”
During step-based processes, such as checking a Bin Collection schedule, the specific information is added to the page title and updated each step eg. “You searched for dn311hu – NELC” and then the address of the selected option replaces the postcode in the page title
The search parameters are included in the title: “you searched for tax | NELC” and should a user use the pagination feature, the page title will update to include the current page out of the number of pages

Results for the entire sample:

Outcome: Passed

Findings: All interactive elements have a focus order that matches the visual focus order and this translates across multiple user agents, viewports and devices

Results for the entire sample:

Outcome: Passed

Findings: Links are descriptive in nature and their purpose is clear both in the context of its surrounding text or taken out of context

Results for the entire sample:

Outcome: Passed

Findings: Site contains a main navigation, accessed from the header, which contains top-level links.
Each top-level link leads to a category page, which lists the second-level links
Each content page has a related links or contents section
There is a Search function
There is a site map, accessed from the footer

Results for the entire sample:

Outcome: Passed

Findings: A logical heading hierarchy is used throughout. All pages tested were tested with a headings map tool, which indicated the relationships in structure, between components, landmarks and the content within.
Labels are used on controls, to good effect and where a text label is not practical, an adequate ARIA label has been used.
In sections where design choices left out a visual label, such as the colophon area in the footer, an adequate hidden label has been added, to assist users of assistive technologies of the content

Results for the entire sample:

Outcome: Passed

Findings: Every control that can receive keyboard focus is visually clear by use of an enhanced focus style
Links use an enhanced focus indicator, which consists of changing the shape and size of the hit area, toggling the underline, changing the colour of the background to a bright yellow, but as an addition a 4 pixel solid border that spans the width of the link is also present
Buttons use a similar style, but in addition change shape, as the rounded borders become right angles
Inputs have the text insertion indicator and the border expands to 4 pixels

Results for the entire sample:

Outcome: Passed

Findings: There is a breadcrumbs trail, which communicates the location, within a set of web pages
There is a site map, which groups all pages logically
Contents page contain a sidebar, that has related links and previous and next links are available in content sections, that have a sufficient label within the link text

Results for the entire sample:

Outcome: Passed

Findings: All links use descriptive and informative text.
Links that direct a user to an external site have an external link icon, which also has a hidden label which makes this information available to screen reader users and users who may bring up a list of links, using software.
Documents have both the file type and the file size contained in brackets and a paperclip icon which indicates it is an attachment and there is hidden text that informs users of assistive technologies of the same information.

Results for the entire sample:

Outcome: Passed

Findings: All sections have sufficient headings and those headings are used in a correct hierarchy which represents relationships in content

Results for the entire sample:

Outcome: Passed

Findings: All functionality can be operated with a single point input

Results for the entire sample:

Outcome: Passed

Findings: The down event never invokes a control and can always be cancelled by moving the pointing device away from the input

Results for the entire sample:

Outcome: Passed

Findings: Controls have a visible label displayed as text or:
The search has sufficient ARIA text, which matches the placeholder text
The button for the search input has sufficient ARIA text, which describes the control “Search button”

Results for the entire sample:

Outcome: Not present

Findings: No motion based interactivity detected within the application

Results for the entire sample:

Outcome: Failed

Findings: Not all controls have a minimum target size of 44 pixels

Results for the entire sample:

Outcome: Passed

Findings: All triggers can be activated with multiple input modalities
All functionality was available with a mouse
All functionality was available with keyboard only
All functionality was available on the laptop’s touch screen display
All functionality was available on an iPad using the touch display
All functionality was available on an iPad using a blue-tooth keyboard
All functionality was available on an Android phone using touch


Principle 3 Understandable

3.1 Readable

Results for the entire sample:

Outcome: Passed

Findings: Language is set on the HTML element

Results for the entire sample:

Outcome: Passed

Findings: Application is all the same language

Results for the entire sample:

Outcome: Failed

Findings: There are multiple uses of advanced vocabulary, which is not explained in text

Results for the entire sample:

Outcome: Failed

Findings: There are occurrences of abbreviations without explanations, recommended for a later improvement

Results for the entire sample:

Outcome: Failed

Findings: Site uses corporate and legal language throughout and the reading age of many pages is higher than that required to satisfy this criteria

Results for the entire sample:

Outcome: Failed

Findings: No pronunciations exist within the application

3.2 Predictable

Results for the entire sample:

Outcome: Passed

Findings: No controls initiate a change of context when they receive focus

Results for the entire sample:

Outcome: Passed

Findings: Inputs do not initiate a change of context, across the application

Results for the entire sample:

Outcome: Passed

Findings: Navigation persists across all pages and is consistent, navigation always remains in the same order and additionally is available though both the footer and the main navigation

Results for the entire sample:

Outcome: Passed

Findings: Download icon is used throughout the application, consistently
External link icon is used throughout the application, consistently
Buttons always have the same accessible name, such as “Menu” and “search button”
Links are both descriptive and specific

Results for the entire sample:

Outcome: Passed

Findings: In all instances, a user is required to action a button to initiate a change of context
No pop ups exists, the navigation menu is a flyout menu, but this requires activation
Links open in the same tab
Inputs for search and bin schedule require activating a button, to submit

3.3 Input Assistance

Results for the entire sample:Outcome: Not present

Findings: Not present on nelincs.gov.uk

Results for the entire sample:Outcome: Not present

Findings: Not present on nelincs.gov.uk

Results for the entire sample:Outcome: Not present

Findings: Not present on nelincs.gov.uk

Results for the entire sample:Outcome: Not present

Findings: Not present on nelincs.gov.uk

Results for the entire sample:

Outcome: Failed

Findings: Help tips do not exist

Results for the entire sample:

Outcome: Failed

Findings: Error prevention does not exist


Principle 4 Robust

4.1 Compatible

Results for the entire sample:

Outcome: Passed

Findings: HTML is implemented according to the spec and no violations are present, throughout the pages tested

Results for the entire sample:

Outcome: Passed

Findings: Semantic HTML has been used throughout and where widgets are implemented, such as accordions, they are marked up correctly, according to the ARIA Authoring Practices.
State is always communicated via aria-expanded
Components have an accessible name
The role is either implicitly stated with a semantic element or explicitly stated with ARIA

Results for the entire sample:

Outcome: Not present

Findings: No status messages or loading spinners/bars exist in the application


Sample of audited web pages


Related WCAG 2 resources