This accessibility statement applies to Heycentric Income Manager.

Heycentric Income Manager is a third-party application.

Heycentric Income Manager is provided by Heycentric to King’s College London to provide a powerful suite of payment handling modules all of which feed into a comprehensive Income Management component. This provides a highly effective overview of an organisation’s cash position, assisting in both tactical and strategic decision making by giving a real-time view of the cash position at any given time.

Application version 3.1. Publication date April 2026

Using the application

We want as many people as possible to be able to use, read and understand the content of Heycentric.

This means that you should be able to:

• change colours, contrast levels and fonts
• zoom in up to 300% without the text spilling off the screen
• navigate the application using just a keyboard
• navigate the application using speech recognition software
  • listen to most of the application using a screen reader

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

How accessible this application is 

We know some parts of HeyCentric are not fully accessible:

• Screen reader users may find that some workflows do not announce content changes, form errors, or modal dialogs correctly. The application has not been fully tested with screen readers or speech recognition software.
• Keyboard-only users may encounter inconsistent behaviour, particularly within complex forms and data tables where some functionality may not be fully operable using a keyboard.
• At higher zoom levels (200–300%), data-heavy pages such as tables and reports may truncate content or require horizontal scrolling, particularly on smaller screens.
• Some dynamic content, including inline validation messages and notification banners, may not be automatically announced to assistive technology users.

Feedback and contact information

If you find any problems not listed in this statement or think we’re not meeting accessibility requirements, email diversity@kcl.ac.uk.

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

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

If you need to escalate your issue further, please contact the Director of Culture and Talent 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.

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

King’s College London is committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This application is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. 

Non-accessible content

HeyCentric is provided by a third party supplier which means that some aspects of accessibility are outside our immediate control.

We know that some parts of this service are not fully accessible. Below are the issues we are aware of, the standards they fail against, where they occur, and suggested assistive technologies that may help while we work to improve the service.

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

1. Screen reader announcements and assistive technology support

• Accessibility issue: Keyboard-only users may encounter inconsistent behaviour, particularly within complex forms and data tables where some functionality may not be fully operable using a keyboard.
• WCAG 2.2 success criteria not met: 
  • 2.1.1 – Keyboard (A), 2.1.2 – No Keyboard Trap (A)
  • 2.4.3 – Focus Order (A)
  • 2.4.7 – Focus Visible (AA)
• Impacted areas:
  • Complex or multi-step forms
  • Data tables (sorting, filtering, inline actions)
  • Interactive controls embedded within grids or reports.
• Assistive technologies and workarounds
  • Use keyboard navigation (Tab, Shift+Tab, Enter, arrow keys)
  • Use browser accessibility tools or extensions (e.g. Accessibility Insights, axe DevTools)
  • Keyboard navigation allows users to operate content without a mouse and is essential for many users with disabilities
• Limitations: Some controls may remain inaccessible where keyboard support has not been fully implemented.
• Planned fix: We are working to improve keyboard accessibility across complex components as part of ongoing UI improvements. A timeline has not yet been confirmed.

2. Keyboard navigation limitations

• Accessibility issue: Keyboard-only users may encounter inconsistent behaviour, particularly within complex forms and data tables where some functionality may not be fully operable using a keyboard.
• WCAG 2.2 success criteria not met: 
  • 2.1.1 – Keyboard (A)
  • 2.1.2 – No Keyboard Trap (A)
  • 2.4.3 – Focus Order (A)
  • 2.4.7 – Focus Visible (AA)
• Impacted areas: 
  • Complex or multi-step forms
  • Data tables (sorting, filtering, inline actions)
  • Interactive controls embedded within grids or reports
• Assistive technologies and workarounds
  • Use keyboard navigation (Tab, Shift+Tab, Enter, arrow keys)
  • Use browser accessibility tools or extensions (e.g. Accessibility Insights, axe DevTools)
  • Keyboard navigation allows users to operate content without a mouse and is essential for many users with disabilities
• Limitations: Some controls may remain inaccessible where keyboard support has not been fully implemented.
• Planned fix: We are working to improve keyboard accessibility across complex components as part of ongoing UI improvements. A timeline has not yet been confirmed.

3. Zoom, reflow, and responsive layout issues

• Accessibility issue: At higher zoom levels (200–300%), data-heavy pages such as tables and reports may truncate content or require horizontal scrolling, particularly on smaller screens. 
• WCAG 2.2 success criteria not met:
  • 1.4.10 – Reflow (AA)
  • 1.4.4 – Resize Text (AA)
• Impacted areas:
  • Data tables
  • Reporting dashboards
  • Data-heavy screens
• Assistive technologies and workarounds
  • Built-in browser zoom
  • Windows Magnifier / macOS Zoom
  • Browser extensions such as Page Zoom or Helperbird
  • Screen magnification tools can enlarge content and improve readability. 
• Limitations: Users may still need to scroll horizontally where layouts are not fully responsive.
• Planned fix: We plan to improve responsive design and content reflow behaviour in future updates. A timeline is not yet confirmed.

4. Dynamic content not announced to assistive technologies

• Accessibility issue: Some dynamic content, including inline validation messages and notification banners, may not be automatically announced to assistive technology users.
• WCAG 2.2 success criteria not met:
  • 4.1.3 – Status Messages (AA)
  • 3.3.1 – Error Identification (A)
• Impacted areas: 
  • Inline validation messages
  • Notification banners / alerts
  • Success, warning, and error messages
• Assistive technologies and workarounds
  • Screen readers such as NVDA, JAWS, VoiceOver, and TalkBack
  • These tools can announce dynamic updates when content is implemented correctly using accessibility techniques such as ARIA live regions.
• Limitations: Where content is not implemented correctly, users may need to manually navigate the page to discover updates. 
• Planned fix: We plan to improve support for dynamic content announcements in a future release. A timeline is not yet confirmed.

Disproportionate burden

​​At this time, we have not made any disproportionate burden claims. ​

Content that’s not within the scope of the accessibility regulations

PDFs and other documents

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we do not plan to fix ​[example of non-essential document].​

Any new PDFs or Word documents we publish will meet accessibility standards.

Live video

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

What we are doing to improve accessibility

King’s College London are working with HeyCentric to fix or provide alternatives for all issues that are we are made aware of or are identified by our internal testing and auditing processes.

Preparation of this accessibility statement

HeyCentric Income Manager was last tested in July 2025. The test was carried out by Heycentric using automated accessibility testing tools. Manual assistive technology testing has not yet been completed for Income Manager.

HeyCentric Payments Portal was last tested in March 2026. The test was carried out using automated accessibility testing tools and complete manual assistive technology testing, including screen reader and keyboard-only verification. All end-user facing payment workflows were tested.

While we are working to resolve these issues, users may find assistive technologies such as screen readers, system magnification tools, and keyboard navigation helpful.

However, due to the current limitations of the service, some functionality may not work as expected even when using these tools.

The application has not been formally verified with screen readers or speech recognition software. Only our end user facing applications have been testes with assistive technology.

This statement was prepared on 19/06/2026.