Archive index

A11y Slackers Gitter Channel Archive 14th of July 2016

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Jul 14 07:58
    [michiel] eagsalazar, note: it's role=dialog, not aria-role=dialog
  2. Job van Achterberg
    @jkva
    Jul 14 08:39
    o/
  3. zakim-robot
    @zakim-robot
    Jul 14 09:15
    [michiel] \o
  4. stevefaulkner
    @stevefaulkner
    Jul 14 10:17

    @eagsalazar wrote:

    "all new html5 elements should also use aria-role"?

    this may also be helpful: http://html5doctor.com/on-html-belts-and-aria-braces/

  5. powrsurg
    @powrsurg
    Jul 14 13:15
    @marcysutton any advice on what to do at that point? I'm glad that hitting tab one more time gets them to the next location, but I'd rather they get to the actual next point
  6. ... though thinking about it now. We actually shouldn't be removing the dialog at that point -- the user should be able to tab to that element. We need to get rid of it later ...
  7. damn, why didn't that occur to me yesterday
  8. zakim-robot
    @zakim-robot
    Jul 14 13:34
    [jv] https://twitter.com/webi18n/status/753271905310937088
  9. zakim-robot
    @zakim-robot
    Jul 14 13:40
    [michiel] >jv @michiel: but i added text too along with photo
  10. [michiel] You did
  11. [michiel] Just, the screenshot specified that it was VoiceOver improvements :)
  12. [michiel] So, it's only for the OS X/iOS version.
  13. [michiel] Screenshot is from OS X, so only OS X version.
  14. [michiel] My point was that there was a lot more information to get from the image than just “a11y improvements in 1Password” :)
  15. [michiel] I'll stop being a jerk now and go back to work.
  16. [jv] i got your point, will add enough info next time. thanks :)
  17. [michiel] Thank you for doing that =D
  18. zakim-robot
    @zakim-robot
    Jul 14 13:46
    [jv] @michiel: I edited the text
  19. [michiel] thumbsup emoji
  20. powrsurg
    @powrsurg
    Jul 14 13:47
    The former SEO in my totally gets "a11y improvements in 1password" as the simple alt-text
  21. zakim-robot
    @zakim-robot
    Jul 14 13:48
    [jv] @powrsurg: I didn’t get your point
  22. [michiel] powrsurg: VoiceOver improvements in OS X version of 1Password
  23. [michiel] or “VoiceOver improvements in 1Password on OS X”
  24. powrsurg
    @powrsurg
    Jul 14 13:51
    I mean, the typical person doing SEO only uses alt text to get over keywords and simple phrases like that are used.
  25. zakim-robot
    @zakim-robot
    Jul 14 13:57
    [michiel] Shouldn't it be “Magical VoiceOver improvement to our superior product 1Password to keep data safe on Apple OS X computers iMac MacBook Pro Air”
  26. zakim-robot
    @zakim-robot
    Jul 14 15:22
    [michiel] Good news everyone! http://www.w3.org/TR/wai-aria-practices/ now points to the latest version of the APG!
  27. [michiel] No more outdated 1.0 stuff.
  28. stevefaulkner
    @stevefaulkner
    Jul 14 15:53
    good
  29. zakim-robot
    @zakim-robot
    Jul 14 16:44
    [alice] \o/
  30. luis garcia
    @garcialo
    Jul 14 16:48
    Great news! :smile:
  31. powrsurg
    @powrsurg
    Jul 14 16:54
    Does anyone have stats on how fast Firefox users upgrade to the latest version? I've updated the codepen I linked to earlier and it now works correctly in IE8+, Chrome, and will work in Firefox 48 (the next version, released August 2nd) once https://bugzilla.mozilla.org/show_bug.cgi?id=962251 (focus/blur events not showing relatedTarget attribute) is fixed. I know this code won't make it up before then, but I don't know how comfortable I feel knowing the tabbing isn't working properly for some users.
  32. zakim-robot
    @zakim-robot
    Jul 14 16:55
    [marcysutton] If you’re testing Firefox with Selenium Webdriver you have to stay on firefox 46 as far as I know. So there’s that.
  33. [marcysutton] But that’s developers, not users.
  34. James Nurthen
    @jnurthen
    Jul 14 16:58
    Most enterprise users will be on an ESR. The current is 45. They will not get upgraded until 52 (and actually probably not until 53 is released is when 52ESR will get released)
  35. powrsurg
    @powrsurg
    Jul 14 18:07
    Yeah, I don't get the ESR notes since they said that ESR 45.3 was equivalent to 48. Do people upgrade to those versions?
  36. I was able to get access to our Google Analytics and saw 72.4% were on 47.
  37. James Nurthen
    @jnurthen
    Jul 14 18:27
    I get ESR dot releases yes.... I'm not sure how it is equivalent to 48 though.....
  38. I'm on 45.2.0 ESR
  39. it is not equivalent to 47 though... It gets "security and stability" fixes only
  40. I would not have thought that anything to do with blur/focus would be included in that
  41. powrsurg
    @powrsurg
    Jul 14 19:04
    Yeah, I don't expect it to be
  42. it's shocking to me that it's taken until Firefox 48 for them to add the necessary support to get the new active focus element from an onblur handler.
  43. Even trying to use document.activeElement in that context is useless since it returns the body
  44. powrsurg
    @powrsurg
    Jul 14 19:25
    And now my NVDA won't bring up the Elements List in Firefox when an element with role="dialog" is open (we use the <dialog> element but Firefox doesn't support that at this time)
  45. Chrome too
  46. eagsalazar
    @eagsalazar
    Jul 14 22:24
    @stevefaulkner That is interesting because http://www.html5accessibility.com/, if you look at header specifically, versus what http://validator.w3.org/nu/?doc=http%3A%2F%2Ftink.uk%2F marks as "unnecessary" don't match up. I get that everything is supported and mapped to the accessibility tree for html4, it looks really spotty for html5, contrary to what your article is suggesting. What's the right answer?
  47. The guideline I was planning on giving my dev team is "if there isn't a green check (fully supported and mapped) for all browsers, use role=, if there is, don't use role= and go ahead and depend on the semantics from the element'
  48. Looking at that list, that essentially boils down to "always use role= for all HTML5 elements". No?
  49. James Nurthen
    @jnurthen
    Jul 14 22:27
    ... if you want to support MSFT browsers :)
  50. eagsalazar
    @eagsalazar
    Jul 14 22:28
    Hah, sadly I have no choice in that matter
  51. James Nurthen
    @jnurthen
    Jul 14 22:32
    @powrsurg If you turn off Forms mode then you can use it... dialogs trigger app mode in NVDA - in order to browse using virtual features you have to toggle it off.