We want everyone who visits the Renfrewshire Council MyAccount website to feel welcome and find the experience rewarding, going above and beyond the The Public Sector Bodies Accessibility Regulations 2018.
This website is run by the Customer Technology team at Renfrewshire Council and is designed to be used by as many people as possible. The text should be clear and simple to understand. You should be able to:
To help us make the Renfrewshire Council MyAccount website a positive place for everyone, we've been using the Web Content Accessibility Guidelines (WCAG) 2.1. These guidelines explain how to make web content more accessible for people with disabilities, and user friendly for everyone.
The guidelines have three levels of accessibility (A, AA and AAA). We've chosen Level AA as the target for the Renfrewshire Council MyAccount website.
We're working hard to achieve our goal of Level AA accessibility, but we realise there are some areas that still need improving and we are only partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.
Our approach to accessibility is iterative, transparent and always under review to make a better experience for all of our users. Our current road map for improvements is an ongoing audit of MyAccount, its pages and forms - implementing changes towards a comprehensive inspection before October 2022.
The following information explains what areas are currently seen as non-accesible, how we've deemed it does not meet success criteria and what we're doing to make the appropriate changes.
Tables are used within forms and sections of the site to display and format data and information. We are working to make sure that these tables make use of appropriate mark-up to meet the success criteria for 1.3.1.
Some form elements and icons do not meet contrast requirements. We will undertake a design review to plan alterations that can correct the levels of contrast on these elements.
Some brand colours do not meet contrast requirements for AA standard. We will be doing a design audit of these areas and altering colours or font sizes as required.
Some of our system pages have changeable dynamic content which has still to be reviewed. Until this has been done we cannot commit to ensuring all content is operable via a keyboard.
We have updated our site time limit to 360 minutes which is the maximum our software allows. We will raise this accessibility issue with the software provider as it still does not comply with 2.2.1 - Timing Adjustable.
We need to review our building structure for forms to ensure there is a consistency for the ability to bypass blocks of content.
Two site pages: home page and contact us, do not appear to have a title that describes the topic and purpose. We will be working with our software supplier to make sure these outlier examples are fixed and behave like all other site pages.
Changeable dynamic content of Accounts and MyRequest pages still have to be reviewed to make sure the purpose of links are clear when read in context.
We need to review our building structure for forms to ensure there is a consistency for headings and labels describing topic and purpose for the user.
Keyboard focus is not always obvious or visible on navigation, call to actions and form elements - failing this accessibility criteria. We plan to review all focus states site wide to produce more consistent and clear results.
Some of the pages generated by the software do not appear to make full use of labels for components to comply with accessibility criteria. We will work with out software supplier to improve this.
Search and Select input elements used on system pages (All Services, MyRequests) need to be reviewed to ensure required labels and instructions are present. These areas are controlled by the software service provider.
We need to review our building structure for forms to ensure there is a consistency for the inclusion of labels and instructions.
System pages Accounts and MyRequests need to be reviewed with their changeable dynamic content to ensure error messages are provided to the user when appropriate.
Documents created in programmes and save in file formats such as PDF's to be used or accessed via our site are not always accessible. This can include but is not limited to missing text alternatives and missing document structure.
Non-HTML documents published before September 2018 do not need to be accessible - unless users need them to use a service.
Addressing some accessibility problems can be considered a disproportionate burden due to resources and costs involved to resolve. This would be taken into consideration if there are plans for future development work that would address issues as part of the project.