Abstract
The
Web
Sustainability
Guidelines
(
WSG
)
cover
a
wide
range
of
recommendations
to
make
web
products
and
services
more
sustainable.
These
guidelines
use
planetary,
people,
and
prosperity
principles
(the
PPP
approach
)
throughout
the
decision-making
process,
allowing
users
to
minimize
their
environmental
impact
in
various
ways.
These
include
user-centered
design,
performant
web
development,
carbon-free
infrastructure,
sustainable
business
strategy,
and,
supported
by
measurability
data,
various
combinations
thereof.
It
should
be
noted
that
these
guidelines
will
not
address
every
possible
mechanism
or
strategy
to
become
more
sustainable.
These
guidelines,
which
are
notably
web-focused,
should
be
seen
as
the
starting
point
of
a
sustainability
journey
that
may
ultimately
cover
other
areas
beyond
the
current
scope,
for
example
manufacturing
or
shipping
of
physical
products.
Following
these
guidelines
will
often
make
web
content
and
services
more
accessible,
usable,
performant,
and
secure
as
a
by-product.
It
is
highly
recommended
that
you
take
a
methodical
approach
in
applying
these
guidelines.
Rather
than
working
through
the
entire
document
and
broadly
attempting
to
apply
everything
to
your
digital
project
or
service,
scroll
through
the
table
of
contents
to
find
a
guideline
that
appeals
to
your
skill
set
or
that
you
feel
comfortable
in
attempting
to
apply.
Sustainable
change
is
measured
in
progress
over
perfection.
By
breaking
down
the
specification
into
achievable
goals
based
on
clear
guidelines
or
even
success
criteria,
you
can
more
easily
make
progress
toward
long-term
sustainability
targets.
Guideline
examples
and
resources
may
also
provide
implementation
guidance,
while
diverse
benefits
can
help
justify
the
effort
and
commitment
to
management.
Status
of
This
Document
This
is
a
preview
Do
not
attempt
to
implement
this
version
of
the
specification.
Do
not
reference
this
version
as
authoritative
in
any
way.
Instead,
see
https://w3c.github.io/sustainableweb-wsg/
for
the
Editor's
draft.
This
section
describes
the
status
of
this
document
at
the
time
of
its
publication.
A
list
of
current
W3C
publications
and
the
latest
revision
of
this
technical
report
can
be
found
in
the
W3C
standards
and
drafts
index
.
This
document
has
been
reviewed
by
Interest
Group
members
and
interested
parties.
This
is
a
draft
document
which
may
be
updated,
replaced,
or
obsoleted
by
other
documents
at
any
time.
It
is
inappropriate
to
cite
this
document
as
other
than
a
work
in
progress.
The
Interest
Group's
role
in
publishing
is
to
draw
attention
to
the
specification
and
to
promote
its
widespread
deployment.
By
publishing
these
guidelines,
the
Interest
Group
does
not
expect
that
the
work
produced
in
this
specification
will
affect
the
work
undertaken
by
other
W3C
sustainability,
accessibility,
or
performance
groups.
The
Interest
Group
will
continue
to
track
these
Working,
Interest,
and
Community
Groups
as
appropriate.
To
provide
feedback
regarding
this
specification,
the
preferred
method
is
using
GitHub.
It
is
free
to
create
a
GitHub
account
to
file
issues.
A
list
of
issues
filed
as
well
as
archives
of
previous
mailing
list
public-sustainableweb@w3.org
(
archive
)
discussions
are
publicly
available.
There
is
currently
no
preliminary
interoperability
or
implementation
report,
however
one
of
the
key
tasks
of
this
Interest
Group
is
to
examine
the
potential
for
better
models
for
digital
sustainability
that
can
feed
into
tooling
(and
thus
into
large
studies
of
implementations)
that
can
be
reported
upon
and
fed
back
into
guidance
for
the
Web
Sustainability
Guidelines.
This
document
was
published
by
the
Sustainable
Web
Interest
Group
as
a
Group
Note
Draft
using
the
Note
track
.
Group
Note
Drafts
are
not
endorsed
by
W3C
nor
its
Members.
This
is
a
draft
document
and
may
be
updated,
replaced,
or
obsoleted
by
other
documents
at
any
time.
It
is
inappropriate
to
cite
this
document
as
other
than
a
work
in
progress.
The
W3C
Patent
Policy
does
not
carry
any
licensing
requirements
or
commitments
on
this
document.
This
document
is
governed
by
the
18
August
2025
W3C
Process
Document
.
Plain
language
summary
of
Introduction
-
The
Web
Sustainability
Guidelines
(
WSG
)
promote
good
sustainability
best
practices
based
on
the
latest
evidence
and
research.
-
WSG
apply
to
applications,
websites,
and
other
Internet-related
products
and
services.
-
The
guidelines
feature
Success
Criteria
you
MUST
comply
with,
and
provide
additional
information
and
other
deliverables
that
can
help
with
decision-making
and
implementation.
-
Digital
sustainability
is
a
complex
topic,
the
guidance
and
metrics
may
change
over
time,
and
other
considerations
(such
as
non-digital
factors)
and
impacts
beyond
carbon
should
be
accounted
for.
Web
Sustainability
Guidelines
(
WSG
)
define
how
to
make
web
products
and
services
more
sustainable
for
people
and
the
planet
.
Web
sustainability
addresses
more
than
just
environmental
issues
[
VARIABLES
];
intersectional
issues
such
as
accessibility,
privacy,
and
security
can
impact
the
sustainability
of
a
project.
We
have
an
Summary
of
Web
Sustainability
if
you
would
like
to
learn
more
about
the
subject.
The
Interest
Group
considers
that
WSG
incrementally
advances
web
sustainability
in
numerous
areas,
but
underscores
that
not
all
environmental
improvements
are
met
by
these
guidelines
,
as
sustainability
is
an
emerging
field
and
research
gaps
may
exist
in
certain
areas.
These
guidelines
may
make
digital
products
and
services
more
performant,
usable,
and
improve
other
metrics
for
end-users
as
a
by-product
of
being
sustainable.
WSG
may
also
be
helpful
to
comply
with
existing
and
upcoming
worldwide
regulatory
frameworks,
reporting
schemes,
and
compliance
requirements
(
laws
and
policies
).
Web
Sustainability
Guidelines
(
WSG
)
were
developed
in
cooperation
with
individuals
and
organizations
around
the
world.
It
does
so,
intending
to
provide
a
shared
strategy
for
web
sustainability
that
meets
the
needs
of
individuals,
organizations,
and
governments
internationally.
WSG
is
designed
to
apply
broadly
to
different
existing
web
technologies
now
and
in
the
future
and
to
be
testable
with
a
combination
of
automated
testing
and
human
evaluation
.
While
content
within
WSG
has
been
categorized
for
ease
of
readability,
considering
sustainability
impacts
beyond
a
field
of
interest
is
critical
to
increase
awareness
and
collective
action.
Web
sustainability
depends
not
only
on
sustainable
products
and
services
but
also
on
sustainable
web
browsers
and
other
user
agents.
Examples
include
the
performance
of
rendering
and
the
accurate
measuring
of
energy
use
through
developer
tooling.
Authoring
tools
also
have
an
important
role
in
web
sustainability,
by
ensuring
performant
code,
reducing
waste,
and
serving
the
results
in
the
most
sustainable
way
possible.
Coverage
should
not
be
restricted
to
what
falls
within
the
digital
sector.
While
for
this
specification,
we
primarily
focus
on
Internet-related
technologies
and
the
people
and
businesses
that
use
them,
sustainability
concerns
exist
beyond
the
scope
of
this
work,
and
as
such,
the
impacts
of
these
differing
areas
of
concern
should
be
addressed
when
meeting
targets,
reporting,
and
complying
with
relevant
legislation.
Note
The
WSG
was
originally
developed
under
the
guidance
of
the
Sustainable
Web
Design
Community
Group
.
W3C
community
groups
act
as
incubator
hubs
where
ideas
for
new
technologies
and
standards
can
be
discussed
without
formal
constraints.
From
April
2022,
with
the
help
of
over
100
subject
matter
experts
from
around
the
globe,
the
group
created
the
first
draft,
and
subsequently,
through
GitHub
and
regular
meetings
continued
work
over
another
year
to
progress
the
WSG
and
its
deliverables
to
a
level
of
maturity
where
the
group
and
its
work
were
ready
to
become
a
part
of
the
W3C
family
in
October
2024.
The
individuals
and
organizations
that
use
WSG
vary
widely.
To
meet
the
varying
needs
of
this
audience,
several
layers
of
guidance
are
provided,
including
overarching
principles
,
guidelines
,
success
criteria
,
and
additional
information
.
-
Principles
:
At
the
top
are
six
principles
that
provide
the
foundation
for
web
sustainability
:
clean,
efficient,
open,
honest,
regenerative,
and
resilient.
-
Guidelines
:
Under
the
principles
are
guidelines.
These
guidelines
provide
the
overarching
goals
that
implementers
should
work
toward
to
make
products
and
services
more
sustainable.
The
guidelines
provide
the
framework
and
overall
objectives
to
help
implementers
understand
the
success
criteria
against
which
they
are
testable,
and
to
implement
better
digital
solutions.
-
Success
Criteria
:
For
each
guideline,
success
criteria
are
provided
as
testable
achievable
statements
to
fulfill.
Impact
ratings,
where
available
are
also
included
to
assist
with
decision
making.
Details
of
machine
testability
are
provided
with
a
link
to
a
suitable
STAR
technique
.
Links
to
supporting
resources
are
also
included
provided.
-
Additional
Information
:
These
guidelines
come
with
a
list
of
benefits
to
justify
the
adoption
of
success
criteria
with
clients,
colleagues,
and
leadership.
Examples,
examples,
where
possible,
are
also
provided
to
showcase
how
a
success
criteria
within
a
guideline
could
be
addressed.
Tags
are
also
provided
in
order
to
help
individuals
and
tooling
identify
the
relationships
that
occur
between
our
material
and
particular
groups.
All
of
these
layers
of
guidance
(principles,
guidelines,
success
criteria,
and
additional
information)
work
together
to
guide
how
to
make
content
more
sustainable.
Implementers
are
encouraged
to
view
and
apply
all
layers
that
they
are
able
to,
to
make
their
project
as
sustainable
as
it
can
become.
While
great
care
has
been
taken
to
make
these
guidelines
as
well-rounded
and
feature-complete
as
possible,
there
will
likely
be
additional
tasks
implementers
can
perform
to
improve
sustainability
that
this
specification
has
failed
to
address.
Note
This
specification
offers
interactivity.
You
can
filter
and
see
only
the
success
criteria
that
apply
to
your
interests/choices
by
selecting
the
filter
button
in
the
Table
of
Contents
of
the
WSG
.
Your
choices
will
reveal
themselves
upon
selecting
from
the
categories
and
checkboxes.
Most
of
the
filters
align
to
content
you
will
find
within
the
specification
such
as
machine
testability,
GRI
within
Addtional
Information
(material,
energy,
water,
and
emission
levels)
and
tags
(considerations
and
categories),
however,
for
standards,
those
listed
and
mentioned
within
relationships
note
specifications
and
other
bodies
work,
cross-referenced
within
our
resources
document.
The
Web
Sustainability
Guidelines
take
the
role
of
data
and
measurement
seriously.
All
success
criteria
are
evidence
and
best-practice
backed,
where
possible
through
materials
available
in
the
resources
document
.
Alongside
supporting
evidence,
the
Interest
Group
will
offer
a
JSON
API
that
integrates
live
sustainability
impact
scores
within
this
specification.
Methods
of
calculating
impact
alongside
details
of
the
scope
of
measurability,
limitations,
and
labels
used
to
showcase
scores
will
be
available
once
the
Task
Force
concludes
their
work
.
Available
scores
will
be
visible
alongside
success
criteria
and
be
updated
by
the
Interest
Group
as
appropriate.
Editor's
note
WSG
provides
a
crude
reporting
metric
for
reporting
and
compliance
purposes
based
on
the
Global
Reporting
Initiative
(
GRI
).
An
open
source
Jupyter
Notebook
was
created.
As
an
input,
it
takes
a
spreadsheet
containing
all
the
guidelines
and
(using
low,
medium,
or
high)
their
indicators
of
impact
on
the
reduction
of
server
resource
usage,
network
transfer,
and
end-user
device
usage.
Then
it
takes
data
from
a
GreenIT
Report
[
FOOTPRINT
]
which
estimates
the
environmental
impact
of
the
mentioned
categories
across
material
use,
water
use,
energy
use,
and
GHG
emissions.
It
then
combines
these
datasets
and
estimates
the
comparative
impact
of
a
given
recommendation
on
different
sections
of
GRI
taxonomy.
-
Low
-
This
will
have
a
minimal
impact
within
a
particular
category.
-
Medium
-
This
will
have
an
impact
worthy
of
consideration
within
a
particular
category.
-
High
-
This
will
have
a
considerable
impact
within
a
particular
category.
When
the
JSON
API
with
more
accurate
scores
weighted
against
the
GRI
is
published,
the
existing
reporting
metrics
will
be
deprecated
and
replaced.
Until
then,
existing
content
may
remain
in
the
additional
information.
Note
The
body
of
work
and
landscape
WSG
builds
on
is
constantly
evolving.
Some,
typically
referred
to
as
"living"
or
"evergreen"
standards,
are
subject
to
change
frequently,
and
their
impact
on
this
publication's
validity
may
be
immediate.
Others
are
updated
less
regularly,
and
the
changes
may
not
affect
WSG
publications
until
a
new
revision
is
issued.
In
all
cases,
it
is
therefore
prudent
that
implementors
should
regularly
ensure
that
best
practices
have
not
changed
due
to
new
research
or
data
and
that
any
tooling
they
are
using
is
frequently
updated
to
account
for
compliance
changes
occurring
as
a
result
of
more
weighty
evidence
and
guidance.
-
Relationship
to
AFNOR
-
Association
Française
de
Normalisation
is
a
Paris-based
standards
organization
and
a
member
body
for
France
at
the
International
Organization
for
Standardization.
WSG
directly
references
the
AFNOR
SPEC
2201
document,
where
guidelines
may
have
relatable
sustainability
associations.
-
Relationship
to
ARCEP
-
The
Autorité
de
Régulation
des
Communications
Électroniques,
des
Postes
et
de
la
Distribution
de
la
Presse
is
the
regulatory
authority
for
telecommunications
in
France.
Explicit
comparison
notes
from
guidelines
that
match
(for
compliance
purposes),
pointing
to
the
General
Policy
Framework
for
the
Ecodesign
of
Digital
Services
inside
each
WSG
relevant
guideline
reference
section,
have
been
provided.
-
Relationship
to
AWS
and
Microsoft
Azure
WAF
-
Amazon
and
Microsoft
Azure
both
provide
a
Well-Architected
Framework
offering
a
set
of
best
practices
that
help
protect
digital
products
from
consuming
excessive
resources.
Where
sustainability
measures
match
the
evidence
and
guidelines
within
the
WSG
,
cross-links
have
been
placed
within
guideline
resources.
-
Relationship
to
Ethical
Principles
for
Web
Machine
Learning
-
The
W3C
Ethical
Principles
for
Web
Machine
Learning
[
webmachinelearning-ethics
]
discusses
ethical
issues
associated
with
using
Machine
Learning
and
outlines
considerations
for
web
technologies
that
enable
related
use
cases.
As
Artificial
Intelligence
and
related
technologies
play
a
key
role
in
digital
sustainability,
guidance
relating
to
the
subjects
underpinned
by
this
resource
can
be
found
throughout
WSG
.
-
Relationship
to
Ethical
Web
Principles
-
The
W3C
Ethical
Web
Principles
sets
out
ethical
principles
that
the
W3C
are
working
towards
[
ethical-web-principles
].
Within
the
document
is
a
principle
(2.9)
"The
web
is
an
environmentally
sustainable
platform",
this
aligns
with
the
message
with
the
WSG
and
what
the
guidelines
strive
to
achieve.
-
Relationship
to
GR491
-
The
Handbook
of
Sustainable
Design
of
Digital
Services
(also
known
as
GR491
)
is
a
series
of
sustainability
best
practices,
published
by
the
Institute
for
Sustainable
IT.
Like
many
other
best
practice
guides,
where
matching
compliance
targets
can
be
found
to
the
WSG
guidelines
and
success
criteria,
cross-links
in
the
resources
section
have
been
provided.
-
Relationship
to
GreenIT
-
The
GreenIT
Best
practice
guidelines
for
web
eco-design
project
is
an
open
source
French
collaboration
to
provide
meaningful
goals
to
reduce
a
digital
carbon
footprint.
As
there
are
many
parallels
between
WSG
and
the
open
source
GreenIT
project,
guideline
references
note
prior
work
from
this
project
where
it
exists.
-
Relationship
to
GRI
-
The
Global
Reporting
Initiative
is
an
international,
independent
standards
organization
that
helps
organizations
and
individuals
understand
and
communicate
their
sustainability
impact.
As
denoted
in
Additional
information
,
WSG
provides
metrics
relating
to
GRI
Standards
to
offer
more
targeted
guidance
for
regulatory
compliance
goals.
As
our
measurability
improves,
our
results
are
subject
to
change.
-
Relationship
to
Human
rights
and
technical
standard-setting
for
the
Web
-
The
Human
rights
and
technical
standard-setting
for
the
Web
specification
talks
about
the
importance
of
being
considerate
of
peoples
human
rights
when
writing
specifications
[
HR-Spec
].
While
an
unofficial
document,
it
has
a
good
ethical
point
and
the
subjects
held
in
high
importance
(such
as
accessibility,
privacy,
and
security)
are
considered
throughout
the
development
of
WSG
as
having
an
ESG
impact.
-
Relationship
to
Mitigating
Browser
Fingerprinting
in
Web
Specifications
-
W3C
Mitigating
Browser
Fingerprinting
in
Web
Specifications
defines
types
of
fingerprinting
and
considers
how
to
mitigate
the
related
privacy
risks
[
fingerprinting-guidance
].
Because
WSG
contains
several
guidelines
that
can
benefit
sustainability
but
there
may
be
considerations
that
fall
into
the
scope
of
this
field,
the
user
impact
is
being
carefully
considered.
-
Relationship
to
OpQuast
-
OpQuast
is
a
quality
assurance
provider
that
offers
checklists
for
things
such
as
Web
quality
assurance
.
While
many
of
the
improvements
noted
fall
out
of
the
sustainability
scope,
several
directly
relate
to
WSG
success
criteria
or
may
impact
guidelines
as
a
secondary
effect
and
should
be
considered.
As
this
list
is
comprehensive,
items
deemed
of
consequence
are
noted
in
the
resources
section
for
relevant
guidelines.
-
Relationship
to
Privacy
Principles
-
W3C
Privacy
Principles
provides
definitions
for
privacy
and
related
concepts
that
are
applicable
worldwide
as
well
as
a
set
of
privacy
principles
that
should
guide
the
development
of
the
web
as
a
trustworthy
platform
[
privacy-principles
].
Because
several
WSG
guidelines
and
success
criteria
have
privacy
considerations
,
also
connecting
into
security
considerations
,
impacts
(either
to
people
or
the
planet)
are
considered.
-
Relationship
to
SDGs
-
In
2015,
the
United
Nations
Member
States,
as
a
result
of
the
2030
Agenda
for
Sustainable
Development
created
the
Sustainable
Development
Goals
.
While
some
of
these
goals
are
notably
difficult
to
achieve
by
individual
action,
wherever
digital/web
technology
interconnects
with
an
explicit
SDG
target
(and
WSG
could
help
shift
towards
compliance),
the
SDG
target
is
noted
within
the
references
for
each
guideline.
-
Relationship
to
Web
Content
Accessibility
Guidelines
(WCAG)
-
Web
Content
Accessibility
Guidelines
(WCAG)
provides
recommendations
for
making
web
content
more
accessible
[
WCAG
].
As
WSG
contains
accessibility
considerations
due
to
the
social
impacts
of
sustainability
overlapping
with
inclusive
design/development,
the
impacts
of
affected
parties
have
been
taken
into
consideration
whenever
possible.
-
Relationship
to
Web
Platform
Design
Principles
-
W3C
Web
Platform
Design
Principles
contains
a
set
of
design
principles
to
be
used
when
designing
web
platform
technologies
[
design-principles
].
The
WSG
took
it's
recommendations
into
consideration
to
encourage
and
embed
the
methodology
of
using
best
practices
when
implementing
sustainable
solutions.
The
WSG
document
is
designed
to
meet
the
needs
of
those
who
need
a
stable,
referenceable
technical
specification.
Other
documents,
called
supporting
documents,
are
based
on
this
document
and
address
other
important
purposes,
including
techniques
regarding
implementation
strategies,
guiding
implementors
through
the
guidelines
that
apply
to
their
use
case,
and
how
WSG
would
be
applied
to
new
technologies.
Supporting
documents
include:
-
Sustainable
Tooling
And
Reporting
(
STAR
)
-
Implementation
advice
for
specification
writers
covering
sustainability,
alongside
an
evaluation
methodology
for
testing
sustainability
within
a
workflow,
and
a
collection
of
machine-testable
techniques,
each
with
its
own
implementation
test
from
our
test
suite.
-
Benefits
for
WSG
-
These
guidelines
come
with
a
list
of
benefits
across
a
range
of
different
categories
to
justify
the
adoption
of
success
criteria
with
clients,
colleagues,
and
leadership.
-
Resources
for
WSG
-
A
collection
of
citations,
evidence-based
research,
academic
papers,
useful
articles,
implementations,
and
tools,
all
relating
to
digital
sustainability,
categorized
by
WSG
Success
Criteria.
-
Web
Sustainability
Laws
and
Policies
-
A
guide
to
the
laws,
policies,
directives,
standards,
and
best
practices
that
have
coverage
in
the
web
sustainability
sector.
-
Summary
of
Web
Sustainability
-
A
guide
summarizing
the
subject
of
web
sustainability
and
how
the
WSG
can
be
useful
in
addressing
this
concern,
including
some
useful
educational
resources
to
learn
more.
-
WSG
at
a
Glance
-
A
brief
overview
of
the
WSG
and
its
contents,
including
some
highlights
chosen
by
members
of
the
Interest
Group
from
the
WSG
.
-
Quick
Reference
for
WSG
-
A
quick
reference
to
the
WSG
containing
a
print-friendly
PDF
checklist
for
ease
of
working
through
the
guidelines.
See
the
Interest
Groups
GitHub
repository
for
further
supporting
materials,
including
education
resources
relating
to
WSG
.
Additional
resources
covering
topics
such
as
tooling
may
also
be
noted
on
a
case-by-case
basis.
If
you
are
creating
content
and
systems
designed
for
users,
then
whether
you
know
it
or
not,
you
are
working
in
user
experience
(
UX
).
Good
user
experience
reduces
time
and
resources
wasted
on
the
journey.
Poor
user
experience
does
the
opposite,
often
also
harming
accessibility.
Meanwhile,
visual
design
choices
and
how
we
present
information
can
have
some
of
the
biggest
impacts
on
asset
size,
performance,
and
overall
web
sustainability.
Goals
include:
-
Identify
and
regularly
audit
product,
user,
and
user
needs
and
the
related
impacts.
-
Improve
ease
of
access
with
a
clear
information
architecture.
-
Ensure
assets
are
suitable
and
optimized
for
the
lowest
possible
footprint.
Benefits
include:
-
Good
user
experience
amplifies
the
positive
impact
of
your
content.
-
Faster
loading
times
reduce
user
drop-off.
This
can
lead
to,
for
example,
more
sign-ups
and
reduced
cart
abandonment
in
e-commerce.
-
Improved
accessibility,
compatibility,
and
usability
boosts
social
inclusion
and
cohesion.
-
Sustainable
user
experience
design
best
practices
will
often
also
improve
performance
and
SEO
.
Plain
language
summary
of
User
Experience
Design
-
Identify
and
address
issues
affecting
your
service,
audience,
users,
users,
non-users,
and
other
affected
parties.
-
Cultivate
a
lightweight
experience
based
around
well-written
content,
thoughtfully
designed
and
optimized
assets,
and
appropriate
alternatives.
-
Guide
users
quickly
to
their
objectives
with
an
effective
navigation
system
and
layout
using
recognized
patterns.
-
Create,
apply,
document,
and
share
efficient
design
systems
to
reduce
duplication.
-
Enable
accessible
interaction,
using
forms
only
when
necessary.
-
Integrate
regular
audits
and
tests
into
your
project
release
calendar.
Identify,
track,
and
publicly
disclose
negative
external
factors.
Machine-testable
and
Resources
Identify
Anticipate
and
identify
existing
or
potential
negative
external
factors
affecting
a
project.
factors.
Disclose
these
in
a
publicly
available
resource,
identifying
areas
where
digital
sustainability
can
be
improved.
Perform
this
audit
at
the
start
of
your
project
and
at
regular
intervals.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Understanding
the
audience
can
identify
potential
improvements
that
go
beyond
basic
inclusive
design
practices.
Environment:
Constructing
a
plan
to
reduce
emissions
enables
improvement
over
time.
Privacy:
Having
an
overview
of
components
makes
it
easier
to
identify
potential
data
protection
risks.
Social
Equity:
Auditing
factors
can
reveal
factors
not
commonly
understood
or
covered
in
established
best
practices,
enabling
better
support
for
underrepresented
groups.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Accessibility,
Compatibility,
Hardware,
Ideation,
Networking,
Performance,
Reporting,
Research,
Social
Equity,
Software
Understand
the
audience
and
their
requirements,
remove
their
constraints
and
barriers,
and
give
them
an
equal
role
in
decision
making.
Machine-testable
and
Resources
Identify
primary
and
secondary
target
users.
Evaluate
and
define
their
needs
through
quantitative
and/or
qualitative
research,
testing,
or
analytics.
Ensure
your
users
and
affected
communities
are
consistently
and
closely
involved
in
the
research
and
testing
process.
Success
Criterion:
User
constraints
Machine-testable
and
Resources
Account
for
potential
user
constraints,
such
as
the
device
age,
operating
system
choice
or
version,
browser,
Virtual
Private
Network
VPN
use,
and
connection
speeds
when
designing
and
assessing
the
quality
of
user
experiences.
Machine-testable
and
Resources
Conduct
internal
and
user
research
to
identify
whether
a
technical,
material,
or
human
constraint
might
require
adaptations
to
reduce
barriers
or
improve
access
to
content.
Human-testable
and
Resources
Remove
identified
barriers
to
access.
These
can
include
deceptive
design
patterns,
accessibility
issues,
or
other
pain
points.
Success
Criterion:
Seat
at
the
table
Human-testable
and
Resources
Assign
all
involved
parties,
including
users,
an
equitable
role
in
the
decision-making
process
when
undertaking
research,
identifying
needs,
or
iterative
design
work.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Understanding
the
needs
of
your
audience
through
accessibility
and
trauma-informed
research
will
help
you
prioritize
design
improvements
to
boost
accessibility
beyond
the
basics.
Conversion:
Meeting
audience
requirements
increases
the
likelihood
that
they
will
use
it
regularly
and
recommend
it
to
others,
improving
its
adoption
rate
and
reputation.
Economic:
Responding
to
the
needs
of
your
audience
means
they
are
more
likely
to
convert
and
purchase.
Environment:
Undertaking
research
to
identify
real
user
needs
and
behaviour
means
developers
can
avoid
wasting
time,
effort,
and
emissions
on
building
unnecessary
features.
Performance:
Use
user
research
to
identify
UX
bottlenecks
that
cause
user
abandonment.
Fixes
can
be
measured,
tested,
and
evaluated
to
further
improve
performance
and
reduce
emissions
through
removing
those
bottlenecks
and
inefficiencies.
Privacy:
Assessing
user
needs
and
being
minimal
with
further
information
requests
will
help
you
comply
with
privacy
legislation.
Social
Equity:
Improving
UX
with
compatibility
in
mind
means
products
or
services
work
better
for
users
who
might
otherwise
face
various
barriers
to
accessing
content
-
such
as
older
devices,
low-bandwidth
environments,
or
restrictive
territories,
language.
This
reduces
e-waste
and
improves
equity
if
older
equipment
meets
needs
for
longer.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Accessibility,
Compatibility,
Ideation,
Patterns,
Reporting,
KPIs
,
Research,
Social
Equity,
UI
,
Usability
Account
for
non-users
who
may
be
indirectly
affected
by
the
environmental
impact
of
the
project.
Machine-testable
and
Resources
Establish
a
plan
of
action
for
non-users
and
other
affected
parties
who
might
be
indirectly
impacted
by
choices
made
in
e-commerce,
this
can
include
neighbors
accepting
parcels
or
traffic
jams
due
to
deliveries.
Other
examples
include
the
local
health
impacts
of
infrastructure
emissions,
or
supply
chain
pressure.
Research
non-user
needs,
understand
how
they
might
be
affected,
and
consider
ways
negative
effects
could
be
mitigated.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Including
people
who
are
not
primary
or
secondary
users,
such
as
people
with
disabilities,
in
research
means
their
specific
needs
can
be
addressed
more
effectively.
Economic:
Researching
the
entire
ecosystem,
including
the
broader
or
indirect
impact
and
services,
helps
organizations
to
manage
budgets
more
effectively.
Environment:
Making
certain
interventions,
such
as
coordinating
planning
with
suppliers,
can
significantly
reduce
the
environmental
impact
of
a
digital
product
or
service.
Social
Equity:
Including
marginalized
or
excluded
groups
in
the
research
process
makes
it
easier
to
avoid
unintended
consequences
or
requirements
relating
to
these
groups
ahead
of
time.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
E-Waste,
Hardware,
Ideation,
KPIs
,
Marketing,
Reporting,
Research,
Social
Equity,
Usability
Optimize
materials
created
at
every
stage
of
the
process
and
involve
users
in
consider
the
creation
process.
needs
of
and
impact
on
users,
the
planet,
and
other
affected
parties.
Human-testable
and
Resources
Optimize
all
branding
materials
and
assets
approved
during
the
ideation
process
in
line
with
sustainability
best
practices
prior
to
deployment.
This
also
applies
to
brand
refreshes,
rebranding,
and
later
enhancements.
Make
publicly
available
branding
guidelines
detailing
the
sustainability
impact
and
best-practice
deployment
of
materials
and
assets.
Human-testable
and
Resources
Use
wireframes
and
rapid
prototyping
to
quickly
build
consensus,
reduce
risk,
and
reduce
the
number
of
resources
needed
to
build
features.
Evaluate
the
impact
of
all
tools
used.
Human-testable
and
Resources
Use
the
participatory
design
approach
to
involve
users
within
the
iteration
and
design
process.
When
conducting
user
testing,
reach
out
to
your
community
to
help
improve
your
product.
Provide
opportunities
for
users
to
apply
their
knowledge
and
experience
to
your
product
or
service.
Additional
information
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Conversion:
Testing
user
interfaces
usually
leads
to
improved
conversion
rates
as
they
can
be
optimized
accordingly.
This
includes
removing
anything
that
causes
friction
and
designing
content
in
a
way
that
optimizes
user
flow,
reducing
emissions
while
maximizing
conversion.
Economic:
Incorporating
wireframes,
prototypes,
and
user
testing
into
early
product
design
cycles
reduces
money
and
effort
otherwise
wasted
building
features
people
will
not
use.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
GRI
301:
Materials
Low
GRI
302:
Energy
Low
GRI
303:
Water
Low
GRI
305:
Emissions
Low
Tags
Ideation,
Research,
Social
Equity,
Software,
Strategy,
UI
2.5
Find
ways
to
resolve
any
affected
party
issues
prior
to
implementation
Consider
the
needs
of
and
impact
on
users,
the
planet,
and
other
affected
parties.
Human-testable
and
Resources
Use
a
human-centered
approach
during
ideation
to
consider
the
needs,
interests,
and
impact
on
directly
and
indirectly
affected
parties.
Human-testable
and
Resources
Consider
planetary
needs
and
the
environmental
boundaries
during
the
ideation
phase.
This
can
include
creating
non-user,
non-human
(animal,
planet)
personas,
or
climate-specific
user
stories
and
sprints.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Understanding
real-world
accessibility
requirements
in
the
early
development
stages
makes
it
possible
to
prioritize
inclusive
design
throughout
the
entire
lifecycle.
This
improves
efficiency,
as
developers
will
not
be
prompted
to
add
in
accessibility
later.
It
will
also
reduce
emissions
associated
with
the
patching
process.
Environment:
Helping
key
contributors
to
better
understand
the
environmental
impact
makes
it
possible
to
track
and
reduce
that
impact
throughout
the
lifecycle
of
a
project.
Social
Equity:
Accounting
for
the
needs
of
users
who
might
otherwise
face
various
barriers
to
accessing
content
-
on
such
as
older
devices,
in
low-bandwidth
environments,
or
have
other
barriers
to
accessing
information
early
in
the
process
will
reduce
the
need
for
costly
redesigns
or
adding
appropriate
alternatives
at
a
later
date.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Accessibility,
Ideation,
KPIs
,
Research,
Social
Equity,
Strategy
Software,
Strategy,
UI
Use
distraction
and
clutter-free
design,
showing
the
visitor
only
what
they
need
without
interruptions
or
wasted
resource
consumption.
Machine-testable
and
Resources
Make
access
as
simple
and
efficient
as
possible.
Displaying
the
time
required
to
complete
an
action,
reduction
of
choice,
and
ensuring
users
understand
requirements
at
the
start
of
a
journey
can
improve
user
efficiency.
Human-testable
and
Resources
Ensure
user
journeys
are
as
smooth
as
possible.
It
also
helps
to
build
on
established
design
patterns
that
people
already
understand.
Machine-testable
and
Resources
Enable
users
to
complete
tasks
without
distractions
or
non-essential
features
getting
in
the
way.
Machine-testable
and
Resources
Only
show
users
information
that
is
relevant
to
their
experience,
hiding
non-essential
information
from
view.
Machine-testable
and
Resources
Ensure
that
disruptive
actionable
information,
such
as
pop-up
or
modal
windows,
can
only
be
initiated
by
the
user.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Providing
intuitive,
lightweight
user
experiences
improves
understanding
and
accessibility,
especially
for
people
with
cognitive
disabilities.
Reducing
confusion,
this
can
reduce
the
time
spent
trying
to
find
content.
Conversion:
Following
conventions
and
patterns
with
a
clean,
distraction-free
layout
reduces
churn,
page
abandonment,
and
barriers
to
entry.
Economic:
Simplifying
interfaces
by
reducing
the
amount
of
information
can
reduce
the
burden
of
choice
and
help
to
convert
users
during
online
decision-to-purchase
processes.
Reduced
user
choice
will
also
reduce
data
payloads.
Environment:
Streamlining
user
experience
to
remove
barriers
and
the
non-essential
reduces
unnecessary
code
and
content
payloads
and
the
amount
of
time
users
spend
on
their
devices
trying
to
complete
tasks
or
find
information.
This
reduces
the
amount
of
energy
used
and
lowers
emissions.
Performance:
Minimizing
the
amount
of
content
on
screen
to
what
is
genuinely
required
reduces
bandwidth
consumption
over
the
lifecycle
project
and
may
make
the
user
experience
feel
faster.
Privacy:
Hiding
non-essential
features
can
improve
data
protection
by
reducing
overall
data
collection
overall,
especially
that
associated
with
the
integration
of
third-party
services.
Social
Equity:
Reducing
device
and
bandwidth
requirements
through
providing
more
lightweight
experiences
can
improve
work
better
for
users
using
older
devices
or
located
in
low-bandwidth
environments,
and
similar.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Content,
Patterns,
Performance,
Social
Equity,
UI
,
Usability
Use
decorative
design
only
when
it
will
enhance
experiences
rather
than
distracting
or
detracting
from
an
interface.
Machine-testable
and
Resources
Use
decorative
design
only
when
it
enhances
user
experience.
Remove
unnecessary
assets
or
those
that
do
not
enhance
user
experience
or
sustainability.
Alternatively,
make
these
optional
and
disabled
by
default.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Focusing
on
clean
design
can
reduce
the
negative
intrusive
or
distracting
feeling
sometimes
associated
with
decorative
design.
Conversion:
Reducing
complexity
and
heavy
elements
makes
it
more
likely
content
will
load
fast,
which
can
lead
to
higher
conversions.
Environment:
Using
fewer
unnecessary
elements
reduces
the
resources
required
to
render
content.
Performance:
Serving
static
assets,
and
fewer
assets
overall,
can
reduce
the
number
of
requests
and
loading
time
per
page,
improving
performance.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
Assets,
Performance,
UI
,
Usability
Provide
good
information
architecture
that
signposts
visitors
to
what
they
need,
both
human
and
machine,
so
they
can
reach
their
destination
as
efficiently
as
possible.
Machine-testable
and
Resources
Provide
an
accessible,
easy-to-use
navigation
menu
with
search
features
to
help
users
easily
find
what
they
need.
Machine-testable
and
Resources
Consider
implementing
an
efficient
and
regularly
updated
sitemap
for
human
users.
While
guidance
beyond
the
navigation
bar
may
be
unnecessary
for
smaller
projects,
clearly
structured
human-readable
sitemaps
can
improve
accessibility
and
help
users
find
their
way
through
websites
or
other
online
content
with
naturally
complex
or
legacy
information
architecture.
Machine-testable
and
Resources
Implement
lightweight
and
efficient
means
for
users
to
learn
about
new
content
and
services.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Enabling
easier
navigation
makes
content
accessible
to
people
with
disabilities.
Bringing
people
to
their
goal
faster
also
reduces
data
consumption.
Conversion:
Optimizing
structure
can
also
boost
conversion
rates
as
people
are
more
likely
to
find
what
they
need.
The
same
applies
when
users
are
made
aware
of
new
content
related
to
their
interests.
Economic:
Shortening
user
journeys
can
also
reduce
hosting
costs
where
this
is
linked
to
data
transfer.
Environment:
Improving
navigation
and
search
efficiency
can
reduce
the
time
users
spend
finding
what
they
need
and
achieving
their
objectives.
This
also
lowers
emissions.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Low
Tags
Accessibility,
HTML
,
Marketing,
UI
,
Usability
Provide
engagement
that
keeps
the
visitor's
focus
where
it
needs
to
be,
avoiding
anything
that
will
either
reduce
efficiency
or
artificially
prolong
engagement.
Machine-testable
and
Resources
Ensure
users
can
easily
control
how
and
when
they
receive
information,
with
respect
for
their
attention,
focus,
and
mental
energy.
Machine-testable
and
Resources
Prioritize
features
that
assist
rather
than
distract
users,
not
unnecessarily
prolonging
the
time
they
spend
engaging
with
your
content.
Machine-testable
and
Resources
Avoid
using
design
strategies
intended
to
artificially
prolong
user
attention,
such
as
infinite
scroll.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Reducing
unnecessary
barriers
can
improve
accessibility
and
navigation
using
assistive
technologies.
Environment:
Using
pagination
rather
than
infinite
scrolling
allows
individuals
to
request
data
on
demand
rather
than
encouraging
overconsumption.
This
reduces
carbon
impact
while
encouraging
healthy
and
sustainable
browsing
habits.
Performance:
Avoiding
attention
traps
improves
user
experience
by
reducing
the
time
spent
clicking
through,
closing,
or
hiding
these
distractions.
Presenting
the
information
in
less
distracting
ways
makes
the
experience
feel
faster,
reduces
barriers
to
access,
and
improves
user
flow.
Social
Equity:
Preserving
user
focus
on
their
objectives
reduces
the
potential
for
confusion,
mistakes,
and
lapses
in
judgment.
Transparency:
Avoiding
deceptive
patterns
will
boost
trust
and
encourage
users
to
return
or
recommend.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Assets,
Patterns,
UI
,
Usability
2.10
Use
established
design
patterns
and
essential
components
Use
established
and
recognizable
patterns
to
increase
the
efficiency
of
the
user
journey.
Success
Criterion:
Design
patterns
Machine-testable
and
Resources
Display
only
essential
components
at
the
time
they
are
needed.
Where
appropriate,
use
familiar
patterns
to
maximize
ease
of
use.
Additional
information
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Using
established
design
patterns
makes
it
easier
for
all
users
to
understand
how
to
perform
a
task,
especially
those
with
greater
accessibility
needs.
Environment:
Building
using
recognized
design
components
will
reduce
the
amount
of
time
users
spend
trying
to
perform
a
task.
The
less
time
users
spend
achieving
their
goals,
the
lower
their
energy
usage
and
emissions.
Performance:
Using
familiar
design
patterns
that
appear
where
users
expect
and
only
when
appropriate
can
increase
perceived
performance
due
to
more
effective
navigation.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
GRI
301:
Materials
Medium
GRI
302:
Energy
Low
GRI
303:
Water
Medium
GRI
305:
Emissions
Low
Tags
Assets,
CSS
,
Patterns,
UI
,
Usability
Avoid
using
patterns,
content,
tools,
or
techniques
that
may
artificially
manipulate
or
deceive
the
visitor
and
waste
energy.
Machine-testable
and
Resources
Avoid
deceptive
design
or
unethical
coding
techniques
that
manipulate
users
into
taking
actions
that
are
not
in
their
best
interest.
Examples
include
anti-right
click,
copy
prevention,
requiring
an
account
to
purchase,
etc.
Human-testable
and
Resources
Select,
present,
and
label
advertisements
and
sponsorships
transparently
and
only
implement
where
these
provide
economic
and
ethical
value
without
diminishing
user
experience.
Machine-testable
and
Resources
Evaluate
and
remove
unnecessary
or
unused
analytics
and
tracking,
including
any
operating
without
user
consent.
Machine-testable
and
Resources
Focus
on
serving
user
intent
through
non-manipulative
search
and
social
media
optimization.
For
example,
do
not
misuse
coding
practices
intended
to
support
assistive
technologies.
This
can
include
content
with
natural
redundancy,
or
unhelpful
or
low-quality
material
designed
only
to
manipulate
search
results.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Avoiding
deceptive
design
patterns
improves
user
experience
for
people
using
assistive
technologies,
as
these
can
be
especially
disruptive
when
using
a
screen
reader.
This
improves
their
trust
and
access
to
your
content.
Conversion:
Avoiding
deceptive
patterns
can
result
in
fewer
complaints,
reduce
barriers,
and
improve
conversion.
Environment:
Avoiding
deceptive
design
patterns
reduces
energy
consumption
because
users
do
not
waste
time
and
energy
trying
to
undo
choices
they
never
intended
to
make.
Performance:
Using
ethical,
non-disruptive
practices
will
accelerate
the
user
journey
and
perceived
speed
and
reduce
unnecessary
friction.
Privacy:
Ensuring
compliance
with
ethical
privacy
practices
and
avoiding
dark
and
deceptive
patterns
reduces
litigation
risk.
It
also
reduces
data
transmission
between
tracking
and
advertising
services
providers.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Tags
Accessibility,
Assets,
Compatibility,
JavaScript,
JavaScript,
Patterns,
Privacy,
Security,
Social
Equity,
UI
,
Usability
Create
well
documented
deliverables
so
that
future
users
can
find
and
make
use
of
them
without
requiring
assistance
or
expending
unnecessary
time
and
resources.
Machine-testable
and
Resources
Create
deliverables,
including
documentation,
in
ways
that
facilitate
later
reuse.
Machine-testable
and
Resources
Document
functionality
and
technical
specifications
so
that
they
can
be
understood
by
everyone
that
needs
creating
easy
to
use
them.
understand
resources.
Machine-testable
and
Resources
Developers
have
access
to
code
comments
and
have
the
ability
to
view
source
to
make
it
easier
to
access,
understand,
maintain,
and
use
code.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Conversion:
Using
open
and
reusable
formats
lowers
barriers
to
entry,
as
there
will
likely
be
no
cost
involved
in
participation.
It
can
encourage
users
to
play
a
more
active
role
in
the
project.
Economic:
Creating
and
maintaining
good
documentation
will
make
implementation
easier
and
reduce
future
ongoing
costs
associated
with
maintenance.
Environment:
Using
common
and
clear
formats
for
deliverables
will
reduce
the
time
users
need
to
spend
familiarizing
themselves
with
and
adapting
to
the
environment.
This
reduces
the
energy
spent
managing
a
project
and
the
associated
emissions.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Assets,
Content,
Education,
Patterns,
Software
Keep
the
components
of
the
project
as
consistent
and
clear
as
possible
by
using
a
design
system
to
organize
reusable
features.
Machine-testable
and
Resources
Use
a
design
system
based
on
web
standards
and
established
established,
familiar
patterns
to
share
reuse
common
interface
components
and
ensure
a
consistent
user
experience.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Using
a
design
system
with
accessible
components
will
improve
access
to
information
for
people
with
disabilities.
Building
design
features
that
integrate
accessibility
from
the
start
ensures
everyone
is
always
included.
Conversion:
Using
design
systems
supports
consistent
user
interfaces.
This
improves
user
trust
because
individuals
will
recognize
familiar
components
and
know
how
to
use
them.
This
can
improve
conversion
rates
as
it
will
reduce
frustration,
abandonment,
and
possible
complaints.
Economic:
Using
standardized
components
and
avoiding
redundancy
can
reduce
development
time
and
the
associated
costs.
Familiarity
makes
the
experience
easier
for
users,
reducing
bounce
rates.
Environment:
Following
web
standards
to
build
consistent
interfaces
requires
less
energy
and
resources,
because
they
are
naturally
more
optimized.
Design
systems
that
incorporate
environmental
criteria
can
help
to
scale
digital
sustainability
and
reduce
redundancy,
reduced
energy
use
and
negative
impact.
Performance:
Building
design
systems
using
standardized
components
reduces
the
need
for
repeat
coding.
This
reduces
developer
coding
time
and
can
improve
performance.
Overall,
sustainable
patterns
reduce
emissions.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Low
Tags
Assets,
CSS
,
Education,
Patterns,
Strategy,
UI
,
Usability
Provide
content
that
meets
the
needs
of
the
audience,
ensuring
it
is
formatted
for
readability
and
incorporating
SEO
for
visibility.
Machine-testable
and
Resources
Write
content
using
plain
and
inclusive
language,
at
an
appropriate
reading
level
for
your
audience.
Account
for
specific
needs
in
relation
to
accessibility,
native
language,
and
internationalization.
Machine-testable
and
Resources
Use
appropriate
formatting
for
digital
media.
Provide
a
clear
document
structure
with
consideration
of
visual
hierarchy.
Use
headings,
bulleted
lists,
line
spacing,
and
highlights
appropriately.
Provide
information
with
appropriate
formatting
for
the
action
users
need
to
take.
Machine-testable
and
Resources
Prioritize
SEO
from
the
early
design
stages
and
throughout
the
lifecycle
to
ensure
content
can
be
found
and
used.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Using
plain-language
makes
content
easier
to
understand
and
accessible
to
more
users.
Good
structure
that
complies
with
standards
and
expectations
works
better
alongside
assistive
technologies,
such
as
screen
readers.
Conversion:
Writing
and
presenting
authoritative
content
with
intent
and
care
can
lead
to
citation
by
third
parties.
This
can
increase
traffic
with
pre-warmed
leads.
Economic:
Being
recognized
as
an
authoritative
source
can
bring
additional
recognition,
users,
and
opportunities.
Environment:
Ensuring
content
is
easy
to
find
and
comprehend
enables
users
to
make
informed
decisions
faster,
taking
less
time
and
resources.
This
reduces
energy
consumption
and
emissions.
Performance:
Creating
well-structured
content
can
improve
search
performance.
When
content
ranks
higher
in
search
engines,
people
are
more
likely
to
land
in
the
right
place
straight
away.
Social
Equity:
Using
inclusive
language
that
avoids
jargon
and
unnecessary
exclusion
can
improve
user
experience
for
a
broader
audience.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Low
Tags
Accessibility,
Content,
Social
Equity,
UI
,
Usability
Ensure
images,
if
required,
are
optimized,
correctly
formatted,
and
sized,
with
lazy
loading
as
appropriate,
and
are
managed
effectively.
Machine-testable
and
Resources
Do
not
include
images
unless
they
provide
positive
value.
Consider
the
quantity,
format,
and
sizes
required.
Machine-testable
and
Resources
Resize,
optimize,
and
compress
each
image.
Provide
images
in
appropriate
sizes
for
different
screen
resolutions.
Machine-testable
and
Resources
Include
lazy
loading
to
ensure
images
only
load
when
they
are
required.
Machine-testable
and
Resources
Provide
the
option
for
images
to
be
disabled
or
provide
a
low-fidelity
alternative.
Machine-testable
and
Resources
Set
up
a
media
management
and
use
policy
to
reduce
the
overall
impact
of
images.
Include
criteria
for
media
compression
and
file
formats.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Optimizing
resources
means
users
with
data
caps
can
preserve
their
resources.
Providers
can
enjoy
reduced
hosting
costs
due
to
less
data
being
transferred.
Environment:
Compressing
and
delivering
images
in
lightweight
formats
can
reduce
the
hardware
burden
on
older
devices.
This
can
reduce
overall
consumer
e-waste
by
slowing
or
eliminating
forced
upgrade
cycles.
Performance:
Optimizing
images
can
accelerate
performance
by
reducing
HTTP
requests,
data
transfer,
and
the
physical
rendering
effort.
All
of
these
have
an
impact
on
user
experience
and
performance.
Social
Equity:
Providing
lightweight
images
makes
it
easier
for
users
in
low-bandwidth
areas
or
those
using
older
devices
to
access
your
content,
provided
these
devices
can
support
the
formats
used.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Example
<picture>
<source type="image/avif" srcset="image.avif">
<source type="image/webp" srcset="image.webp">
<img width="100px" height="100px" src="image.jpg" alt="" loading="lazy"/>
</picture>
Tags
Assets,
Content,
HTML
,
Performance,
Software,
UI
,
Usability
Ensure
any
animation
deemed
necessary
is
not
overdone
and
that
the
user
can
control
its
ability
to
run.
Human-testable
and
Resources
Use
animation
only
when
it
adds
value
and
not
for
decorative
elements.
Machine-testable
and
Resources
Progressively
display
an
appropriate
number
of
animations
to
avoid
overburdening
the
user
or
negatively
impacting
device
performance.
This
includes
setting
a
maximum
number
of
replays
or
iterations.
Machine-testable
and
Resources
Allow
users
to
start,
stop,
pause,
or
otherwise
control
animated
content.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Environment:
Disabling
and
reducing
animation
to
the
essential,
with
appropriate
optimization
and
user
control,
reduces
rendering
impact
and
associated
emissions.
Performance:
Compressing,
removing,
or
otherwise
reducing
animation
files
reduces
complexity,
improving
performance.
Social
Equity:
Catering
to
different
perspectives
on
and
preferences
in
relation
to
animation
can
improve
acceptance
and
access
for
individuals
using
different
devices
and
from
different
backgrounds.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Example
@media (prefers-reduced-motion: reduce) {
body *,
body *::before,
body *::after {
animation-delay: -1ms !important;
animation-duration: 1ms !important;
animation-iteration-count: 1 !important;
background-attachment: initial !important;
transition-duration: 1ms !important;
transition-delay: -1ms !important;
scroll-behavior: auto !important;
}
}
Tags
Accessibility,
CSS
,
JavaScript,
Performance,
UI
,
Usability
Provide
custom
fonts
in
a
highly
optimized
and
correct
format,
but
with
a
preference
for
pre-installed
typefaces
where
possible.
Machine-testable
and
Resources
Use
pre-installed,
web-safe
typefaces
wherever
possible.
Machine-testable
and
Resources
Limit
the
number
of
fonts
used.
Design
or
subset
fonts
to
omit
unnecessary
or
unused
variations,
such
as
font
weight
or
characters.
Use
the
most
performant
file
format
available.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Environment:
Reducing
the
number
and
complexity
of
custom
fonts
used
reduces
data
transfer
and
rendering
effort,
which
lowers
associated
emissions.
Performance:
Using
optimized
web
fonts
or
system
fonts
supports
a
smoother
user
experience
and
faster
rendering.
Social
Equity:
System
fonts
are
preinstalled
and
are
reliable,
ensuring
content
can
always
be
presented
fast
in
a
font
users
are
familiar
with.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Example
font-family:
-apple-system,
BlinkMacSystemFont,
avenir
next,
avenir,
segoe
ui,
helvetica
neue,
helvetica,
Cantarell,
Ubuntu,
roboto,
noto,
arial,
sans-serif;
Tags
CSS
,
Performance,
UI
,
Usability
2.21
Consider
the
experience
in
non-visual
browsers
and
interfaces
Ensure
visitors
who
access
your
content
using
non-visual
methods
have
an
equal
experience.
Success
Criterion:
Alternative
interactions
Machine-testable
and
Resources
Support
non-visual
browsing
methods
and
various
non-graphical
ways
to
interact
with
content.
This
includes
anything
from
assistive
technologies
to
voice
agents.
Consider
and
provide
working
alternatives
to
visual
interfaces.
Additional
information
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Supporting
non-visual
browsing
methods
means
people
can
access
your
content
more
easily
when
using
specialized
accessibility
aids.
Conversion:
Increasing
compatibility
by
supporting
a
wider
range
of
devices,
beyond
the
most
popular
or
well-known
hardware
and
software,
will
enable
interactions
with
new
audiences
and
increase
the
likelihood
of
a
positive
outcome.
Environment:
Allowing
non-visual
browsers
to
interact
with
your
content
can
help
to
reduce
overall
emissions.
Non-visual
browsers
may
lack
a
display,
which
reduces
the
environmental
impact
of
browsing.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
GRI
301:
Materials
Medium
GRI
302:
Energy
Low
GRI
303:
Water
Medium
GRI
305:
Emissions
Low
Example
code {
background-color: #292a2b;
color: #e6e6e6;
font-family: monospace;
speak: literal-punctuation; /* Reads all punctuation out loud in iOS VoiceOver */
}
Tags
Accessibility,
Compatibility,
Content,
HTML
,
Performance,
Social
Equity,
Software,
UI
,
Usability
Ensure
any
required
notifications
or
alerts
are
clearly
explained
before
activation,
and
that
the
user
can
both
control
and
change
them.
Human-testable
and
Resources
Remove
non-essential
notifications.
Justify
and
reduce
email,
text
message
(
SMS
),
and
other
invasive
or
energy-intense
notifications
to
what
is
strictly
necessary.
Useful
notifications,
such
as
alerts
for
new
content
should
be
used
with
care
and
restraint,
having
both
the
users
understanding
and
informed
consent.
Human-testable
and
Resources
Let
the
user
adjust
their
own
notification
and
messaging
settings.
Ensure
the
options
to
unsubscribe,
log
out,
and
close
an
account
should
be
available
and
visible.
Ensure
it
is
possible
for
the
user
to
change
their
contact
details.
Machine-testable
and
Resources
Clearly
explain
the
result
of
a
potential
input
through
helpful
prompts
and
messages
that
explain
errors,
next
steps,
and
other
relevant
information.
This
will
help
to
manage
user's
expectations.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Signposting
individuals
to
information
through
helpful
notifications
or
error
messages
will
reduce
abandonment.
All
information
must
be
presented
in
a
way
that
does
not
discriminate,
as
this
could
exclude
many
potential
users.
Environment:
Notifying
users
about
important
events
can
reduce
the
need
to
constantly
refresh
pages.
These
notifications
provide
a
shortcut,
ensuring
content
is
loaded
when
it
becomes
available.
This
can
save
emissions.
Privacy:
Using
notifications
appropriately
ensures
personalized
content
is
only
displayed
on
specific
devices,
reducing
the
risk
of
information
exposure.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Low
Example
<form>
<label for="choose">Would you prefer a banana or cherry? (required)</label>
<input id="choose" name="i-like" required />
<button>Submit</button>
</form>
Tags
JavaScript,
Privacy,
UI
,
Usability
Reduce
the
need
for
physical
documents
as
much
as
possible
by
allowing
the
saving
of
well-labeled,
optimized
digital
downloads
and
having
a
print
style
sheet.
Machine-testable
and
Resources
Design
your
process
to
reduce
the
need
for
paper
documents.
Where
the
production
of
paper
documents
is
essential,
it
should
be
designed
to
have
the
lowest
impact
possible.
Include
a
CSS
print
style
sheet
and
test
it
with
different
types
of
content.
Encourage
saving
documents
in
digital
formats
over
paper-based
storage
and
archiving.
Machine-testable
and
Resources
Optimize
and
compress
all
downloadable
documents.
Make
them
available
in
a
variety
of
accessible
file
formats.
Machine-testable
and
Resources
Avoid
duplicating
effort.
If
a
document
will
be
reused,
generate
and
save
it
once
on
the
server
side
for
reuse,
ideally
on
a
cookie-free
domain.
Machine-testable
and
Resources
Display
the
document
name,
a
summary,
the
file
size,
and
the
format
prior
to
downloading.
Allow
users
to
choose
the
right
format
and
language
for
their
needs
where
possible.
Avoid
embedding
documents
directly;
provide
a
link
to
download
or
view
them
within
the
browser
instead.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Providing
a
range
of
inclusively
designed
downloadable
documents
in
a
variety
of
formats
benefits
those
with
accessibility
needs
as
they
can
choose
the
ideal
format
for
their
device
and
use
case.
Environment:
Reducing
the
need
to
print
documents
or
providing
a
print
friendly
style
sheet
reduces
emissions
associated
with
paper,
ink,
and
the
act
of
printing.
Performance:
Compressing
or
otherwise
optimizing
documents
means
they
can
be
downloaded
faster,
avoiding
users
needing
to
wait
to
view
documents
prepared
for
offline
viewing.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Low
Tags
Assets,
Compatibility,
Content,
E-Waste,
Hardware,
Performance,
Software,
UI
,
Usability
Document
how
you
test
new
features
with
real
users
and
validate
the
results,
ensuring
resources
and
training
are
provided
to
maintain
the
project's
viability.
Machine-testable
and
Resources
Outline
processes
used
to
prototype
and
test
new
features,
product
ideas,
and
user
interface
components.
Test
with
real
users
who
represent
different
perspectives
and
user
constraints.
Success
Criterion:
Resourcing
and
viability
Human-testable
and
Resources
Ensure
prototyping
and
testing
processes
are
sufficiently
resourced
to
support
long-term
viability
and
avoid
project
abandonment.
Success
Criterion:
Training
and
onboarding
Human-testable
and
Resources
Produce
or
provide,
training
materials
to
properly
educate
and
onboard
new
contributors.
Success
Criterion:
Testing
and
validation
Human-testable
and
Resources
Conduct
regular
and
extensive
testing
alongside
user
interviews
to
validate
whether
released
features
meet
internal
goals
and
audience
needs.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Conversion:
Using
a
well-built,
thoroughly
tested
interface
is
likely
to
reduce
user
frustration
and
churn.
Economic:
Prioritizing
user
research
in
organizational
policies
helps
to
reduce
and
mitigate
risks
and
costs
associated
with
building
unnecessary
features,
which
would
also
incur
technical
debt.
Performing
iterative
testing
and
prototyping
reduces
the
resources
needed
to
build
new
features.
Environment:
Enabling
users
to
complete
tasks
more
quickly
and
efficiently
reduces
energy
use
and
emissions.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
Accessibility,
Education,
Governance,
Ideation,
Research,
Social
Equity,
Strategy,
UI
,
Usability
Regularly
audit
for
issues
or
problems,
running
tests
at
regular
intervals
in
both
simulated
and
real-world
scenarios
to
ensure
stability
of
the
project.
Machine-testable
and
Resources
Check
the
codebase
for
bugs,
identify
performance
issues,
and
account
for
accessibility
or
security
problems
at
appropriate
regular
intervals,
such
as
every
month
or
quarter.
Machine-testable
and
Resources
Implement
non-regression
tests
for
all
critical
features.
Machine-testable
and
Resources
Incorporate
regression
testing
into
each
release
cycle
to
ensure
new
features
do
not
introduce
bugs
or
otherwise
conflict
with
existing
functionality.
Additional
information
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Maintaining
inclusivity
over
time
through
regular
audits
and
testing
reduces
outages,
improves
access
to
information,
and
creates
a
better
experience
for
all
users,
not
just
those
with
accessibility
needs.
Economic:
Performing
ongoing
regression
testing
improves
security,
which
reduces
risk
and
its
associated
costs.
Environment:
Carrying
out
regular
service
audits
reduces
technical
debt,
which
improves
performance
and
environmental
sustainability.
Regression
analysis
also
supports
continuous
improvement
and
lowers
resource
use
over
time,
which
in
turn
reduces
emissions.
Security:
Auditing
a
product
or
service
regularly
will
identify
potential
sources
of
breaches
and
areas
of
improvement
in
security
and
privacy.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
GRI
301:
Materials
Medium
GRI
302:
Energy
Medium
GRI
303:
Water
Medium
GRI
305:
Emissions
Medium
Tags
Accessibility,
Compatibility,
KPIs
,
Performance,
Privacy,
Reporting,
Research,
Security,
Social
Equity,
Strategy,
UI
,
Usability
2.26
Measure
and
test
for
performance
Check
for
performance
issues
in
both
simulated
and
real-world
scenarios
while
also
accounting
for
compliance
issues.
Machine-testable
and
Resources
Identify
and
resolve
bottlenecks
or
issues
in
the
underlying
code
or
infrastructure
which
could
impact
sustainability
and
performance.
Consider
both
simulated
and
real-world
metrics.
Monitor
performance
across
every
release
cycle
using
appropriate
tooling
or
through
research
and
auditing.
Machine-testable
and
Resources
Collect
only
data
required
to
provide
a
streamlined
and
effective
user
journey
and
comply
with
relevant
accessibility
and
data
protection
legislation.
Put
policies
in
place
to
ensure
strict
adherence.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Conversion:
Increasing
page
load
speed
can
measurably
improve
conversion
rates,
as
users
will
be
less
likely
to
abandon
a
product
or
service
if
the
content
appears
instantaneously.
Economic:
Storing
and
transferring
less
data
reduces
costs
for
content
hosts
and
website
and
application
owners.
Environment:
Improving
performance
of
a
website
or
application
increases
device
longevity,
as
users
will
be
less
compelled
to
upgrade
their
devices.
Performance:
Loading
less
data
improves
performance.
Lighter
pages
are
rendered
and
available
to
users
quicker,
helping
to
improve
the
UX
.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Example
<link
rel="prefetch"
href="/articles/"
as="document">
Tags
Accessibility,
Compatibility,
KPIs
,
Networking,
Performance,
Privacy,
Reporting,
Research,
Security,
Social
Equity,
Software,
Strategy,
UI
,
Usability
Factor
the
ways
people
use
the
project
into
your
decision
making
and
consider
how
this
can
be
optimized
for
both
people
and
the
planet.
Human-testable
and
Resources
Monitor
user
feedback,
adoption,
and
churn
rates
in
relation
to
different
features
and
incorporate
these
insights
into
future
releases.
Additional
information
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Conversion:
Acting
on
feedback
often
improves
conversion
rates
because
it
ensures
that
your
digital
product
or
service
reflects
the
needs
of
your
audience.
Economic:
Avoiding
wasted
development
time
building
features
that
bring
little
value
to
the
consumer
means
resources
can
be
focused
where
they
deliver
more
value.
Environment:
Learning
from
feedback
enables
choices
that
improve
environmental
impact.
An
example
of
this
would
be
making
sure
that
the
most
frequently
used
features
are
placed
higher
in
the
visual
hierarchy.
This
reduces
the
effort
and
time
users
must
invest
to
achieve
their
goals.
Performance:
Performing
user
testing
allows
you
to
retain
focus
on
goal
and
maintain
good
performance
without
unnecessary
complexity.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
GRI
301:
Materials
Medium
GRI
302:
Energy
Medium
GRI
303:
Water
Medium
GRI
305:
Emissions
Medium
Tags
KPIs
,
Research,
Strategy,
Usability
2.28
Verify
that
real-world
users
can
successfully
use
your
work
Run
usability
tests
to
determine
if
the
impact
of
the
project
can
be
further
iterated
to
reduce
friction
points.
Human-testable
and
Resources
Incorporate
extensive
usability
testing
and
user
interviews
into
product
cycles
and
routinely
measure
the
impact
of
these
tests
for
future
releases.
Validate
whether
released
features
meet
internal
goals
and
audience
needs.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Gathering
feedback
from
people
with
disabilities
can
guide
key
improvements.
This
ensures
your
project
can
be
used
by
the
widest
possible
audience.
Environment:
Ensuring
users
can
quickly
and
easily
accomplish
tasks
or
access
information
reduces
the
energy
used
searching
for
answers.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Accessibility,
Education,
Governance,
Ideation,
KPIs
,
Research,
Social
Equity,
Strategy,
UI
,
Usability
Produce
a
regularly
updated
compatibility
policy
that
details
support
levels,
scenarios
tested
against,
and
technology
used
to
benefit
users.
Machine-testable
and
Resources
Establish
and
maintain
a
compatibility
policy
which
covers
current
and
obsolete
devices
and
software
versions,
listing
the
supported
device
brands,
operating
systems,
and
browsers
(including
versions).
Update
this
regularly
in
line
with
new
releases.
Machine-testable
and
Resources
Avoid
planned
obsolescence.
Strive
to
maintain
compatibility
for
as
long
as
possible
and
communicate
clearly
whether
an
update
is
evolutionary,
as
in
large
updates
that
can
significantly
reduce
performance,
or
corrective,
as
in
smaller
updates
that
fix
bugs
or
improve
security.
Machine-testable
and
Resources
Test
performance
Account
for
potential
user
constraints
in
various
scenarios
to
ensure
compatibility.
Testing
should
cover
weak,
unstable,
restricted,
or
slow
connections,
old
browsers,
and
devices
older
than
five
years.
Success
Criterion:
Mobile
friendly
Human-testable
and
Resources
Use
device-adaptable
methods
such
as
responsive
design
and
prototype
interfaces
to
support
progressive
enhancement
Virtual
Private
Network
(
VPN
)
use,
operating
system
choice
or
version,
browser,
and
content
prioritization.
the
device
age.
Machine-testable
and
Resources
Use
a
PWA
over
a
native
mobile
application
if
it
meets
sustainability,
interoperability,
and
compatibility
criteria.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Incorporating
accessibility
into
early
prototypes
ensures
it
remains
a
priority
throughout
the
lifecycle.
Broken
code
can
also
impact
assistive
technologies,
such
as
screen
readers,
and
how
they
describe
content
to
individuals
with
visual
disabilities.
Semantic
code
can
help
to
deliver
an
equal,
error-free
experience
to
all.
Conversion:
Delivering
products
and
services
that
last
longer
and
enjoy
longer-lasting
compatibility
can
increase
conversion
rates,
due
to
the
lower
abandonment
rates
and
a
broader
audience
that
is
able
to
use
a
barrier-free
version
of
the
product
or
service.
Economic:
Saving
time
and
improving
quality
results
in
cost
reductions,
because
increased
stability
reduces
the
need
for
refactoring.
Users
benefit
from
greater
trust
and
potentially
lower
costs
and
maintenance
fees
as
upgrades
may
not
be
required
as
frequently.
Environment:
Avoiding
incompatibility
issues
can
significantly
reduce
e-waste,
with
planned
obsolescence
being
is
one
of
the
biggest
contributors
to
e-waste
worldwide.Extending
lifespans
and
improving
compatibility
within
your
service
plan
can
improve
sustainability
and
slow
the
upgrade
cycle
otherwise
driven
by
sluggish
digital
experiences.
Performance:
Deploying
incompatible
code
has
an
energy
cost.
When
code
is
non-standard,
deprecated
or
does
not
work
on
a
device,
it
can
take
additional
time
to
render
because
it
is
usually
not
optimized
for
the
environment.
This
puts
pressure
on
the
CPU
and
wastes
battery.
Using
modern
web
standards
will
help
your
service
run
reliably
in
modern
browsers.
Social
Equity:
Enhancing
compatibility
and
longevity
helps
to
reduce
the
digital
divide.
This
can
be
significant
in
relation
to
income
inequality,
infrastructure
robustness,
or
accessibility,
for
example.
Broader
support
can
therefore
open
your
work
to
new
markets,
or
extend
the
viability
of
existing
access.
Similarly,
because
progressive
web
applications
use
established
web
standards,
they
are
available
to
more
people
than
more
cost-prohibitive
closed
systems.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
Accessibility,
Compatibility,
KPIs
,
Research,
Security,
Social
Equity,
Software,
Strategy,
UI
,
Usability
Sustainable
web
design
and
development
practices
at
the
front-end
and
back-end
often
intersect
with
best
practices,
unlocking
numerous
benefits
for
people
and
the
planet
alike.
Front-end
and
back-end
web
development
play
a
big
role
in
creating
a
sustainable
web.
The
result
is
code
that
runs
more
efficiently
and
transparently.
Products
are
better
able
to
meet
user
and
user
objectives,
fast,
while
reducing
the
burden
on
hardware
resources.
Sustainable
web
development
offers
scaling
and
wide-reaching
advantages.
Goals
include:
-
Optimize
code
for
sustainability
impact
targets.
-
Maximize
product
and
service
efficiency
to
reduce
hardware
load
and
requirements.
-
Add
and
adapt
technical
features
to
increase
digital
sustainability.
Benefits
include:
-
Sustainable
coding
practices
promote
faster,
more
efficient
code
that
is
easier
to
scale
and
maintain.
-
Similarly,
reducing
client
device
entry
requirements
may
allow
you
to
expand
your
services
to
include
those
using
less
advanced
client
devices.
-
Lower
abandonment
rates
thanks
to
optimized
code
on
both
the
client
and
server-side
means
fewer
errors,
less
downtime,
and
better
user
experience.
-
More
efficient
web
services
inevitably
translate
to
better
performance
and
technical
SEO
,
boosting
search
engine
visibility.
Plain
language
summary
of
Web
Development
-
Optimize
your
project
by
eliminating
unnecessary
or
duplicate
code.
-
Develop
your
project
to
sustainably
meet
the
needs
of
your
audience.
-
Assess
the
necessity
and
quality
of
third-party
services,
dependencies,
and
first-party
code.
-
Eliminate
incorrect
code,
blocking
events,
form
errors,
security
issues,
and
outdated
code.
-
Design
interfaces
to
be
responsive,
and
adaptable
to
different
devices
and
user
preferences.
-
Include
useful
files
expected
by
browsers,
search
engines,
and
other
services.
-
Use
the
latest
version
of
tools
and
software
and
use
native
features
where
able.
Break
down
large
components
into
smaller,
self-contained
pieces
that
can
be
requested
only
when
required
to
save
bandwidth.
Machine-testable
and
Resources
Break
down
bandwidth-heavy
components
into
smaller,
modular
segments
that
can
be
loaded
only
when
required.
This
applies
to
both
front-end
and
back-end
code.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Conversion:
Modularizing
code
can
accelerate
performance,
improving
user
experience
while
reducing
the
chance
of
abandonment.
This
is
especially
impact
for
users
of
low-resource
devices,
such
as
handhelds.
Economic:
Reducing
the
size
of
large
files
will
reduce
bandwidth
expenses
for
service
providers.
Performance:
Using
smaller,
modular
components
allows
for
more
effective
caching
of
commonly
those
reused
components,
while
loading
functions
only
when
required
reduces
the
payload.
Unused
portions
of
a
larger
resource
will
not
be
downloaded,
which
can
have
a
considerable
impact.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Example
link.addEventListener("click", (e) => {
e.preventDefault();
import("/modules/my-module.js")
.then((module) => {
/* Do something */
})
.catch((err) => {
console.error(err.message);
});
});
Tags
CSS
,
JavaScript,
Performance
Clear
out
dead
or
unused
code
as
it
builds
up
in
a
project
to
reduce
the
amount
of
wasted
data
being
transferred.
Machine-testable
and
Resources
Identify
and
eliminate
unused
and
dead
code,
commonly
within
CSS
and
JavaScript.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Eliminating
unused
code
means
reducing
maintenance
work
and
expense.
It
can
otherwise
affect
other
code'
or
add
unnecessary
complexity.
Environment:
Removing
unused
code
eliminates
wasted
bytes,
reducing
download
size
and
potentially
improving
rendering
time.
Performance:
Reducing
downloaded
code
that
otherwise
offers
no
benefit
to
users
frees
up
cache
and
RAM
resources
on
their
devices,
while
saving
time.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Example
export function read(props) { return props.book }
import { read } from 'utilities';
eventHandler
=
(e)
=>
{
read({
book:
e.target.value
})}
Tags
CSS
,
JavaScript,
Performance
Improve
solutions
rather
than
recreating
them,
using
good
organization
strategies
to
simplify
code
where
possible
and
reduce
redundancy.
Human-testable
and
Resources
Remove
duplication
and/or
simplify
and
optimize
your
code
for
better
performance,
focusing
on
essential
features
so
you
have
a
cleaner,
less
redundant
product
and
codebase.
Human-testable
and
Resources
Improve
existing
solutions
rather
than
redeveloping
and
redesigning
products
from
scratch,
since
the
latter
would
duplicate
the
coding
effort
and
maintenance
burden
for
developers
rather
than
reduce
the
learning
burden
for
users.
Machine-testable
and
Resources
Use
organization
methodology
and
systems
such
as
Don't
Repeat
Yourself
(
DRY
)
or
Write
Everything
Twice
(
WET
)
to
optimize
the
arrangement
and
output
of
your
JavaScript
and
CSS
.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Following
naming
conventions
used
in
methodologies
can
be
easier
for
developers
with
accessibility
needs
to
follow
and
use
compared
to
generic
selector
identifiers.
Economic:
Using
an
optimized
and
reusable
codebase
can
enhance
productivity
and
code
quality
leading
to
a
better
return
on
investment.
Environment:
Integrating
certain
methodologies
can
add
code
to
your
markup,
but
they
also
improve
maintainability.
This
reduces
development
time
at
scale,
and
could
reduce
energy
consumption
as
developers
optimized
workflows
will
reduce
the
time
and
energy
spent
on
tasks.
Performance:
Avoiding
repetitive
code
reduces
waste
in
markup,
which
reduces
the
time
it
takes
to
download
site
data.
This
also
reduces
server-side
impact.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Example
.opinions_box {
margin: 0 0 8px 0;
text-align: center;
&__view-more {
text-decoration: underline;
}
&__text-input {
border: 1px solid #ccc;
}
&--is-inactive {
color: gray;
}
}
Tags
CSS
,
JavaScript,
Patterns,
Performance
Avoid
using
large
third-party
libraries
and
frameworks
where
possible,
and
where
these
must
be
used,
self
host,
defer
loading,
allow
the
user
to
object,
and
provide
alternatives.
Machine-testable
and
Resources
Assess
third-party
content
and/or
services
(including
plugins,
widgets,
feeds,
maps,
carousels,
tracking
scripts,
and
more)
as
early
as
possible
in
the
ideation
or
creation
process.
Use
as
few
as
possible,
preferring
lighter,
less
complex
solutions
to
reduce
the
overall
environmental
impact,
including
Scope
3
emissions.
Machine-testable
and
Resources
Use
click-to-load
triggers
based
on
an
import
on
interaction
pattern
to
prevent
automatic
loading
of
third-party
content
and/or
services
(see
above).
Offer
suitable
alternatives
to
third-party
use,
for
example,
a
link
to
a
contact
form
as
an
alternative
to
a
chat
widget.
Success
Criterion:
Libraries
and
frameworks
Machine-testable
and
Resources
Avoid
using
large
libraries
and
frameworks.
Integrate
these
only
when
unable
to
use
a
more
performant
alternative
to
achieve
the
same
goal.
Machine-testable
and
Resources
Prioritize
self-hosted
content
over
embedding
Host
your
content
from
third-party
services.
Success
Criterion:
Avoid
dependencies
Machine-testable
and
Resources
Host
assets,
such
as
icons
and
widgets
widgets,
directly
on
your
own
server,
site
rather
than
relying
on
third-party
services
to
host
and
deliver
these
store,
deliver,
or
embed
third-party
functionality
within
your
project.
those
features.
Machine-testable
and
Resources
Respect
user
preferences
around
the
use
of
third-party
products
and
services,
similar
to
the
implementation
of
cookie
consent
modals.
Provide
mechanisms
to
disable
or
refuse
non-first-party
features
alongside
explanations
of
their
purpose
unless
it
is
possible
to
show
these
third-party
features
are
critical
for
functionality.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Environment:
Replacing
heavy
tooling
and
third-party
services
with
lightweight
tooling
reduces
user
bandwidth
usage
and
compute
impact.
It
does
require
learning
a
new
way
of
doing
things
or
reducing
the
visibility
of
impactful
features
until
they
are
requested.
It
can
significantly
reduce
a
page's
overall
'environmental
impact,
including
the
data
you
have
no
control
over.
This
is
especially
relevant
when
calculating
Scope
3
emissions.
Performance:
Self-hosting
fully
self-contained
services,
features,
and
content
are
more
performant
by
design.
They
avoid
additional
server
and
rendering
requests
or
other
complications
associated
with
third-party
content.
You
can
choose
to
only
include
the
required
features,
further
reducing
overall
bandwidth
usage
and
associated
emissions.
Privacy:
Choosing
not
to
embed
and
automatically
load
third-party
content
may
be
perceived
as
a
privacy
benefit
by
privacy-conscious
users,
because
this
reduces
opportunities
for
their
user
data
to
be
exploited.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Example
<iframe
src="https://example.com"
loading="lazy"
width="600"
height="400"></iframe>
Tags
JavaScript,
Performance,
Privacy,
Security,
Software,
UI
,
Usability
Use
semantic
markup
free
of
optional
or
non-standard
code,
use
the
latest
version
of
technical
specifications,
and
only
using
custom
solutions
when
native
ones
are
insufficient.
Machine-testable
and
Resources
Use
accurate
markup
according
to
the
relevant
standard(s).
Machine-testable
and
Resources
Remove
optional
HTML
elements,
attribute
quotes,
and
default
attributes
only
when
they
do
not
negatively
impact
functionality,
accessibility,
or
readability.
Retain
them
when
they
enhance
accessibility,
maintain
clarity
without
compromising
on
performance,
or
ensure
consistent
browser
rendering.
Machine-testable
and
Resources
Avoid
using
non-standard
HTML
elements
non-standard,
deprecated,
proprietary,
or
attributes.
outdated
formats
and
web
standards.
Only
use
such
code
where
this
is
required
to
meet
a
documented
customer
need
and
if
there
is
a
justifiable
benefit
that
cannot
otherwise
be
met.
Justifiable
reasons
could
include
compatibility
with
essential
legacy
systems
and/or
hardware,
accessibility,
or
emissions
reduction.
Use
polyfills
only
when
necessary,
and
regularly
audit
code
to
see
if
they
can
be
removed.
Human-testable
and
Resources
Prioritize
the
use
of
standard
HTML
elements
and
attributes.
Only
use
custom
elements
or
Web
Components
if
you
cannot
use
native
pre-existing
elements
or
if
you
require
them
for
the
purposes
of
producing
reusable
design
system
components.
Resources
Use
web
platform
features
and
APIs
over
writing
your
own.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Applying
semantic
approaches
means
your
content
will
be
easier
to
navigate
via
assistive
technologies
and
keyboard.
Many
tags
phave
native
semantics,
reducing
the
need
for
additional
tagging.
This
can
also
help
technologies
to
better
understand
your
content.
better.
Conversion:
Ensuring
your
code
is
efficient
and
works
reduces
the
risk
of
broken
features
and
users
giving
up.
Economic:
Conforming
to
accessibility
legislation
and
regulations
avoid
lawsuits
and
fines.
Environment:
Following
standards
ensures
users
have
a
coherent
experience
-
reducing
bugs,
saving
time
spent
fixing
bugs,
and
avoiding
wasted
resources.
Bloated
markup
can
otherwise
lead
to
waste
data,
while
broken
markup
can
even
trigger
memory
leaks.
Performance:
Clean,
modern
code
renders
better
than
deprecated
or
poorly
maintained
code.
While
Web
Components
do
outperform
framework
components,
they
cannot
outperform
the
native
elements
they
are
built
on.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Example
<header></header>
<section>
<article>
<figure>
<img>
<figcaption></figcaption>
</figure>
</article>
</section>
<footer></footer>
<button onclick="window.dialog.showModal();">open dialog</button>
<dialog id="dialog">
<p>I'm a dialog.</p>
<form method="dialog">
<button>Close</button>
</form>
</dialog>
Tags
Accessibility,
Compatibility,
Content,
HTML
,
Social
Equity,
Usability
Avoid
render-blocking
slowdowns
by
asynchronously
loading,
deferring,
or
prioritizing
external
resources
as
appropriate.
Machine-testable
and
Resources
Defer
loading
of
non-essential
external
assets
or
set
these
to
load
asynchronously
to
avoid
a
Flash
Of
Unstyled
Content
(FOUC).
Machine-testable
and
Resources
Where
external
resources
are
required
to
be
used
upon
the
documents
load,
optimize
loading
using
resource
and
priority
hints.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
If
data
is
not
loaded
unless
needed,
you
will
reduce
your
server's
bandwidth
use.
Environment:
Lazy
loading
videos
and
images
so
that
they
are
only
loaded
once
required
by
the
user.
This
reduces
transferred
data
and
the
required
processing
power.
Performance:
Allowing
text
to
render
first
make
the
user
feel
that
everything
is
loading
faster
while,
as
the
remaining
content
loads
in
the
background
or
on
demand.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Example
<img
src="image.png"
loading="lazy"
alt="…"
width="200"
height="200">
Tags
Assets,
CSS
,
JavaScript,
Performance
Ensure
that
search
engines,
as
well
as
accessibility
tooling,
tooling
can
access
a
project
to
reduce
wasted
unnecessary
journeys.
Success
Criterion:
Metadata
and
microdata
Machine-testable
and
Resources
Optimize
and
only
include
suitable
metadata
and
microdata.
Success
Criterion:
Search
engines
Machine-testable
and
Resources
Permit
appropriate
access
to
search
engines
while
blocking
unsustainable
robots
and
scripts.
Machine-testable
and
Resources
Provide
accessibility
and
usability
aids,
such
as
skip
links
and
signposts,
to
help
users
find
and
navigate
content.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Including
skip
links
and
other
accessibility
aids
can
accelerate
the
user
journey,
reducing
system
resources
required
and
allowing
them
to
find
the
content
they
need.
Conversion:
Providing
clearly
navigable
structures
and
sitemaps
ensure
search
engines
are
better
able
to
index
content.
Economic:
Enabling
quicker
visits
that
complete
the
user's
objective
can
help
to
encourage
return
visits.
Environment:
Reducing
the
time
people
spend
searching
for
the
information
they
want
and
aiding
them
on
their
journey
will
reduce
energy
use,
including
battery
drain.
Social
Equity:
Allowing
users
to
achieve
objectives
faster
reduces
resource
consumption
while
potentially
enhancing
user
health
and
well-being.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Example
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://www.example.com/foo.html</loc>
<lastmod>2022-06-04</lastmod>
</url>
</urlset>
<a href="#content">Skip to main content</a>
...
<main id="content">
<h1>Heading</h1>
Tags
Accessibility,
AI,
HTML
,
Marketing,
UI
,
Usability
Use
a
mix
of
carbon-aware
design
techniques
to
adapt
to
different
layouts,
different
modes
of
interaction,
and
also
progressively
enhance
content.
Machine-testable
and
Resources
Allow
Use
responsive
and
adaptive
design
techniques
to
ensure
your
project
to
work
and
adapt
seamlessly
across
a
variety
supports
an
wide
range
of
devices
and
screen
sizes,
including
smartphones,
tablets,
laptops,
desktop
computers,
smart
TVs,
and
other
emerging
platforms.
This
ensures
that
content
and
functionality
can
be
easily
accessed
and
are
suitably
optimized
for
display
on
both
smaller
mobile
devices
and
larger
displays
without
limiting
accessibility,
usability,
or
design
features
on
any
specific
device
type.
Implement
robust
fallback
strategies
to
ensure
that
the
digital
product
or
service
will
not
fail
if
it
encounters
unsupported
technologies.
Machine-testable
and
Resources
Use
progressive
enhancement
to
enhance
overall
sustainability.
This
can
involve
a
single
approach
or
starts
with
baseline
HTML
,
and
increases
the
user
experience
without
reliance
on
style
and
interaction
to
ensure
a
careful
combination,
such
as
adaptive
design,
mobile-first
design,
or
dynamic
serving.
robust
project.
Machine-testable
and
Resources
Use
carbon-aware
design
techniques
to
maximize
your
use
of
carbon-free
energy.
This
is
achieved
by
adapting
the
delivery
of
your
project
to
current
electricity
availability
and
user
grid
load.
This
should
include
using
situational
design
to
reduce
the
codebase
and
disable
non-essential
functionality
during
high-intensity
periods.
Similarly,
it
should
be
possible
to
adapt
the
user
interface
to
perform
better
with
reduced
hardware
resources,
where
this
measure
can
be
taken
to
avoid
scaling
hardware
resources
and
the
resultant
increase
in
emissions.
It
can
also
include
designing
algorithms
that
can
automatically
disable
features
based
on
set
thresholds.
Machine-testable
and
Resources
Support
additional
indirect
non-visual/indirect
methods
of
interaction,
such
as
interaction.
This
includes
assistive
technologies,
voice
(speech),
code
agents,
scanned
input
(
QR
,
etc.),
reader
view
(browser,
application,
or
RSS
),
or
connected
technologies
(watch,
appliance,
transport,
etc.).
devices.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Incorporating
large,
touch-friendly
buttons,
simplified
navigation
menus,
and
clear
readable
fonts
on
your
mobile
websites
can
make
it
easier
for
individuals
with
visual
or
motor
impairments
to
interact
with
your
content.
A
device-adaptable
strategy
that
considers
the
limitations
of
each
approach
helps
to
maximize
accessibility
and
usability
across
all
devices,
enhancing
accessibility
and
optimizing
experience.
Conversion:
Broadening
the
compatibility
of
your
products
and
services
can
equally
broaden
their
appeal
and
use,
even
in
scenarios
you
may
not
have
originally
envisaged.
Economic:
Ensuring
your
website
or
application
works
well
on
desktop
devices,
smartphones,
and
other
resolutions
alike
can
provide
a
financial
benefit
by
enabling
individuals
to
make
purchases
wherever
and
whenever
it
suits
them.
Social
Equity:
Ensuring
content
works
well
on
older
and
low-powered
devices
is
important,
as
these
are
more
frequently
used
in
developing
nations.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Low
Example
@media screen and (min-width: 600px) {
body {
color: red;
}
}
Tags
AI,
Compatibility,
Content,
CSS
,
Performance,
Social
Equity,
UI
,
Usability
Use
JavaScript
in
an
energy-efficient
and
accessible
way,
only
using
APIs
and
making
external
calls
when
this
enhances
a
project's
sustainability.
Machine-testable
and
Resources
Improve
sustainability
through
accessible
and
performant
code.
Machine-testable
and
Resources
Integrate
energy-relevant
APIs
-
such
as
Battery
Status,
Compression
Streams,
Page
Visibility,
or
Vibration
-
where
these
can
reduce
energy
consumption.
Human-testable
and
Resources
Call
client-
or
server-side
APIs
only
when
necessary.
Equally,
ensure
an
API
is
optimized
to
only
send
data
that
is
actually
required.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Conversion:
Creating
fallbacks
for
technology
that
might
fail
can
'enable
sales
you
would
otherwise
miss
out
on.
Economic:
Providing
easier,
reliable
access
in
more
situations
allows
you
to
sell
to
more
people.
Environment:
Reducing
unnecessary
visual
effects
-
such
as
animations
-
when
a
page
is
not
visible,
helps
to
prevent
wasted
processing
in
background
tabs.
This
can
potentially
help
users
who
leave
multiple
tabs
open
conserve
battery.
Performance:
Using
low-impact
scripting
can
reduce
heavy
codebase
sizes.
Providing
fallbacks
for
unavailable
JavaScript
ensures
older
or
less
capable
devices
can
still
access
your
content.
Privacy:
Allowing
script-free
users
to
easily
access
your
content
can
protect
the
privacy
of
users
with
increased
privacy
needs.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Example
const audio = document.querySelector("audio");
// Handle page visibility change:
// - If the page is hidden, pause the video
// - If the page is shown, play the video
document.addEventListener("visibilitychange", () => {
if (document.hidden) {
audio.pause();
} else {
audio.play();
}
});
Tags
Accessibility,
JavaScript,
Security
Regularly
check
code
for
exploitable
security
issues
that
could
affect
both
users
and
hosting
infrastructure.
Machine-testable
and
Resources
Check
scripts
and
associated
code
for
vulnerabilities,
exploits,
header
issues,
and
code
injection.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Preventing
security
issues
ahead
of
time
c
protects
you
and
your
users
from
financial
crime.
Environment:
Securing
your
project
against
threats
and
closing
vulnerabilities
makes
them
a
less
likely
target
for
individuals
who
might
exploit
them,
consuming
vast
amounts
of
data
in
the
process.
Performance:
Protecting
your
project
against
breaches
reduces
your
risk
of
large
amounts
of
data
being
stolen,
corrupted,
or
destroyed.
Security:
Maintaining
security
helps
to
maintain
trust
and
prevent
personal
information
from
being
exposed
and
exploited.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
JavaScript,
Privacy,
Security,
Social
Equity
Use
libraries
and
frameworks
only
where
necessary,
when
vanilla
plain
code
or
smaller
packages
are
inappropriate
for
the
use
case,
and
they
are
kept
up
to
date.
Machine-testable
and
Resources
Prevent
developers
from
downloading
and
installing
libraries
and
frameworks
to
run
client-side
when
they
are
not
needed
by
checking
for
unused
dependencies.
Follow
up
by
uninstalling
those
that
are
not
needed.
Machine-testable
and
Resources
Limit
your
use
of
libraries
and
frameworks
to
the
genuinely
necessary
as
this
will
reduce
the
amount
of
code
that
has
to
be
downloaded
and
parsed
by
the
browser.
Consider
whether
you
can
use
vanilla
plain
code
instead.
Check
the
package
size
and
whether
individual
modules
can
be
installed
and
imported
individually,
individually
or
a
more
performant
alternative
can
be
used
in
its
place,
as
opposed
to
the
entire
library.
Machine-testable
and
Resources
Regularly
check
dependencies
and
keep
them
up
to
date.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Environment:
Removing
code
packages
developers
or
users
do
not
need
reduces
wasted
energy
during
rendering.
Performance:
Reducing
client-side
JavaScript
reduces
rendering
time
and
ensures
a
faster,
smoother
user
experience.
Security:
Keeping
packages
up-to-date
and
using
fewer
third-party
libraries
reduces
the
likelihood
of
security
vulnerabilities.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Example
npm
uninstall
<package-name>
Tags
JavaScript,
Patterns,
Performance,
Privacy,
Security,
Software
Always
provide
expected
files
and
optionally
offer
environmentally
or
otherwise
beneficial
files
to
enhance
the
project.
Machine-testable
and
Resources
Include
favicon.ico,
robots.txt,
opensearch.xml,
site.webmanifest,
and
sitemap.xml
files
by
default.
Also
ensure
that
any
similar
files
defined
in
future
web
standards
or
specifications
are
included.
Machine-testable
and
Resources
Include
beneficial
files
such
as
ads.txt,
carbon.txt,
humans.txt,
security.txt.
Also
ensure
that
any
similar
files
defined
in
future
web
standards
or
specifications
are
included.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Integrating
expected
files
enables
the
browser''s
default
search
box
to
search
a
service,
replacing
any
custom
solution.
This
can
increase
accessibility
as
it
encourages
the
use
of
a
browser-native
component
and/or
keyboard
shortcuts,
which
can
often
better
meet
accessibility
requirements.
Conversion:
Configuring
robots.txt
appropriately
can
help
to
ensure
content
is
correctly
indexed
and
users
are
better
guided
to
appropriate
content
on
your
project.
Economic:
Including
robots.txt
and
sitemap
files
helps
search
engines
to
discover
and
index
your
website.
This
can
lead
to
more
users
and
potentially
more
customers.
The
ads.txt
file
may
reduce
advertising
fraud
and
could
similarly
benefit
your
business.
Environment:
Providing
files
expected
by
search
engines
or
browsers
will
reduce
loading
errors
and
may
improve
efficiency
in
how
users
find
or
interact
with
a
site.
Plain
text
requires
no
rendering.
If
users
or
search
engines
are
able
to
find
these
files,
such
as
carbon.txt,
they
can
load
more
quickly
and
with
less
CPU
/
GPU
impact
than
any
formatted
webpage.
Performance:
Satisfying
requests
for
expected
files
improves
interactions
with
search
engines
or
browsers
requesting
them,
while
also
potentially
avoiding
additional
requests
once
they
are
discovered.
Plain
text
files
contain
no
links,
no
markup,
and
has
a
low
rendering
impact.
Including
details
such
as
site
credits
in
such
a
file
will
reduce
data
transfer
and
have
a
lower
rendering
footprint.
Transparency:
Providing
a
humans.txt
file
allows
you
to
credit
the
people
involved
in
the
creation
process,
while
security.txt
provides
critical
points
of
contact
if
an
issue
is
discovered.
Both
increase
transparency.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Example
User-agent: *
Disallow:
/cgi-bin/
Tags
Assets,
Compatibility,
Marketing,
Patterns,
Security,
UI
3.18
Avoid
using
deprecated,
proprietary,
or
outdated
code
Stick
to
the
latest
version
of
language
specifications
when
coding
unless
you
have
a
documented
need
to
do
otherwise.
Success
Criterion:
Preferred
code
Machine-testable
and
Resources
Avoid
using
deprecated,
proprietary,
or
outdated
formats
and
web
standards.
Always
adopt
up-to-date,
widely
recognized
standards.
Only
use
deprecated,
proprietary,
or
outdated
code
where
this
is
required
to
meet
a
documented
customer
need
and
if
there
is
a
justifiable
benefit
that
cannot
otherwise
be
met.
Justifiable
reasons
could
include
compatibility
with
essential
legacy
systems
and/or
hardware,
accessibility,
or
emissions
reduction.
Use
polyfills
only
when
necessary,
and
regularly
audit
code
to
see
if
they
can
be
removed.
Additional
information
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Using
modern
web
standards
helps
to
ensure
better
support
in
assistive
technologies.
Environment:
Avoiding
deprecated
standards
ensures
your
code
is
optimized
for
and
supported
by
modern
browsers,
ensuring
full
functionality
and
a
smooth
experience.
This
helps
to
reduce
browsing
time
and
associated
energy
use.
Performance:
Moving
on
from
deprecated
or
less
efficient
standards
increases
the
longevity
of
your
digital
product
or
service
and
reduces
the
need
for
a
carbon-intensive
redesign.
Security:
Keeping
up
with
modern
standards
reduces
the
risk
of
security
exploits.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
GRI
301:
Materials
Low
GRI
302:
Energy
Low
GRI
303:
Water
Low
GRI
305:
Emissions
Low
Tags
Accessibility,
Compatibility,
CSS
,
HTML
,
JavaScript,
Performance
Identify
the
project
requirements,
use
the
most
efficient
approach,
aim
for
static
over
dynamic
where
possible,
and
consider
the
impact
of
extensions
and
components.
Machine-testable
and
Resources
Identify
the
requirements
and
use
this
as
a
basis
to
help
you
select
the
most
appropriate
implementation
for
your
project.
A
simpler
technological
implementation
may
use
more
human
resources
but
could
have
a
smaller
footprint.
A
prebuilt
solution
may
use
more
system
resources
and
have
a
bigger
emissions
impact
on
render,
but
it
could
have
a
faster
build
time
-
meaning
less
carbon
is
emitted
in
development.
Human-testable
and
Resources
Use
the
most
effective
approach
for
your
use
case.
Most
of
the
time,
coding
from
scratch
will
often
provide
the
most
performant
results.
Where
an
existing
solution
is
present
and
is
being
actively
maintained,
this
may
be
better
optimized
than
what
you
can
reasonably
produce
yourself.
Favor
native
components
and
file
systems
over
WYSIWYG
editors
-
including
visual
page
builders
-
or
other
heavy
frameworks.
Be
mindful
of
the
impact
of
third-party
solutions.
Human-testable
and
Resources
Deliver
static
in
place
of
dynamic
content
wherever
possible.
If
you
choose
to
use
a
code
generation
tool,
then
favor
the
most
efficient
tool
available,
such
as
Static
Site
Generators
(
SSGs
).
Content
delivered
by
a
dynamic
CMS
will
involve
much
more
server-side
processing
and
uses
bulkier
libraries.
Machine-testable
and
Resources
Carefully
select
and
review
plugins,
extensions,
and
themes
to
maximize
interoperability,
accessibility,
and
performance.
Audit
these
regularly
over
time
to
ensure
continued
compatibility.
Human-testable
and
Resources
Pay
particular
attention
to
user
interface
components
with
respect
to
their
sustainability
impact.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Making
assistive
technologies
a
core
part
of
project
specifications
from
the
very
start
and
throughout
a
product
or
service''s
lifecycle
improves
access
for
people
with
disabilities.
Economic:
Avoiding
tooling
at
risk
of
overburdening
user
experience
may
result
in
financial
savings,
especially
if
tooling
has
associated
maintenance
expenses,
licensing
fees,
or
subscription
costs.
Environment:
Evaluating
long-term
technology
implications
and
taking
the
time
to
ensure
they
are
optimized
and
efficiently
utilized
helps
a
team
measurably
reduce
the
environmental
impact
of
a
product
or
service.
Performance:
Reducing
complexity
in
your
infrastructure
will
increase
developer
productivity,
while
also
reducing
overhead.
This
further
reduces
emissions.
Privacy:
Prioritizing
security
and
user
privacy
helps
an
organization
better
comply
with
current
and
emerging
legislation.
Security:
Maintaining
a
software
product
and
restricting
your
use
of
third-party
solutions
to
the
essential
will
improve
overall
security.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Compatibility,
Ideation,
Performance,
Software,
Strategy
Consider
the
environmental
impact
of
the
chosen
syntax
language,
while
always
ensuring
you
use
the
latest
build
of
any
language
or
framework.
Machine-testable
and
Resources
Use
the
latest
build
of
your
chosen
syntax
language
and
its
coupled
framework.
Human-testable
and
Resources
Use
the
most
appropriate
programming
language
for
the
task.
Many
tools
and
programming
languages
are
optimized
for
the
performance
of
particular
tasks.
Applying
the
most
appropriate
tools
to
the
problem
can
justify
any
time
or
effort
involved
in
their
adoption,
especially
if
there
is
a
reasonable
user
base,
provided
it
does
not
impact
the
wellbeing
of
those
involved
or
risk
becoming
cost-prohibitive.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Using
the
latest
and
more
performant
language
version
can
help
hosting
companies
to
reduce
their
costs.
That
could
be
beneficial
for
the
company
and
customers
alike.
Environment:
Using
the
latest
language
version
can
improve
efficiency
and
reduce
data
center
energy
consumption.
Although
do
verify
that
benefits
are
worthwhile
before
major
build
upgrades.
Performance:
Updating
the
language
version
will
often
offer
performance
improvements.
Compiled
languages,
such
as
C
or
Rust,
can
have
greatly
reduced
execution
times
and
energy
usage
for
algorthims
compared
to
the
same
algorithms
written
in
interpreted
languages,
such
as
Python
or
JavaScript.
Security:
Maintaining
update
and
upgrade
schedules
is
good
for
security,
allowing
you
to
reduce
the
risk
of
security
vulnerabilities
in
older
versions.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Compatibility,
Performance,
Security
3.21
Take
advantage
of
native
features
and
functionality
Use
native
features
and
functionality
that
exist
within
languages
before
constructing
new
ones
that
may
not
be
as
optimized.
Success
Criterion:
Native
over
custom
Machine-testable
and
Resources
Use
native
functions,
APIs
,
and
features
over
writing
your
own.
Additional
information
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Using
existing
features
means
you
do
not
need
to
invest
more
time
in
'development
or
maintenance,
which
reduces
costs.
Environment:
Avoiding
repetition
of
pre-existing
features
improves
efficiency,
which
ultimately
will
reduce
redundancy,
development
time,
and
emissions
associated
with
building
the
product
or
service.
Performance:
Using
browser-native
functionality
and
features
allows
you
to
take
advantage
of
their
natural
optimization.
They
will
generally
load
faster
while
using
fewer
resources.
Custom
components
are
unlikely
to
beat
their
performance.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
GRI
301:
Materials
Medium
GRI
302:
Energy
Medium
GRI
303:
Water
Medium
GRI
305:
Emissions
Medium
Example
<button onclick="window.dialog.showModal();">open dialog</button>
<dialog id="dialog">
<p>I'm a dialog.</p>
<form method="dialog">
<button>Close</button>
</form>
</dialog>
Tags
Compatibility,
CSS
,
HTML
,
JavaScript,
Patterns,
UI
Optimize
any
information
provided
via
databases,
both
in
terms
of
access
schedules
and
how
queries
are
sent
and
received.
Human-testable
and
Resources
Optimize
database
queries,
especially
for
frequently
accessed
information.
If
you
need
information
that
is
stored
in
a
database,
and
you
require
it
or
it
is
likely
to
be
requested
more
than
once
in
your
code,
the
database
should
only
be
accessed
once
and
the
data
stored
locally
for
subsequent
processing.
Avoid
relying
on
framework
helpers
that
might
defer
filtering
to
later
in
the
process.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Optimizing
the
codebase
to
avoid
pushing
multiple
additional
demands
to
the
server
reduces
bandwidth
overheads,
while
also
reducing
the
risk
of
stress
failures
and
lost
business.
Environment:
Filtering
out
unneeded
data
at
a
deeper
level
of
the
application
can
reduce
energy
usage,
as
it
reduces
the
processing
required
for
(de)serialization.
Performance:
Holding
the
data
locally
rather
than
remotely
eliminates
the
need
to
wait
for
additional
requests
to
process
the
query.
Relational
databases
and
other
specialist
data
stores
are
usually
heavily
optimized
for
data
filtering
and
retrieval.
Performing
transformations
at
this
level
of
the
application
creduces
processing
time
and
delivers
responses
faster.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Example
$value
=
get_post_meta(
int
$post_id,
string
$key
=
'',
bool
$single
=
false
):
mixed
Tags
Networking,
Performance
Even
data
has
a
home.
Whether
you
are
developing
tools,
processing
data,
maintaining
online
systems,
operating
websites
or
something
else
-
conscious
choices
in
this
area
can
have
an
enormous
impact.
Sustainable
or
green
web
hosting,
infrastructure,
and
systems
covers
the
energy
our
data
centers
use,
but
it
ultimately
goes
much
further:
It
is
also
about
where
and
what
data
is
processed
or
stored
and
the
technologies
used.
Conscious
provisioning
choices
and
best
practices
can
improve
both
sustainability
and
operational
efficiency.
Goals
include:
-
Find
sustainable
providers
for
hosting,
CDNs
,
and
other
third-party
solutions.
-
Adjust
back-end
settings
to
ensure
proper
caching,
compression,
and
error
handling.
-
Ensure
your
processes
reflect
best
practices
to
maximize
efficiency
and
sustainability.
Benefits
include:
-
Reduced
system
resource
requirements
mean
potential
cost
savings
both
in
hardware
and
in
energy
use.
-
Efficient,
sustainable
hosting,
infrastructure,
and
systems
can
create
new
marketing
opportunities
for
your
business:
impressing
green-minded
or
privacy-driven
customers.
-
Gain
economic
benefits
in
the
form
of
reduced
hardware
investment
and/or
operational
expenses
and
lower
maintenance
costs
thanks
to
better
processes
and
appropriate
provisioning
of
resources.
Plain
language
summary
of
Hosting,
Infrastructure,
and
Systems
-
Select
a
green
hosting
provider
with
a
scalable
plan
that
meets
your
requirements,
in
the
location
where
you
need
it.
-
Optimize
your
files,
while
ensuring
appropriate
file-related
caching
and
error
handling.
-
Automate
processes
and
services
where
and
when
able.
-
Manage
the
processing
and
storage
of
data
with
care.
-
Monitor
the
sustainability
impact
of
projects
using
metrics.
Ensure
hosting
and
domain
service
providers
support
monitoring
of
resource
use,
use
carbon-free
electricity,
and
maintain
and
recycle
equipment
properly.
Machine-testable
and
Resources
Monitor
key
indicators
to
assess
and
transparently
report
the
environmental
impact
of
hosting
and
identify
overconsumption.
These
include
energy
and
water
usage,
but
also
hardware
factors,
such
as
CPU
usage
and
memory
usage.
Similarly,
track
the
allocation
of
servers
and
CPU
cores
to
optimize
resource
efficiency.
Consumers
should
monitor
and
providers
should
both
calculate
and
transparently
share,
environmental
impact
metrics.
Metrics
should
include
Power
Usage
Effectiveness
(
PUE
),
Water
Usage
Effectiveness
(
WUE
),
and
Carbon
Usage
Effectiveness
(
CUE
).
Human-testable
and
Resources
Maintain
hardware
to
extend
its
lifespan
as
long
as
possible.
Use
it
efficiently
at
an
appropriate
capacity,
and
ensuring
it
has
the
necessary
certifications.
New
purchases
should
be
from
reliable
long-lifespan
suppliers.
Success
Criterion:
E-waste
management
Human-testable
and
Resources
Responsibly
recycle
or
upcycle
unwanted
waste.
Materials
should
be
recovered
and
reused,
where
possible,
or
otherwise
disposed
of
appropriately.
Machine-testable
and
Resources
Use
electricity
with
the
lowest
possible
carbon
intensity.
Examine
location-based
emissions
factors
to
calculate
calculate,
in
publicly
available,
evidence-based
documentation,
the
carbon
intensity
of
available
electricity
from
the
regional
grid.
Include
the
impact
of
on-site
electricity
generation,
including
backup
generators,
in
calculations.
Human-testable
and
Resources
Balance
unavoidable
remaining
carbon
emissions
with
high-quality
market
based
instruments
or
other
evolving
instruments
from
the
voluntary
carbon
market,
until
additional
carbon-free
energy
resources
become
available.
The
quality
of
market-based
instruments
should
be
verified
by
non-profit
third-party
organizations
with
sufficient
supporting
evidence.
Machine-testable
and
Resources
The
impact
of
domain
names
is
disclosed
by
registries
and
registrars,
and
registrants
consider
and
(where
possible)
mitigate
against
these
environmental
issues.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Conversion:
In
cases
where
a
badge
or
link
about
sustainable
hosting
providers
appears
on
a
website,
users
concerned
about
the
issue
may
use
and
reuse
the
site
preferentially.
Environment:
Using
hosting
providers
that
operate
with
lower
emissions,
better
power
efficiency,
and
more
responsible
electronic
waste
management
reduces
negative
environmental
impacts
from
websites
and
products.
Social
Equity:
Hosting
providers
with
transparent
environmental
sustainability
are
minimizing
the
negative
impacts
on
their
local
communities.
Transparency:
Sharing
the
efficiency
and
carbon-free
energy
metrics
of
hosting
services
allows
the
public
to
verify
and
understand
sustainable
websites
and
products.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Tags
AI,
E-Waste,
Hardware,
Networking,
Social
Equity
Use
caching
on
all
appropriate
resources,
prioritizing
the
ability
to
use
the
resource
offline
if
possible.
Machine-testable
and
Resources
Use
server-side
caching
where
possible
to
reduce
processing
time
and
repeated
database
lookups
or
API
calls.
Configure
caching
via
server
settings
to
control
file-type
expiration
using
appropriate
headers,
such
as
Expires
or
Cache-Control.
Cache
dynamic
page
responses
where
possible
to
serve
static
versions
to
future
users.
Support
client-side
caching
of
frequently
used
static
assets
to
minimize
repeat
server
requests.
Machine-testable
and
Resources
Ensure
resources
remain
available
and
accessible
even
if
the
user
is
disconnected,
using
methods
such
as
JavaScript
Service
Workers,
Web
Workers,
and
browser
local
storage
features.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Bandwidth
to
serve
users
cost
money
and
reducing
the
amount
of
data
transfer
saves
money.
Environment:
Caching
enables
websites
to
deliver
content
without
unnecessary
server
requests,
sparing
the
carbon
emissions
driven
by
networks
and
the
data
center.
Performance:
Enabling
browser
caching
can
reduce
page
reload
speeds
for
return
users
and
deliver
better
website
performance.
Social
Equity:
Optimizing
browser
caching
often
enables
users
to
view
content
when
their
network
connection
has
failed
or
when
they
must
use
a
low
quality
network.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
High
Example
<IfModule mod_expires.c>
ExpiresActive on
# Default: Fallback
ExpiresDefault "access plus 1 year"
# Specific: Assets
ExpiresByType image/x-icon "access plus 1 week"
ExpiresByType application/rss+xml "access plus 1 hour"
ExpiresByType application/json "access"
</IfModule>
Tags
Assets,
HTML
,
JavaScript,
Networking,
Performance,
Software
Use
compression
on
all
appropriate
resources
either
before
or
as
part
of
the
transfer
process.
Machine-testable
and
Resources
Use
server-side
compression
to
reduce
file
sizes
before
delivery.
Server-side
compression
settings
and
tools
can
be
used
to
compress
most
commonly
used
file
types,
reducing
energy
consumption
while
minimizing
load
times,
saving
bandwidth,
and
improving
overall
performance.
Machine-testable
and
Resources
Use
media
compression
tools
to
reduce
the
file
size
of
images,
videos,
audio,
and
any
other
media
before
uploading
to
a
server.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Environment:
Applying
compression
effectively
reduces
network
demand,
consequently
lowering
power
consumption
and
carbon
emissions.
Performance:
Reducing
data
transfer
volumes
and
data
consumption
delivers
faster
performance
to
all
users.
Social
Equity:
Decreasing
demand
on
networks
enables
users
with
slower
network
connections
to
enjoy
the
same
experience
and
performance
as
users
with
high
speed
networks.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Example
<IfModule mod_deflate.c>
<IfModule mod_setenvif.c>
<IfModule mod_headers.c>
SetEnvIfNoCase ^(Accept-EncodXng|X-cept-Encoding|X{15}|~{15}|-{15})$ ^((gzip|deflate)\s*,?\s*)+|[X~-]{4,13}$ HAVE_Accept-Encoding
RequestHeader append Accept-Encoding "gzip,deflate" env=HAVE_Accept-Encoding
</IfModule>
</IfModule>
<IfModule mod_filter.c>
AddOutputFilterByType DEFLATE "application/atom+xml application/javascript application/json application/ld+json application/manifest+json application/rdf+xml application/rss+xml application/schema+json application/geo+json application/vnd.ms-fontobject application/wasm application/x-font-ttf application/x-javascript application/x-web-app-manifest+json application/xhtml+xml application/xml font/eot font/opentype font/otf font/ttf image/bmp image/svg+xml image/vnd.microsoft.icon image/x-icon text/cache-manifest text/calendar text/css text/html text/javascript text/plain text/markdown text/vcard text/vnd.rim.location.xloc text/vtt text/x-component text/x-cross-domain-policy text/xml"
</IfModule>
<IfModule mod_mime.c>
AddEncoding gzip svgz
</IfModule>
</IfModule>
Tags
Assets,
Networking,
Performance
Use
error
and
redirection
handling
on
projects
to
reduce
the
impact
of
wasted
unnecessary
journeys
or
unhelpful
detours.
Machine-testable
and
Resources
Set
up
proper
error
handling
and
error
pages
to
clearly
inform
users
when
something
goes
wrong,
guide
them
back
to
useful
content,
and
maintain
a
consistent,
trustworthy
experience.
Machine-testable
and
Resources
Regularly
audit
to
check
for
broken
and
outdated
links.
Update
these
as
necessary
and
add
redirects
to
guide
users
and
search
engines
to
the
correct
content
to
ensure
efficient
browsing
and
protect
SEO
value.
Test
all
redirects
to
ensure
they
function
as
intended
and
avoid
impactful
redirect
loops.
Favor
the
most
efficient
redirection
system
for
your
setup
(e.g.,
server
rules
over
database
lookups).
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Error
pages
and
appropriate
redirects
matter
because
every
user
requires
appropriate
assistance
to
find
their
path.
Navigation
and
signage
that
successfully
support
individuals
with
cognitive
disabilities
to
find
their
path
deliver
the
best
design
for
all
users.
Conversion:
Users
who
find
their
way
out
of
an
error
quickly
have
a
faster
and
more
enjoyable
experience
that
encourages
return
visits.
Economic:
Every
page
load
costs
money,
so
minimizing
erroneous
page
loads
saves
money.
Environment:
When
users
load
fewer
pages
on
their
way
to
desired
content,
a
project
becomes
less
carbon
intensive.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Example
ErrorDocument
404
/404.html
Tags
Compatibility,
Content,
Marketing,
Networking,
UI
,
Usability
Reduce
the
number
of
unnecessary
virtualized
environments
to
save
hardware
utilization.
Human-testable
and
Resources
Minimize
the
number
of
active
environments,
including
virtualized
environments
(such
as
containers).
Audit
codebases
for
unused
branches
and
environments
and
remove
them
as
appropriate.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Removing
unnecessary
environments
reduces
the
resources
that
must
be
provisioned.
This
reduces
infrastructure,
maintenance,
and
process
costs.
Environment:
Power
and
energy
resources
will
be
conserved
from
avoiding
utilizing
unnecessary
environments
and
lowering
carbon
emissions
will
result.
Social
Equity:
Scaling
back
the
usage
of
data
centers
reduces
the
need
for
new
facilities
that
may
bring
negative
community
impacts
and
strain
national
resources.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Tags
AI,
Hardware,
Networking,
Performance,
Software
Automate
recurring
tasks
only
where
this
saves
resources,
such
as
scaling
services
to
reduce
consumption
or
handling
suspicious
activity.
Human-testable
and
Resources
Automate
recurring
tasks,
such
as
deployment,
testing,
and
compilation
in
alignment
with
continuous
integration
and
continuous
delivery
best
practices.
Human-testable
and
Resources
Run
automated
tasks
only
when
necessary
to
reduce
unnecessary
resource
utilisation.
Human-testable
and
Resources
Use
automated
scaling
to
promptly
adjust
server
capacity
up
or
down
based
on
demand,
ensuring
efficient
resource
allocation.
Implement
buffering
and
throttling
to
manage
load
and
maintain
performance
without
overprovisioning.
Machine-testable
and
Resources
Restrict
the
activity
of
unwanted
and
unnecessary
third-party
crawlers,
suspicious
user
agents,
unwanted
users,
bots,
and
scrapers
from
accessing
or
downloading
your
content.
Follow
best
practices,
such
as
server
access
rules
and
security
tools,
while
ensuring
your
content
remains
accessible
to
users,
search
engines
and
any
helpful,
welcome
crawlers.
Consider
that
scrapers
may
be
used
to
inform
and
train
large
language
models.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Maximizing
the
number
of
tasks
carried
out
rapidly
by
machine
brings
down
maintenance
and
infrastructure
costs.
Environment:
Optimizing
workflows
can
reduce
the
amount
of
energy
used
during
peak
periods
where
it
may
be
most
costly
or
unsustainable
to
run.
Operations:
Automating
repetitive
tasks
allows
humans
to
focus
on
valuable,
novel,
and
creative
tasks
that
can
offer
greater
job
satisfaction
and
expand
skills.
Security:
Evading
unwanted
bots,
crawlers,
and
similar
users
protects
websites
from
harm
and
avoids
potential
downtime.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Tags
AI,
Performance,
Security,
Software
Decide
when
to
refresh
data
based
on
a
balance
of
user
and
sustainability
considerations.
Machine-testable
and
Resources
Define
the
revalidation
and
refresh
frequency
for
the
cache,
local
data,
and
page
content
based
on
user
needs,
balancing
performance,
data
accuracy,
and
resource
efficiency.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Conversion:
Eliminating
unnecessary
data
refreshes
delivers
a
better
user
experience
that
makes
return
visits
more
likely.
Economic:
Caching
or
simply
not
updating
data
unnecessarily
can
potentially
reduce
costs
by
reducing
the
amount
of
data
transmitted
over
a
network.
Environment:
Minimizing
data
refreshes
reduces
server
and
network
usage,
which
brings
down
power
consumption
and
carbon
emissions
in
turn.
Social
Equity:
Reducing
live
data
refresh
rates
makes
it
easier
for
people
with
limited
or
slow
network
access
to
access
and
use
website
content.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
JavaScript,
Networking,
Performance,
Usability
Back
up
data
at
regular
intervals
to
ensure
that
there
are
failsafes
that
can
be
relied
upon
should
an
issue
occur.
Human-testable
and
Resources
Ensure
backups
of
system
and
user
data
are
secure
and
incremental
to
minimize
storage
use,
reduce
backup
time,
and
protect
against
data
loss
or
breaches.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Using
efficient
backup
processes
that
are
automated
and
include
only
incremental
changes
to
critical
data
results
in
less
storage
being
used,
reducing
costs.
Environment:
Designing
backups
as
efficiently
as
possible
minimizes
power
consumption
and
carbon
emissions
by
eliminating
excess
processes
and
storage.
Performance:
Ensuring
the
availability
of
critical
data
allows
continuation
or
speedier
resumption
of
service
when
problems
occur,
such
as
data
loss
or
outages.
Security:
Keeping
efficient,
stable,
and
well-protected
backups
is
good
practice,
meaning
work,
data,
and
business
value
are
not
irreparably
lost
during
a
data
breach.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Tags
Hardware,
Performance
Account
for
the
energy
involved
in
data
transfer,
considering
factors
such
as
the
protocol
used,
whether
it
is
processed
client-
or
server-side,
and
the
environment
used.
Human-testable
and
Resources
Use
existing
and
supported
carbon-aware
computing
methods
to
automate
batching
and
scheduling
according
to
real-time
electrical
grid
carbon
intensity
data
or
shift
workloads
to
lower-carbon
regions
to
optimize
sustainability
while
maintaining
performance.
Machine-testable
and
Resources
Choose
communication
protocols
appropriate
to
user
needs
and
the
type
of
data
being
transferred.
Avoid
insecure
options
such
as
HTTP
and
FTP
,
and
prioritize
secure,
efficient
alternatives
such
as
HTTPS
and
SSH
.
Use
modern
protocols
to
take
advantage
of
newer
features,
while
maintaining
backward
compatibility
for
older
devices.
Human-testable
and
Resources
Consider
using
event-driven
architecture
and
microservices
when
building
products
with
state
changes
that
do
not
require
full
page
refreshes.
Favor
these
where
they
offer
a
more
energy-efficient
alternative
to
traditional
APIs
based
on
performance,
power,
and
processing
factors.
Choose
the
approach
that
reduces
server
workload
and
environmental
impact.
Human-testable
and
Resources
Avoid
redundant
processing.
When
data
processing
is
necessary,
carefully
compare
the
relative
effects
of
client-
versus
server-side
processing
based
on
efficiency,
performance,
security,
and
sustainability
metrics
to
make
an
informed
decision.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Improving
the
efficiency
of
data
processing
saves
money
due
to
energy
and
infrastructure
needs.
Environment:
Running
servers
for
less
time
reduces
carbon
emissions.
Performance:
Processing
data
in
energy
efficient
batches
can
reduce
thrashing
of
hardware
during
high-intensity
periods,
maintaining
performance
stability.
Social
Equity:
Reducing
data
processing
demand
means
the
resources
that
data
centres
demand,
and
can
place
a
strain
on
local
communities
can
also
be
reduced.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Tags
AI,
JavaScript,
Networking,
Performance
Use
CDNs
where
they
bring
a
sustainability
benefit,
ensuring
the
provider
itself
is
sustainable,
has
nodes
local
to
an
audience,
and
they
are
only
used
to
serve
static
resources
on
them.
Machine-testable
and
Resources
Deploy
static
content,
assets,
and
other
read-only
resources
via
a
Content
Delivery
Network
(
CDN
)
on
a
case-by-case
basis,
where
judged
to
be
beneficial.
Carefully
evaluate
the
environmental
impact
of
any
CDN
service
used,
similar
to
a
web
hosting
provider.
Machine-testable
and
Resources
Select
CDN
providers
that
make
commitments
to
sustainability
and
report
on
their
progress.
Machine-testable
and
Resources
When
serving
an
exclusively
local
audience,
consider
whether
a
CDN
is
required
at
all.
Instead,
select
hosting
providers
with
servers
close
to
your
target
audience.
Machine-testable
and
Resources
Avoid
deploying
dynamic
or
frequently
changing
resources
to
a
CDN
.
Browser
behaviors
such
as
cache
partitioning
and
cross-origin
resource
sharing
(
CORS
)
can
limit
performance
gains,
hinder
caching
and
interaction,
and
attempting
to
override
these
can
introduce
security
or
privacy
risks.
This
does
not
apply
to
static
assets
or
JSON
files,
which
are
well
suited
to
CDN
delivery.
Human-testable
and
Resources
Perform
data
transformations,
transfers,
and
processing
between
the
layers
of
an
application
as
close
to
the
source
as
possible.
This
reduces
unnecessary
serialization
overhead
and
avoids
wasting
resources.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Using
a
CDN
may
save
money
because
their
data
transfer
rates
are
often
cheaper
than
hosting
providers.
Environment:
Using
a
CDN
to
host
content
closer
to
users
lowers
network-related
carbon
emissions
while
also
reducing
user
device
energy
use
because
they
can
load
content
more
quickly.
Performance:
Using
a
CDN
to
locate
content
closer
to
users
gives
them
faster
access
to
content.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Medium
Tags
AI,
Content,
Hardware,
Networking,
Performance
Maintain
the
infrastructure
you
require
rather
than
over-provisioning
and
autoscale
to
meet
demand
instead
to
preserve
hardware
resources.
Human-testable
and
Resources
Select
infrastructure
that
meets
your
requirements
and
customer
agreements
without
over-provisioning.
Favor
standalone
instances
over
multi-zone
or
distributed
setups
when
requirements
allow.
Provision
for
average
loads
rather
than
peaks
to
ensure
efficient
resource
use.
Use
autoscaling
to
handle
fluctuations
without
underutilizing
infrastructure.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Environment:
Reducing
provisioned
resources
reduces
wasted
energy
and
water
costs,
even
when
resources
are
not
used
to
capacity.
Operations:
Keeping
a
closer
eye
on
actual
and
anticipated
use
allows
an
organization
to
better
understand
its
own
functions
and
anticipate
future
needs.
Economic:
Avoiding
overprovisioning
means
avoiding
unnecessary
costs.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Tags
E-Waste,
Hardware,
Performance
Set
expiration
dates
on
data
so
it
can
be
archived,
made
available
offline,
or
removed
when
no
longer
used
or
required,
with
the
remaining
content
tagged
for
future
management.
Human-testable
and
Resources
Regularly
audit
for
and
delete
redundant,
abandoned,
or
single-use
data
-
often
referred
to
as
dark
data
-
to
reduce
storage
demand
and
energy
use.
Machine-testable
and
Resources
Assign
expiration
and/or
maximum
retention
dates
to
stored
data
where
appropriate,
treating
excess
data
as
a
form
of
technical
debt.
Simultaneously
observe
any
applicable
minimum
data
retention
periods.
Make
data
cleanup
an
established
organization-wide
routine
to
prevent
long-term
data
accumulation.
Machine-testable
and
Resources
Implement
a
data
classification
and
tagging
policy
to
improve
visibility,
simplify
management,
and
enable
efficient
removal
of
outdated
or
unused
data.
Human-testable
and
Resources
Store
data
only
when
it
cannot
be
easily
or
accurately
regenerated.
Machine-testable
and
Resources
Optimize
log
collection
and
storage
by
scheduling
backups
during
low-activity
hours,
rotating
logs
appropriately,
and
using
off-site,
sustainable
providers.
Human-testable
and
Resources
Make
large,
long-term
assets
available
for
easy
download
in
order
to
provide
users
with
regular
offline
access
without
requiring
persistant
server
resources.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Storing
less
data
reduces
the
expense
of
operating
excessively
large
storage
and
archiving
systems.
Environment:
Reducing
data
storage
brings
down
the
carbon
emissions
driven
by
storage
system
operation.
Security:
Storing
smaller
amounts
of
data
reduces
the
amount
of
data
exposed
to
potential
security
issues
and
reduces
monitoring
effort.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Example
Accept-Encoding:
zstd,
gzip,
br,
deflate
Tags
Content,
E-Waste,
Hardware,
Performance,
Privacy
Designing
websites
and
applications
for
better
sustainability
requires
good
business
strategy
and
product
management.
Anyone
who
owns,
manages,
or
operates
a
website
or
application
has
significant
capacity
to
improve
the
sustainability
footprint
of
their
organization.
Business
owners
and
other
C-level
executives
are
likely
to
be
the
main
people
responsible
for
the
most
impactful
strategic
decisions
an
organization
can
make.
But
all
individuals
working
online
can
also
make
a
big
difference.
Work
in
this
area
can
improve
the
sustainability
of
various
non-technical
considerations
that
stretch
beyond,
or
affect,
a
digital
product
or
service.
Goals
include:
-
Use
your
influence
to
ensure
projects
are
developed
more
sustainably,
at
scale,
across
organizations
of
different
sizes.
-
Raise
awareness
while
publicly
disclosing
and
reporting
on
your
efforts.
-
Support
your
organization
from
within
to
ensure
it
and
its
staff
are
better
able
to
meet
relevant
targets.
Benefits
include:
-
Proper
evaluation
and
reporting
make
it
easier
to
meet
compliance
targets,
comply
with
legislation,
and
avoid
the
risk
of
potential
lawsuits.
-
Transparency
about
your
sustainability
impact
can
improve
public
perception
of
your
company.
This
can
boost
customer
loyalty
and
staff
retention
alike
-
reducing
associated
costs.
-
Clear
policies
and
continuity
planning
build
trust
in
your
organization,
while
providing
the
opportunity
to
identify
quantifiable
risks
and
include
relevant
affected
parties.
-
Appreciating
users'
time
and
resources
can
improve
trust
in
a
product
or
organization.
Plain
language
summary
of
Business
Strategy
and
Product
Management
-
Plan,
create,
and
maintain
policies
and
statements
to
cover
sustainability
initiatives.
-
Appoint
someone
to
take
responsibility
for
sustainability.
Inform
and
train
others.
-
Make
efforts
to
understand
your
impact.
Set
goals
and
targets.
Report,
verify,
and
disclose
your
progress.
-
If
a
project
is
necessary,
document
its
evolution
and
manage
its
lifespan.
-
Share
benefits
with
your
workers.
Involve
all
relevant
affected
parties
in
the
decision-making
process.
-
Be
ethical
in
your
approach
to
sensitive
materials,
including
data,
or
emerging
technologies,
such
as
AI.
-
Be
an
inclusive
workplace.
-
Give
back
to
good
causes
and
support
open-source
initiatives
Produce
policies
and
documents
showcasing
evidence,
achievements,
and
onboarding
underpinned
by
good
governance.
Machine-testable
and
Resources
Develop,
publish
and
maintain
key
policies,
such
as
a
code
of
ethics,
product
guidelines,
sustainability
statements,
and/or
other
documents
that
include
language
specific
to
digital
products,
services,
policies,
and
programs.
Make
these
publicly
accessible
and
transparently
versioned
formats.
Machine-testable
and
Resources
Publish
achievements,
features,
compliance,
and
anything
beyond
the
scope
of
these
guidelines
within
a
dedicated
sustainability
section.
Human-testable
and
Resources
Provide
evidence
to
demonstrate
how
digital
sustainability
policies,
climate
policies,
and
related
practices
are
effectively
implemented,
monitored,
and
governed
over
time.
Human-testable
and
Resources
Provide
training
decks
Advocate
for
and
workshops
comply
with
responsible
legislation
that
supports
employment
rights,
transparency,
and
accountability
related
to
support
onboarding
new
team
members
sharing
economic
benefits,
along
with
policies
that
impact
your
organization
in
relation
to
sustainable
product
strategies.
Success
Criterion:
Documentation
Machine-testable
and
Resources
Document
your
methodology
through
impact
storytelling,
documentation,
and
creating
resources
to
help
individuals
make
more
informed
decisions
and
raise
awareness
among
your
users.
Success
Criterion:
Carbon-free
evidence
Machine-testable
and
Resources
Demonstrate
how
emerging
technologies
and/or
digital
products
and
services
are
powered
using
carbon-free
energy.
sustainability.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Communicating
the
ways
you
can
share
the
economic
benefits
of
your
digital
work
raises
awareness
of
social
inequalities.
Similarly,
enabling
users
to
make
more
informed
decisions
can
ensure
your
project
is
more
financially
sustainable
overall.
Environment:
Establishing
clear
sustainability
statements
should
make
it
easier
to
align
organizational
policies
and
practices
with
measurable
metrics
and
support
goals.
Integrating
this
early
in
the
digital
product
strategy
can
improve
efficiency
and
reduce
environmental
impact.
Operations:
Establishing
ethical
and
sustainability
policies
can
help
to
ensure
product
teams
are
more
engaged
in
the
work
they
are
doing.
Privacy:
Reducing
your
emissions
and
explaining
to
your
audience
how
you
aim
to
keep
to
your
sustainability
commitments
provides
the
opportunity
to
highlight
other
key
issues
of
interest
to
your
users,
such
as
privacy
and
security.
This
can
boost
user
trust
in
your
brand.
Social
Equity:
Highlighting
intersectional
social
issues
in
documentation,
storytelling,
and
marketing
materials
raises
awareness
of
problems
and
potential
solutions.
Transparency:
Maintaining
clear
and
public-facing
policies
helps
internal
and
external
affected
parties
to
better
understand
an
organization's
sustainability
commitments,
while
making
it
easier
to
report
on
the
impact
of
these
efforts.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
Accessibility,
AI,
Education,
Ideation,
KPIs
,
Research,
Social
Equity,
Strategy
Appoint
a
sustainability
advocate
who
is
provided
with
what
they
require
to
speak
about
and
for
issues
relating
to
sustainability.
Machine-testable
and
Resources
Assign
a
sustainability
advocate
with
specific
digital
expertise
and
provide
them
with
the
resources,
budget,
tools,
and
time
they
need
to
achieve
their
stated
goals.
In
some
organizations,
expanding
this
into
a
climate
working
group
comprising
motivated
individuals
can
add
further
benefits.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Nominating
a
sustainability
representative
helps
the
organization
remove
barriers
to
access.
These
can
inherently
cost
bandwidth,
have
monetary
value,
and
carry
potential
legal
implications.
Environment:
Appointing
dedicated
sustainability
representatives
means
they
can
maintain
quality
assurance
and
guide
decisions
that
measurably
reduce
the
environmental
impact
of
your
digital
products
and
services.
Privacy:
Having
dedicated
sustainability
representatives
on
the
team
enables
them
to
maintain
intersectional
data
privacy
standards
and
watch
out
for
legal
compliance
issues
within
the
organization.
Social
Equity:
Ensuring
someone
on
the
team
is
dedicated
to
these
concerns
will
help
to
reduce
the
digital
divide
through
internal
awareness
raising
and
requesting
features
or
information
be
provided
to
support
those,
for
example
on
older
devices
or
in
low-bandwidth
areas.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Education,
Ideation,
Marketing,
Social
Equity
Empower
visitors,
allowing
them
to
make
decisions
when
their
choices
can
influence
the
environmental
impact
they
have.
Human-testable
and
Resources
Clearly
communicate
the
environmental
impact
of
different
user
choices
and
allow
users
to
configure
settings
based
on
the
information
provided.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Conversion:
Communicating
the
impact
and
allowing
the
user
to
set
preferences
with
the
environmental
impact
in
mind
can
encourage
more
individuals
to
make
environmentally
friendly
choices
and
improve
your
image
among
ethical
consumers.
Environment:
Allowing
users
to
select
more
environmentally
friendly
settings
within
software
naturally
reduces
the
environmental
impact.
Performance:
Reducing
unnecessary
or
wasteful,
less
sustainable
behaviors
will
often
improve
performance
and
accessibility,
as
these
are
often
interlinked.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Content,
Education,
Marketing,
Reporting
Calculate
the
environmental
impact
of
the
project
and
any
tooling
you
use,
and
even
that
of
a
competitor,
where
possible,
as
this
may
be
useful
for
comparison.
Human-testable
and
Resources
Conduct
a
full
life-cycle
analysis
based
on
the
analysis/assessment
(
LCA
)
to
define
sustainability-related
functional
unit
defined
under
guideline
5.15.
impacts
throughout
a
project's
lifetime.
Machine-testable
and
Resources
Calculate
the
environmental
impact
of
your
or
a
competitor's
current
service
project
compared
to
that
of
market
alternatives
to
inform
decision-making
targets.
Establish
the
need
for
your
product
by
comparing
the
value
offered
by
your
project
compared
to
these
same
alternatives.
Human-testable
and
Resources
Include
the
impact
or
estimated
impact
of
any
tooling
or
third-party
solutions
used
at
any
stage
in
your
pipeline.
While
not
created
by
you,
the
emissions
generated
in
production,
maintenance,
and
use
are
also
integral
to
your
overall
solution.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Auditing
for
accessibility
can
be
included
as
a
key
part
of
a
digital
Life-Cycle
Assessment
(
LCA
),
provided
the
key
parameters
are
defined
up
front
and
maintained
throughout
the
project
to
eliminate
barriers
to
access.
These
parameters
can
include
conformity
with
WCAG
guidance,
including
manual
checks.
Environment:
Conducting
a
rigorous
LCA
can
reveal
significant
opportunities
to
reduce
overall
environmental
impact
through
the
identification
and
elimination
of
factors
and
vectors
of
digital
emissions
such
as
water
and
e-waste.
Performance:
Including
a
detailed
overview
of
optimizations
in
your
LCA
provides
a
clear
direction
to
improve
sustainability
and
performance.
Social
Equity:
Including
intersectional
social
metrics
in
your
LCA
can
provide
an
opportunity
to
simultaneously
consider
and
work
on
issues
such
as
inequality,
which
also
affect
sustainability.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
AI,
Ideation,
KPIs
,
Research,
Social
Equity,
Software,
Strategy
Publish
a
set
of
sustainability
goals
that
can
be
used
to
track
progress
over
a
period
of
time.
Machine-testable
and
Resources
Define
and
publish
a
clear
set
of
sustainability
goals.
Publicly
communicate
how
these
goals
can
be
met,
including
which
performance
metrics
can
be
measured
to
help
the
organization
and
its
various
affected
parties
act
more
sustainably.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Aligning
with
existing
standards
or
frameworks
makes
it
easier
for
organizations
to
include
digital
impact
in
their
overall
sustainability
reporting.
Environment:
Setting,
measuring,
and
communicating
clear
sustainability
goals
aligns
an
organization's
impact
aspirations
with
ongoing
efforts
to
meet
these
goals.
Transparency:
Helping
affected
parties
such
as
employees,
clients,
and
partners
to
better
understand
how
the
organization
creates
shared
value
in
its
various
sustainability
policies
and
programs.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Tags
AI,
Governance,
Ideation,
KPIs
,
Research,
Social
Equity
Obtain
and
maintain
third-party
certifications
to
externally
validate
progress
toward
sustainability
goals.
Machine-testable
and
Resources
Obtain
one
or
more
sustainability
certifications
and
incorporate
operational
policies
and
practices
in
alignment
with
their
guidance.
Human-testable
and
Resources
Maintains
sustainability
certifications
through
continuing
to
meet
their
criteria
and
evolving
policies
and
practices
over
time.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Certifications,
vetted
for
conflicts
of
interest,
can
operationalize
sustainability
principles
and
verify
and
endorse
levels
of
social
and
environmental
performance,
accountability,
and
transparency.
Operations:
Obtaining
third-party
sustainability
certifications
can
make
it
easier
for
organizations
to
align
operational
practices
with
their
mission,
vision,
and
values,
and
communicate
this
to
their
affected
parties.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Governance,
KPIs
5.8
Implement
sustainability
onboarding
guidelines
Provide
training
materials
and
incentives
to
encourage
participation
from
members
of
the
organisation
toward
meeting
sustainability
goals.
Success
Criterion:
Training
materials
Human-testable
and
Resources
Create
and/or
deliver
dedicated
training
manuals,
workshops,
and
materials
to
outline
the
sustainability
policies
and
practices
adopted
and
how
to
implement
them.
Manage
and
maintain
these
materials
over
time,
adapting
them
as
new
policies
and
best
practices
arise.
Success
Criterion:
Incentivize
progress
Human-testable
and
Resources
Incentivize
leadership,
teams,
and
individuals
to
make
progress
toward
the
goals
outlined
in
their
training.
Examples
include
dedicating
time
for
sustainability-related
activities,
recognizing
completion,
and
other
benefits.
Success
Criterion:
Negative
factors
Human-testable
and
Resources
Anticipate
and
map
potential
negative
external
factors
and
act
to
minimize
their
overall
impact.
Additional
information
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Providing
sustainability
training
and
onboarding
practices
has
been
shown
to
lead
to
higher
retention
rates,
improved
performance,
and
improved
systems
for
maintaining
business
continuity.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
GRI
301:
Materials
High
GRI
302:
Energy
High
GRI
303:
Water
High
GRI
305:
Emissions
High
Tags
Education,
Strategy
Create
policies
and
documents
showing
evidence
of
commitment
towards
impact
progress,
how
this
is
achieved,
and
any
applicable
regulations
you
are
meeting.
Machine-testable
and
Resources
Create
and
publish
policies
and
practices
to
disclose
the
social
and
environmental
impacts
of
its
products,
programs,
and
services
in
line
with
existing
reporting
standards
such
as
GRI
,
SASB
,
etc.
Machine-testable
and
Resources
Produce
a
publicly
available
impact
report
outlining
progress
compared
to
previous
reports
on
social
and
environmental
goals
at
least
once
per
year.
Machine-testable
and
Resources
Publicly
and
transparently
demonstrate
commitment
over
time
to
following
and
adopting
existing
and/or
emerging
environmental
standards
and
legislative
policy
that
promotes
mandatory
emissions
disclosures
and
reporting.
Human-testable
and
Resources
Clearly
identify
how
environmental
impact
is
being
reduced,
with
careful
avoidance
of
double
accounting,
greenwashing,
data
exclusion,
or
other
misleading
or
manipulative
techniques.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Conversion:
Demonstrating
transparency
through
regular
reporting
and
showing
measurable
improvement
over
time
can
increase
an
organization's
appeal
to
potential
employees,
partners,
potential
customers,
investors,
and
suppliers
who
perceive
shared
values
and
an
aligned
mission.
Economic:
Being
ahead
of
the
curve
affords
businesses
greater
resilience
in
the
face
of
more
rigorous
standards.
Environment:
Adopting
reporting
standards
ahead
of
schedule
provides
more
immediate
environmental
benefits,
and
allows
you
to
mitigate
environmental
issues
before
they
build
into
more
complex
or
long-lasting
ones.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
AI,
Content,
KPIs
,
Reporting
Produce
a
document
that
shows
how
the
organisation
is
taking
steps
to
become
as
resilient
as
possible.
Human-testable
and
Resources
Complete
and
operationalize
a
theory
of
change
process
with
requisite
documentation
to
identify
the
impact
the
organization
aspires
to
achieve,
how
it
will
generate
revenue,
how
it
will
create
shared
or
added
value
from
these
activities,
and
how
it
will
measure
results
based
on
desired
outcomes.
In
the
case
of
projects
already
underway,
how
these
are
generating
revenue
and
actively
tracking
and
measuring
progress
against
desired
outcomes.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Environment:
Business
models
focused
on
the
customer
and
the
wider
ecosystem
rather
than
just
financial
indicators
can
benefit
the
environment
such
as
through
reducing
overconsumption
of
resources
and
disencouraging
incentives
for
unethical
behavior,
leading
to
a
reduction
of
emissions.
Social
Equity:
Adding
social
indicators
(such
as
the
shared
value
within
digital
services)
can
reduce
negative
social
impacts
such
as
impoverishment
or
exploitation.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
Content,
Ideation,
Research,
Strategy
Explain
through
documentation
how
projects
will
be
maintained,
managed,
resourced,
and
note
issues
while
tracking
measurements
over
time.
Machine-testable
and
Resources
Produce
and
maintain
documentation
to
outline
how
the
organization
approaches
product
management
and
maintenance.
Human-testable
and
Resources
Establish
maintenance
and
security
plans
for
all
digital
products
and
services.
Human-testable
and
Resources
Appropriately
resource
products
Ensure
that
products,
prototypes,
testing,
and
supporting
processes
are
sufficiently
resourced
over
time
via
-
including
staffing
and
budgeting
to
support
code
refactoring,
-
so
that
teams
can
maintain
capacity,
address
technical
debt,
refactor
code,
introduce
new
product
features,
test
functionality,
support
long-term
care
and
produce
product
or
service
maintenance
plans
to
continue
supporting
maintenance,
and
avoid
project
abandonment
for
customers,
users,
and
other
all
affected
parties.
Human-testable
and
Resources
Incorporate
carbon
and
resource
measurement
into
maintenance
programs
and
show
measurable
improvement
over
time.
Human-testable
and
Resources
Identify
and
document
Key
Failure
Indicators
(
KFIs
)
and
implement
resolutions
to
prevent
negative
sustainability
impacts.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Maintaining
performance
can
boost
customer
retention,
and
organizations
with
clear
product
maintenance
and
management
practices
tend
to
benefit
from
greater
resilience
in
the
face
of
digital
disruption.
Environment:
Implementing
product
management
and
maintenance
strategies
provides
another
opportunity
to
improve
climate
resilience
and
manage
and
reduce
emissions
over
time.
Performance:
Following
good
product
management
and
maintenance
strategies
means
affected
digital
products
and
services
benefit
from
better
security,
reduced
technical
debt,
and
improved
data
privacy.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
Compatibility,
Strategy
Continuously
improve
projects
through
regular
reviews
and
iteration,
integrating
technical
debt
and
security
management,
determining
if
new
or
existing
functionality
is
required.
Human-testable
and
Resources
Establish
policies
and
practices
to
enable
continuous
improvement
and
resource
practices
appropriately
to
support
these
efforts
over
time.
Human-testable
and
Resources
Review
deliverables
and
update
frequency
to
ensure
project
teams
have
enough
time
to
conduct
user
research,
identify
technical
debt,
and
produce
high-quality
output
as
well
as
share
what
they
learned.
Machine-testable
and
Resources
Display
a
track
record
of
continuous
improvement
(iteration)
processes
to
analyze
the
digital
product
or
service.
Simultaneously
address
any
potential
consequences
of
ongoing
experimentation,
such
as
technical
debt,
product
performance,
and
emissions.
Analytics
are
limited
to
strictly
necessary
features
that
aid
decision-making,
encouraging
user
feedback,
and
comparing
performance
against
business
goals
and
user
needs.
Human-testable
and
Resources
Justify
and
prioritize
the
retention
of
existing
features,
the
creation
of
new
functionality,
and
the
decommissioning
or
elimination
of
unused
functionality
or
low-traffic
content
throughout
the
product's
life
cycle
on
a
case-by-case
basis.
Machine-testable
and
Resources
Provide
corrective
security
and
policy
updates
during
the
product
or
service
life
cycle.
These
should
be
distinguished
from
more
extensive
evolutionary
updates.
Human-testable
and
Resources
Develop
sustainable
product
and
data
strategies
using
appropriate
training
techniques.
These
should
help
your
team
build
capacity
and
learn
new
skills
to
manage
and
maintain
products
and
services
over
time.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Adopting
an
iterative
approach
supports
inclusive
design,
providing
the
agility
and
adaptability
for
organizations
to
expand
their
accessibility.
Conversion:
Providing
a
reliable
user
experience
boosts
user
trust,
encouraging
repeat
business.
Economic:
Ensuring
agility
and
continuous
improvement
helps
organizations
be
more
resilient
in
the
face
of
disruption
and
a
changing
climate.
Long-term,
these
practices
save
the
organization
time,
money,
and
resources.
Environment:
Focusing
on
continuous
improvement
reduces
waste
and
energy
use
by
iteratively
identifying
opportunities
to
improve
the
product
or
service.
Operations:
Fostering
a
culture
of
experimentation
encourages
innovation.
This
supports
team
building
and
improves
overall
organizational
resilience
and
efficiency.
Performance:
Establishing
good
review
processes
reduces
buildup
of
technical
debt.
Focusing
on
continuous
improvement
rather
than
large
single-scale
releases
means
bottlenecks
can
be
resolved,
and
they
become
apparent.
This
is
helpful
as
new
third-party
tools,
and
software
can
affect
performance
without
adaptation.
Privacy:
Having
a
high-quality,
regularly
updated
product
or
service
will
reduce
the
chances
of
a
data
breach,
which
improves
privacy.
Security:
Ensuring
products
or
services
are
maintained
and
updated
over
time
reduces
risk
and
improves
security.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
AI,
Compatibility,
KPIs
,
Performance,
Security,
Strategy,
UI
Provide
documentation
to
help
users
find
their
way
whenever
functionality
changes.
Human-testable
and
Resources
When
a
feature
is
added,
updated,
or
removed
to
improve
user
experience,
clear
documentation
of
the
changes
is
provided
in
a
well
structured,
semantically
versioned
document.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Updating
digital
products
and
services
regularly
requires
less
development
time
and
reduces
the
risk
of
negative
consumer
impact
from
the
extended
downtime
that
can
result
from
needing
to
start
from
scratch
if
a
product
or
service
is
otherwise
left
to
become
outdated
beyond
repair.
Environment:
Maintaining
an
intuitive,
lightweight
user
experience
while
adding
new
features
or
updating
software
reduces
frustration,
churn,
and
the
energy
users
expend
when
the
interface
performs
in
ways
users
do
not
expect.
Performance:
Maintaining
an
optimized
user
experience
that
is
regularly
updated
in
line
with
best
practices
usually
means
content
and
assets
will
load
quickly
and
as
expected
by
users.
Security:
Maintaining
evergreen
status
often
means
fewer
issues
due
to
a
strong
release
cycle.
This
involves
making
necessary
changes
and
keeping
users
informed
while
maintaining
transparency.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Example
# Changelog - Website
## [Unreleased]
- N/A
## 1.0.0 - YYYY-MM-DD
### Added
- Content.
## [Guide]
- Added: New features.
- Changed: Altered functionality.
- Deprecated: Disappearing features.
- Removed: Eliminated features.
- Fixed: Bugs patched.
-
Security:
Solved
vulnerabilities.
Tags
Compatibility,
Content,
Education,
Usability
Determine
whether
a
project
is
necessary,
avoiding
duplication
of
existing
efforts,
creating
eliminating
obstacles
for
users,
and
aligning
with
SDGs
and
sustainability
principles.
Machine-testable
and
Resources
Identify
where
the
product
or
service
aligns
with
one
of
the
U.N.
(
SDG
s)
and
its
appropriate
targets
within
a
sustainability
statement.
Human-testable
and
Resources
Determine
that
the
product
or
service
is
necessary
based
upon
desirability,
feasibility,
and
viability
factors.
Success
Criterion:
Avoid
duplication
Human-testable
and
Resources
Establish
that
no
existing
digital
product
or
service
offers
the
same
value.
Conduct
an
analysis
to
understand
the
market
for
this
requirement.
Human-testable
and
Resources
Remove
or
alleviate
any
obstacles
to
using
a
product
or
service,
such
as
accessibility,
equality,
technical,
or
territorial.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Preventing
unnecessary
digital
products
or
services
from
being
created
can
make
it
easier
to
find
and
access
existing
information,
provided
an
accessible
replacement
is
available.
Economic:
Reducing
unnecessary
research
and
development
allows
organizations
to
cut
costs.
Environment:
Determining
that
a
digital
product
or
service
is
not
necessary
means
the
potential
environmental
impacts
associated
with
its
creation
and
use
can
be
avoided.
Operations:
Avoiding
creating
unnecessary
products
or
services
prevents
organizations
from
wasting
time
or
resources
on
their
creation
and
maintenance.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
AI,
E-Waste,
Ideation,
Reporting,
Software
5.15
Conduct
a
full
life-cycle
assessment
Identify
the
potential
impact
that
a
digital
product
or
service
will
have
throughout
its
lifetime
by
conducting
an
LCA
.
Success
Criterion:
Life-cycle
assessment
Human-testable
and
Resources
Conduct
a
life-cycle
assessment
(
LCA
)
to
define
sustainability-related
functional
impacts
throughout
a
product's
lifetime.
Additional
information
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Using
a
functional
unit
approach
supports
a
robust
product
or
service
while
avoiding
unnecessary
and
potentially
costly
features.
Environment:
Using
functional
units
enables
the
comparison
of
non-equivalent
products
or
services
in
the
assessment
of
environmental
impacts.
Performance:
Focusing
on
a
functional
unit
drives
performance-based
choices
for
a
better,
more
efficient,
and
faster
user
experience.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
GRI
301:
Materials
Medium
GRI
302:
Energy
Medium
GRI
303:
Water
Medium
GRI
305:
Emissions
Medium
Tags
AI,
Ideation,
Reporting,
Research
Vet
suppliers
before
onboarding,
then
collaborate
to
promote
and
encourage
better
sustainability
practices.
Machine-testable
and
Resources
Create
specific
policies
to
vet
potential
partners
along
the
supply
chain
based
on
sustainability
principles.
Human-testable
and
Resources
Partner
with
suppliers
to
create,
track
and
measure
impact
on
issues
that
impact
affected
parties.
Machine-testable
and
Resources
Promote
and
disclose
partnerships
in
a
publicly
available
place,
along
with
information
on
how
the
partnership
creates
a
collective
impact.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Applying
standards
of
practice
can
help
an
organization
better
align
affected
party
needs
with
its
mission,
vision,
and
values,
which
builds
trust
and
improves
relationships.
Environment:
Vetting
suppliers
and
partners
can
help
an
organization
define,
track,
and
reduce
its
scope
3
emissions.
Operations:
Examining
suppliers
and
partners
more
closely
can
increase
diversity
within
the
technology
sector.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
AI,
Content,
Governance,
Hardware,
Ideation,
Social
Equity
Share
benefits
associated
with
being
sustainably
resilient
with
workers,
incentivizing
efforts,
and
advocating
for
those
involved
to
meet
sustainability
goals.
Machine-testable
and
Resources
Publicly
commit
to
paying
employees,
contractors,
and
other
affected
parties
a
living
wage.
Human-testable
and
Resources
Have
policies
and
practices
to
incentivize
affected
parties,
such
as
workers
and
contractors,
to
meet
impact
goals.
Machine-testable
and
Resources
Provide
benefits
to
employees
in
accordance
with
resources,
including,
where
relevant,
healthcare,
retirement
planning,
flex
time,
profit
sharing,
and
more.
Success
Criterion:
Legislation
advocacy
Human-testable
and
Resources
Advocate
for
responsible
legislation
that
supports
employment
rights,
transparency,
and
accountability
related
to
sharing
economic
benefits.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Collaborating
with
affected
parties
to
coordinate
mutually
beneficial
economic
incentives
builds
stronger
relationships.
Social
Equity:
Paying
a
living
wage
and
offering
good
benefits
often
leads
to
higher
employee
retention
rates.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
Governance,
Social
Equity
Ensure
that
all
affected
parties
have
the
opportunity
to
get
involved
in
helping
the
organisation
become
more
sustainable.
Human-testable
and
Resources
Align
the
project
team's
goals
with
key
business
objectives,
and
Assign
all
affected
parties
(for
example,
parties,
from
users
to
project
managers)
managers,
an
equitable
role
in
the
decision-making
process.
Ensure
all
internal
involved
parties
have
the
necessary
power
and
autonomy
to
make
key
decisions
on
the
organization's
behalf.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Environment:
Emissions
can
be
reduced
through
group
action
and
commitments
at
an
organizational
level.
Operations:
Incentivizing
project
teams
with
key
sustainability
goals
and
granting
the
authority
to
make
decisions
based
on
these
criteria
enables
them
to
measurably
improve
a
range
of
metrics
within
the
business,
design,
development,
and
infrastructure
categories.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Tags
Accessibility,
Ideation,
Social
Equity,
Strategy
Implement
JEDI
practices
to
foster
inclusive
hiring
practices
within
an
organization,
showing
evidence
of
improvement
over
time.
Human-testable
and
Resources
Document
commitments
to
JEDI
practices
with
clear
policies
on
how
marginalized
or
otherwise
underserved
communities
are
prioritized.
Machine-testable
and
Resources
Establish
a
publicly
displayed
accessibility
policy
and
demonstrate
this
via
accessible
digital
products
or
services.
Human-testable
and
Resources
Provide
JEDI
-related
training
materials
and
schedule
regular
workshops
related
to
how
this
topic
manifests
itself
in
digital
products
and
services,
covering
topics
such
as
algorithmic
bias,
digital
divide,
employment,
mis-
and
disinformation.
Human-testable
and
Resources
Show
measurable
improvement
over
time
across
hiring,
leadership,
and
operations.
Success
Criterion:
JEDI
legislation
Human-testable
and
Resources
Advocate
for
responsible
legislation
relating
to
JEDI
practices,
especially
as
they
relate
to
digital
products
and
services.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Accessibility:
Incorporating
more
diverse
affected
party
perspectives
leads
to
enacting
more
inclusive
policies,
often
resulting
in
better
products,
services,
and
programs.
JEDI
practices
boost
an
organization's
resilience
and
ability
to
collaborate.
This
improves
diversity
in
the
tech
sector
and
the
overall
accessibility
of
the
web.
Economic:
Having
clear
policies
and
practices
reduces
the
risk
of
legal
issues.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
Accessibility,
Ideation,
Social
Equity,
Strategy
Allow
users
to
manage,
control,
and
delete
their
data
upon
request,
while
making
outdated
content
searchable
via
a
lightweight
and
simple
archive.
Machine-testable
and
Resources
Archive
and
delete
outdated
or
otherwise
expired
product
content
and
data
via
automated
expiration
dates
and
scheduled
product
audits.
Publish
the
archiving
schedule,
ensuring
a
lightweight
version
of
the
old
searchable
content
is
maintained
for
those
that
may
require
it.
Machine-testable
and
Resources
Allow
users
to
control,
manage,
and
delete
their
data,
subscriptions,
and
accounts.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Requiring
less
data
reduces
storage
requirements,
allowing
organizations
to
scale
down
their
hosting
package
or
be
charged
less
for
pay-by-use
infrastructure
costs.
Environment:
Storing
less
data
reduces
the
computing
power
required
to
maintain
a
service,
reducing
energy
and
infrastructure-related
emissions.
Performance:
Moving
older
and
less
relevant
content
onto
a
smaller
scaled-down
version
of
your
digital
product
or
service
will
reduce
your
bandwidth
usage.
Archived
information
will
have
significantly
fewer
users,
meaning
this
is
unlikely
to
have
a
negative
impact
on
their
experience.
Privacy:
Improving
data
management
supports
better
data
protection
practices.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Tags
Privacy,
Security,
Social
Equity,
Strategy
Ensure
that
a
project
is
suitably
budgeted
for
and
funded
through
sustainable
and
ethical
sources.
Machine-testable
and
Resources
Divest
from
fossil
fuels
and
move
banking,
sponsorship,
and
other
affiliations
to
more
responsible
partners.
Human-testable
and
Resources
Engage
in
flexible
financing
and
responsible
budgeting
to
accommodate
long-term
care
and
maintenance.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Sourcing
responsible
financing
for
digital
products
and
services
improves
their
resilience
and
saves
the
organization
time,
money,
and
resources
over
time.
Environment:
Divesting
from
fossil
fuels
moves
us
more
quickly
to
an
economy
that
is
powered
by
carbon-free
energy,
which
can
reduce
the
catastrophic
impacts
of
climate
change.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
Governance,
Ideation,
Social
Equity
Provide
the
opportunity
to
give
back
to
the
community
through
charitable
or
volunteer
efforts
via
your
organisation.
Machine-testable
and
Resources
Establish
a
clear
corporate
giving
policy
and
create
philanthropic
partnerships
with
strategically
aligned
organizations.
Human-testable
and
Resources
Engage
in
free
or
volunteer
projects
to
help
teams
learn
new
tools
and
tactics,
while
also
helping
charities
and
non-profit
organizations
to
build
capacity.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Following
clear
philanthropic
strategies
means
there
is
usually
a
system
of
checks
and
balances
in
place
to
support
better
financial
practices
overall.
Operations:
Having
clear
philanthropy
strategies
that
include
volunteer
or
free
projects
with
team
stretch
goals
can
boost
employee
engagement
and
retention.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
Content,
Governance,
Social
Equity
Produce
documentation
to
ensure
that
when
a
project
is
shut
down,
visitors
are
made
aware
of
what
will
happen
to
their
data.
Human-testable
and
Resources
Provide
clear,
documented
end-of-life
guidelines
that
include
data
disposal,
archiving,
file
deletion,
and
other
relevant
guidance.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Removing
redundancy
in
the
product
or
service
can
generate
savings
in
hosting,
security
costs,
and
other
third-party
subscriptions.
Environment:
Planning
for
end-of-life
reduces
long-term
environmental
impacts
after
a
digital
product
or
service
is
no
longer
needed.
This
eliminates
waste
and
frees
up
resources.
Performance:
Removing
unnecessary
features,
functions,
and
data
of
a
service
improves
performance
and
resilience
as
the
resources
which
were
utilizing
data
will
be
better
spent
on
more
popular
functionality,
and
the
gains
made
from
their
elimination
will
be
felt
in
terms
of
emissions
through
saved
development
time.
Privacy:
Incorporating
clear
end-of-life
policies
that
include
a
user's
right
to
be
forgotten
will
benefit
the
user
by
explaining
how
you
enforce
data
protection
and
comply
with
legislation.
Security:
Providing
regular
maintenance,
updates,
and
care
on
outdated
software
and
data
can
significantly
reduce
security
risks.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Compatibility,
E-Waste,
Research,
Social
Equity,
Software,
Strategy
Include
policies
and
documentation
explaining
how
sustainable
e-waste,
recycling,
repairing,
and
refurbishment
are
handled.
Resources
Responsibly
recycle
or
upcycle
unwanted
waste.
Materials
should
be
recovered
and
reused,
where
possible,
or
otherwise
disposed
of
appropriately.
Human-testable
and
Resources
Establish
specific
policies
around
e-waste
recycling
and
repair
owned
technology
products
whenever
possible.
Human-testable
and
Resources
Form
relationships
with
local
partners
for
e-waste
recycling
and
repair.
Human-testable
and
Resources
Buy
refurbished
equipment
whenever
possible.
Human-testable
and
Resources
Allow
consumers
to
repair
the
consumables
they
purchase
to
the
best
of
their
ability,
offering
replacement
components
if
possible
at
cost,
and
provide
clear
instructions
to
help
resolve
faults
that
occur.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Extending
the
shelf-life
of
hardware
and
clear
e-waste
and
recycling
policies
reduce
costs.
Environment:
Following
clear
e-waste
and
recycling
policies
reduces
environmental
impact
and
promotes
circularity,
while
also
extending
the
shelf
life
of
hardware.
When
coupled
with
clear
philanthropic
policies,
donated
hardware
can
also
support
resource-constrained
charities.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
High
-
GRI
302:
Energy
-
High
-
GRI
303:
Water
-
High
-
GRI
305:
Emissions
-
High
Tags
Content,
E-Waste,
Governance,
Hardware,
Ideation,
Social
Equity
Produce
a
policy
around
open
collaboration
and
contribution
to
creating
and
sustaining
open
source
projects.
Machine-testable
and
Resources
Establish
a
clear
open
source
policy
that
outlines
how
open-source
tools
are
used
and
any
practices
used
to
support
open-source
development.
Human-testable
and
Resources
Show
a
track
record
of
collaboration
and
building
communities
around
open-source
principles.
Machine-testable
and
Resources
Contribute
regularly
in
terms
of
code,
human-time,
and/or
financially,
to
open-source
community-based
projects.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Using
open-source
tools
can
significantly
reduce
development
time
when
managed
properly.
Social
Equity:
Supporting
collaboration
and
building
communities
around
open-source
practices
engenders
trust
and
helps
to
reduce
inequalities.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Medium
-
GRI
302:
Energy
-
Medium
-
GRI
303:
Water
-
Medium
-
GRI
305:
Emissions
-
Medium
Tags
Assets,
Ideation,
Social
Equity,
Software,
UI
Create
a
plan
of
action
with
a
system
to
recover
from
failure
or
alert
users
if
or
when
a
loss
of
service
occurs.
Human-testable
and
Resources
Create,
regularly
review,
and
occasionally
test
a
plan
of
action
to
determine
readiness
in
case
of
an
incident
and
establish
procedures
to
quickly
recover
from
any
incident.
Machine-testable
and
Resources
Maintain
regular
and
transparent
communication
with
the
audience
regarding
issues
that
may
affect
service
delivery
or
user
data.
Show
/
Hide
additional
information
to
understand
this
guideline
and
its
success
criteria.
Benefits
Economic:
Limiting
the
extent
of
the
disruption
has
obvious
economic
benefits.
Operations:
Creating
transparency
around
digital
resilience
procedures
encourages
trust
that
a
product
or
service
can
be
depended
upon
for
critical
use.
Social
Equity:
Providing
uninterrupted
access
to
potentially
vital
online
services
in
case
of
a
disaster
or
emergency
benefits
users.
Reporting
You
can
find
details
about
complying
with
[
GRI
]
through
the
body
behind
the
standard.
-
GRI
301:
Materials
-
Low
-
GRI
302:
Energy
-
Low
-
GRI
303:
Water
-
Low
-
GRI
305:
Emissions
-
Low
Tags
AI,
Governance,
Security,
Strategy
Additional
information
about
participation
in
the
Sustainable
Web
Interest
Group
can
be
found
within
the
GitHub
repository
of
the
Interest
Group.
Alexander
Dawson,
Alisa
Bonsignore,
Andrea
Davanzo,
Andrew
Wright,
Andy
Blum,
Anne
Faubry,
Arnaud
Levy,
Ben
Clifford,
Berwyn
Powell,
Brett
Tackaberry,
Brian
Louis
Ramirez,
Chris
Adams,
Chris
Augier,
Chris
Butterworth,
Chris
Needham,
Chris
Sater,
Chris
Wilson,
Claire
Thornewill,
Daniel
Appelquist,
David
Jeanmonod,
Dennis
Lemm,
Diogo
Abrantes
Da
Silva,
Dom
Robinson,
Dominique
Hazael-Massieux,
Emily
Trotter,
Emma
Horrell,
Fershad
Irani,
Florian
Rivoal,
Francesco
Fullone,
François
Burra,
Gaël
Duez,
Hidde
de
Vries,
Iain
McClenaghan,
Ian
Jacobs,
Ines
Akrap,
Ismael
Velasco,
Iulia
Raluca
Ionita,
James
Christie,
Jeffrey
Yasskin,
Jennifer
Strickland,
Jens
Oliver
Meiert,
Jim
McCool,
Josh
Kim,
Julien
Wilhelm,
Kazuhito
Kidachi,
Kenneth
G.
Franqueiro,
Laurent
Devernay
Satyagraha,
Len
Dierickx,
Leon
Brocard,
Łukasz
Mastalerz,
Marie
Ototoi,
Michelle
Barker,
Mike
Gifford,
Morgan
Murrah,
Nahuai
Badiola,
Neil
Clark,
Nick
Doty,
Nick
Lewis,
Nicola
Bonotto,
Nigel
Megitt,
Orie
Steele,
Owen
Barton,
Owen
Rogers,
Peter
Krautzberger,
Philippe
Le
Hégaret,
Romuald
Priol,
Rose
Newell,
Rudolf
Van
Der
Berg,
Ryan
Sholin,
Sandy
Dähnert,
Sarah
Zama,
Shane
Herath,
Siddhesh
Wagle,
Simon
Perdrisat,
Sorca
Duffy,
Susannah
Hill,
Tantek
Çelik,
Thibaud
Colas,
Thorsten
Jonas,
Tim
Frick,
Tzviya
Siegman,
Youen
Chéné,
Yuna
Orsini,
Zoe
Lopez-Latorre.
Adam
Newman,
Aiste
Rugeviciute,
Alekh
Gupta,
Alicia
Pritchett,
Anthony
Vallée-Dubois,
Antoine
Abélard,
Asim
Hussain,
Bee
Flaherty,
Boris
Schapira,
Brian
Sharpe,
Carine
Bournez,
Christian
H
Brown,
Christophe
Clouzeau,
Christos
Bacharakis,
Crystal
Preston-Watson,
Danielle
Subject,
Denis
Didier,
Edward
Bender,
Elise
West,
Eloisa
Guerrero,
Emma
Horrell,
Florence
Maurice,
Gerry
McGovern,
Greg
McDonald,
Hannah
Smith,
Ignacio
Rondini,
Ivano
Malavolta,
James
Cannings,
James
Gallagher,
Jan
Henckens,
Jean
Rigotti,
Jeroen
Hulscher,
Jon
Gibbins,
Juan
Sotés,
Julien
Robitaille,
Kate
Mroczkowski,
Katya
Dreyer-Oren,
Kimi
Wei,
Laila
Tamani,
Leah
Goldfarb,
Lenchi
Danch,
Loren
Velasquez,
Louise
Towler,
Luciene
Bulhões
Mattos,
Luis
Tiago,
Manfred
Jurgovsky,
Marie
Koesnodihardjo,
Mark
Butcher,
Marketa
Benisek,
Mert
Altinöz,
Michelle
Sanver,
Moritz
Guth,
Nick
Oliveira,
Nick
Sollecito,
Nicolas
Lanthemann,
Nicholas
Oliveira,
Nicolas
Oren,
Oliver
Winks,
Patrick
Hypscher,
Pietro
Jarre,
Radu
Micu,
Rafael
Lebre,
Rebecca
Brocton,
Rick
Butterfield,
Rick
Viscomi,
Robin
Whittleton,
Samuel
Pitoňák,
Sandra
Pallier,
Sarven
Capadisli,
Sebastien
Solere,
Sylvain
Tenier,
Thierry
Leboucq,
Thomas
Alexander
Munch-Woolff,
Tom
Greenwood,
Tom
Howells,
Torsten
Beyer,
Tristan
Nitot,
Yelle
Lieder,
Youcef
Bekhti.