惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Google DeepMind News
Google DeepMind News
C
CERT Recently Published Vulnerability Notes
C
Cisco Blogs
Cloudbric
Cloudbric
The Last Watchdog
The Last Watchdog
L
LINUX DO - 热门话题
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Application and Cybersecurity Blog
Application and Cybersecurity Blog
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
Security Archives - TechRepublic
Security Archives - TechRepublic
TaoSecurity Blog
TaoSecurity Blog
V2EX - 技术
V2EX - 技术
H
Heimdal Security Blog
S
Security Affairs
L
Lohrmann on Cybersecurity
Hacker News - Newest:
Hacker News - Newest: "LLM"
Simon Willison's Weblog
Simon Willison's Weblog
WordPress大学
WordPress大学
小众软件
小众软件
Security Latest
Security Latest
AWS News Blog
AWS News Blog
Apple Machine Learning Research
Apple Machine Learning Research
GbyAI
GbyAI
Engineering at Meta
Engineering at Meta
阮一峰的网络日志
阮一峰的网络日志
罗磊的独立博客
F
Full Disclosure
S
Schneier on Security
L
LangChain Blog
MyScale Blog
MyScale Blog
Know Your Adversary
Know Your Adversary
P
Privacy International News Feed
Google Online Security Blog
Google Online Security Blog
Scott Helme
Scott Helme
Stack Overflow Blog
Stack Overflow Blog
爱范儿
爱范儿
A
Arctic Wolf
Martin Fowler
Martin Fowler
B
Blog RSS Feed
大猫的无限游戏
大猫的无限游戏
博客园 - 三生石上(FineUI控件)
The Register - Security
The Register - Security
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
博客园_首页
Latest news
Latest news
F
Fortinet All Blogs
G
GRAHAM CLULEY
T
The Exploit Database - CXSecurity.com
Hacker News: Ask HN
Hacker News: Ask HN

TetraLogical Blog

Designing for people with reading disabilities - TetraLogical Designing for people who are D/deaf - TetraLogical Designing accessible documents - TetraLogical Introduction to creating accessible documents - TetraLogical Inclusive user research: vulnerable people - TetraLogical Designing for people who are blind - TetraLogical Designing for people with low vision - TetraLogical Meet the team: Niamh Madden - TetraLogical Designing for people with anxiety - TetraLogical Designing for people with disabilities - TetraLogical Accessible building blocks for the web videos - TetraLogical Common accessibility misconceptions - TetraLogical Common misconceptions about testing accessibility - TetraLogical Common misconceptions about implementing accessibility - TetraLogical Common misconceptions about WCAG - TetraLogical Common misconceptions about disability - TetraLogical Meet the team: Grace Snow - TetraLogical Sustainable accessibility in complex organisations: strategic foundations - TetraLogical Sustainable accessibility in complex organisations: organisational realities - TetraLogical Sustainable accessibility in complex organisations: external factors - TetraLogical Common misconceptions about screen readers - TetraLogical Guide to the Inclusive Design Principles - TetraLogical Meet the team: Ian Lloyd - TetraLogical Annotating designs using common language - TetraLogical Meet the team: Catriona Morrison - TetraLogical Championing inclusive language - TetraLogical Press release: TetraLogical launches accessible self-led training courses to help digital teams build confidence in accessibility - TetraLogical Accessible Recruitment - TetraLogical Accessibility and the agentic web - TetraLogical Meet the team: Craig Abbott - TetraLogical Foundations: types of assistive technology and adaptive strategies - TetraLogical European Accessibility Act (EAA) FAQ - TetraLogical Screen reader HTML support tables - TetraLogical Interview with Lola Odelola - TetraLogical Understanding EN 17161 Design for All - TetraLogical Inclusive user research: building rapport - TetraLogical Foundations: Keyboard accessibility - TetraLogical Can generative AI write contextual text descriptions? - TetraLogical Understanding the European Accessibility Act (EAA) - TetraLogical Meet Josh: a sportsman who has spinal muscular atrophy - TetraLogical Meet Jonathan: a photographer who has ADHD - TetraLogical Foundations: grouping forms with `<fieldset>` and `<legend>` - TetraLogical XR Accessibility: for people with moving disabilities - TetraLogical Meet Andre: a music producer and blind screen reader user - TetraLogical Foundations: types of disability - TetraLogical Meet Lauren: a film editor who has ADHD - TetraLogical Meet Steve: a photographer who is deaf and low vision - TetraLogical Foundations: form validation and error messages - TetraLogical Meet Hasmukh: a blind cricketer and screen reader user - TetraLogical XR Accessibility: for people with hearing disabilities - TetraLogical XR Accessibility: for people with thinking disabilities - TetraLogical XR Accessibility: for people with seeing disabilities - TetraLogical Introduction to XR Accessibility - TetraLogical Foundations: labelling text fields with input and label - TetraLogical Design patterns and WCAG - TetraLogical Does WCAG 2.2 apply to native apps - TetraLogical Why are my live regions not working? - TetraLogical Building a culture of accessibility - TetraLogical When to use tabindex= Accessibility foundations - TetraLogical Meet the team: Demelza Feltham - TetraLogical Can generative AI help write accessible code? - TetraLogical Meet the team: Steve Faulkner - TetraLogical Meet the team: Gez Lemon - TetraLogical Keyboard accessibility myths and WCAG - TetraLogical Amendment to the Public Sector Accessibility Regulations - TetraLogical What Considerations for TV user interface accessibility - TetraLogical Meet the team: Alistair Duggin - TetraLogical Sticky content: focus in view - TetraLogical The only accessibility specialist in the room - TetraLogical Meet the team: Ian Pouncey - TetraLogical Meet the team: Dean Holden - TetraLogical Meeting WCAG Level AAA - TetraLogical Foundations: accessible names and descriptions - TetraLogical Inclusive XR: accessible augmented reality experiences - TetraLogical Foundations: pointer gestures - TetraLogical Meet the team: Graeme Coleman - TetraLogical Adding sign language to videos - TetraLogical Foundations: introduction to WAI-ARIA - TetraLogical Meet the team: Joe Lamyman - TetraLogical Inclusive XR: accessible 3D experiences - TetraLogical Foundations: visible focus styles - TetraLogical Foundations: target sizes - TetraLogical Meet the team: Henny Swan - TetraLogical Meet the team: Ela Gorla - TetraLogical Foundations: native versus custom components - TetraLogical Foundations: HTML semantics - TetraLogical Accessibility and supporting Internet Explorer - TetraLogical Meet the team: Felicity Miners-Jones - TetraLogical Accessibility and QR codes - TetraLogical Inclusive user research: recruiting participants - TetraLogical Research insight: accessibility of images - TetraLogical Meet the team: Léonie Watson - TetraLogical Android accessibility: roles and TalkBack - TetraLogical Accessible design systems - TetraLogical Meet the team: Patrick H. Lauke - TetraLogical Inclusive user research: analysing findings - TetraLogical How to write user stories for accessibility - TetraLogical Triaging WCAG 2.1 Level AAA - TetraLogical
Why inclusive products are green products - TetraLogical
2025-09-01 · via TetraLogical Blog

Posted on by Ela Gorla in Design and development

Tags: Inclusive Design Principles

More and more organisations are conscious about the environmental impact of their products - both physical or digital - and are trying to make positive changes.

Applying inclusive best practices when designing digital products results not only in more accessible products but also in more sustainable ones.

One of TetraLogical's founding principles is Ethical:

We make decisions for the good of our customers and their customers, our team, and for the world at large.

We also strive to be Sustainable:

We work collaboratively and efficiently to amplify enduring accessibility.

As part of our commitment to being ethical and sustainable, we are constantly looking for long-lasting solutions to reduce our environmental impact for the good of the planet. We are glad to find that more and more of our customers share our dedication to sustainability. While we are not experts on the subject, we can still contribute to their sustainability goals by helping them create inclusive products. This is because inclusive digital products are often green products.

Using the Inclusive Design Principles to build green digital products

When considering digital products and sustainability, many people think of the environmental costs of building, using, and dismantling hardware or the footprint of inefficient code. Few realise the huge impact that design choices can have on the carbon emissions of websites and mobile apps.

The Inclusive Design Principles (IDP) are a set of seven high-level principles that can help create truly inclusive experiences by considering the needs and preferences of all people. As this post illustrates, these principles can also help build greener products.

Here is an overview of how applying each principle can help you reduce your carbon emissions.

Principle 1: Provide comparable experience

Provide comparable experience: Ensure your interface provides a comparable experience for all so people can accomplish tasks in a way that suits their needs without undermining the quality of the content.

The first Inclusive Design Principle invites designers to think about comparable alternatives to content that may not be accessible to all. For example, people who are blind or have a slow Internet connection may not be able to see or load images; people who are Deaf or are in a noisy environment without headphones may not be able to hear audio content. To provide an equitable experience in these two scenarios, provide an alternative, comparable format such as an accurate text descriptions for images or a comprehensive text transcript for audio content. The same applies to documents such as PDFs, animations, and other multimedia content.

A similar requirement is in the Web Sustainable Guidelines being currently developed by the World Wide Web Consortium (W3C). Being larger in size, media content and some downloadable files require a larger amount of energy to load and transmit compared to text-based content. When a text alternative is available, many people may decide to access the alternative instead of playing the multimedia content or downloading the large document. By providing a comparable alternative you will not only ensure everybody has access to information, you'll also potentially reduce your website's carbon footprint.

Principle 2: Consider situation

Consider situation: People use your interface in different situations. Make sure your interface delivers a valuable experience to people regardless of their circumstances.

People are likely to access your digital products on a wide variety of devices and in a variety of situations. For example using a laptop while sitting at a desk, using their smartphone outdoors, or using a smart speaker while cooking.

When designing digital products, ensure they work well across devices, Operating Systems (OSs), screen sizes, and even without a screen!

This greatly helps people with disabilities who may need to use a specific device, assistive technology, or a specific orientation. It also helps reduce e-waste; when products don't work well across all devices (especially older devices) people are forced to replace them, which results in unnecessary and harmful landfill. Furthermore, devices with smaller or no screens consume less energy, which again reduces carbon emissions.

Principle 3: Be consistent

Be consistent: Use familiar conventions and apply them consistently.

Consistency makes digital products easier to use for everybody. When User Interface (UI) components use consistent visuals, labels, and locations people can find and operate them with ease.

Consistency is particularly important for people with permanent, temporary, and situational thinking disabilities, such as people with a brain injury or a migraine.

Better User Experience (UX) generally means less time spent on your website or app, as people are able to complete tasks quicker. The positive environmental impact of this is lower energy consumption. Using existing components, for example from an accessible design system or component library, reduces organisations' carbon emissions as developers won't use additional energy (and time) to write new code. The code of well-established components is also likely to be tidier and more efficient.

Principle 4: Give control

Give control: Ensure people are in control. People should be able to access and interact with content in their preferred way.

Inclusive products support people using assistive technologies and adaptive strategies. Some people may need to navigate a website using a screen reader for example, some may prefer to use a mobile app with an external keyboard, some may choose to customise the way content is displayed.

Other than working well with a wide variety of assistive technologies and input devices (as discussed under Principle 2: Consider situation above), your products must support OSs' and browsers' customisation options. Things like dark themes, larger text, reduced animation, and so on.

Customisation support is a key concept of inclusion - you cannot predict how someone may like or need to access your content, hence your content must adapt and adjust as required.

It can also help you reach your sustainability goals. Many of the customisation options available in OSs and browsers consume less energy than the standard content display. For example, animations can be quite large and require a considerable amount of energy to play. By ensuring your animations pause when reduced motion (or a similar option) is selected in a device's settings, you lower your content's carbon footprint. Similarly, researches have shown that using dark themes in devices with an OLED display has a positive impact on the environment.

Principle 5: Offer choice

Offer choice: Consider providing different ways for people to complete tasks, especially those that are complex or non standard.

People like to do things differently. For example, some people like to use a mouse, others a keyboard, and others voice commands. Some people may find using a search functionality the easiest way to find information on a website, others may prefer to use the navigation menu.

When possible, design alternative ways to complete tasks. This will improve the user experience for many people.

Some of these alternative ways of completing actions may also result in a lower energy consumption. If your service can be accessed both on a visual device (such as a laptop) and on a screenless device (such as a smart speaker), some people will choose to use the screenless device which consumes less energy. If your website contains both a navigation menu and a search functionality, some will use search and find information faster and with less page loading, again consuming less energy overall.

Principle 6: Prioritise content

Prioritise content: Help users focus on core tasks, features, and information by prioritising them within the content and layout.

With so much content on the screen, it is sometimes difficult to focus on the task at hand. This is particularly true for some people with thinking disabilities, such people with ADHD. This is why prioritising content is so important.

When designing pages, prioritise key information and components; decorative images and animations, ads, and other unnecessary content should be limited as much as possible.

A simplified design helps people who may struggle to focus and complete tasks otherwise. It also makes it easier for everybody to understand and find the information and functionality available on a website or app.

Less time spent looking for information or completing a task means less energy used. A clean design also means less data to load, especially when free of heavy media files and animations.

Principle 7: Add value

Add value: Consider the value of features and how they improve the experience for different users.

The last Inclusive Design Principle is all about identifying and using features that can improve people's experience on your website or app.

As mentioned earlier, better UX reduces the amount of time spent trying to complete tasks, which in turn reduces carbon emissions.

As an example, a simple feature you can include when designing a login form is the "Show password" button. This can prevent many people from submitting an incorrect password and having to re-fill the form. Such a simple solution improves the experience for your users and reduces the environmental impact of your website by avoiding unnecessary form reloads.

Summary

Applying inclusive best practices can help you design products that are better for the people and for the planet.

  • Design text-based alternatives for rich media content
  • Ensure your products work well across all devices (older and new), OSs, and screen sizes
  • Use well-known UI components consistently
  • Support OSs and browsers' customisation options
  • Design alternative ways to complete tasks
  • Avoid or limit unnecessary content
  • Include features that can help people complete tasks more efficiently

Further reading

Here are some resources on digital sustainability you may find interesting:

Next steps

For more information on how we can help you create inclusive products, visit our Services page or contact us at hello@tetralogical.com.