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 as standard, with documentation on request. GDPR-compliant. Procurement-ready on day one.
[ Hero image: accessible publication with screen reader and keyboard navigation overlay ]
The problem
Opt-in accessibility creates procurement risk
Universities are increasingly required by procurement, legal and accreditation processes to confirm that recruitment content meets WCAG standards. Generic digital publishing tools either skip accessibility entirely or treat it as an opt-in setting you have to verify per document. Both approaches create procurement risk and exclude prospective students with assistive technology needs.
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 design system, navigation, contrast, alt text and semantic structure built in at component level. Accessibility flows downstream automatically because the components are accessible.
01
WCAG 2.1 AA on every publication
Every publication is built to WCAG 2.1 AA standard by default. No per-publication accessibility setup, no audit-then-retrofit, no manual contrast checks. The standard ships with the platform, not as an optional upgrade.
[ Image: WCAG 2.1 AA compliance checklist passing across every publication ]
[ Image: mobile-first design with screen-reader friendly semantic structure ]
02
Mobile-first, screen reader friendly
Every template is mobile-first and screen reader friendly. Semantic headings, proper alt text, keyboard navigation, in-browser translation support across languages. The accessible experience is the default experience, not a fallback.
03
Procurement-ready
Every theRACK publication is built to WCAG 2.1 AA with documentation available on request. Fully GDPR-compliant with a Data Processing Agreement available. Each institution's specific IT, legal, accessibility and procurement framework is supported through bespoke client setup.
[ Image: procurement documentation pack with DPA and accessibility statement ]
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, not after the contract is signed. theRACK is built to WCAG 2.1 AA, GDPR-compliant with DPA available, and supports each institution's bespoke IT, legal and accessibility framework as standard.
See accessibility built in
Explore how theRACK delivers WCAG 2.1 AA recruitment content as standard for higher education, not as an afterthought.