Feature
WCAG 2.1 AA on every publication.
Accessibility is built in at the design stage, not retrofitted at audit. Every theRACK publication meets WCAG 2.1 AA, GDPR-compliant, procurement-ready on day one.
The problem
Opt-in accessibility creates procurement risk
Procurement, legal and accreditation processes increasingly require recruitment content to meet WCAG standards. Most publishing tools either skip accessibility or treat it as an opt-in setting you check per document. Both create procurement risk.
How theRACK solves it
Accessibility, built into the components
theRACK is built the other way. Every publication starts on a WCAG 2.1 AA-compliant template, with contrast, alt text and semantic structure built in at component level. Accessibility flows downstream because the components are accessible.
01
WCAG 2.1 AA on every publication
Every publication is built to WCAG 2.1 AA by default. No per-publication setup, no audit-then-retrofit, no manual contrast checks. The standard ships with the platform.
02
Mobile-first, screen reader friendly
Every template is mobile-first and screen reader friendly. Semantic headings, alt text, keyboard navigation, in-browser translation across languages. Accessible is the default, not a fallback.
03
Procurement-ready
Every publication is built to WCAG 2.1 AA with documentation on request. GDPR-compliant with DPA available. Each institution's IT, legal and accessibility framework is supported through bespoke client setup.
In practice
Built for the procurement reality of HE
Universities running procurement reviews need a vendor who answers WCAG, GDPR and accessibility questions on day one. theRACK is built to WCAG 2.1 AA, GDPR-compliant with DPA available, and supports each institution's bespoke framework as standard.