Archive index

A11y Slackers Gitter Channel Archive 28th of December 2016

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Dec 28 10:02
    [nchardon] Hello! I am trying to test an angularjs application with pa11y and I get the following error :
    Error: HTML CodeSniffer: SyntaxError: DOM Exception 12
    at Object.<anonymous> (D:\npm\node_modules\pa11y\lib\pa11y.js:65:16)
    at Object.f [as onCallback] (D:\npm\node_modules\pa11y\node_modules\once\once.js:17:25)
    at D:\npm\node_modules\pa11y\node_modules\node-phantom-simple\node-phantom-simple.js:636:30
    at Array.forEach (native)
    at IncomingMessage.<anonymous> (D:\npm\node_modules\pa11y\node_modules\node-phantom-simple\node-phantom-simple.js:617:17)
    at emitNone (events.js:72:20)
    at IncomingMessage.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:913:12)
    at nextTickCallbackWith2Args (node.js:442:9)
    at process._tickCallback (node.js:356:17)
    I have tried using the wait parameter, still I got the same error. Any suggestions to get pa11y to work?
  2. zakim-robot
    @zakim-robot
    Dec 28 15:28
    [sylvia] Good morning everyone! I have a JAWS/Windows configuration issue. Yesterday, I finally got an upgrade to JAWS 18 on my work machine (up from 12! My IT department has be sluggish). I love the new JAWS, and it's working great. However, the first time I turned it on it completely borked my system fonts. They are jagged an very hard to read.
  3. [sylvia] Jaws 18, Windows 7, work machine with limited admin access. I tried a restart, and no luck, even with JAWS off. Has anyone experienced this issue?
  4. [sylvia] Screenshot of font issue
  5. zakim-robot
    @zakim-robot
    Dec 28 15:33
    [quidkid] I’m trying to redo my menu and one of the guidelines is this: "Any key that corresponds to a printable character: Move focus to the next menu item in the current menu whose label begins with that printable character.” i guess the brute force way is to listen for the beginning of each character of each item but surely there is a more efficient way?
  6. [quidkid] @sylvia no idea but tried some googling and maybe this might help? maybe JAWS turned off a font smoothing thing http://www.thewindowsclub.com/disable-font-smoothing-windows (although in your case try enabling it)
  7. zakim-robot
    @zakim-robot
    Dec 28 15:38
    [quidkid] actually this seems more straightforward @sylvia http://www.howtogeek.com/howto/28790/tweak-cleartype-in-windows-7/
  8. Mallory
    @StommePoes
    Dec 28 15:44
    My fonts look like that but I didn't think it was from JAWS, it was stuff I had to manually turn off like clearType and then something additionally in Firefox for old ZoomText
  9. zakim-robot
    @zakim-robot
    Dec 28 15:44
    [sylvia] @quidkid Thanks, I'll check. Re: your menu; what kind of menu is it? You may be able to take advantage of a built in HTML features.
  10. [sylvia] I'd be hesitant to add a keystroke listener, because it might override useful screen reader shortcuts
  11. [quidkid] @sylvia you click on a hamburger icon and it slides out from the right
  12. [sylvia] Native mobile or HTML?
  13. Mallory
    @StommePoes
    Dec 28 15:46
    @nchardon no idea though if nothing else comes along, you could maybe try tweeting at @_hollsk
  14. zakim-robot
    @zakim-robot
    Dec 28 15:46
    [quidkid] also where do we put the role=”menu item” on the actual a tag or the li tag
  15. [quidkid] @sylvia html
  16. [sylvia] Hmmm. That's not really a typical feature for a menu, especially with a limited number of options. Where is this guidelien from?
  17. [quidkid] from ssbart they gave me a list of things to fix in my menu. I had it completely working trap focus and all with the tab but they want arrow keys within. lemme get it for ya
  18. [sylvia] Cleartype did fix the issue, thanks
  19. zakim-robot
    @zakim-robot
    Dec 28 15:51
    [sylvia] I'm really hesitant to recommend the menu-first-letter thing. It's not a feature I have seen, so not something I would think to try, outside of a select box. However, it really might break other keyboard shortcuts, especially for screen reader users
  20. [sylvia] Any screen reader/keyboard-only users on the channel have thoughts? Is this a feature you would enjoy, or would you find it annoying?
  21. [sylvia] It is in the W3C WAI-ARIA best practices, which is where the report is pulling from
  22. [quidkid] another issue is that i have to pass the guidelines. We need to meet WCAG AA and 508 since our client has government funding so if that’s necessary then I have to do it :(
  23. zakim-robot
    @zakim-robot
    Dec 28 15:56
    [sylvia] Best practices are suggestions, not rules, at least in most settings
  24. [sylvia] Your internal policies may vary, of course.
  25. [sylvia] Yeah, that feature is listed as optional
  26. [sylvia] https://www.w3.org/TR/wai-aria-practices/#menu
  27. [sylvia] I think it's meant for to apply to a menu in a desktop-style application, like the File menu in Windows programs
  28. zakim-robot
    @zakim-robot
    Dec 28 16:06
    [quidkid] @sylvia wow thank you!! haha he didn’t tell me it was optional. but yeah, would be curious whether it is an annoying or welcome feature
  29. [sylvia] The guidelines change from time to time; your reporter may have been working off a previous version.
  30. [sylvia] The newer version has different advice around TAB as well:
  31. [sylvia] Tab: Moves focus to the next element in the tab sequence, and if the item that had focus is not in a menubar, closes its menu and all open parent menu containers. Shift + Tab: Moves focus to the previous element in the tab sequence, and if the item that had focus is not in a menubar, closes its menu and all open parent menu containers
  32. [quidkid] whoa
  33. [sylvia] I would recommend that pattern for sure, instead of just the up/down arrows, because it's less likely to break mobile screen readers like VoiceOVer
  34. [quidkid] so i didn’t need to trap focus
  35. [quidkid] wait im not sure i understand what im supposed to be doing anymore
  36. [quidkid] before i had it working nicely with tab and it traps focus within the menu
  37. [sylvia] How do you get out of the menu?
  38. [quidkid] then i now added immediate focus on the first item upon opening the menu instead of waiting for tab
  39. [quidkid] you tab to the close button and hit enter
  40. zakim-robot
    @zakim-robot
    Dec 28 16:13
    [sylvia] Defensible, but I'd find it slightly annoying to have to tab through the whole menu.
  41. [sylvia] That's really a UX question, though. If you really can't do user testing, I'd go with the latest version of the WAI-ARIA practices, as linked above.
  42. [sylvia] If you do have have some users you can test with, I'd see what works best for them.
  43. [sylvia] Or at least see what some users on the channel think. I'm only a part-time screen reader/keyboard user, so I'm not the best judge of what is convenient.
  44. zakim-robot
    @zakim-robot
    Dec 28 16:25
    [quidkid] @sylvia so i’ll use tab to get in and out and arrows to navigate within. i have trouble implementing this though if you have any suggestions
  45. [sylvia] The guidelines actually suggest using tab to navigate in addition to the arrows. So if you are moving from item 2 to item 3, tab would work. If you tab off the last item, it would close the menu.
  46. [sylvia] Specific code suggestions? What tools/frameworks are you using?
  47. [quidkid] jquery, javascript, html, css
  48. zakim-robot
    @zakim-robot
    Dec 28 17:32
    [marcysutton] @nchardon I would google that error, it can give you a hint about where the error might be coming from (illegal id attributes)
  49. zakim-robot
    @zakim-robot
    Dec 28 20:45
    [quidkid] @sylvia whew finally got the arrows working. they currently don’t loop through the whole thing though. i’ll add that even though that’s optional but for tab, so instead of trapping focus, after the last one, it will close the menu -question which element would have the focus? the menu button or the next item?
  50. zakim-robot
    @zakim-robot
    Dec 28 20:59
    [sylvia] @quidkid: congrats! Sorry to wander off there; all the meetings today
  51. [sylvia] I'd go to the menu button, so people could reopen the menu or browse non-interactive content between the button and the next focusable
  52. [quidkid] @sylvia thank you so much!!