TEST YOUR HOME
TEST YOUR HOME

ACCESSIBILITY STATEMENT

About this website and statement

  • This accessibility statement applies to https://www.futurenowpeterborough.co.uk.
  • The site is managed by PECT and Peterborough City Council. It covers pages under this domain. It does not cover third‑party content or services embedded on our site (for example, maps, social media widgets, or external platforms), which are governed by their own accessibility statements.

How accessible this website is

You should be able to:

  • Change colours, contrast levels, and fonts using your browser or device settings
  • Zoom in up to 400% without loss of content or functionality
  • Navigate most of the website using a keyboard or speech recognition software
  • Listen to most of the website using a screen reader (including current versions of JAWS, NVDA, and VoiceOver)
  • Use the site on small screens without horizontal scrolling (reflow)
  • See a clear visible focus when tabbing through interactive elements.

We aim to use plain English and write content at an accessible reading level. Where documents are complex (for example, detailed reports), we can provide summaries or alternative formats on request.

Help with accessibility settings

To personalise your device or browser for better accessibility, visit:

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA, under the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, because we are continuously monitoring and improving the site. We are not currently aware of any accessibility issues.

Non-accessible content

We are not currently aware of any accessibility issues on this website. We conduct periodic audits and fix issues as they arise. If you find a problem that is not listed on this page, please let us know.

Feedback and contact information

If you need information on this website in a different format (for example, accessible PDF, large print, easy read, audio, braille, or BSL), or if you find any accessibility problems, contact us:

  • Email: info@pect.org.uk
  • Phone: 01733 568408 (Mon–Fri, 9am–5pm)
  • By post: PECT, Ham Lane House, Ham Lane, Peterborough PE2 5UU

Please include the page URL and tell us what format you need. We will consider your request and get back to you within 5 working days.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS): https://www.equalityadvisoryservice.com/

Technical information about this website’s accessibility

  • We aim to meet WCAG 2.2 AA. The site uses semantic HTML, ARIA where appropriate, responsive design, and accessible component patterns.
  • Supported environments: the latest two major versions of Chrome, Edge, Firefox, and Safari, plus current iOS and Android browsers.
  • Assistive technologies tested: NVDA with Firefox, JAWS with Chrome, and VoiceOver on iOS.

What we’re doing to improve accessibility

  • Continuous monitoring using automated checks on new and updated pages
  • Regular manual testing of key user journeys, including keyboard-only and screen reader use
  • Accessibility requirements embedded in our content and development workflows
  • Staff training on creating accessible web content and documents
  • Remediation targets:
    • Critical issues: within 4 weeks
    • Major issues: within 12 weeks
    • Minor/content issues: as part of routine updates

Preparation of this accessibility statement

  • This statement was prepared on 01/09/2025 and last reviewed on 01/09/2025.
  • Last test: 22/11/2025
  • Testing was carried out by contracted web developer.
  • We tested a representative sample of page templates and tasks, including the home page, key landing pages, content pages, forms, and media.

About testing: what it involves and who does it

  • What testing involves:
    • Automated checks: Tools like axe, WAVE, or Lighthouse to flag common issues (for example, missing alt text, colour contrast failures, heading structure).
    • Manual checks: Keyboard-only navigation, focus order and visibility, forms and error messaging, link purpose, page titles and landmarks, reflow/zoom at 400%, and operation without pointer gestures or motion.
    • Assistive tech checks: Quick passes with screen readers (NVDA/JAWS/VoiceOver), captions/transcripts for media, and reading order in PDFs.
    • Representative sampling: Choose pages that cover different templates and user journeys (home, content, search, forms, media, any third-party embeds).
  • Who normally does it:
    • Many organisations use a mix: trained internal staff for ongoing checks plus a third‑party specialist for periodic audits.
    • Third‑party auditors can provide an independent report, issue list mapped to WCAG criteria, and remediation guidance.
  • Qualifications or experience needed:
    • There is no legal requirement for a specific certification, but testers should understand WCAG 2.2 AA and how to use assistive technologies for testing.
    • Helpful credentials include IAAP Certified Professional in Accessibility Core Competencies (CPACC) or Web Accessibility Specialist (WAS), but they are not mandatory.
    • Practical experience with manual testing and knowledge of HTML/ARIA and UX is valuable.

Statement last reviewed 01/09/2025