Archive index

A11y Slackers Gitter Channel Archive 28th of August 2016

What fresh hell is THIS now? - Patrick Lauke
  1. Fiona Holder
    @FionaHolder
    Aug 28 07:07
    Decent write up I found of the discussion we were having the other day about changing how a screen reader pronounces things: http://www.ssbbartgroup.com/blog/zip-z-p-z-p-forcing-correct-pronunciation-screen-readers/
  2. stevefaulkner
    @stevefaulkner
    Aug 28 10:41

    [michiel] karlgroves: ARIA WG works with various AT vendors to get stuff implemented. Everything in 1.1 needs two implementations to survive to CR/RC

    CR exit criteria for ARIA is browser implementation only AFAIK

  3. zakim-robot
    @zakim-robot
    Aug 28 10:43
    [jv] What is the best way to practice/learn using Voiceover on mac?
  4. [jv] How much important is to learn to use Voicer over to operate other things Mac other than the Web browser?
  5. zakim-robot
    @zakim-robot
    Aug 28 12:22
    [michiel] stevefaulkner: I thought it was AT? I'll look it up.
  6. [michiel] From 1.0:
  7. [michiel] Because many of the tests depend on mapping to accessibility APIs which often have only one implementation, successful mapping of a given WAI-ARIA feature need only be demonstrated for any accessibility API, not necessarily each accessibility API.
    [michiel] In general, a distinct implementation is counted as a distinct user agent on a given operating system mapping to a particular platform. For instance, Firefox on Windows mapping to MSAA + UIA Express is one implementation, and Safari on OS X mapping to AXAPI is another.
  8. [michiel] Looking for the 1.1 version.
  9. zakim-robot
    @zakim-robot
    Aug 28 12:30
    [michiel] jv, this might help: http://www.apple.com/voiceover/info/guide/
  10. stevefaulkner
    @stevefaulkner
    Aug 28 19:22

    @MichielBijl

    assistive technology behavior will not be tested as a formal part of the Candidate Recommendation process.

    https://www.w3.org/WAI/ARIA/1.0/CR/

  11. zakim-robot
    @zakim-robot
    Aug 28 21:28
    [michiel] Thanks Steve
  12. zakim-robot
    @zakim-robot
    Aug 28 23:58
    [caesar] Is there a way to make nested menus read correctly in most/all SR? I'm currently using aria menu roles in a list structure, but <ul role="menu"> is causing JAWS (for example) to read every item in the submenu when entering.
  13. [caesar] Example: optus.com.au/about. Entering into the 2nd level menu causes JAWS to read "Menu sustainability corporate our network careers etc..." and then tabbing to each element makes them read twice, e.g. "corporate corporate"
  14. [caesar] VO seems to ignore nesting/aria menu roles altogether.