You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h2class="heading settled" id="boilerplate-user-benefit"><spanclass="content">Appendix B: Boilerplate Explanations of User Benefit</span><aclass="self-link" href="#boilerplate-user-benefit"></a></h2>
925
+
<p>Some classes of features are meant to
926
+
help authors achieve some kind of user benefit,
927
+
like security, accessibility, or performance,
928
+
more easily.
929
+
Explainers for these features should say why that general area helps users,
930
+
but explainer authors should
931
+
spend most of their time explaining why the feature improves the area.
932
+
This section provides some boilerplate for some common areas
933
+
so that authors don’t need to rewrite it every time.</p>
<p>This feature is meant to improve website accessibility,
937
+
which ensures all users can browse the web,
938
+
even if they need to interact with their computers
939
+
differently from the majority.</p>
940
+
</blockquote>
941
+
<h3class="heading settled" id="authoring-user-benefit"><spanclass="content">Ease of Authoring</span><aclass="self-link" href="#authoring-user-benefit"></a></h3>
942
+
<p>End-users come before authors
943
+
in the <ahref="https://w3ctag.github.io/design-principles/#priority-of-constituencies">priority of constituencies</a>,
944
+
so when explaining features designed for authors,
945
+
you need to clearly establish that there’s no negative effect on end-users.</p>
946
+
<p>For example, <adata-biblio-display="inline" data-link-type="biblio" href="https://drafts.csswg.org/css-nesting/">CSS nesting</a> primarily makes it easier to write stylesheets,
947
+
and the potential reduction in file sizes wasn’t measured as part of justifying the feature.
948
+
On the other hand,
949
+
a feature like <adata-biblio-display="inline" data-link-type="biblio" href="https://w3c.github.io/ppa/">Privacy-Preserving Attribution</a>
950
+
isn’t in this category because it does have some negative effect on end-users
951
+
(via bandwidth costs and information exposure under its privacy budgets),
952
+
so its specification argues that these costs are justified by greater end-user benefits.</p>
953
+
<blockquote>
954
+
<p>This feature is meant to make it easier to write websites
955
+
and to have no negative effects on end-users.
956
+
When websites are easier to write,
957
+
users get more of them
958
+
and don’t need to pay as much (in fees or ads)
959
+
to access them.
960
+
[If it’s not obvious:]
961
+
See <code><a href="#<var>later-section</var>"></code>below<code></a></code>
962
+
for an analysis of why the proposed solution doesn’t harm end-users.</p>
0 commit comments