.svg){kind=icon}
What is ISO 22458?
ISO 22458 is a standard focused on consumer vulnerability and the design of inclusive services.
ISO 22458 is a standard focused on consumer vulnerability and the design of inclusive services.
In simple terms, it helps organisations make sure their services are designed and delivered in a way that supports people who may be vulnerable, disadvantaged, excluded or at risk of harm during a customer journey.
That could include people affected by disability, poor health, bereavement, financial difficulty, language barriers, low digital confidence, caring responsibilities, mental health challenges or temporary life events that make dealing with a service more difficult.
ISO 22458:2022 is officially titled Consumer vulnerability — Requirements and guidelines for the design and delivery of inclusive service. It provides requirements and guidance for organisations on how to provide inclusive service at all stages of service delivery.
Is ISO 22458 a website standard?
Not exactly.
ISO 22458 is not just a web design standard and it is not something that applies only to a website. It applies to the organisation’s wider service delivery.
However, websites and portals are often a major part of that service journey. If a customer uses a website to apply, register, pay, make a complaint, request support, upload documents or manage an account, then that digital journey can directly affect whether the organisation is providing an inclusive service.
- how customers access a service
- how staff identify and respond to vulnerability
- how customer journeys are designed
- how information is communicated
- how complaints and support requests are handled
- how vulnerable customers are protected from poor outcomes
- how the organisation reviews and improves its service
What does ISO 22458 mean for a website or portal?
For a website or portal, ISO 22458 is mainly about making sure the digital journey does not accidentally exclude, pressure, confuse or disadvantage people who may need additional support.
That means looking beyond visual design and thinking carefully about how different people experience the service.
This is where inclusive digital design becomes more than a nice to have. It becomes part of the organisation’s risk management, customer care and compliance approach.
- Can a user understand what is being asked of them?
- Can they complete a form without unnecessary barriers?
- Is there a clear route to get help?
- Are there alternatives if the digital journey is too difficult?
- Does the service avoid pressuring people into decisions?
- Can a user explain a support need safely?
- Are staff notified when a customer may need extra help?
- Is information written clearly and accessibly?
- Are complaints, cancellations and payment issues handled with care?
Examples of ISO 22458-aligned website and portal features
A website or portal designed with ISO 22458 in mind might include:
The goal is not to make assumptions about individual users. The goal is to design the service so that people can access support without feeling excluded, embarrassed or forced through a process that does not work for them.
- plain-English content
- accessible forms
- clear progress indicators
- save-and-return functionality for long forms
- alternative contact options
- clear need help routes
- support for nominated representatives or authorised contacts
- flexible communication preferences
- simple explanations of fees, obligations and next steps
- clear complaints and escalation routes
- non-pressurised user journeys
- careful handling of sensitive information
- staff alerts or workflow triggers where support may be needed
Why ISO 22458 matters commercially
ISO 22458 is especially relevant for organisations that deal with consumers in sectors such as telecoms, utilities, financial services, housing, healthcare, care, education, public services and other regulated or customer-sensitive environments.
For these organisations, poor service design can create real harm.
A confusing billing journey, an inaccessible form, a digital-only process, unclear cancellation terms or a lack of support routes can all create problems for vulnerable customers.
By designing services around ISO 22458 principles, organisations can reduce risk, improve customer trust and show that they take inclusive service seriously.
How ISO 22458 relates to accessibility
ISO 22458 and digital accessibility are closely connected, but they are not the same thing.
Accessibility usually focuses on whether people with disabilities can access and use a website or digital service. This is commonly measured against WCAG, the Web Content Accessibility Guidelines.
ISO 22458 is broader. It looks at vulnerability in the wider service experience.
For example, a website could technically pass many accessibility checks but still create problems for vulnerable customers if:
- the language is confusing
- the process is too long
- the user cannot pause and return later
- there is no human support route
- the customer is forced into digital-only communication
- important consequences are hidden in small print
- staff do not know how to respond when someone asks for help
Does a business need ISO 22458 certification?
That depends on the organisation, sector and reason for adopting the standard.
Some organisations may use ISO 22458 as an internal improvement framework. Others may pursue external recognition or certification through an assessment route such as the BSI Kitemark for Inclusive Service.
For website and portal projects, the important thing is to be clear about scope.
A digital agency should not usually claim that a website is ISO 22458 certified by itself. A more accurate statement would be that the website or portal has been designed to support ISO 22458-aligned inclusive service principles as part of the organisation’s wider service approach.
This distinction matters because the standard applies to the organisation’s full service, not only the digital interface.
How we approach ISO 22458-aligned digital projects
For websites and portals where inclusive service matters, the digital project should include more than design and development.
A good project approach includes:
1. Customer journey mapping
Identify the key user journeys and where vulnerable customers could face barriers.
2. Content review
Make sure language is clear, direct and easy to understand.
3. Accessibility planning
Build the interface around recognised accessibility principles and WCAG expectations.
4. Form and portal review
Remove unnecessary friction, confusing questions and avoidable upload barriers.
5. Support route design
Make it clear how users can get help if they cannot complete the journey online.
6. Escalation planning
Define what happens when a user discloses vulnerability or appears to need additional support.
7. Evidence pack creation
Document decisions, risks, testing, user journeys and known limitations.
Final thoughts
ISO 22458 is not about adding a few accessibility features at the end of a project.
It is about designing services so that customers are not disadvantaged when they are vulnerable, under pressure or in need of extra support.
For websites and portals, that means creating digital journeys that are clear, accessible, flexible and connected to real human support where needed.
If your service includes a website, portal or digital application process, WCAG 2.2 accessibility should also be considered as part of your inclusive service approach.
Sources and further reading
Wayne O'Keefe
Founder and Growth Strategist · Wayne helps businesses turn scattered activity into clearer systems for growth, bringing together strategy, websites, CRM and marketing.