Accessibility statement

What this statement covers

This statement covers the public marketing website at credicorp.co.uk: the product and pricing pages, the loan calculators and money tools, the application entry point at /apply/, the guides, FAQs, glossary, newsroom and sector pages, and the legal library. It applies whether you are a director researching a facility for your limited company, an accountant checking our terms on a client's behalf, or a bookkeeper downloading our published policies.

The customer portal at clients.credicorp.co.uk — where a borrowing company manages its live facility — is covered by the same commitment but is assessed separately, because it is a different application with its own release cycle. PDF documents we publish (policies, agreements, schedules) are in scope and are called out under known limitations below.

Conformance status

This website is partially conformant with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. "Partially conformant" means most of the content meets the standard, and the parts that do not are listed in full under known limitations — we would rather tell you exactly where the gaps are than claim a level we have not earned.

We hold ourselves to WCAG 2.2 AA even though, as a private limited company, credicorp.co.uk is not subject to the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. Our duty to make reasonable adjustments under the Equality Act 2010 does apply, and this statement is part of how we meet it.

What we have built for accessibility

Accessibility on this site is built in, not bolted on:

• Useful without JavaScript. Core pages, navigation, pricing explanations and server-rendered calculator examples remain readable with scripts disabled. Some interactive calculators, filters and application services use scripts; where they do, we provide explanatory content or a direct contact route.
• Keyboard first. Every interactive element is reachable and operable with a keyboard alone. A skip-to-content link appears on first Tab press, and the visible focus ring is never removed — it is layered so it stays visible on both light and navy surfaces.
• Semantic landmarks. Each page exposes one banner (header), one main content region and one contentinfo (footer) landmark, so screen-reader users can jump between regions rather than reading linearly.
• Simple View. Every public page has a plain-English condensed mirror at /simple/<page>/ — the toggle sits in the footer and in the floating "Aa" shortcut on every page.
• Your system preferences are honoured. If your device asks for reduced motion, animations and transitions are collapsed to effectively instant. If it asks for increased contrast, secondary text and hairline borders darken and plain links gain thicker underlines. Windows High Contrast / forced-colours mode keeps a visible focus outline.
• No pointer-only interactions. Nothing on the site requires dragging, hovering as the only path, or precise gestures — menus, calculators and forms all work with clicks and key presses (WCAG 2.2, dragging movements and target size).
• Consistent help. Search, Sign in and the contact routes sit in the same place in the header and footer of every page (WCAG 2.2, consistent help).
• Forms that explain themselves. Every field has a visible label; errors are written in words next to the field they concern, not colour-coded alone.
• Welsh, Scottish Gaelic and Scots. Translated marketing pages and policies for visitors who prefer them, with the document language declared so screen readers switch pronunciation correctly.

Known limitations

The following do not yet fully conform, despite our best efforts. We list them so you can decide whether to ask us for the content another way (see the next section) rather than discover a barrier mid-task:

• Some older PDFs. The PDF versions of a few regulatory documents are tagged for screen readers, but the reading order on some legacy templates is not yet right. We are rebuilding those templates; the HTML page carrying the same content is always conformant and is the version we recommend.
• Some support videos. A small number of older support-article videos do not yet have closed captions. New videos are captioned before publication.
• One complex table. The Slice instalment schedule renders as a table that not every screen reader announces as a data table. The same schedule is available as a written list on request.
• Third-party embedded content. Where a page embeds content we do not build (for example an external register lookup), we cannot guarantee that the embedded frame meets Level AA. We link to the provider's own page as an alternative wherever we can.

Accessible formats and getting help

If any content on this site — a rate table, a policy, an instalment schedule, an application form — is not accessible to you, we will provide it in a format that is. That includes large print, plain-text email, an accessible PDF, or a person on the phone reading the figures with you before your company applies.

Email accessibility@credicorp.co.uk with the page address and the format you need. We aim to resolve high-impact accessibility problems within 5 working days and everything else within 30 days — the same targets published in our legal statement since launch.

How we test

Conformance is currently established by self-assessment, not an external audit. Every release runs automated accessibility checks (axe-core rules and HTML validation) across desktop, tablet and mobile viewports in three browser engines, and we do manual keyboard-only and screen-reader spot checks on changed pages. When we commission an independent audit we will say so here and publish the result honestly, including anything it finds.

If we get it wrong

If you report an accessibility problem and are unhappy with how we respond, you can escalate it. The Equality Advisory and Support Service (EASS) advises on the Equality Act 2010, and the Equality and Human Rights Commission (EHRC) is responsible for enforcing it in England, Scotland and Wales. Telling us first is not a condition of contacting them — but we would welcome the chance to fix it.

About this statement

This statement was prepared on 13 July 2026 against WCAG 2.2 and is reviewed at least annually, and sooner whenever a feature materially changes the visitor journey. It supersedes the WCAG 2.1 statement in our legal library, which remains published for the record.