Archive index

A11y Slackers Gitter Channel Archive 17th of September 2016

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Sep 17 06:45
    [chris__pearce] Calculator
  2. zakim-robot
    @zakim-robot
    Sep 17 12:50
    [car] @chris__pearce You probably want to make sure that typing the values on the keyboard works, so that the user can, for example, type: 1+1= (output probably needs a label (i.e. "Result"), and yes, it should probably be a live region). I'm not sure AT users would want to navigate through the buttons, but if so, you might give them 2D arrow key navigation (up/down/left/right), at least for the numbers section. Does the OS X calculator work well with keyboard?
  3. zakim-robot
    @zakim-robot
    Sep 17 13:01
    [car] You probably want to make sure that the Copy and Paste shortcuts work too (when anything has focus - not just the output).
  4. [chris__pearce] @car thanks for that, makes sense.

    Does the OS X calculator work well with keyboard?

    It seems OK, each number maps to a number key and same for the operators, ESC = clear and ENTER = ‘=‘.

  5. [chris__pearce] Ah yes copy and paste shortcuts work too
  6. zakim-robot
    @zakim-robot
    Sep 17 13:06
    [chris__pearce] @car any advice on the markup?
  7. [car] Not really - sorry. Although the usual advice is to stay away from role="application". :)
  8. [car] Have you tried it in VoiceOver?
  9. zakim-robot
    @zakim-robot
    Sep 17 13:25
    [car] My thinking is that the screen readers will "help" you answer your markup questions (by working well, or not working at all...) ;)
  10. zakim-robot
    @zakim-robot
    Sep 17 13:31
    [chris__pearce] Ok thanks, yeah that’s good advice about role=“application”. I haven’t tried testing in SR’s yet, still trying to complete the JavaScript. When I get there I’ll test on both NVDA and VoiceOver +1.
  11. zakim-robot
    @zakim-robot
    Sep 17 13:42
    [car] Ok, cool. Just FYI, I fired up the Windows calculator, and I see that they chose to not let the buttons take focus at all. So the only control that gets focus is their Result text, i.e. tab key & arrow keys do nothing. The keyboard user has to enter equations directly using keyboard (i.e. 1+1= or paste equation, etc). So I guess that's one way to do it that may or may not be helpful to AT/keyboard users. You said you were doing it as a learning exercise, though, so you might want to keep the navigation keys working so you can play with how the markup works with the screen readers. Have fun!
  12. zakim-robot
    @zakim-robot
    Sep 17 14:01
    [michiel] For those interested, I posted my APG talk slides: https://twitter.com/MichielBijl/status/777083482736558080
  13. zakim-robot
    @zakim-robot
    Sep 17 18:42
    [garcialo] You should make a series of "The practical guides"
  14. [michiel] The practical series?
  15. [michiel] I’m not sure that is very, err, practical.
  16. zakim-robot
    @zakim-robot
    Sep 17 18:52
    [michiel] Patrick said he’d be doing a “Practical Guide to Michiel”
  17. zakim-robot
    @zakim-robot
    Sep 17 21:11
    [car] Good slides, @michiel - thanks for posting! Loved the group photo!