Accessibility Statement for CoreStream GRC Platform

This is an accessibility statement from CoreStream GRC.

Measures to Support Accessibility

CoreStream GRC takes the following measures to ensure accessibility of the CoreStream GRC Platform:

  • Include accessibility as part of our mission statement.
  • Assign clear accessibility goals and responsibilities.
  • Employ formal accessibility quality assurance methods.
  • Schedule regular professional audits to measure and monitor accessibility.

Conformance Status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. CoreStream GRC Platform is partially conformant with WCAG 2.2 Level AA. Partially conformant means that some parts of the content do not fully meet the accessibility standard.

Feedback

We welcome your feedback on the accessibility of the CoreStream GRC Platform. Please let us know if you encounter accessibility barriers:

  • Phone: +44 207 100 4378
  • Email: support@corestream.co.uk
  • Postal Address: 20 Grosvenor Pl, London, SW1X 7HN, UK
    We aim to respond to feedback within one business day.

Compatibility with Browsers and Assistive Technology

CoreStream GRC Platform is designed to be compatible with the following assistive technologies:

  • Chrome 138 with JAWS desktop screen reader on Windows
  • Edge 138 with NVDA desktop screen reader on Windows
  • Safari 18 with VoiceOver desktop screen reader on macOS
  • Safari 18 with VoiceOver mobile screen reader on iOS
  • Chrome 138 with TalkBack mobile screen reader on Android
  • Chrome 138 with Windows Magnifier screen magnifier on Windows
  • Chrome 138 with Dragon NaturallySpeaking speech recognition on Windows

CoreStream GRC Platform is not compatible with:

  • Browsers older than three major versions may not fully support accessibility features.

Technical Specifications

Accessibility of CoreStream GRC Platform relies on the following technologies to work with your web browser and any assistive technologies or plugins installed on your device:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript
  • SVG
    These technologies are necessary for conformance with the accessibility standards used.

Limitations and Alternatives

Despite our best efforts to ensure accessibility, some limitations may exist, particularly in less commonly used features. Below is a description of known limitations and potential solutions. Please contact us if you encounter an issue not listed below.

Known limitations for CoreStream GRC Platform:

  • Text within the graphs on the Dashboard page can be obscured and may be hard to read when zooming text only to 200%. This fails WCAG 2.2 success criterion 1.4.4 (Resize Text). We plan to resolve this in the next release.
  • Some checkboxes in an unselected state within the ‘Column Selection’ pop-up—accessed via the ‘Toggle Side Panel’ button in the grid header—have a contrast ratio of only 1.6:1. This fails WCAG 2.2 success criterion 1.4.11 (Non-Text Contrast). We plan to resolve this in the next release.
  • Some page content may be obscured, missing, or not function as expected when zooming to 400%. This fails WCAG 2.2 success criterion 1.4.10 (Reflow). We plan to resolve this by the end of financial year.
  • Text editors across the website cannot be accessed using a keyboard through tabbing. Information to access the controls using a shortcut are not provided on the page accessible by keyboard. The text editor controls can be accessed using ALT+F10. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard). We plan to resolve this in the next release.
  • When using Android TalkBack, the fullscreen button for the graphs on the dashboard does not function as intended. Activating the button does not open the content in fullscreen mode. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard). We plan to resolve this in the future release. 
  • This website includes a time limit that may result in users being timed out. Currently, there is no option to pause, extend, or disable this timeout. This fails WCAG 2.2 success criterion 2.2.1 (Timing Adjustable). We plan to resolve this in the future release. 
  • Some pages may only be navigated through the navigation bar which may not always be accessible to the user. Alternative ways to navigate to selected pages are not present. This fails WCAG 2.2 success criterion 2.4.5 (Multiple Ways). We plan to resolve this in the next release.
  • When navigating the graphs on the Dashboard Overview using keyboard tabbing, slider elements do not announce any content when focused by a screen reader other than Voice Over. Additionally, screen readers other than Voice Over are unable to interact with these sliders during navigation. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this in the future release. 
  • When viewing a graph in fullscreen mode from the Dashboard Overview page, the graph key elements can receive focus via a screen reader, but no content is announced, resulting in empty tab stops. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this in the future release. 
  • Users navigating with Dragon Naturally Speaking (speech recognition software) are unable to interact with dropdown fields and cannot effectively access or control table content that can be found across multiple pages. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this by the end of financial year.
  • Users navigating with Dragon Naturally Speaking are unable to interact with file upload features using voice commands. This is a known issue with the software. Users may need to rely on manual commands such as using the “mouse grid” feature to access file upload inputs. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). On both iOS VoiceOver and Android TalkBack, dropdown menu items can receive focus even when the dropdown has not been expanded. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this by the end of financial year.
  • Visually hidden buttons within the text editor can receive focus by Android TalkBack, despite not being visually present. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this in the future release. 
  • When viewing a graph from the Dashboard Overview page in fullscreen mode, the graph cannot receive focus using iOS VoiceOver, rendering its content inaccessible to screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this in the future release. 
  • The table sort and options buttons feature similar accessible names. This results in the same text being announced by screen readers in a row. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this in the future release. 

What We’re Doing to Improve Accessibility

We are committed to enhancing the accessibility of the CoreStream GRC Platform as part of our bi-monthly release schedule. During each release cycle, we focus on resolving specific accessibility issues, such as form fields, buttons, and keyboard navigation.
Following each major release, we will conduct an external audit to validate accessibility improvements.

Assessment Approach

CoreStream GRC assesses the accessibility of its platform using the following methods:

  • External Evaluation: A formal accessibility audit was conducted by Zoonou, using WCAG-EM to define the test scope and approach.

Formal Approval of This Accessibility Statement

This Accessibility Statement is approved by:

CoreStream GRC
Matthew Eddolls
Commercial Director

Date

This statement was updated on July 25th, 2025, using the W3C Accessibility Statement Generator Tool.

The platform was last tested on July 25, 2025 by Zoonou.