forked from w3ctag/ethical-web-principles
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
324 lines (299 loc) · 12.2 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
<!DOCTYPE html>
<meta charset="utf-8">
<title>W3C TAG Ethical Web Principles</title>
<script class="remove" src="https://www.w3.org/Tools/respec/respec-w3c">
</script>
<script class="remove">
var respecConfig = {
specStatus: "draft-finding",
editors: [
{
name: "Daniel Appelquist",
company: "Samsung",
},
{
name: "Hadley Beeman",
company: "Invited Expert",
},
],
group: "tag",
wgPublicList: "www-tag",
github: "w3ctag/ethical-web-principles",
format: "markdown",
canonicalURI: "https://www.w3.org/2001/tag/doc/ethical-web-principles/",
localBiblio: {
"UDHR" : {
title: "Universal Declaration of Human Rights",
href: "https://www.un.org/en/universal-declaration-human-rights/",
publisher: "United Nations",
},
},
};
</script>
<body class="informative">
<section id="abstract">
The web should be a platform that helps people
and provides a net positive social benefit.
As we continue to evolve the web platform,
we must therefore consider the ethical consequences of our work.
The following document sets out ethical principles
that will drive the TAG's continuing work in this direction.
</section>
<section id="sotd">
This document is a draft Technical Architecture Group (TAG) Finding.
It does not contain any normative content.
This document reflects the consensus of the TAG at the time of publication.
It will continue to evolve and the TAG will issue updates as often as needed.
</section>
## Introduction {#intro}
The web should empower an equitable, informed and interconnected society.
It has been, and should continue to be, designed
to enable communication and knowledge-sharing for everyone.
In order for the web to continue to be beneficial to society,
we need to include ethical thinking when we build
web technologies, applications, and sites.
The web is made up of a number of technologies and technical standards.
HTML, CSS and JavaScript are often thought of as the web's core set of technologies
but there are a raft of other technologies, standards,
languages and APIs that come together to form the "web platform."
In the 30 years since development of the web began,
it has become clear that the web platform can often be used in ways that subvert its original mission,
or even be used to cause harm.
The web should be a platform that helps people
and provides a net positive social benefit.
As we continue to evolve the web platform,
we must therefore consider the ethical implications of our work.
The web must be for good.
One of the web platform's differentiators has always been a strong ethical framework;
for example an emphasis on
[internationalization](https://www.w3.org/International/),
[accessibility](https://www.w3.org/WAI/),
[privacy](https://www.w3.org/Privacy/), and
[security](https://www.w3.org/Security/).
Web technologies are also offered
[royalty free](https://www.w3.org/Consortium/Patent-Policy/)
to enable open source implementation.
These are often cited as some of the strengths of the web.
The architecture of the web is designed with
the important notion of different classes of application that retrieve and process content,
and represent the needs of the application's users.
This includes web browsers,
web-hosted applications such as search engines,
and software that acts on web resources.
This lends itself well towards empowering people
by allowing them to choose the browser, search engine, or other application
that best meets their needs
(for example, with strong privacy protections).
The web should also support human rights, dignity and personal agency.
We need to put internationally recognized human rights at the core of the web platform [[?UDHR]].
And we need to promote ethical thinking across the web industry
to reinforce this approach.
The principles in this document are deliberately unordered,
and many are interconnected with each other.
While all of the principles together aim to provide pillars that collectively support
a web that is beneficial for society, there are cases where upholding one principle
may diminish the efficacy of another principle.
Thus in applying these principles, there are benefits and tradeoffs
that may need to be carefully balanced. When faced with principles
which appear to be in conflict with one another,
it is important to consider the context in which a particular technology
is being applied, the expected audience(s) for the technology,
who the technology benefits and who it may disadvantage,
and any power dynamics involved (see also the
<a data-cite="design-principles#priority-of-constituencies">priority of constituencies</a>).
The purpose of this document is
to inform TAG review of new specifications
and candidate additions to published recommendations,
and to inform other documents such as the
[[[Design-Principles]]], [[[security-privacy-questionnaire]]]
or other similar checklists and sets of principles used by specification authors and editors.
It also serves to raise awareness of the ethical responsibilities of web makers.
## Principles
<section>
<h3 id="oneweb" data-export="" data-dfn-type="dfn">
There is one web
</h3>
<p>
When we are adding new web technologies and platforms,
we will build them to cross regional and national boundaries.
People in one location should be able to view web pages
from anywhere that is connected to the web.
</p>
</section>
<section>
<h3 id="noharm" data-export="" data-dfn-type="dfn">
The web should not cause harm to society
</h3>
<p>
When we are adding a feature or technology to the web,
we will consider what harm it could do to society or groups,
especially to vulnerable people.
We will prioritize potential benefits for web users over potential benefits to web developers,
content providers, user agents, advertisers or others in the ecosystem,
in line with the
<a data-cite="design-principles#priority-of-constituencies">priority of constituencies</a>.
We will ensure the requirements and views of marginalized communities
and underrepresented groups are heard and respected.
We will build new web technologies in a collaborative manner
according to open processes
(for example, the <a href="https://www.w3.org/Consortium/Process/">W3C process</a>),
and adhering to codes of conduct
(such as the W3C <a href="https://www.w3.org/Consortium/cepc/">Code of Ethics and Professional Conduct</a>).
</p>
</section>
<section>
<h3 id="community" data-export="" data-dfn-type="dfn">
The web must support healthy community and debate
</h3>
<p>
We are building technologies and platforms for distributing ideas,
for virtual interaction,
and for mass collaboration on any topic.
While those tools can be used for good,
they can also be used for spreading misinformation,
revealing private personal information (doxing),
harassment, and persecution.
We will consider these risks in the work we do,
and will build web technologies and platforms
that respect individuals' rights
and provide features to empower them against dangers like these.
</p>
</section>
<section>
<h3 id="allpeople" data-export="" data-dfn-type="dfn">
The web is for all people
</h3>
<p>
Anyone should be able to meaningfully participate
in the creation of specifications, user agents, and content,
and the platform should enable a fully accessible end user experience.
We will build internationalization and localization capabilities
into our specifications and websites.
We will accommodate people on low bandwidth networks and with low specification equipment.
The web platform and the tools we use to create it
must be accessible to people with disabilities,
including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.
</p>
</section>
<section>
<h3 id="privacy" data-export="" data-dfn-type="dfn">
Security and privacy are essential
</h3>
<p>
When we add features to the web platform,
we are making decisions
that may change the ability of people to protect their personal data.
This data includes their conversations,
their financial transactions
and how they live their lives.
We will start by creating web technologies
that create as few risks as possible,
and will make sure people understand
what risks they are taking when they use the web.
</p>
</section>
<section>
<h3 id="expression" data-export="" data-dfn-type="dfn">
The web must enable freedom of expression
</h3>
<p>
We will create web technologies and platforms
that encourage free expression,
where that does not contravene other human rights.
Our work should not enable state censorship, <a data-cite="RFC7258#section-1">surveillance</a>
or other practices that seek to limit this freedom.
This principle must be balanced with respect for other human rights,
and does not imply that individual services on the web must therefore support all speech.
(For example: hate speech, harassment or abuse may reasonably be denied a platform).
</p>
</section>
<section>
<h3 id="verify" data-export="" data-dfn-type="dfn">
The web must make it possible for people to verify the information they see
</h3>
<p>
We have a responsibility to build web technologies to counter misinformation,
allowing information sources to be traceable and facts to be checkable.
The concept of origin and source is core to the web's security model.
We will make sure the new web technologies we create
do not work against this architectural principle.
</p>
</section>
<section>
<h3 id="control" data-export="" data-dfn-type="dfn">
The web must enhance individuals' control and power
</h3>
<p>
We recognize that web technologies can be used
to manipulate and deceive people, complicate isolation, and encourage addictive behaviors.
We seek to mitigate against these potential abuses
and <a href="https://en.wikipedia.org/wiki/Dark_pattern">patterns</a>
when creating new technologies and platforms,
and avoid introducing technologies that increase the chance of
people being harmed in this way.
As part of this, we favor a decentralized web architecture
that minimizes single points of failure and single points of control.
We will also build web technologies for individual developers
as well for developers at large companies and organizations.
The web should enable do-it-yourself developers.
</p>
</section>
<section>
<h3 id="sustainable" data-export="" data-dfn-type="dfn">
The web must be an environmentally sustainable platform
</h3>
<p>
The web, as a whole, is a big source of carbon emissions, because it is a big consumer of power.
New web technologies should not make this situation worse.
We will consider power consumption and the resulting emissions
when we introduce new technologies to the web.
This includes maximizing the lifespan of physical devices
through maintaining compatibility,
as well as minimizing data storage and processing requirements.
</p>
</section>
<section>
<h3 id="transparent" data-export="" data-dfn-type="dfn">
The web is transparent
</h3>
<p>
The web was built on a "view source" principle,
currently realized through robust developer tools built into many browsers.
We will always make sure it is possible
to determine how a web application was built
and how the code works.
Furthermore, we will always make sure it is possible
to audit and inspect web applications and underlying software
for security, privacy or other considerations.
</p>
</section>
<section>
<h3 id="multi" data-export="" data-dfn-type="dfn">
The web is multi-browser, multi-OS and multi-device
</h3>
<p>
We will not create web technologies that encourage the creation of websites
that work only in one browser,
or only on particular hardware.
We expect that content provided by accessing a URL
<a data-cite="mobile-bp#tc">should yield a thematically consistent experience</a>
when someone is accessing it from different devices.
The existence of multiple interoperable implementations
enables competition, and thus a variety of choices
for web users.
</p>
</section>
<section>
<h3 id="render" data-export="" data-dfn-type="dfn">
People should be able to render web content as they want
</h3>
<p>
People must be able to change web pages according to their needs.
For example, people should be able to install style sheets,
assistive browser extensions,
and blockers of unwanted content or scripts or auto-played videos.
We will build features and write specifications
that respect peoples' agency,
and will create user agents to represent those preferences on the web user's behalf.
</p>
</section>