Skip to content
Last updated

This accessibility statement applies to the Creditsafe Connect API Documentation Portal at:

  • https://doc.creditsafe.com

1. Introduction

Creditsafe is committed to making this documentation portal accessible in line with the accessibility requirements that apply under the European Accessibility Act (EAA), EN 301 549, and WCAG 2.1 Level AA.

We also use WCAG 2.2 checks as part of continuous improvement.

2. Compliance Status

This website is partially compliant with WCAG 2.1 AA due to the items listed in section 5.

3. Scope

This statement covers public-facing content and components in this portal, including:

  • Documentation pages in the Connect API catalog
  • Shared layout and navigation elements
  • Public UI scripts and styling used by the portal

This statement does not apply to:

  • Internal-only tooling and administrative interfaces that are not publicly published
  • Third-party services or external platforms outside our direct implementation control

4. Compatibility with Browsers and Assistive Technology

This portal is designed to be compatible with commonly used modern browsers and assistive technologies, including:

  • Current versions of Chrome, Edge, Firefox, and Safari
  • Screen readers and accessibility features such as NVDA, VoiceOver, and built-in operating system accessibility tools

5. Technical Specifications

The accessibility of this portal relies on the following technologies:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript

6. What We Have Improved (Q1 2026)

During Q1 2026, we completed a remediation programme covering previously identified high-priority defects, including:

  • Added accessible text summaries for Mermaid flow diagrams across public-facing product documentation
  • Improved color contrast for changelog type styling in shared theme styles
  • Improved changelog widget accessibility, including keyboard support, focus handling, reduced-motion behavior, and dialog semantics
  • Updated quick-start guidance and added keyboard-accessible links for full-size instructional images
  • Improved heading readability and consistency in key landing/entry pages

7. Known Accessibility Limitations

We continue to monitor and improve the following areas:

  • Third-party or platform-rendered components where behavior is controlled by upstream product/framework implementations
  • Low-priority content consistency improvements identified during periodic re-testing

Where issues are identified, they are triaged and scheduled according to user impact and legal risk.

8. Feedback and Accessible Alternatives

If you need information from this portal in another accessible format (for example, accessible PDF, large print, or another support format), contact:

  • support@creditsafe.com

When contacting us, please include:

  • The page URL
  • A description of the issue
  • Your preferred accessible format (if applicable)

We try to respond to accessibility feedback as quickly as possible.

9. Enforcement Procedure

If you are not satisfied with our response, you may contact the relevant national enforcement body in your jurisdiction for accessibility complaints under applicable law.

10. Statement Preparation and Review

  • Statement prepared: March 2026
  • Last tested: Q1 2026
  • Testing method: Combination of manual and automated accessibility testing
  • Basis: Accessibility audits completed in December 2025 and re-tested in Q1 2026
  • Last reviewed: March 2026

This statement will be reviewed and updated periodically as remediation and platform changes are delivered.

11. Ongoing Publication Controls

To reduce the risk of non-conformant content being published:

  • In the short term, accessibility adherence is manually checked as part of the technical writing publication workflow.
  • In parallel, an automated pre-publish accessibility checking process is being implemented in CI/CD pipelines.
  • The target operating model is a publication gate that blocks deployment when defined accessibility checks fail.