Archive index

A11y Slackers Gitter Channel Archive 17th of April 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Apr 17 17:56
    [mayabenari] Do people have thoughts on how product managers can incorporate accessibility into their project workflow? How it should it be represented in their definition of done / acceptance criteria for new features and stories? Thanks!
  2. Eric S. Johansson
    @alsoeric
    Apr 17 18:02
    mayabenari, Accessibility has to be built-in from the beginning. As a disabled developer requiring speech recognition, I learned that slapping on accessibility features on top of the GUI loses most of the meta-information you need in order to be able to provide a good interface based on text to speech or speech recognition.
  3. For example, if I was to build an editor designed for speech use, it would be a little resemblance to existing editors. Instead of navigating by characters and lines, you would operate on structural elements of the data and patterns you can speak.
  4. zakim-robot
    @zakim-robot
    Apr 17 18:11
    [spell] @mayabenari Check out this talk from last years ID24. Very insightful. https://youtu.be/JcdYkxjLtaM
  5. [mayabenari] Agree @alsoeric that it has to be considered from the start and built in as you go, which is why we want to ensure it’s being considered at each user story / feature
  6. zakim-robot
    @zakim-robot
    Apr 17 18:16
    [mayabenari] Thanks @spell, I watched it, good stuff
  7. Eric S. Johansson
    @alsoeric
    Apr 17 18:19

    @mayabenari It would be interesting to have a look see at the product and how you are planning on approaching speech recognition and text-to-speech based interfaces.

    For example, gitter is almost completely inaccessible to me. I need to dictate into a separate editing box and then cut and paste the text into the chat box. I can't access any of the UI elements by speech because they don't have names. The best I can do is move the mouse over the item and say "mouseclick"

  8. @mayabenari Another thing to remember with accessibility features is that automation and customization of the user interface is incredibly important. My speech interface changes on the workflow in use within an application, not just between applications.
  9. zakim-robot
    @zakim-robot
    Apr 17 18:38
    [karlgroves] @mayabenari I have a few thoughts http://www.karlgroves.com/category/agile-accessibility/
  10. [shawn.henning] Do any screen reader users use Emacs? I did some exploring this weekend, and Emacs in Terminal with VoiceOver on macOS seems pretty accessible, but I am not sure I want to learn another keyboard paradigm. Minor gripe so far is that <down arrow> reads the entire line while C-n (next line native command) does not.
  11. powrsurg
    @powrsurg
    Apr 17 21:40
    @mayabenari, for certain people you are going to have to sell that as crafting the user experience. A good portion of that is described as creating an Aural UI. Some of that you can sell as designing for better integration with services like Home, Alexa, Siri, etc (I realize some of these don't work with the web yet)
  12. If it helps you can also sell captions and transcripts on videos as a part of SEO