Skip to content

Share your feedback on our website

We are making some improvements to our website and are looking for your feedback to help us understand more about your experience today. It will help us see how well it’s working and shape future changes.

Complete this short survey to let us know what you think – it should take no more than five minutes to complete. Thank you for your help.

A icon

Princh Accessibility Statement

This statement applies to content published on the Princh Web app.  The Princh web app is used for printing in the library.  Users can bring their own device and print out on the library printers using the Princh web app.

This website is run by Princh on behalf of Islington Council.  We want as many people as possible to be able to use this site.  You should be able to:

  • Change colours, contrast levels and fonts using browser or device settings
  • Zoom in up to 400% without the text spilling off the screen
  • Navigate most of the website using just a keyboard or speech recognition software
  • Listen to most of the website using a screen reader

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

How accessible this website is

We know some parts of this website are not fully accessible:

  • In order to print, users need to enter the printer code. The printer code input, underneath the text ‘Please select your printer by entering a printer-ID’ does not have an accessible name.On the initial print cart page, screen reader users should type in the printer ids to the controls which are identified as ‘spin box’.There are six controls, one for each number of the printer id.As soon as the correct printer code is entered the page moves to the file upload page.
  • After activating the settings button, screen reader users should immediately press the tab key once to listen to the settings dialog.
  • The colour contrast is not always sufficient.Partially sighted users may wish to turn on high contrast mode.
  • Partially sighted users navigating via keyboard may wish to use keyboard focus enhancements because it is not always easy to determine which control has the keyboard focus.
  • The accessible names and the visible names do not always match.Voice recognition software users who cannot use a mouse may need to navigate by voicing keyboard shortcuts such as ‘Press tab’ and ‘Press enter’.
  • Screen reader users and keyboard only users can only change the print colour via the settings button.
  • Users who have difficulty transcribing the printer ID may need to ask library staff for help.
  • When a dialog is closed, screen reader users are advised that the virtual focus (what the screen reading software is reading) is sent back to the beginning of the page.

         

Feedback and contact information

Feedback on our site

Please contact us if you find any problems not listed on this page, think we’re not meeting accessibility requirements or would like information in an alternative format like accessible print, large print, easy read, audio recording or Braille.

We’ll consider your request and get back to you in 10 working days.  Issues relating to the digital accessibility of the site will normally be looked into by the relevant service provider and the Web Services team of Islington Digital Services.  Requests for alternative format will normally be dealt with by the relevant service provider and the Communications team.

Contacting the service

If due to an accessibility problem with this site you are unable to find the information that you need or submit a request please contact the Library directly by emailing libraries@islington.gov.uk.

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

Islington 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 has been tested against the Web Content Accessibility Guidelines version 2.2 AA standard (WCAG 2.2 AA).

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.

Non-accessible content

Non-compliance with accessibility regulations

The content listed below is not accessible for the following reasons.

  • The words ‘Print cart’, ‘Payment’, and ‘Print., which are present on all pages do not have sufficient colour contrast against the background.  This could make the affected text difficult or impossible to see for some partially sighted users. WCAG success criteria: 1.4.3 Contrast Minimum
  • Light blue text is used throughout the site.  The blue text does not have sufficient colour contrast against the background.  Examples include the numbers ‘1’,’2’ and ‘3’ which appear on all pages, the words ‘Printer name’, ‘Location’, ‘Total pages’ and ‘Total price’, which appear on the file upload page.  This also affects the text ‘Page range and ‘No of selected pages’ in the print preview dialog.  This could make the affected text difficult or impossible to see for some partially sighted users.  WCAG success criteria: 1.4.3 Contrast Minimum
  • The text on many of the buttons does not have sufficient colour contrast against the background.  Examples include the ‘Accept’ ‘Preview’ and ‘Remove’ buttons on the settings dialog on the file upload page, and the ‘Continue’ button also on the file upload page, and the ‘Done’ and ‘Print another document’ on the print page.  This could make the affected text difficult or impossible to see for some partially sighted users.  WCAG success criteria: 1.4.3 Contrast Minimum
  • The ‘tick’ icons to indicate a completed stage do have alternative text.  However, the alternative text is not read out by screen reading software because the icons are not marked up as images.  As a result screen reader users who cannot see the screen may be confused as to which point in the process they have reached.  WCAG success criteria: 4.1.2 Name role value 1.1.1 Non text content.
  • The three stages ‘Print cart’, ‘Payment’, and ‘Print’ are not marked up as a list despite appearing to be a list to sighted users.  This makes the stage indicator more difficult to understand for screen reader users.  WCAG success criteria: 1.3.1 Info and relationships
  • As soon as the correct printer code is entered the page moves to the file upload page.  This is disorientating for screen reader users who cannot see the screen who will not anticipate being taken to a different page.  WCAG success criteria: 3.2.2 On input
  • The keyboard focus indicator ‘Accept’, ‘Preview’ and ‘Remove’ buttons on the settings dialog on the file upload page and the ‘Continue’ button also on the file upload page  does not have sufficient colour contrast against the button.  This also affects the ‘Done’ and ‘Print another document’ buttons on the print page.  Partially sighted keyboard only users may not be able to discern when the ‘Accept’, ‘Preview’ and ‘Remove’ buttons have the keyboard focus.  WCAG success criteria: 1.4.11 Non text contrast
  • When the ‘Preview’ and ‘Settings’ dialogs are closed on the file upload page the keyboard focus is not sent back to the invoking control (control which opened the dialogue). This can be disorientating for screen reader users who cannot see the screen.  WCAG success criteria: 2.4.3 Focus order              
  • The printer details and print job details which appear visually to be a table are not marked up programmatically as tables <table><th><td>. The printer details are on the file upload page. This makes the structure of the page more difficult to understand for screen reader users who cannot see the screen. WCAG success criteria: 1.3.1 Info and relationships
  • The black-and-white and colour print radio buttons are not marked up as radio buttons and are not in the tab index. This means that screen reader users who cannot see the screen will not be aware of the existence of the controls, and keyboard only users will not be able to change the setting from black-and-white to colour. This appears on the file upload page.  WCAG success criteria: 2.1.1 Keyboard, 4.1.2 Name role value
  • When the settings dialogue on the file upload page is opened, the keyboard focus is not immediately sent to the settings dialogue. This means that if a screen reader user who cannot see the screen opens the settings dialogue and then immediately presses the down arrow, instead of the dialogue contents being read aloud the page behind the content is read aloud.  WCAG success criteria: 2.4.3 Focus order
  • On the settings dialogue on the file upload page some of the settings controls do not have accessible names. The ‘Paper format’, ‘Colour’ and ‘Print on both sides’ controls do not have accessible names. Names do appear visually next to the controls (e.g. ‘Paper format’) but these are not marked up as labels and not programmatically associated with the controls themselves. This means the function of these controls on the settings dialogue will be difficult for screen reader users who cannot see the screen to discern.  WCAG success criteria: 4.1.2 Name role value
  • On the settings dialogue on the file upload page the buttons at the bottom of the page have different accessible names to visible names.  The accessible name for the remove button is ‘Delete document’, the accessible name for the ‘Preview’ button is ‘Show preview’ and the accessible name for the ‘Accept’ button is ‘Close’. The ‘Continue’ button, also on the file upload page has an accessible name of ‘Go to payment’. As a result, voice recognition users cannot activate the button by saying ‘click [control name]’ as they would normally expect to be able to do. WCAG success criteria: 2.5.3 Label in name
  • On the file upload page, the button ‘click here to select and upload file’ does not have an accessible name.  This is because the aria label, which should provide the accessible name, has been applied to the wrong tag. As a result, voice recognition users cannot activate the button by saying ‘click click here to select and upload a file’, as they would normally expect to be able to do.  WCAG success criteria: 2.5.3 Label in name
  • On the print cart screen the input to enter the printer ID does not have an accessible name. This means that screen reader users will not be aware what the purpose of this input is. Therefore, screen reader users who cannot see the screen are unlikely to be able to enter the printer ID and successfully print.  WCAG success criteria: 4.1.2 Name role value
  • The page title ‘print web app’ is the same for all pages. This is despite the fact that the content and purpose of each page is distinct. The page title is announced to screen reader users who cannot see the screen. When the page title is ambiguous the function of the page can be difficult to determine. WCAG success criteria: 2.4.2 Page titled
  • It is not possible to copy and paste the printer code into the ‘Please select your printer by entering a printer-ID’.  Some users with cognitive difficulties will have difficulties transcribing the printer number. WCAG success criteria: 3.3.8 Accessible authentication.

The accessibility problems in this website will be resolved by 31/12/2025 .

What we are doing to make this website more accessible

This website will be accessible by the end of 2025 .

Preparation of this accessibility statement

This statement was prepared on 01/12/2025. It was last reviewed on 01/12/2025

This website was last tested on 01/12/2025.  The test was carried out by Islington Council using a combination of manual and automated testing using assistive technology.

When this accessibility statement will next be reviewed on 01/12/2025.

Was this information helpful?



Data protection: We will handle your personal information in line with the Data Protection Act 1998 and in accordance with the council’s Fair Processing Notice.