Digital accessibility is not a nice extra. It is basic access.
If people cannot use your website, form, PDF or digital service, your inclusion statement is not doing much for them.
If people cannot use your website, form, PDF or digital service, your inclusion statement is not doing much for them.
'Digital accessibility is not polish. It is access'.
Too many organisations still treat digital accessibility like a finishing touch. Something to revisit after launch. Something to improve later. Something for specialist teams rather than leaders, policy owners, comms staff or procurement. That mindset is one of the clearest signs that disabled people were not built into the design in the first place.
The legal and policy position is not vague. GOV.UK guidance says public sector websites and apps must meet accessibility requirements and publish an accessibility statement under the 2018 accessibility regulations. Those regulations apply across the UK public sector framework, including Northern Ireland. They are grounded in the practical expectation that digital services should be perceivable, operable, understandable and robust.
The scale of the problem is wider than many organisations admit. The government’s Digital Inclusion Action Plan: One Year On, published on 24 March 2026, says some groups are more likely to struggle digitally, including disabled people, older people and those on lower incomes, and highlights ongoing work to make digital services more accessible and inclusive. At the same time, WebAIM’s 2026 Million report found that 95.9% of home pages tested had detectable WCAG 2 failures. That figure is startling not because accessibility problems are rare, but because they are normalised.
Organisations need to stop treating this as an IT niche. Accessibility affects recruitment, complaints, learning, assessments, bookings, public information, customer trust and legal risk. Audit your website. Fix inaccessible PDFs. Review forms, captions, colour contrast, headings and keyboard access. Most importantly, stop acting as though access is an optional enhancement. It is the point.
Sources
Accessibility requirements for public sector websites and apps: https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps
Digital Inclusion Action Plan: One Year On: https://www.gov.uk/government/publications/digital-inclusion-action-plan-one-year-on/digital-inclusion-action-plan-one-year-on
WebAIM Million 2026 report: https://webaim.org/projects/million/