Accessibility

This statement was last reviewed on 06/07/2023.

Piclo is committed to making its websites and web applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This accessibility statement currently applies to the web application at https://picloflex.com, including various key sub-domains that act as instances of our core web application. 

Compliance status

These web applications are partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliance and the exemptions listed below.

Please note that Piclo creates specialist software for end-users in specialist roles. We have direct, one-on-one relationships with our customer-base and have a clear understanding of their needs. The following therefore represents the parts of our web application experience where improving accessibility was strategically deprioritised to allow us to spend time in other, more targeted areas.

Where we are likely not compliant

The content listed below is non-accessible for the following reason(s):

Non-compliance with the accessibility regulations

Support for assistive technologies such as screen readers: 

(Related to guideline PERCEIVABLE: Create content that can be presented in different ways, including by assistive technologies, without losing meaning.)

  • Piclo’s web applications,  in many areas, technically support screen readers and other assistive technologies, however Piclo has yet to formally assess the quality of this implementation.
  • Please see the methodology outlined below as to how Piclo intends to continually identify and address accessibility issues.

User interface text content:

(Related to guideline UNDERSTANDABLE: Make text readable and understandable.)

  • Piclo doesn’t currently formalise copywriting standards for the user interface of Piclo Flex. As such, text-based content is likely harder to read in some areas.
  • Please see the methodology outlined below as to how Piclo intends to continually identify and address accessibility issues.

Miscellaneous, one-off technical issues:

(Related to various guidelines, for example OPERABLE: Make all content available from a keyboard.)

  • Piclo currently maintains a backlog of accessibility issues that it would like to address, including issues that have very narrow scope. These are addressed as and when capacity allows.
  • Please see the methodology outlined below as to how Piclo intends to continually identify and address accessibility issues.

Semantic heading hierarchy

(Related to various guidelines, for example OPERABLE: Provide ways to help users navigate, find content, and determine where they are..)

  • Piclo Flex currently makes use of heading elements in a way that sometimes skips a level, or is used inconsistently. This has the potential to confuse users who rely on assistive technologies.
  • Please see the methodology outlined below as to how Piclo intends to continually identify and address accessibility issues.
  • In addition to this, Piclo plans to spend time revising the page composition of Piclo Flex in order to address this more holistically over time. 

Disproportionate burden

Mapping and other third-party libraries

  • Piclo uses Mapbox to provide mapping functionality within its web applications. In some instances maps provide key functionality for end users and Piclo has no direct control of how accessible the experience is. 
  • Content and data Piclo presented via Mapbox can still be accessed in alternative formats, or by contacting Piclo’s Customer Support team.

Preparation of this accessibility statement

This statement was first prepared on 26/06/2023 after a 6 month period of review and subsequent action.

The next formal review period will occur between January–June 2024, though it should be noted that we conduct accessibility testing and quality assurance on an ongoing basis.

Methodology

Piclo uses a mix of manual and automated testing tools, and responsibility for the work is decentralised, with one team dedicated to building expertise, to establish good practices. Some of the tools we use to evaluate accessibility are as follows:

  • Lighthouse
  • Deque AXE (Chrome Extension) 
  • Wave (Chrome Extension)
  • Keyboard navigation checks (manual)
  • VoiceOver, prebuilt in to macOS (manual)
  • Various Figma plugins (Able, Stark)

Any issues discovered are documented, then added to a product backlog, with the discovering team tasked with ensuring solutions to any issues are delivered in a timely manner, as per their respective priorities. 

This ensures continuous improvement over time, and shared responsibility.

Feedback and contact information

We welcome and encourage feedback on the above from everyone in our community. If you would like to submit feedback please get in touch via support@picloflex.com.

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) or Equalities Commission for Northern Ireland (ECNI).