Skip to main content
Back to home
Legal

Accessibility statement

How NAfSA approaches digital accessibility on public marketing pages and core member-facing flows, including known limitations and how to request support.

Last updated: 25 June 2026

Legal entity

National Alliance for School Attendance Ltd (NAfSA). Registered in England and Wales. Company Registration Number: 10252699. Registered Office: Cleveland, Hayscastle, Haverfordwest, Wales, SA62 5NY.

Our commitment

National Alliance for School Attendance Ltd (NAfSA). Registered in England and Wales. Company Registration Number: 10252699. Registered Office: Cleveland, Hayscastle, Haverfordwest, Wales, SA62 5NY.

National Alliance for School Attendance (NAfSA) serves education professionals across the UK — attendance officers, pastoral staff, administrators, leaders, and allied colleagues in schools, trusts, and local authorities. We aim to make the platform usable by as many people as possible, including colleagues who rely on assistive technology, keyboard-only navigation, or screen magnification.

Our target standard is Web Content Accessibility Guidelines (WCAG) 2.2 Level AA for public marketing pages and core member journeys (sign-in, membership, dashboard navigation, and widely used portal tools). This statement describes our current position honestly. It is published as best practice for schools, trusts, and local authorities reviewing our platform — NAfSA is a private social enterprise and this is not a Public Sector Bodies Accessibility Regulations (PSBAR) declaration.

How accessible this website is

We consider the platform partially compliant with WCAG 2.2 Level AA. Semantic HTML, labelled form controls, keyboard focus patterns, and automated testing are in place on many surfaces, but we have not completed a full independent WCAG audit and we do not claim full AA conformance today.

Automated axe-core scans and ESLint accessibility rules help us catch regressions during development. Manual review and member feedback remain essential — automated tools cannot detect every barrier, especially in complex data views or third-party sign-in interfaces.

The member portal and public legal pages (including this statement) generally use a light, high-contrast layout. Some public marketing pages use a dark visual theme where muted text colours do not yet meet WCAG 2.2 AA contrast requirements in every section. Those issues are documented below and scheduled for remediation.

Feedback and contact

If you find an accessibility barrier on NAfSA, need information in a different format, or want to request a reasonable adjustment to how we deliver a service, please email support@nafsa.org.uk or use our contact form at contact page.

Please tell us which page or feature you were using, what you were trying to do, and which assistive technology or browser you use if relevant. We aim to respond within 5 working days and will work with you to find a practical solution where we can.

Enforcement procedure

The Equality Act 2010 requires service providers to make reasonable adjustments for disabled users where applicable. If you are not satisfied with our response to an accessibility concern, you may contact the Equality and Human Rights Commission (EHRC), which enforces equality law in England, Scotland, and Wales.

Equality and Human Rights Commission: https://www.equalityhumanrights.com/

If you are based in Northern Ireland, you may also contact the Equality Commission for Northern Ireland (https://www.equalityni.org/).

Technical information

We use the following approaches to support accessibility across the codebase:

For how we handle personal data in connection with the platform, see our Privacy Policy at Privacy Policy. For procurement and governance information, see procurement pack.

  • Static analysis — eslint-plugin-jsx-a11y runs as part of our lint workflow to flag missing alternative text, invalid ARIA, and similar JSX issues.
  • Automated browser testing — @axe-core/playwright smoke tests run against key public pages (homepage, about, membership, and this accessibility statement) using WCAG 2.x rule tags.
  • Keyboard and focus — membership sector tabs use a tablist pattern with arrow-key navigation; portal module navigation includes keyboard support and visible focus rings on primary controls.
  • Authentication — sign-in and account management are delivered through Clerk. Clerk’s hosted UI is a third-party surface; we configure appearance where possible, but some limits may sit outside NAfSA’s direct control.
  • Payments — Stripe checkout is used for card payments; Stripe’s payment flows are third-party and subject to Stripe’s own accessibility work.

Non-accessible content

The following known issues affect accessibility today. We are not claiming these are resolved:

  • Colour contrast on dark marketing pages — text-slate-500 and similar muted slate text on dark backgrounds (for example on /, /about, membership page, procurement pack, and /advertise) often falls below WCAG 2.2 AA contrast ratios (4.5:1 for normal text). Remediation is planned through a design-token pass on public marketing surfaces; this statement does not imply that work is complete.
  • Complex data visualisations — member analytics, benchmarking charts, and heatmaps may rely on charts and colour encoding. Where implemented, some views include data tables or textual alternatives; not every chart has a full non-visual equivalent yet.
  • Procurement pack printing — the “Print or save as PDF” function on procurement pack uses your browser’s print dialog. Layout, contrast, and tagging of the resulting PDF depend on browser and operating-system settings and are not fully controlled by NAfSA.
  • Third-party embeds — occasional embedded content (for example payment or authentication flows) may not meet the same standard as NAfSA-authored pages.

Preparation of this statement

This accessibility statement was prepared by NAfSA using internal development standards, automated test results, and documented known gaps. It was last reviewed on 25 June 2026.

We will review and update this statement when we make significant platform changes, resolve known accessibility issues, or receive substantive feedback from members or procurement reviewers.