Hello. I am probably not going to on this formerly-known-as-bird app very much because I have been dealing with very bad, very draining health issues. Back offline I go.
I hope you're all well.
“This is what disability advocates have said all along…The able and the disabled aren’t two different kinds of people but the same people at different times. Last year, I was healthy; this year, I had a breathing ailment, even if nobody could say exactly what that ailment was.”
The other thing I need ALL of my people to embrace is this: you cannot outperform, out accolade, out accomplish, etc., white supremacy. You cannot. It’s not a meritocracy. You’re mad because deep down, you still think it is, even if it’s unbalanced. It’s not.
me opening a PR that touches twenty-five (25) files: RIP to the other people who were smitten by the gods for their hubris, but i'm different. perhaps even better than the gods
Almost every argument against accessibility comes down to the belief that someone's business, product, or service deserves to exist more than disabled people deserve to have access and community. It presupposes that disabled people are burdensome. That's garden-variety ableism.
1. Nobody has ever said you can't build things for fun, actually
2. If the idea of serving your users crushes the fun of web development for you, you're weird and miserable
I love when people are bold with their ableism.
"I would have no problem if [building accessible websites] were only a moral obligation [...]. Legal obligations that require a developer add something frustrate me, because they essentially crush people doing things for fun."
@fiinixdesign I'd say both. Disabled don't people "need" non-Disabled support to succeed, and I'm not saying we should ever prioritize hiring non-Disabled people specifically – only that non-Disabled people should be the ones bearing the brunt of an ableist environment where possible.
hear me out: i don’t think that hiring Disabled people for accessibility work is always the right call.
unless they’re prepared for it, i wouldn’t want to put Disabled people into a space where no one has done work on inaccessibility or ableism. that’s a recipe for more harm.
@alvaro_montoro My post addressed devs, the people who can ingest news of this bug and work around Apple's shortcomings. My choice to pick a specific topic for my post on this microblogging website and then do a little quip at the end does not mean I am letting browser vendors off the hook.
PSA: Accessibility mappings for <summary> are broken in Safari as of at least version 17 (can't test earlier at the moment).
- MacOS: VoiceOver doesn't report changes in state of <summary> when you toggle it
- iOS: VoiceOver doesn't report *any* semantics or state changes.
1/2
@alvaro_montoro I'm aware of that. My grumble at the end is because people often (well-meaningly) say that we get accessibility "for free" by using things that come from the web platform. People have the impression that platform-native things are flawless. They obviously aren't.
@pauljadam I can't say how long this exact bug has existed but comboboxes have been broken in Safari for a long time. I'm on Safari 17 in MacOS 13.6. I don't know my Blind user's config, sadly, but they are definitely on an earlier OS and Safari version
Who do I have to talk to about getting comboboxes working in Safari? I shouldn’t have to tell a Blind user that they might need to switch browsers because there’s nothing my team and I can do to make their chosen tools (Safari + VoiceOver) work in our app
@pauljadam These are broken with Safari with VoiceOver for me as well. Pressing VO+Space on your combobox does nothing in Safari, but works just fine in Chrome. VoiceOver only interacts with your implementation correctly when I remove role=combobox, which aligns with my other findings.