Schappit Ltd (Piota Apps) Accessibility Statement ​

Accessibility Statement ​

Schappit Ltd (Piota Apps) Accessibility Statement ​

30 September 2024

Introduction

This accessibility statement covers:

  • Mobile applications (“apps”) from Schappit Ltd (trading as Piota Apps) on iOS or Android devices
  • Our website at https://www.piota.co.uk

We aim to make our apps and website accessible to as many people as possible. You should be able to:

  • Change colours, contrast levels, and fonts
  • Zoom in up to 300% without text spilling off the screen
  • Navigate most of the website using only a keyboard
  • Use speech recognition software to navigate the website
  • Listen to most of the content using a screen reader, including the latest versions of JAWS, NVDA, and VoiceOver

Schappit Ltd commits to making its website accessible according to the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Schappit develops technology and licences the ‘Piota’ app platform to third-party organisations. These organisations (our clients) control the content published on their apps. Schappit ensures that the technical features and functions embedded in the apps meet accessibility standards, while our clients are responsible for making the content accessible.

Using accessibility settings on your device

On a phone or tablet you can use the built-in device accessibility settings to make some parts of Piota’s apps more accessible:

AbilityNet has further advice to help you make your device easier to use if you have a disability.

How accessible are Piota’s apps?

We test the Piota platform to Web Content Accessibility Guidelines (WCAG) 2.1 on iOS and Android devices. 

WCAG 2.1 consists of 78 ‘success criteria’, of which 51 are the responsibility of Schappit as the technology provider. Criteria graded conformance level A are considered the most important, AA the next most important and AAA the least.

On the basis of an “80%+ True” test, our apps currently comply with 50 out of the 51 applicable criteria. By 80%+ True, we mean that the accessibility requirement identified in a success criterion is fulfilled on 80%+ pages in the app. See the optimisation work section below for a list of ongoing improvement work.

A full list of the app’s compliance vs success criteria is itemised in the appendix and a summary is shown here:

WCAG 2.2, containing new success criteria, is scheduled to be completed and published in 2023 Q3 (July, August, September). We will update this Accessibility Statement after publication.

Non-accessible technical features

Piota’s app platform is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliance listed below:

“Success Criterion 1.3.4 Orientation (AA): Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.”

At present the app is fixed in portrait mode on phones and tablets. Due to the page design structure that we have developed to date, the overall app is not user friendly to view in landscape orientation. Some elements such as PDF documents can be viewed in landscape orientation.

We intend to develop a landscape orientation version of the overall app design, however that is unlikely to be ready for release during 2023.

Ongoing optimisation work

We know some parts of apps supplied by us are not fully accessible. These include:

  • Additional support for image and video descriptions

  • Improvements to image gallery navigation

  • Improvements to accessible paging on long articles

  • Improvements to Android Voice Access labels

  • Keyboard support on iOS is available when Full Keyboard Access is not enabled

  • Additional support for landscape orientation

  • Improvements for VoiceOver and TalkBack descriptions, including bullet points

Non-accessible content

As explained above, content on the app is not within our control. We provide advice to clients about recommended good practice, however responsibility for implementation of accessible content belongs to them.

How accessible is Piota’s website?

Our website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard due to multiple non-compliances.

As a mobile app technology company we have focused most of our time and resources on improving the product for mobile app users. Keeping the website up to date has lagged and we are aware it has multiple accessibility failings – see for instance this report using WebAim’s website accessibility checker.

We intend to redesign/ rewrite the website before the end of 2023 on a more accessible platform and will incorporate accessibility upgrades to it then. We feel it would be a disproportionate burden to address accessibility issues before then as any changes would be swiftly superseded by the redesign/ rewrite.

How to report accessibility problems or give feedback

We are always looking to improve the accessibility of our apps. If you find any problems not listed on this page or you think we are not meeting accessibility requirements, please email support@piota.co.uk with details.

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

We aim to respond to all enquiries within 72 hours. If your message relates to a responsibility of the content creator, we will forward it to the app lead there and notify you that we have done so.

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).

Preparation of this accessibility statement 

This statement was prepared on 2 June 2023. It was last reviewed on 16 June 2023.

Our app platform and website were last tested in May 2023. The test was carried out internally.

We used the “80%+ True” method outlined above to decide on a sample of sections in our apps to test, concentrating testing on the most frequently used sections. Itemised results of this testing are included in the Appendix below.

Appendix: WCAG 2.1 success criteria 

Screenshot 2023-06-16 123144.png

Screenshot 2023-06-16 123814.png
Screenshot 2023-06-16 123859.png
Screenshot 2023-06-16 123953.png
Screenshot 2023-06-16 124303.png
Screenshot 2023-06-16 124356.png
Screenshot 2023-06-16 124439.png
 
 
 

Have any questions?

Feel free to contact us anytime - (+44) 01702 780051