The other thing i "love" about them is that ~50% of the time I take them off music starts playing on my laptop, even if: - it's at the other end of the house - I wasn't listening to anything to begin with - the last time they played anything it was from my phone.
Just 🤦♀️
also, we ridicule them for the USELESS "underwear" case when they come out and in v2 they revise NOTHING about it, not even the fact that the power cord cutout is slightly misplaced.
haha they do have a mind of their own sometimes, it feels. I'm not much of a wireless ear user; I find my screen reader is just too slow at the speeds I need to code.
My wife's got a new set of pods and a phone and the lag is far less, she says. but I skim at over 800 wpm. even a small amount of latency is difficult to adjust to when I'm used to a lightning fast response, you know?
@cachondo Yeah. I can imagine. I listened to a blind person demonstrating how they listened to web pages - i think it was a web page - and like, jesus effing christ it was absolutely incomprehensible to me. Pretty sure he'd gone way past 800.
I get it, there's so much crap on most web pages that you absolutely aren't interested in being forced to read.
That's part of why I made BackupBrain only archive the core content of pages.
there's also a stupid amount of context around web content. things like "graphic", "Link", "heading level x", "button", "list of x items", "navigation landmark" etc. It's rarely just the text.
@cachondo Yeah. I occasionally test my stuff in VoiceOver and it's horrible.
related: I've never found a guide that told me how to design a page that has navigation links & buttons for interactions but doesn't make that miserable for blind readers.
I have no idea what the best practice is that would let me not force blind people to listen to that crap but also provide it for them if they need it.
it's on the screen reader, honestly. You can turn it off. Best experience is to design using regular standard HTML and let the blind people do it. Much of the problem is honestly new users and lack of training, secondarily it's inconsiderate web developers not using standards or not coding properly for nonstandard things they work on.
I don't think it's subobtimal more than, the way the world has to work. A screen reader user might need to know whether something's a heading or a link. How it conveys that information should be on the user and screen reader to decide, not the content author.
Sean Randall
in reply to masukomi • • •masukomi
in reply to Sean Randall • • •@cachondo *gasp in disbelief*
The other thing i "love" about them is that ~50% of the time I take them off music starts playing on my laptop, even if:
- it's at the other end of the house
- I wasn't listening to anything to begin with
- the last time they played anything it was from my phone.
Just 🤦♀️
also, we ridicule them for the USELESS "underwear" case when they come out and in v2 they revise NOTHING about it, not even the fact that the power cord cutout is slightly misplaced.
Sean Randall
in reply to masukomi • • •I'm not much of a wireless ear user; I find my screen reader is just too slow at the speeds I need to code.
masukomi
in reply to Sean Randall • • •@cachondo Wait. What‽
What's the connection between screen reader speed and wireless headphones?
Matt Campbell
in reply to masukomi • • •Sean Randall
in reply to Matt Campbell • • •Sean Randall
in reply to masukomi • • •masukomi
in reply to Sean Randall • • •Huh. TIL
That being said, if you haven't tried already, and you're on a mac, you should 100% see if you can try out some of the new AirPods / AirPods Max.
Apple's layered something funky on top of Bluetooth that - in my experience - addresses the lag. Only works with other apple devices though.
Maybe they'd let you try at an apple store?
They're stupid expensive, & i do complain about them, but I also re-bought when my last pair died.
Sean Randall
in reply to masukomi • • •but I skim at over 800 wpm. even a small amount of latency is difficult to adjust to when I'm used to a lightning fast response, you know?
masukomi
in reply to Sean Randall • • •@cachondo Yeah. I can imagine. I listened to a blind person demonstrating how they listened to web pages - i think it was a web page - and like, jesus effing christ it was absolutely incomprehensible to me. Pretty sure he'd gone way past 800.
I get it, there's so much crap on most web pages that you absolutely aren't interested in being forced to read.
That's part of why I made BackupBrain only archive the core content of pages.
Sean Randall
in reply to masukomi • • •masukomi
in reply to Sean Randall • • •@cachondo Yeah. I occasionally test my stuff in VoiceOver and it's horrible.
related: I've never found a guide that told me how to design a page that has navigation links & buttons for interactions but doesn't make that miserable for blind readers.
I have no idea what the best practice is that would let me not force blind people to listen to that crap but also provide it for them if they need it.
If you come across any, please let me know.
Sean Randall
in reply to masukomi • • •Much of the problem is honestly new users and lack of training, secondarily it's inconsiderate web developers not using standards or not coding properly for nonstandard things they work on.
masukomi
in reply to Sean Randall • • •@cachondo That seems… sub-optimal.
But on the up-side, everything I write these days is just raw HTML with no JavaScript bullshittery involved in page generation.
I've tried to add all the Aria tags on notable things, but I should probably revisit it in Backup Brain just to be sure.
Sean Randall
in reply to masukomi • • •A screen reader user might need to know whether something's a heading or a link. How it conveys that information should be on the user and screen reader to decide, not the content author.