Discover and share stories

of adventure, connection, and change making.

12 people think this is good

Discuss

  1. {{attachment.file.name}}
  1. {{fields.video_link.url}}

Ready to post! You’ve uploaded the maximum number of images.

Your video is ready to post!

Oops! Nice pic, but it’s just not our (file) type. Please try uploading a .jpg or .png image.

Well, this is embarrassing. Something went wrong when posting your comment. Care to try again?

That image is too large. Maximum size is 6MB.

Please enter a valid URL from YouTube or Vimeo.

Embedding has been disabled for this video.

{{c.errors.other}}

Posting comment...

  • Eric Johansson

    I'm afraid I'm going to be a bit of a buzz kill. I'm afraid that what you propose as a training/education regime will not address important social needs. Specifically, you are not addressing needs of the disabled users or disabled developers like myself.

    I could go into a whole long description about what it means to be hand disabled, an invisible disability and how hard it is to get any support from people with hands to write the code to make your environments work better. I have been involved for the past 10 years in programming using speech recognition. I finally have a solution that's pretty small and powerful but picking out as much code as my hands allow and trying to make a living at the same time, not so much fun.

    https://docs.google.com/document/d/1In11apApKozw_UOPAhVz0ePqns72_6652Dra34xWp4E/edit is a Google documents that is close to what I'm currently working on.

    The big gold color the big picture is something called "no UI" and we are close to it with web apps but veering away because of the lack of vision in the disabled community. Specifically, "no UI" means applications have no user interface built into them. User interface, separately such as in a browser or a standard GUI. By providing an API, software vendors do not need to create a poorly designed accessibility interface that serves no one very well and instead lets the community build their own interfaces based on actual need.

    I think the the good community phrasing for that would be: accessibility is defined by what the user needs, not what the software developer is willing to give.

    oone thing I consider really sick about the problem. To build a test case with a browser isn't that expensive. It would just be a plug-in that would reveal the dom so it can be read and written, then invoke various bits of JavaScript. Not terrible difficult. The hard part is the speech or acoustic user interface but that's where my years of experience come in. yet even with simplicity and ease of prototyping something like this, vendors aren't interested. They are not willing to make a small investment in an API because even that investment costs them more than the perceived value to disabled users. The end result being disabled users end up sitting on the sidelines, increasingly isolated from the online world we live with.

    I do like what good is about and I should probably try your test/education path. I don't think I would pass only because my hands don't work right even though I have over 18 years software development experience and another 20 as a consultant dealing with infrastructure.

    • Eric Johansson

      urg.. we have a saying in the community. "Speech recognition in use, makes mistakes, I correct some". Apologies for the recognition errors I missed

  • Alessandra Rizzotti

    So many assistants I know that aren't in the tech world aren't climbing to the top because no one is training them to get there. Employers need to start thinking outside the box. Why not train their employees in areas that aren't job specific, using tools like Coding for GOOD? Rather than letting an assistant sit in on a call or meeting, have them do work that is challenging.