Inclusive design
A common fact is that 1 in 5 people have a permanent disability. This doesn't include people who may have temporary or short-term disabilities, like an injury, or situational disabilities, like holding a baby.
Disabilities can be grouped into different types, and a person might experience more than one. Good accessibility helps everyone, not just those with disabilities.
Permanent disabilities
A person who has one arm, is deaf, or is blind would be considered to have a permanent disability.
Permanent disabilities are the ones most people think of when it comes to inclusive design and accessibility.
Designing for those with permanent disabilities can create products and websites that work for everyone, including those with temporary or situational disabilities.
Temporary disabilities
A temporary disability is a short-term condition, like a broken bone, recovering from laser eye surgery, or a concussion.
People with temporary disabilities can benefit from the same inclusive design principles that help those with permanent disabilities.
For example, designing for keyboard accessibility will help someone with a broken arm navigate a service.
Providing functionality that's responsive to zoom, works with magnification, and uses good contrast ratios, can help someone recovering from laser eye surgery. Avoiding content that causes motion sickness or dizziness can help someone with concussion.
Situational disabilities
A situational disability is something that almost everyone has experienced.
For example, watching a video in a busy setting, such as a nursery or school, using a website while holding a baby, or trying to open a door with your hands full. Good design can solve these problems.
Captions and transcripts allow people to understand the content of a video in a noisy environment. Websites designed for full keyboard navigation let parents or caregivers use them with one hand, without needing a mouse. An automatic door means that people can still pass through when carrying something.
Universal design principles
The 7 design principles are guidelines for designing spaces and products that everyone can use. They were first created for architecture and product design but can also apply to digital services.
When designing DfE products and websites, we should use these principles to ensure they are accessible and easy for everyone.
The 7 principles:
- Principle 1: equitable use
- Principle 2: flexibility in use
- Principle 3: simple and intuitive use
- Principle 4: perceptible information
- Principle 5: tolerance for error
- Principle 6: low physical effort
- Principle 7: size and space for approach and use
Equitable use
Provide equal access to DfE products and websites to everyone who wants to use a service.
You should:
- avoid cluttered layouts
- use the correct language for people with disabilities
- not exclude anyone
- not disadvantage or stigmatise anyone
- make the design appealing to all users
- ensure users can access with assistive technology
Flexibility in use
Not all users will use your service in the same way. People need different settings, preferences, and adaptive ways of working. We should ensure that they are not forced to work in a certain way.
You should:
- allow users to change settings to suit their needs
- ensure pages can reflow
- allow for high contrast
- use responsive units for text
- allow users to work at their own pace
- avoid timeouts or allow users to extend
Simple and intuitive use
Users want to be able to navigate products and websites with ease. When content is hard to understand, it makes it harder for users to move through a service.
People with English as an additional language, are new users, have learning disabilities, low literacy, and memory issues could all have issues with products and websites which are not simple and intuitive.
A person's background, language, or experience should not make it harder for them to understand how to use DfE products and websites.
You should:
- write in plain language
- provide descriptions for acronyms
- avoid jargon
- be consistent in positioning components
- avoid unnecessary complexity
- provide effective prompting and feedback on task completion
- accommodate a wide range of literacy and language skills
Perceptible information
Users perceive content in different ways. Not everyone reads blocks of content visually, or watches videos. This could be because they are blind and cannot view the video but can read the transcript with a screen reader.
People who are deaf cannot hear the audio in a meeting, but can follow the conversation by using the captions.
When designing DfE products and websites, we should think about the different ways in which users may perceive content.
You should:
- provide captions and transcripts for meetings and videos
- provide alt text for all images
- not use colour alone to provide information
- use colours that contrast sufficiently
Tolerance for error
Provide a way for users to avoid errors, or if they do make them, provide clear information and a way to fix them. Clear content, which gives information on how to do a task, and hint text in a form, can minimise the chance of an error occurring. This avoids frustration and repetition which can be difficult for many people with disabilities.
People who are deaf cannot hear the audio in a meeting, but can follow the conversation by using the captions.
When designing DfE services, we should think about where users are most likely to cause an error to occur. We should ensure that things are in place to avoid or rectify these errors.
You should:
- allow copy and paste
- allow password managers
- provide a forgot password functionality
- use the check your answers
- provide an error summary for every error
- provide specific error information
- provide help
Low physical effort
DfE products and websites should be easy to use, intuitive, and allow users to navigate and interact without fatigue.
Clear, simple, easy-to-read content ensures users do not suffer cognitive load. Creating robust products means that people can use our websites with ease on their preferred input device.
When websites are not fully accessible, some users will try to use alternative methods. For example, some people with RSI (repetitive strain injury) who use Dragon, will stop using speech recognition and reach for a mouse to navigate. This can cause further pain and discomfort.
You should:
- make mobile components reachable
- make services speech recognition accessible
- provide full keyboard accessibility
- cognitive load
- minimise repetitive actions
Size and space for approach and use
Make sure users have the tools they need to use a product or website, and those tools are easy to find and access. Buttons and other elements should be big enough and spaced out so that people with limited mobility can use them easily.
Design elements and components should be simple to reach, click, or select, no matter what device or input method someone is using.
You should:
- provide enough spacing between elements
- provide sufficient target size for clickable or tappable components
- use full width buttons on mobile where possible
- ensure all elements are speech recognition accessible
- provide responsive viewports that adapt to users preferences
Information about this page
- Created
- 7 January 2025
- Last reviewed
- 7 January 2025
- Last updated
- 7 January 2025
- Reason this page exists
- This page exists to help people understand inclusive design principles
- Suggest a change or comment
- Issue 72