Low impact ๐ŸŒฟ

Use a design system to prioritize interface consistency

Design systems allow common components and patterns to be formalized and managed within a website or application. By using such a tool, designers and developers can avoid reinventing existing tooling and thereby reduce wasted time (and emissions).

Actions checklist
  • Design System

    Employ a design system based on web standards and recognizable patterns to mutualize interface components and provide a consistent experience for visitors.

โ˜ž See on W3C

๐Ÿฆพ๐Ÿฆพ

Medium impact ๐ŸŒฟ

Undertake systemic impacts mapping

There are many variables which can impact the user-experience, and a bunch of these can impact how sustainable your website will be. Attempting to identify where you can make a difference to the visitor and give them a more sustainable experience will be beneficial.

Actions checklist
  • External Variables

    List the negative external variables and identify where your product's sustainable impact can be diminished (systemic design).

โ˜ž See on W3C

๐Ÿฆพ๐Ÿฆพ

Medium impact ๐ŸŒฟ

Incorporate usability testing into each minor release cycle

Researching a product or service and how it is used over time allows you to iterate and ensure the features and functionality being offered match how user-needs change over time. Doing so will help you reduce code redundancy further and reduce emissions through optimization.

Actions checklist
  • Usability Testing

    Incorporate usability testing into product cycles and measure the impact of these tests for future releases.

โ˜ž See on W3C

๐Ÿฆพ๐Ÿฆพ

High impact ๐ŸŒฟ

Incorporate compatibility testing into each release cycle

Compatibility is a critical part of the sustainability mindset and should be prioritized through all products and services. If individuals wish to use older devices (or cannot upgrade due to cost), or do not wish to upgrade as frequently, it will reduce the amount of e-waste which enters the system. If something doesn't work, it's also likely to result in visitors suffering a wasted effort or are refused access to your service (and thereby emitting further emissions).

Actions checklist
  • Compatibility Policy

    Establish a policy for compatibility with obsolete devices and software versions, listing the supported devices brands, operating systems, and browsers (including versions).

  • Maintaining Compatibility

    Avoid planned obsolescence in software updates, striving to maintain compatibility for as long as possible and clearly communicating whether an update is evolutionary (large updates that can significantly reduce performance) or corrective (smaller updates that fix bugs or improve security).

  • Frequent Testing

    Regularly test the product or service with weak connections, old browsers, and on devices older than five years to ensure compatibility.

  • Mobile Friendly

    Prototype your interfaces using mobile-first methods to ensure progressive enhancement, content prioritization, and improved accessibility.

  • Progressive Web Application's (PWAs)

    Consider whether a PWA will be more sustainable and compatible over a native mobile application.

โ˜ž See on W3C

๐Ÿฆพ๐Ÿฆพ

Medium impact ๐ŸŒฟ

Use html elements correctly

HTML semantics are important. They don't just play a key role in making the Web look the way it does, they have a function in accessibility, in SEO, and even in sustainability. Ensuring that you markup your content correctly and avoid cluttering your markup wastefully will reduce emissions.

Actions checklist
  • Semantic Code

    Ensure content is marked up semantically using the right HTML element for the right job.

  • Optional Features

    Consider removing optional HTML tags (which aren't required for rendering), attribute quotes, or attributes that are set to their default value.

  • Avoid Non-standard Code

    Avoid using non-standard elements or attributes.

  • Custom Code

    Only use custom elements or Web Components if you cannot utilize native HTML elements or if you need tightly regulated control over the implementation of design system components.

โ˜ž See on W3C

๐Ÿฆพ๐Ÿฆพ

Medium impact ๐ŸŒฟ

Account for stakeholder issues

Brainstorming allows you to flush out ideas before you commit to pursuing a path. Being considerate of not just your visitors but other individuals who may be affected by your product or service (including non-humans, like the environment!) is a useful practical exercise as it may influence your decisions in how you scope your project.

Actions checklist
  • Human-Centered Brainstorming

    In the brainstorming process, consider all stakeholders using a human-centered approach.

  • Ecological Brainstorming

    In the brainstorming process, take the planetary needs and ecological boundaries into account.

โ˜ž See on W3C

๐Ÿฆพ๐Ÿฆพ

Low impact ๐ŸŒฟ

Avoid using deprecated or proprietary code

The Web is full of dead, often proprietary code, created using standards which have been superseded or by groups which aren't recognized. By following recognized coding standards, you ensure that your code will be rendered properly by browsers (and reduce the potential for added emissions occurring from unmaintained rendering processes).

Actions checklist
  • Deprecated Code

    Upgrading or avoiding deprecated formats is important, the only exception being if consumer support demands maintaining older standards to provide a functional product.

  • Outdated Code

    Don't use an older standard if a newer recommendation will do the same job as or more effectively.

โ˜ž See on W3C

๐Ÿฆพ๐Ÿฆพ

Medium impact ๐ŸŒฟ

Provide suitable alternatives to web assets

Media, images, fonts, and documents enrich the Internet. The problem is that people may not want to watch a video, listen to an audio file, look at an image, or use a specific application. By providing alternative formats to anything you embed, you ensure the widest possible audience can benefit from it (and reduced carbon output will occur as alternative text will induce less consumer hardware thrashing than its rich media alternative).

Actions checklist
  • Open Formats

    All proprietary file formats (such as PDF) should also be offered in HTML for accessibility and to ensure future availability.

  • Font Subsetting

    All custom typefaces (using font-display) should be subsetted and offered as part of a font stack with a system font as a backup.

  • Alternative Text

    All images should provide meaningful alternative text for screen reader users (or when images fail to load) accessibility.

  • Audio Alternatives

    Audio should provide text transcripts of conversations as an alternative to playing the media.

  • Video Alternatives

    Video should provide text transcripts (at minimum), subtitles (using WebVTT), and for accessibility best practice, offer closed captions and sign language options.

โ˜ž See on W3C

๐Ÿฆพ๐Ÿฆพ