2 ms·
> Accessibility is important, but once you build a wheelchair ramp into a building, the ramp builders have nothing more to do Okay, now see how well that wheel
by acdha 4y ago
> Accessibility is important, but once you build a wheelchair ramp into a building, the ramp builders have nothing more to do
Okay, now see how well that wheelchair user can use the elevators and bathrooms. Do you have braille signs everywhere someone goes? Does your building have ambient features which are difficult for people with sensory processing issues? Are there controls which are hard for people with limited motor skills or only one hand? Did the market change and now people are using motorized wheelchairs which are larger than you designed the ramp for?
Accessibility is like performance or cost optimization: there isn’t a point where you’re done and everything you do affects it. An accessibility team should be working with the developers closely to make sure that their changes don’t impact accessibility and working with users to identify where they could be doing better. Some of that requires fairly deep skills (e.g. screen reader proficiency) where it makes sense to have dedicated specialists to help everyone else understand challenges and evaluate trade offs.
- exodust 4y agoThe building analogy is no longer suitable if you're suggesting the ramp suddenly fails to accommodate new wheelchair designs. The wheelchair design should be your new focus of scrutiny. If the new wheelchair fails to conform to EXISTING ramps found everywhere, the wheelchair is the problem, not the ramp. Ramps are built according to a strict building code. Your suggestion the ramp might need modifying in only the Twitter building by a dedicated team, doesn't add up when considering all ramps in all buildings. > there isn’t a point where you’re done My point is accessibility is inherently part of the design process anyway. Designers are not just making things pretty, clueless to accessibility. After all, Twitter is primarily text. You can always recruit outsiders from time to time, who will stress test and audit. That's a good way to keep on top of accessibility, by getting actual users who need accessibility features, to evaluate your service. But full time in-house? No.
- acdha 4y ago> After all, Twitter is primarily text. You can always recruit outsiders from time to time, who will stress test and audit. That's a good way to keep on top of accessibility, by getting actual users who need accessibility features, to evaluate your service. But full time in-house? This is like saying you don’t need ML specialists because it’s just math, or that we don’t need those expensive security people because Accenture told the CIO they could us experts any time we need them. Accessibility is far more than just “can a screen reader produce text for this element” — starting from the fact that there are many accessibility concerns to which the issue of media forms is irrelevant but going much deeper into how you organize that information. Even if we ignore the prevalence of non-text content, Twitter isn’t a single chunk of prose but the much harder problem of a lot of complex elements which update frequently. You can’t treat this as some quarterly exercise where a consultant runs a scanner - there’s a lot of behavior which must be designed in and tested continuously. When you talk about meeting outside users, yes, that’s good. Guess which team organizes that? Guess which team makes sure you get representative users? Guess who helps make sure developers and designers get the training and time they need?