top of page

Accessibility Statement

This statement was last updated on 15th August 2025

 

What web accessibility is

Last updated: 15th August 2025

Bladecycle Solutions ("we", "our", "us") is committed to ensuring that our website, https://www.bladecyclesolutions.com, is accessible to the widest possible audience, regardless of technology or ability.

Our Commitment

We aim to conform to Web Content Accessibility Guidelines (WCAG) 2.1 AA standards across our site. We continuously improve usability and accessibility as part of our design and development process.

Measures We Take

We implement the following measures to ensure accessibility:

  • Accessibility embedded in our design system and development workflow

  • Semantic HTML with appropriate headings, landmarks, and lists

  • Keyboard navigability and visible focus states

  • Text alternatives for non-text content (alt text, labels)

  • Color contrast checks for text, UI components, and states

  • Resizable text and responsive layouts without loss of content or functionality

  • ARIA attributes where necessary (and only when semantic elements aren’t sufficient)

  • Captions/transcripts for audio/video where provided

  • Avoidance of content that flashes more than three times per second

  • Regular automated and manual testing (see “Assessment Approach”)

Compatibility with Browsers and Assistive Technology

Our goal is to support the current and previous major versions of:

  • Desktop: Chrome, Firefox, Safari, Edge

  • Mobile: iOS Safari, Android Chrome

  • Assistive technologies: Screen readers (NVDA, JAWS, VoiceOver), screen magnifiers, speech recognition software, and keyboard-only navigation

If you experience issues with a specific combination of browser/assistive tech, please let us know (see “Feedback & Contact”).

Technical Specifications

Accessibility of our website relies on the following technologies to work with the combination of web browser and any assistive technologies or plugins installed on your computer:

  • HTML, WAI-ARIA, CSS, JavaScript

These technologies are relied upon for conformance with WCAG 2.1.

Known Limitations

We are aware of the following areas that may not fully meet WCAG 2.1 AA:

  • [Example: Some legacy PDF downloads may not be fully tagged for screen readers.]

  • [Example: Occasional missing captions on older videos.]

Planned remediation:

  • If you find an issue not listed above, please contact us.

Third‑Party Content

Our site may integrate third‑party services or embedded content (e.g., maps, video players, forms). While we strive to ensure accessibility of these components, some may be outside our control. We will work with providers to address issues where possible and offer accessible alternatives upon request.

Feedback & Contact

We welcome your feedback on the accessibility of our website. If you encounter accessibility barriers, need content in an alternative format, or have suggestions:

We aim to respond within 2 business days and provide a resolution or timeline within 10 business days.

Requesting Alternative Formats

For documents or media that are not accessible, you can request:

  • Large print, braille, or audio

  • Accessible tagged PDF or HTML versions

  • Transcripts or captions for multimedia

Please include the web address (URL) of the content, your preferred format, and your contact details.

Enforcement Procedure (UK/EU Optional)

If you are unhappy with our response to your accessibility feedback:

  • UK: Contact the Equality Advisory and Support Service (EASS) for guidance on your rights under the Equality Act 2010.

  • EU: You may have the right to escalate to your national enforcement body for accessibility of public sector websites and mobile apps.

(Bladecycle Solutions is a private entity; references above are provided for user rights information.)

Assessment Approach

We assess the website’s accessibility by:

  • Automated testing (e.g., axe, Lighthouse) during CI/CD

  • Manual audits against WCAG 2.1 success criteria

  • Assistive technology spot‑checks (NVDA + Firefox, VoiceOver + Safari)

  • User testing with keyboard-only and screen reader users when feasible

Latest audit: [DD Month YYYY] — Conformance target: WCAG 2.1 AA

Preparation of This Accessibility Statement

This statement was prepared on [DD Month YYYY] and last reviewed on [DD Month YYYY].

Shortcuts & Best Practices Implemented

  • Skip‑to‑content link available on all pages

  • Logical tab order and focus management for modals/menus

  • No reliance on colour alone to convey meaning

  • Form fields have programmatic labels and error messaging with guidance

  • Touch targets sized to at least ~44 × 44 px where possible

Non‑Accessible Content (Regulatory Template Language)

Some content may be non‑accessible for the following reasons:

  1. Non‑compliance with WCAG 2.1: [Describe specific failures and pages]

  2. Disproportionate burden: [Explain if fixing specific legacy items would be unreasonably costly and provide a roadmap]

  3. Content not within the scope of applicable legislation: [e.g., third‑party documents not funded, developed, or under our control]

We will review and update this section as remediation progresses.

Contact for Accessibility & Data Protection

We are committed to continual improvement and welcome suggestions to enhance accessibility across our digital services.

bottom of page