NOTICE: Isolation payment applications now open
Read more

Accessibility Statement

This accessibility statement applies to https://www.powys.gov.uk, run by Powys County Council.

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 per cent 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.

We've designed this website with features that make it easier to use by everyone, including those with visual, auditory, physical, speech, cognitive, or neurological disabilities. We aim to reach the level AA of the Web Content Accessibility Guidelines (WCAG) 2.1. These are the international standard for accessible websites and content.

On this page:

Listen to this site using Browsealoud

Websites associated with Powys County Council

How accessible is this website?

Feedback and Contact information

Enforcement procedure

Technical information about this website's accessibility

Disproportionate burden

Content that's not within the scope of the regulations

How we tested this website

What we're doing to improve accessibility

Accessibility Roadmap

Last updated
 


Listen to this site using Browsealoud

You can listen to the contents of this website being read aloud to you using the Browsealoud widget on the site.

Follow these steps:

  • To activate Browsealoud, click on the widget Browsealoud logo at the bottom right of your screen.
  • This will open a toolbar on the page displaying different options.
  • You can move the navigation bar by selecting the arrows and dragging the bar to where you would like it. You can use Browsealoud for the following:
    • Text-to-speech
    • Spoken and written translation
    • Text magnification
    • MP3 generation
    • Screen mask
    • Web page simplifier
    • Customisable options

For further help and support on how to use Browsealoud, click on the question mark in the Browsealoud toolbar.

There are also a number of customisation options for your browser and device that could help you use this website and other websites more effectively.

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

 

Websites associated with Powys County Council

There are other websites associated with Powys County Council, which may be linked to from this website. This Accessibility Statement does not cover those websites. Please see each individual website for their Accessibility Statements.

 

How accessible is this website?

We know some parts of this website aren't fully accessible, for example:

  • many older PDF documents aren't fully accessible to screen reader software
  • some pages show a Google map which screen reader users and keyboard users can find difficult to use

 

Feedback and Contact information

We're always looking to improve the accessibility of this website.

If you have an accessibility query including:

  • if you are experiencing issues with accessing information or using the website
  • if you find an accessibility problem not listed on this statement
  • if you have positive feedback on the accessibility considerations made.

Please contact:

Digital Access Team
Customer Services
email: website@powys.gov.uk
Telephone: 01597 826000

We also provide a free of charge service via our webchat facility​ where you can talk to us online.
 

Alternative formats

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

We'll consider your request and get back to you as soon as we can.

If you cannot view the map on our 'contact us' page, please call or email us for directions.
 

Contacting us by phone or visiting us in person

Our offices have audio induction loops, or if you contact us before your visit, we can arrange a British Sign Language (BSL) interpreter.

We provide a text relay service (Relay UK) for people who are D/deaf, hearing impaired or have a speech impediment.

Follow this link for Text Relay Instructions

Note: Relay UK costs an extra 1p per minute to use, in addition to standard call charges, and can connect with us using the app or a textphone.

We also provide a free of charge service via our webchat facility​ where you can talk to us online.

Find out how to contact us on this page:  www.powys.gov.uk/contact

 

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the 'accessibility regulations'). If you're not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
 

Technical information about this website's accessibility

Powys County 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

  • A small number of images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
    These images relate to our Live Chat button which is provided by a 3rd party. We have asked the 3rd party to resolve this issue and have a support ticket pending.
    When we publish new content, we'll make sure our use of images meets accessibility standards.
  • Some of our forms do not contain submit buttons This technically fails WCAG 2.1 success criterion 3.2.2 However, because in these instances we are using a form template to display, and sometimes search through, data from a database, a submit button is not required.
  • On fewer than 5 pages, a label in the document fragment do not point to valid IDs. This fails WCAG 2.1 success criterion 1.3.1. This issue is contained within a 'widget' supplied by a 3rd party. We have contacted the 3rd party and requested a resolution.
  • Some of our tables lack a 'scope' attribute. This fails WCAG 2.1 success criterion 1.3.1. Our Content Management System does not currently allow us to set this attribute. We have contacted our supplier and requested this feature be added.
  • Our website currently does not allow users to quickly skip to content. This fails WCAG 2.1 success criterion 2.4.1. We have contacted our supplier and requested a fix for this.
  • All our webpages contain duplicate IDs.  This fails WCAG 2.1 success criterion 4.1.1
    This is a result of Browse aloud inclusion. We have contacted our supplier and requested a fix for this.  
  • With some of our forms it isn't possible to Identify the purpose of fields programmatically. This fails WCAG 2.1 success criterion 1.3.5. We have contacted our supplier and requested a fix for this.
  • Some of our PDF documents published before 23 September 2018 are essential to providing our services and do not meet the accessibility standards for various reasons (see the list below). We plan to identify the 10% most accessed documents and work with our services to fix any problems.
  • Approximately 985 PDF documents published after 23 Sept 2018 do not meet the accessibility standards for various reasons (see the list below).
    We plan to address these issues for approx. 420 of these documents by April 2021.
    The remaining documents relate to our Local Development Plan, which is covered under the section on Disproportionate Burden below.

Some of our PDF documents don't currently meet WCAG requirements because:

  • Ensure labels in the document fragment point to valid IDs (WCAG A 1.3.1)
  • Ensure the first heading in a PDF is a H1 (WCAG A 1.3.1)
  • Ensure PDF headings follow a logical order (WCAG A 1.3.1)
  • Ensure text has sufficient contrast (WCAG AA 1.4.3)
  • Ensure PDFs are machine readable (WCAG A 1.1.1)
  • Ensure long PDFs use bookmarks to aid navigation (WCAG AA 2.4.5)
  • Improve weak PDF titles (WCAG A 2.4.2)
  • Define a title for all PDFs (WCAG A 2.4.2)
  • Fix untagged PDFs (WCAG A 1.3.1)
  • Ensure PDFs specify a default language (WCAG A 3.1.1)
  • Specify headings for every PDF (WCAG A 1.3.1)

 

Disproportionate burden

PDF documents published after 23 September 2018

There are approximately 985 PDF documents published after 23 September 2018 which do not meet the accessibility regulations for various reasons. 557 of these relate to our Local Development Plan.

We've assessed the cost of fixing the issues relating to the 557 LDP documents. We believe that doing so now, for both English and Welsh documents, would be a disproportionate burden within the meaning of the accessibility regulations. We will periodically review this decision and make sure that PDF documents for the new LDP due in 2026 meet the accessibility standards.

PDF documents published before 23 September 2018 which are essential to providing our services

There are over 2,500 PDF documents published before 23 September 2018. Some of them are essential to providing our services and do not meet the accessibility regulations for various reasons.

We've assessed the cost of identifying and fixing these issues. We believe that doing so now, for both English and Welsh documents, would be a disproportionate burden within the meaning of the accessibility regulations. However, we plan to ensure that the 10% most accessed documents meet the accessibility regulations by September 2021 and are committed to providing accessible versions of remaining documents on request.

We have also started an exercise to review this document list and remove any documents that are no longer relevant.

When we publish new PDF documents, we'll make sure they meet the accessibility standards.

 

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

PDFs and other documents

Most of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they're accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).

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. For example, we do not plan to fix old PDF newsletters, posters or campaign materials that might still be published and accessed through our website.

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

Many of our policy documents are not written in plain English / Welsh. These types of documents are exempt from the regulations as they are not 'needed for active administrative processes relating to the tasks performed', so we do not currently have any plans to make them accessible.

Live video

Live video streams do not have captions. This fails WCAG 2.1 success criterion 1.2.4 (captions - live).

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

Pre-recorded videos published before 23 September 2020

Most of our pre-recorded videos published before 23 September 2020 do not include captions. This doesn't meet WCAG 2.1 success criteria 1.2.2 Captions (Pre-recorded). We may not add captions to these videos because pre-recorded video published before 23 September 2020 is exempt from meeting the accessibility regulations.

Some pre-recorded videos published before 23 September 2020 may require, but don't include, audio description. This doesn't meet WCAG 2.1 success criteria 1.2.5 Audio Description (Pre-recorded). We will not add audio description to these videos because pre-recorded video published before 23 September 2020 is exempt from meeting the accessibility regulations.

Any pre-recorded video content we publish after 23 September 2020 will meet accessibility standards.

 

How we tested this website

Tests were carried out manually by our Digital Access Team as well as using automated site-wide testing software from Silktide: https://silktide.com/solutions/accessibility/

We tested:

We tested 3000 English web pages and 2,987 English pdf documents. We then applied identical fixes to both English and Welsh web pages and documents as necessary.

This website is subsequently tested every 5 days.

 

What we're doing to improve accessibility

We're doing our best to try fix the issues outlined above. We continually monitor the accessibility compliance of our site and improving our site is part of the Digital Access Teams' daily work.

  • Appropriate staff have received accessibility training and are working with our service areas to raise awareness of the need to meet the accessibility regulations.
  • We have controls in place to make sure that all new content published on the website complies with the accessibility regulations.
  • We run an automated, site-wide accessibility check every 5 days and work with service area staff to fix any issues.

 

Accessibility Roadmap

  • March 2020  -        We performed a manual indicative accessibility audit of website content and pdf documents.
  • April 2020  -           We put controls in place to ensure all our new website content and documents comply with Accessibility Regulations.
  • April 2020  -           We procured and implemented an automated, site-wide accessibility testing tool.  Silktide (https://silktide.com/solutions/accessibility/)
  • May 2020  -            We began remedial work on web pages and pdf documents
  • August 2020  -       We contacted the 3rd party supplier of a widget used by our website and requested a resolution of this issue: 'a label in the document fragment do not point to valid IDs. This will ensure we comply with WCAG 2.1 success criterion 1.3.1.
  • August 2020  -       We contacted the 3rd party supplier of our Content Management System and requested a resolution of this issue: 'pages containing tables lack a 'scope' attribute.' This will ensure we comply with WCAG 2.1 success criterion 1.3.1.
  • August 2020  -       We contacted the 3rd party supplier of our Content Management System and requested a resolution of this issue: 'skip to content WCAG success criterion 2.4.1'. A fix for this is planned before the end of September.
  • August 2020  -       We contacted the 3rd party supplier of our Content Management System and requested a resolution of this issue: 'Fix duplicate IDs ' WCAG 2.1 success criterion 4.1.1'.  A fix for this is planned before the end of September.
  • August 2020  -       We contacted the 3rd party supplier of our Content Management System and requested a resolution of this issue: 'Identify the purpose of fields programmatically. WCAG 2.1 success criterion 1.3.5'.
  • August 2020  -       We contacted the 3rd party supplier of our Content Management System and requested a resolution of this issue with our 'Live Chat' button (support ticket pending): 'Specify alternative text for images inside links WCAG 2.1 success criterion 1.1.1 (non-text content)'. A fix for this is planned before the end of December.
  • October 2020  -    We plan for text alternatives to be in place for all images to ensure we comply with WCAG 2.1 success criterion 1.1.1 (non-text content).
  • April 2021  -          We plan to ensure that approximately 420 English and Welsh PDF documents published after 23 Sept 2018 meet the following accessibility standards currently showing as issues in our website accessibility audit:
  • September 2021  -  Some of our PDFs and Word documents published before 23 September 2018 are essential to providing our services and do not meet the accessibility regulations for various reasons. We plan to ensure that at least 10% most accessed documents meet the accessibility regulations.

 

This statement was prepared on 18 September 2020. It was last updated on 1 October 2020.

 

If you have any ideas or suggestions to help improve the site then please contact us.

Share this page

Facebook icon Twitter icon Email icon

Print

Print icon