core(config): Re-weight a11y scores based on severity and frequency#3515
Merged
core(config): Re-weight a11y scores based on severity and frequency#3515
Conversation
patrickhulce
approved these changes
Oct 10, 2017
Collaborator
patrickhulce
left a comment
There was a problem hiding this comment.
nice, love the data driven decision here! these all seem reasonable to me, seems like the best we can do in absence of applicability tests 👍
mind rebasing and double-checking we don't have any tests dependent on the current weights since its failing travis atm?
52dc75d to
f92cfb7
Compare
Contributor
Author
|
Cool thanks for looking it over folks 😁
…On Tue, Oct 10, 2017, 6:27 PM Paul Irish ***@***.***> wrote:
Merged #3515 <#3515>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3515 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABBFDb29uOUmzMw0DoR40VTdQDfQayWQks5srBl3gaJpZM4PzG34>
.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here's a stab at re-weighting the a11y tests, accounting for severity and frequency. This isn't a super scientific process but I'll try to explain my methodology.
For each weight I tried to consider two factors:
Because we don't have the ability to identify non-applicable tests yet, it means that there are some items which are uncommon but should be fatal. For example, a video without captions is pretty bad and should really sting, but if we weigh it too heavily, it's like an automatic free 10 points to the 99.9% of sites which don't use
<video>. In these cases I had to stick to a middle-of-the-road weight so they still hurt if they actually occur, but they also don't give too much of a free boost to everybody else. Fixing dequelabs/axe-core#473 will help a lot here.I tested the new weights against 3 sites. I don't want to publicly shame anyone here so I'll just call them "Good site", "OK site", and "Bad site". Here's a before and after of their scores:
New weights are as follows: