Skip to main content
King's College London

Accessibility Statement for Staff Survey People Insight

We want as many people as possible to be able to use the Staff Survey, to find, read and understand the content.

Gathering staff feedback will allow the business to celebrate successes and identify any areas for improvements.  The survey tool is expected to help with action planning and will provide benchmarking against other institutions.  This Survey will enable the university to build a thriving staff community, as part of Strategy 2026, allowing the university to measure, report and improve staff engagement and satisfaction at all levels. 

Using Staff Survey

Staff Survey People Insight is run by King’s College London, and we want as many people as possible to be able to use it. For example, that means you should be able to: 

  • Zoom in up to 300% without the text spilling off the screen. 
  • Set the font size and preference within your browser (except for section headings). 
  • Navigate most of the website using just a keyboard. 
  • Skip to main content using keyboard navigation. 
  • Navigate most of the website using speech recognition software. 
  • Use screen readers such as JAWS and VoiceOver.
  • Collapse the course menu to reduce the clutter on the page and help you focus on the task at hand. 
  • Use a range of devices to access the Staff Survey e.g. mobile phone, tablet, laptop.

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

Technical information about Staff Survey accessibility

King’s College London is committed to making Staff Survey, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. We work to achieve and maintain WCAG 2.1 AA standards, but it is not always possible for all our content to be accessible.

The survey system is WCAG AA compliant. The reporting dashboard for the administrators is not yet fully AA compliant. People Insight are following WCAG 2.0 AA recommendations whenever possible. However, due to the wide range of available screen readers and their frequent changes and updates, different interpretation of standards and different methods available for browsing a web page within said readers, we are unable to guarantee error free operation in all available readers and their versions. Below are the following limitations of the reporting dashboard.

  • Some buttons do not have a text alternative. If a text alternative is not provided, buttons represented by images or icons may be unusable to visitors using assistive technology. In this case, the text alternative should describe what the button does or what users can expect to happen if they click it (not the visual features of the button). This doesn’t meet WCAG 2.1 success criterion 4.1.2.
  • Some images and vector images do not have a text alternative. Text alternatives are used to describe images to people who are unable to see them. This includes people who use screen readers to access the web. The text alternative should describe the image within the context of the page — letting visitors know what the image means and why it was included. This doesn’t meet WCAG 2.1 success criterion 1.1.1.
  • Various form fields are not labelled. Unclear labels make form-filling harder for everyone. A label may already be visible on the page — but to be accessible, that label needs to be associated with the form element in the HTML. This helps visitors using screen readers to understand what information is required, while also making it easier for speech-input users to control the form element. This doesn’t meet WCAG 2.1 success criterion 3.3.2.
  • The scrollable element is not keyboard accessible. Keyboard accessibility is an essential component of an accessible website. Visitors who can't easily use a mouse may instead use a keyboard (or keyboard alternative) for navigation. This includes people who are blind and people with motor disabilities. This doesn’t meet WCAG 2.1 success criterion 2.1.1.
  • The colour contrast does not meet minimum requirement. Text that is too faint can cause problems for users who are colour blind or have low vision. WCAG requires a minimum colour contrast ratio of at least 4.5:1 for normal text, and 3:1 for large text (18pt and above, or 14pt bold). This doesn’t meet WCAG 2.1 success criterion 1.4.3.
  • Field input error is not announced in full. Completing a poorly designed form can be a confusing experience for users with cognitive or visual impairments. Users need to understand what information is required and in what format. If the user inputs the wrong information, they need to be made aware of it with an error message that provides context and instructions. Marking a form error message as aria-atomic ensures that a screen reader will read out the error in full each time it occurs. If aria-atomic is missing, then only the corrected input will be read out. Without the error being announced in full in association with the input field, it may make it difficult for the user to complete the form successfully. This doesn’t meet WCAG 2.1 success criterion 3.3.1.
  • Visible label and accessible name do not match. Using two different names for a single page element can create a confusing user experience for assistive technology users. For example, speech-input users may have difficulty activating a control if the label displayed on-screen does not match its accessible name. This doesn’t meet WCAG 2.1 success criterion 2.5.3.
  • Element IDs are not unique. Sometimes it's important to know how different page elements fit together. Whereas sighted visitors may be able to get this information from the visual layout, visitors using screen readers rely on page elements being marked up correctly in the HTML. This doesn’t meet WCAG 2.1 success criterion 4.1.1.
  • Text is clipped when resized. Visitors with low vision may not be able to access information if text is clipped (cut off) when scaled up.

You can test this issue by:

  • zooming in on the page
  • increasing the font size in your browser settings

The options available for increasing the text size depend on your browser. This doesn’t meet WCAG 2.1 success criterion 1.4.4.

  • Inline frame without a text alternative. Inline frames (iframes) are used to insert content from other parts of the web. A title that summarizes the visual content will help screen reader users to understand the iframe's purpose on the page. ). This doesn’t meet WCAG 2.1 success criterion 4.1.2.
  • Link without a text alternative. Links represented by images or icons can be problematic for visitors who are blind or have low vision. The text alternative should describe the link's purpose — or what visitors can expect to find after they click it. This doesn’t meet WCAG 2.1 success criterion 2.4.4, 2.4.9 and 4.1.2.

What to do if you can’t access parts of the Staff Survey

If you need information on the Staff Survey in a different format like accessible PDF, large print, easy read, audio recording or braille email diversity@kcl.ac.uk.

We’ll consider your request and get back to you in 7 days.

Reporting accessibility problems with the Staff Survey

We’re always looking to improve the accessibility of the Staff Survey. If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements email diversity@kcl.ac.uk.

Escalation procedure

If you need to escalate your issue further, contact the Director of Equality, Diversity & Inclusion via diversity@kcl.ac.uk. You can expect an acknowledgement of your issue within 7 days and a full reply within 14 days. If your complaint raises complex issues that cannot be answered within 14 days we will keep you informed of progress until we can fully respond.

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

How we tested this website

This website was last tested on 25th May 2023. The test was carried out manually by Charlotte Tolson.

What we’re doing to improve accessibility

King’s College London has convened a college-wide action group to address the accessibility of its digital information and actions are currently being undertaken around:

  • Assessing, prioritising and improving the accessibility of the 100+ digital platforms in use at King’s and highest priority is being given to those holding student teaching materials;
  • Improving the accessibility of online teaching materials;
  • ensuring all future purchases or development of digital platforms are accessible;
  • ensuring that all future teaching materials being developed and uploaded are accessible.

This statement was prepared on 03/07/23. It was last updated on 03/07/23.