Re: I'm kind of concerned about the culture surrounding usability
Oh my, that's a little worrisome. I used to think FS was kind of a questionably comfortable business model, but seeing that its being eaten up by these UX companies, I think my attention has shifted elsewhere... I haven't watched them because I really don't have 24 hours to kill and my specialty isn't web UI, but lets be honest here, I think these people bank on the fact that most people are like me and don't have 24 hours to kill, and would rather just pay for their services instead.
I've noticed on most of the UX events advertised on twitter that few people outside of the community attend, which really limits their ability to "educate". Why don't they encourage colleges or high schools even to learn the standards properly? When I was in college in 2013 the standards were glossed so over that when it was not web related my fucking professors had no idea what I was talking about, and the web accessibility was glossed over in a sin gle class.
This attitude that "its the developer's responsibility" I think is costing accessibility in the long run and perpetuating their business model. I'm not one for conspiracies but I think this is pretty clear at this point. I'd love to hear why they AREN'T do things that would actually improve this situation and are instead inflating themselves to be social justice warriors, in the most literal sense.
One thing I hear a lot as well from these people - "we shouldn't change the standards because it would confuse a lot of people!". Now, correct me if I'm wrong, but aren't most applications, web and non-web, only provide a linear navigation system with tabbing? It seems that the better applications out there do offer better options sometimes but it's subject to the developer. IMHO this does not produce an EQUIVALENT experience because it's goddamn annoying to tab through everything. Maybe I don't k now all the key commands.
Instead I've had an idea, that I proposed in the OP, where a toolkit that could produce a "tree like tab structure" could be used. AKA, you would have the top layer of stuff, then go down with more detailed information. We could work on making an API or even a GUI that allows tab order to be easily organized by the developer, thus easing time and allowing them to just to it themselves. I think the main reason why accessibility isn't implemented is really because devs don't know how to, so we should make it easier for devs, instead of rubbing off to how great we are. (we don't do that of course, nuh uh!)
no wonder they don't want a scalable model... it would put them out of business. lol. Maybe in the future when I have a bit more momentum behind my back I can sponsor a few of us to work together to try to produce that very model.
_______________________________________________ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
