That something loads faster or has better support for blind people or renders better on my iPad doesn't mean that it's more relevant to my search. I'll wait 30 seconds longer for a webpage to load and stomach its crappy design if it has more accurate and relevant content, so I don't think it makes sense for Google to throw its weight around like this.
I mean, we're all on HN yet it's atrocious on my smartphone. And <table> spam probably sucks for screen readers. Doesn't mean something you're not looking for should rank above it just because you can read that unwanted content easier if you're blind.
Ideally you could opt in to additional weights like "I'm on a slow connection" and "blind-friendly results first please".
If I am penalised not for relevance but for accessibility then I fix the accessibility.
I am then both relevant and accessible and the world is a better place.
We shouldn't lose that content which can still be very relevant just because they're not following the current trend of constant website updates.
To a blind person, whether a website works well with a screen reader is extremely relevant to their search. Why are their needs less important than yours?
> Ideally you could opt in to additional weights like "I'm on a slow connection" and "blind-friendly results first please".
This just makes it easier for websites to bloat up or ignore accessibility. I have no issue with search engines penalizing websites to encourage them to take accessibility seriously.
It will be improving the quality of search for non-blind users because websites will be structured better for Googlebot.
Any gimping will be temporary as the websites rush to comply.
The gimping can be non-existent if Google simply announces ahead of time that accessibility will weigh more heavily. That'll give devs time to adjust. Look how Google pushed the adoption of HTTPS.