31–40 of 367 posts
Does this meet the required standard for accessibility users? Do they have any such obligations?
I'm really thankful I haven't yet had a job where all I'm developing is new ways to force people to see ads. Imagine working on a 'feature' like this for weeks or months, and the end result is simply that people who don't want to see ads now have to see ads.
meanwhile https://text.npr.org/ ps: thanks for the comments below, I was curious about similar websites
I'm really thankful I haven't yet had a job where all I'm developing is new ways to force people to see ads. Imagine working on a 'feature' like this for weeks or months, and the end result is simply that people who don't want to see ads now have to see ads.
That reminds me of a quote about dentistry: "You're in a career where nobody wants to see you and you're the last place they want to come back to and it's depressing." ( https://tonic.vice.com/en_us/article/5344jz/are-dentists-rea... )
"What are you doing at work these days, kid?"
"I'm inventing new ways to make people see advertising."
"Have you considered doing something positive with your life?"
I'm really thankful I haven't yet had a job where all I'm developing is new ways to force people to see ads. Imagine working on a 'feature' like this for weeks or months, and the end result is simply that people who don't want to see ads now have to see ads.
Anyone who has written a few scrappers knows how brutally ineffective this is. Yelp tried to pull the same thing and it took me about 3 minutes to rectify my "for fun" scraper. It's also really not that difficult to write a smart scraper that you say, "Look for these things in this post. However you find them, replicate it for the others". Which is ultimately what I made my Yelp scraper do. If there's a pattern, I wi…
Does this meet the required standard for accessibility users? Do they have any such obligations?
One of my first thoughts when I saw this was about screen readers. If searching "Sponsored" in Chrome doesn't match the posts, I'd wager screen readers would just go ahead and try to pronounce all the extra 'S's.
Screen readers obey CSS, this uses CSS to hide all of the additional elements (display: none). Screen readers are also designed to work when text is broken up by other inline elements e.g.:
Hello world
In this case it reads out both the words Sponsored and Public.
> If searching "Sponsored" in Chrome doesn't match the posts
That also worked perfectly fine in Chrome, Firefox, and Edge. Did you scroll enough to render any Sponsored posts?
meanwhile https://text.npr.org/ ps: thanks for the comments below, I was curious about similar websites