5 ms·

Make hammers inaccessible to the disarmed? A hammer is a tool for a function. It's not the materialization of privilege for the armed.

ndarilek 8y ago
Sure, but in the context of building a visual layout tool, for someone to say that it shouldn't or doesn't need to be accessible to a blind person because OMG, visual! completely misses the point that it can be, and that other tools before it are. To say "I didn't have time to focus on accessibility because I was struggling with the challenges of making a Java codebase run under wasm" is one thing, and a thing I myself can relate to, having banged my head on wasm's challenges myself. To say "there's just no way to make a visual layout tool accessible to folks who can't see, so I'll just throw up my hands and give up" is another entirely. And I don't think that's what OP is doing, but I do think it's what some in this comment thread are advocating, and that's what bugs me.
- ndarilek 8y ago
  Also, on a note directly applicable to this example, if you think hammers are unusable by folks without arms, might I suggest the documentary Right Footed? I can't say whether or not she uses a hammer without arms, but she flies a plane and drives with her feet, so I can't imagine her not using a hammer if she didn't want to. It feels a bit inspiration-porny at times, and my girlfriend and I both cringed quite a bit while watching it, but I think it makes the point I'm trying to much better than I am. Please don't dismiss a challenge out of hand because you can't imagine in 15 seconds of thought how it might be overcome. "you" being a generic term applicable to anyone reading this, BTW.
  - ralusek 8y ago
    > a challenge _out of hand_ -_-
- ralusek 8y ago
  Making something accessible for a group of people is an opportunity cost at every step in the process. For some reason you've determined that "making the Java codebase run under wasm" is an acceptable diversion from making it accessible, but what makes other decisions less so? For example, I haven't bothered supporting IE for many years, regardless of the fact that there are potential users that will be unable to use services because of it. Same thing with internationalization, there's an opportunity cost that has to be made. That doesn't mean don't make the decision to expand support, I'm just saying that it IS a decision and it DOES have a cost. If you don't perceive it that way, you have to accept that there is a near infinite number of accessibility measures to contend with. Maybe I add support for red green color blindness, and then discover there are other types. The package bundle is too large for users in countries with poor internet access, so you need to have a fallback that removes features, and dedicate some resources to minimizing the initial load time. Oh, the input configuration doesn't make sense for users who are unable to use keyboard and mouse, but use an alternative input mechanism, you have to change it to support that. Oh no, adding support to assist those users has made able users switch to the assisted input configuration, and given them a competitive advantage in your game. Every company cannot service every need. Those that service a need open potential to acquire the market. That may or may not be worth it or possible at any given point, and that's okay.
  - squeaky-clean 8y ago
    > or some reason you've determined that "making the Java codebase run under wasm" is an acceptable diversion from making it accessible, They didn't say that. They said "I didn't have time to focus on accessibility because I was struggling with the challenges of [...]" You're focusing on the [...] which could be anything, it doesn't matter. The point is they're acknowledging it's a legitimate issue that they just didn't have the time or ability to fix. As opposed to saying it's a non-issue or something they refuse to fix. For example, "My personal website isn't accessible because I wrote the code from scratch to learn myself and it's not perfect" is fine. "My personal website isn't accessible because I don't have any blind friends so it doesn't need to be" is less so.
    - ndarilek 8y ago

ndarilek 8y ago

Sure, but in the context of building a visual layout tool, for someone to say that it shouldn't or doesn't need to be accessible to a blind person because OMG, visual! completely misses the point that it can be, and that other tools before it are. To say "I didn't have time to focus on accessibility because I was struggling with the challenges of making a Java codebase run under wasm" is one thing, and a thing I myself can relate to, having banged my head on wasm's challenges myself. To say "there's just no way to make a visual layout tool accessible to folks who can't see, so I'll just throw up my hands and give up" is another entirely. And I don't think that's what OP is doing, but I do think it's what some in this comment thread are advocating, and that's what bugs me.

ndarilek 8y ago
Also, on a note directly applicable to this example, if you think hammers are unusable by folks without arms, might I suggest the documentary Right Footed? I can't say whether or not she uses a hammer without arms, but she flies a plane and drives with her feet, so I can't imagine her not using a hammer if she didn't want to. It feels a bit inspiration-porny at times, and my girlfriend and I both cringed quite a bit while watching it, but I think it makes the point I'm trying to much better than I am. Please don't dismiss a challenge out of hand because you can't imagine in 15 seconds of thought how it might be overcome. "you" being a generic term applicable to anyone reading this, BTW.
- ralusek 8y ago
  > a challenge _out of hand_ -_-
ralusek 8y ago
Making something accessible for a group of people is an opportunity cost at every step in the process. For some reason you've determined that "making the Java codebase run under wasm" is an acceptable diversion from making it accessible, but what makes other decisions less so? For example, I haven't bothered supporting IE for many years, regardless of the fact that there are potential users that will be unable to use services because of it. Same thing with internationalization, there's an opportunity cost that has to be made. That doesn't mean don't make the decision to expand support, I'm just saying that it IS a decision and it DOES have a cost. If you don't perceive it that way, you have to accept that there is a near infinite number of accessibility measures to contend with. Maybe I add support for red green color blindness, and then discover there are other types. The package bundle is too large for users in countries with poor internet access, so you need to have a fallback that removes features, and dedicate some resources to minimizing the initial load time. Oh, the input configuration doesn't make sense for users who are unable to use keyboard and mouse, but use an alternative input mechanism, you have to change it to support that. Oh no, adding support to assist those users has made able users switch to the assisted input configuration, and given them a competitive advantage in your game. Every company cannot service every need. Those that service a need open potential to acquire the market. That may or may not be worth it or possible at any given point, and that's okay.
- squeaky-clean 8y ago
  > or some reason you've determined that "making the Java codebase run under wasm" is an acceptable diversion from making it accessible, They didn't say that. They said "I didn't have time to focus on accessibility because I was struggling with the challenges of [...]" You're focusing on the [...] which could be anything, it doesn't matter. The point is they're acknowledging it's a legitimate issue that they just didn't have the time or ability to fix. As opposed to saying it's a non-issue or something they refuse to fix. For example, "My personal website isn't accessible because I wrote the code from scratch to learn myself and it's not perfect" is fine. "My personal website isn't accessible because I don't have any blind friends so it doesn't need to be" is less so.
  - ndarilek 8y ago