Did you see this Facebook crap?
"Why do I need a 4Ghz quadcore to run facebook?" This is why. A single word split up into 11 HTML DOM elements to avoid adblockers. pic.twitter.com/Zv4RfInrL0
— Mike Pan (@themikepan) February 6, 2019
I popped over to Facebook to verify that and what I saw was a different and even more nested mess:
They are trying to fight your ad blocker browser extension. Of course they are. I’m sure at their scale not doing this means losing millions of dollars. But I wonder if it’s really losing money when you factor in losing trust, and potentially losing people on the platform entirely.
It just feels so rude, doesn’t it? Like a user specifically installs technology onto their computer in order to exert some control over what they allow onto their computers and into their eyeballs. And they are saying, “No, we do not respect that choice. We are going to fight your technology with our technology and force feed this stuff onto your computer and your eyeballs.” Doesn’t sit right.
I’m not unaware that ad blockers have ad adverse effect on the ability for websites to make money. That’s quite literally how I make money. But I don’t want to do it fighting and at the expense of breaking trust. I want to do it gracefully while building trust.
I wonder what writing HTML to help ad blockers would look like instead:
<!-- start: advertisement -->Sponsor:<a href="https://sponsor.com" rel="nofollow">Company</span> </div> <!-- end: advertisement -->
The good ones have been doing it for ages.
Turns out that doesn’t affect on-page search (i.e. if you search for “dog,” you’ll find
<span>d</span><span>o</span><span>g</span>), but it does affect some screen readers in that they will treat each letter distinctly, which can result in pretty awful audio output, like pauses between letters where you wouldn’t expect or want them.
It’s totally solvable though!
I just read about how powerful
aria-labelis via Web Platform News, quoting Amelia Bellamy-Royds:
aria-labelattribute on a button or link effectively replaces the text content of that element with the new label.
It was cool to see that’s what Lettering.js does by default! And Splitting.js is figuring out the best method for them, which involves
The post <span>L</span><span>e</span><span>t</span><span>t</span><span>e</span><span>r</span><span>s</span> appeared first on CSS-Tricks.