Medium impact 🌿

Document and share project outputs

Everything produced by designers, developers, writers and those involved with a project should be in an open format, well maintained, and curated in a common format (so everyone is working from the same model).

Actions checklist
  • Deliverables Reusability

    The deliverables output, including documentation, are used upstream of the project and produced in ways that will allow it to be reused in subsequent projects.

  • Deliverables Documentation

    Design functionality and technical specifications are documented so that deliverables are comprehensible by the project team and transferable to the development team.

☞ See on W3C

🦾🦾🦾

Medium impact 🌿

Incorporate value testing into each major release cycle

Occasionally, you may find that features you have developed for a product or service have little to no active users or could be better implemented to bring better value. Undertaking research to identify redundancy allows you to optimize your codebase (and reduce emissions).

Actions checklist
  • Usage Changes

    Consider visitor feedback and monitor adoption and churn rates of product or service features, incorporating insights into future releases.

☞ 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 🌿

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

🦾🦾

Medium impact 🌿

Identify relevant technical indicators

Performance is a key part of the sustainability mindset as reductions in loading times can have a considerable impact on energy loads within CPU, GPU, RAM and hard drive caching (among other variables), as such ensuring a performant product is essential.

Actions checklist
  • Performance Goals

    Set performance goals which impact the environment and performance of the service, for example HTTP requests, or the amount of DOM elements which need to be rendered.

☞ See on W3C

🦾🦾

Medium impact 🌿

Reduce the impact of downloadable or physical documents

Printing or downloading documents can both be a net benefit and a net cost in terms of sustainability as it can reduce repeat requests to websites, but the act of printing (especially when unoptimized) wastes valuable ink and paper.

Actions checklist
  • Printing Documents

    Design documents to limit the printing impact. If the production of paper documents is essential, it should be designed to limit its impact to the lowest possible. Create a CSS Print stylesheet and test it with different types of content. Ensure PDF printing is encouraged over paper-based storage.

  • Optimize Documents

    Offer optimized, compressed documents in a variety of accessible file formats.

  • Optimize Delivery

    If a document is likely to be re-used, generate the document once on the server-side (preferably on a cookie-free domain) rather than forcing the effort to be duplicated.

  • Labels And Choice

    Clearly display the document name, a summary, the file size, and the format, allowing the visitor a choice if possible of both the format, and the language (if not the same as the web page). Furthermore, be sure to avoid embedding the document within Web pages (provide a direct link to download or view within the browser instead).

☞ See on W3C

🦾

Medium impact 🌿

Research non visitor s needs

If you provide physical goods or services, you may also have to account for the sustainability impact of delivery services. This can often be tricky, but courier companies may provide useful tooling to help you identify emissions data for routing.

Actions checklist
  • Non-Human Impact

    Consider and work with non-users and other stakeholders who might be passively impacted by a digital product or service, such as neighbors accepting parcels, traffic jams due to deliveries, etc. Research their needs and understand how they might be affected.

☞ See on W3C

🦾🦾

Medium impact 🌿

Use recognized design patterns

Visitors can identify patterns fairly easily, and they like browsing websites and apps and feeling as if they know what they are dealing with. As such, focusing your efforts on producing a product or service that is clean and has key components in easy-to-recognize locations (and visuals) will allow faster user-experiences and fewer emissions.

Actions checklist
  • Design Patterns

    Provide only essential components visible at the time they are needed. Where appropriate, interfaces should deploy visual styles (patterns) that are easily recognized and used.

☞ See on W3C

🦾