Application Accessibility Statement

We believe that every voice has the power to change the working world. That’s why we’re committed to making our software easily usable by everyone, regardless of disability.


For a start, wherever you are within the Hive platform, you should always be able to:

  • Zoom in up to 200% without the text spilling off the screen
  • Navigate most of the software using just a keyboard
  • Listen to most of the content using a screen reader (including JAWS, NVDA and VoiceOver).


In tandem with the platform’s functionality changes, we’re constantly updating our existing interfaces to be more accessible, and all new interfaces are built with:

  • Colour contrast ratios of at least 4.5:1 for normal text and 3:1 for large text
  • Left-aligned content
  • No reliance on colour alone to convey information
  • Minimum 13px text size
  • Linear, predictable content hierarchy
  • No time-based media
  • Signposting and messaging to help users avoid and correct mistakes.


A note about content: While we always aim to communicate as clearly as possible, Hive is a self-service platform and we cannot control all content which is input into our system (e.g. question wording). If you have difficulty understanding any custom content in Hive, please contact the Hive administrator within your organisation.

Hive’s commitment to software accessibility

We’re committed to continue to improve the accessibility of our software. We’ve partnered with a number of charities and public sector organisations to frequently assess the overall accessibility of our product offering, and we aim to make improvements in a timely manner, in conjunction with our feature development.

Reporting accessibility problems with our software

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please contact our Product Team at

Escalation procedure

If you raise an issue with us, we’ll do everything we can to resolve it. But if you’re still not happy with our response, you can take it further by contacting the Equality Advisory and Support Service (EASS).

Preparation of this accessibility statement (version 1.2)

This statement was prepared on 05/05/2021. It was last reviewed and updated on 21/03/2022.

Our feedback software was audited on 21/02/2020. The audit was carried out by our Product and Engineering teams, in partnership with Guide Dogs for the Blind’s Assistive Technology Team.

Employee-feedback collection-areas

This section applies to the following feedback collection-areas of Hive software:

  • Hive Surveying
  • Hive Fives
  • Hive Open Door
  • Employee Homepage
  • Hive Messenger

WAI-ARIA 1.1 compliance status

Our global component library follows WAI-ARIA 1.1 standardswith no known exceptions.
In addition to these standards, we implement focus and keyboard interactions for components that need them, for example:
  • Buttons respond to ‘Enter’ and ‘Space’ keys.
  • Focus is trapped within any dialog box when it’s open.
  • Pressing ↑ ↓ → ← moves focus between Tabs.
  • Tabbing implements all the interactions a component will need to be fully accessible.
  • This is used by Buttons, Checkboxes and Form inputs.
  • Optimised compatibility for current user agents, including assistive technologies.

WCAG 2.1 compliance status

Our software is compliant with the Web Content Accessibility Guidelines version 2.1 AAwith no known exceptions.

Administrator and Manager console

This section applies to the following areas of Hive that require an administrator or manager login:

  • Survey builder
  • Survey results
  • Heatmaps
  • Hive Open Door
  • Hive Fives
  • Hive Messenger
  • User section
  • Settings
  • Dashboard
  • Exports


Known issues:


  • Survey results:
    • Some items have dropdown options indicated by a down arrow icon. In certain areas these aren’t indicated with screen readers and can’t be activated with the keyboard.
    • Word clouds can’t be read by screen readers and can be difficult to interpret when using screen magnification.
    • Survey detail icons aren’t read by screen readers.
    • Survey detail content isn’t consistently ordered in a predictable hierarchy.
    • Date-filter fields aren’t labelled, and if you edit one and then arrow down, you have to travel through the date picker.
    • The columnar information layout may be difficult to navigate when magnifying the screen.


  • Mobile navigation
    • Submenus aren’t indicated or reported with screen readers.


  • Buttons
    • Certain components use icon-only buttons, which some users may have difficulty interpreting.


  • Navigation
    • Icon-only navigation may be difficult to interpret for some users.
    • There is some inconsistency with screen-reader labelling depending on which area of the platform the user is in.


  • Colour
    • Some areas of contrast colour don’t work well with the majority of inverse colour options that are available in Windows 10.


  • Third-party service-providers
    • We use Pendo to create and manage in-app guidance. There are some accessibility issues with Pendo guides that affect their compatibility with screen readers. Pendo is aware of these issues and working to resolve them as part of their own accessibility improvements.