Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reach calculator: Improve reduction assumption explanation #205

Merged
merged 1 commit into from
Apr 30, 2024
Merged

Reach calculator: Improve reduction assumption explanation #205

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions tools/reach-calculator.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,7 +158,7 @@ <h2>Site Breakage Reach Calculator</h2>
</div>

<div>
<label>[Optional] <abbr title="Should the reach of this breakage be reduced? This should be based on data if available, or your best estimate. 100% = no reduction.">Reduction assumption (%):<br>
<label>[Optional] <abbr title="Percentage of users that might encounter this breakage. This should be based on data if available, or your best estimate. 100% = no reduction.">Reduction assumption (%):<br>
<input type="number" id="reductionFactorInput" min="0" max="100"></abbr></label>
</div>

Expand Down Expand Up @@ -190,7 +190,7 @@ <h2>FAQ</h2>

<details>
<summary>What is "reduction assumption"?</summary>
<p>Should the reach of this breakage be reduced? This should be based on data if available, or your best estimate. 100% (or no input) = no reduction. Examples of when this could apply:</p>
<p>Percentage of users that might encounter this breakage. You should adjust this if only a subset of all domain visitors are likely to experience breakage, for example visitors on a particular platform version. This should be based on data if available, or your best estimate. 100% (or no input) = no reduction. Examples of when this could apply:</p>
<ul>
<li>A specific platform version, e.g. only Big Sur users, which might account for 5% of all macOS users.</li>
<li>A specific user action, e.g. only when users pause a video, which might be 10% of all video plays.</li>
Expand Down
Loading