Accessibility Statement.

Spalce Technologies Ltd is committed to making the Spalce website (spalce.dev) and the platforms we operate accessible to as many people as possible, including people with visual, auditory, cognitive, motor, or speech disabilities, and people using assistive technologies. Accessibility is not an afterthought in our delivery process: it is treated as a first-class quality attribute alongside security, performance, and reliability.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the W3C Web Accessibility Initiative. Where they apply to a specific market or customer engagement, we additionally align with EN 301 549 v3.2.1 (the harmonised European standard cited by the European Accessibility Act), Section 508 of the United States Rehabilitation Act, and the Persons with Disability Act, 2006 (Act 715) of the Republic of Ghana.

This commitment applies to digital surfaces operated by Spalce as well as to the engineering services we deliver to customers under a statement of work, subject to the scope agreed in that statement of work.

The Spalce website (spalce.dev) is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means that some parts of the content do not yet fully meet every applicable success criterion. The known gaps are documented in Section 5 below, together with the timeframes within which we plan to remediate them.

The most recent independent audit of the Spalce website was completed on 12 April 2026 by an external auditor specialising in digital accessibility. The audit covered the production website, the marketing properties, and the authenticated areas of the Spalce customer portal. The auditor identified no Level A blockers; the residual findings are at Level AA and below.

Spalce treats accessibility as an engineering discipline that runs through design, development, code review, quality assurance, and release. Concretely:

• Accessibility is built into our design tokens: colour, typography, focus, and spacing tokens are defined with WCAG contrast and target-size requirements as constraints rather than guidelines.
• Body text is verified at a contrast ratio of at least 4.5:1 against its background, and large text and interactive components at a ratio of at least 3:1, in line with WCAG 2.2 success criteria 1.4.3 and 1.4.11.
• Our continuous-integration pipeline runs automated accessibility checks on every pull request using axe-core, and blocks merge on any serious or critical violation.
• Every release that touches user-facing surfaces is exercised in a keyboard-only manual test pass; release engineers verify focus order, focus visibility (1.4.11, 2.4.7), and the absence of keyboard traps (2.1.2).
• Critical user journeys (sign-in, contact, support, billing) are tested with at least one screen reader on each major platform before they ship to production.
• We use semantic HTML by default. ARIA attributes are introduced only where native semantics are not sufficient, in line with the W3C ARIA Authoring Practices.
• Form controls have programmatically associated labels and descriptive error messaging; errors are announced to assistive technology rather than communicated by colour alone.
• Motion and animation are constrained by the user's prefers-reduced-motion setting; no content flashes more than three times per second (2.3.1).
• Engineers and designers receive accessibility training during onboarding, and a refresher review at least once per calendar year.

Accessibility of the Spalce website and platforms relies on the following technologies working with the user's browser and any assistive technologies installed on their device:

• HTML (semantic markup as defined by the WHATWG HTML Living Standard).
• WAI-ARIA 1.2 for roles, states, and properties where native HTML semantics are insufficient.
• CSS, including media queries that respect user preferences such as reduced motion, increased contrast, and forced colours.
• JavaScript, with non-essential functionality designed to degrade gracefully where scripts are blocked.

These specifications are relied upon for conformance with WCAG 2.2 success criteria. The Spalce website is tested against the most recent two major versions of the following user agents and assistive technologies:

We publish our known gaps openly so that users and procurement teams can make informed decisions. Each limitation below is tracked in our engineering backlog with a target remediation date.

• Some embedded third-party video players on our case-study pages do not yet expose full keyboard navigation for their player controls. We are migrating to a vetted accessible player and expect this to be resolved by Q4 2026.
• Spalce-authored PDF documents published before 1 January 2025 may not be fully tagged for screen-reader navigation. We are re-issuing the prioritised back catalogue (procurement, security, and SLA documents) by Q3 2026; older marketing PDFs will follow on a best-effort basis.
• A small number of legacy data tables on archived blog posts do not have programmatically associated headers. These are being migrated to a new article template; archived posts will be updated by Q3 2026.
• Some animated decorative illustrations on the homepage continue to animate even when prefers-reduced-motion is enabled. The fix is scheduled for the next homepage release in Q3 2026.
• Automatic captions on certain pre-2025 webinar recordings have not yet been human-corrected. Corrected transcripts can be requested via the accessibility contact below and will be provided within five business days.

Spalce assessed the accessibility of its digital surfaces using a combination of self-evaluation, third-party audit, automated tooling, and manual testing with assistive technologies.

• Self-evaluation: internal designers and engineers reviewed each release against the WCAG 2.2 AA checklist before sign-off.
• Third-party audit: an external accessibility consultancy completed a full audit of the Spalce website and customer portal in April 2026.
• Automated tooling: axe-core runs in our continuous-integration pipeline; Pa11y runs as a scheduled crawl against the production website.
• Manual testing: keyboard-only walkthroughs of all critical user journeys, and screen-reader passes (NVDA, JAWS, VoiceOver, and TalkBack) on at least one journey per release.

We do not treat automated tooling as a sufficient substitute for manual testing. Automated checks typically detect 30 to 40 percent of accessibility issues; human judgement is required for the remainder.

When Spalce builds software on behalf of a customer, the accessibility target is scoped explicitly in the relevant statement of work. The default target for any new (net-new) build is WCAG 2.2 Level AA, regardless of whether accessibility is mentioned in the request for proposal. Accessibility is audited as part of our standard quality-assurance gates before any release is delivered to the customer.

Where a customer requires WCAG 2.2 Level AAA conformance, EN 301 549 conformance, or compliance with sector-specific accessibility regulations (such as ADA Title II for U.S. state and local government, or PSBAR for U.K. public-sector bodies), we can target those standards on request and document the residual gaps using a VPAT 2.5 (Voluntary Product Accessibility Template) or equivalent.

Where Spalce is asked to extend an existing system that is already partially non-conformant, we will document the inherited gaps in writing before work begins and propose a remediation plan with the customer.

We welcome feedback on the accessibility of the Spalce website and platforms. If you encounter an accessibility barrier, need information in an alternative format, or have a suggestion for improvement, please contact us using any of the channels below.

• Email: [email protected]
• Telephone: +233 (0) 30 000 0000 (Monday to Friday, 09:00 to 18:00 GMT)
• Post: Accessibility Team, Spalce Technologies Ltd, Accra, Ghana

We aim to acknowledge accessibility feedback within two business days and to provide a substantive response within five business days. If you have requested content in an alternative format (for example, a tagged PDF, an audio description, or a corrected transcript), we will deliver it within ten business days of your request, or contact you with a clear timeline if the request requires longer.

In Ghana, users who consider that they have not received a satisfactory response from Spalce can also raise the matter with the National Council on Persons with Disability (NCPD) for escalation.

If you have followed the feedback process above and remain dissatisfied with our response, you can escalate to the relevant regulator or body in your jurisdiction:

• Ghana: the National Council on Persons with Disability (NCPD), the body designated under the Persons with Disability Act, 2006 (Act 715).
• European Union: the national enforcement body designated under the European Accessibility Act (Directive (EU) 2019/882) in your Member State.
• United Kingdom: the Equality and Human Rights Commission (EHRC) for matters under the Equality Act 2010.
• United States: the U.S. Department of Justice for complaints under Title III of the Americans with Disabilities Act (ADA), or the relevant federal agency for Section 508 matters.

Where the engagement is governed by a signed contract that specifies a different dispute-resolution route, that route takes precedence.

This Accessibility Statement was first created on 1 June 2026 and was last reviewed on 1 June 2026. It is reviewed at least once per calendar year, and additionally whenever the Spalce website or the customer portal undergoes a material change.