Archive index

A11y Slackers Gitter Channel Archive 22nd of September 2016

What fresh hell is THIS now? - Patrick Lauke
  1. Peter Krautzberger
    @pkra
    Sep 22 06:48
    Good morning, slackers! :coffee:
  2. Job van Achterberg
    @jkva
    Sep 22 07:13
    \o/
  3. Peter Krautzberger
    @pkra
    Sep 22 07:26
    \o/ @jkva
  4. I'm wondering what people think about using a checkbox to toggle visibility of an adjacent span (using CSS).
  5. Job van Achterberg
    @jkva
    Sep 22 07:29
    @pkra you could, and use aria-expanded & aria-owns to indicate that, no>
  6. (even given the problems with aria-owns support)
  7. Peter Krautzberger
    @pkra
    Sep 22 07:30
    cool. I wasn't aware of those.
  8. Peter Krautzberger
    @pkra
    Sep 22 07:31
    From a quick test, it seemed like screenreaders would read out the content anyway when toggled.
  9. Job van Achterberg
    @jkva
    Sep 22 07:31
    Gah, I mean aria-controls, not owns, sorry
  10. pkra: if you use display:none for toggling, they still read it out?
  11. Peter Krautzberger
    @pkra
    Sep 22 07:31
    no no.
  12. zakim-robot
    @zakim-robot
    Sep 22 07:32
    [michiel] No no no no, no no there's no limit.
  13. Peter Krautzberger
    @pkra
    Sep 22 07:32
    I mean, when I reveal, the AT would read out the entire label (which wraps input + span).
  14. michiel mtha mtha mtha mtha. no no ...
  15. Job van Achterberg
    @jkva
    Sep 22 07:33
    Can you use the label separately and associate with a for=? That's overall better supported iirc
  16. zakim-robot
    @zakim-robot
    Sep 22 07:33
    [michiel] Mtha?
  17. Job van Achterberg
    @jkva
    Sep 22 07:33
    beat noise?
  18. Peter Krautzberger
    @pkra
    Sep 22 07:33
    @jkva gets me.
  19. zakim-robot
    @zakim-robot
    Sep 22 07:33
    [michiel] Ahh
  20. Job van Achterberg
    @jkva
    Sep 22 07:33
    ntsh
  21. zakim-robot
    @zakim-robot
    Sep 22 07:33
    [michiel] What do I get?
  22. Peter Krautzberger
    @pkra
    Sep 22 07:34
    not having to meet me?
  23. :(
  24. zakim-robot
    @zakim-robot
    Sep 22 07:34
    [michiel] :(
  25. Job van Achterberg
    @jkva
    Sep 22 07:34
    :)
  26. zakim-robot
    @zakim-robot
    Sep 22 07:34
    [michiel] I'm still here today.
  27. Job van Achterberg
    @jkva
    Sep 22 07:34
    Sorry, don't want the room to be all sad
  28. zakim-robot
    @zakim-robot
    Sep 22 07:35
    [michiel] gives flowers to jkva
  29. Peter Krautzberger
    @pkra
    Sep 22 07:35
    @jvka I don't see how to style it sensibly if I'm not wrapping everything in the label.
  30. :( :( :(
  31. which is a sad reason, I know.
  32. (just a pen to play)
  33. Job van Achterberg
    @jkva
    Sep 22 07:36
    @pkra can you give me the edit link?
  34. let's clean that up a bit...
  35. Job van Achterberg
    @jkva
    Sep 22 07:41
    Ah right, I see what you're saying
  36. Peter Krautzberger
    @pkra
    Sep 22 07:41
    what was I saying? :smile:
  37. (also: the realization that footnotes are terrible thing in general)
  38. Job van Achterberg
    @jkva
    Sep 22 07:43
    @pkra: I'd use a toggle button
  39. And style it appropriately
  40. Peter Krautzberger
    @pkra
    Sep 22 07:44
    you mean <button>?
  41. Job van Achterberg
    @jkva
    Sep 22 07:44
    And you can indicate it with aria-pressed to AT
  42. yes
  43. label it with Show footnote [N]
  44. well, aria-label
  45. or just 'footnote 1' in general, that's clear to everybody
  46. and easier to click with mouse or finger
  47. Peter Krautzberger
    @pkra
    Sep 22 07:45
    I was trying to avoid that (non-JS fallbacks).
  48. Job van Achterberg
    @jkva
    Sep 22 07:45
    you can still superscript it
  49. Peter Krautzberger
    @pkra
    Sep 22 07:45
    I wished I didn't have to superscript this ;-)
  50. jkva @jkva thinks
  51. Job van Achterberg
    @jkva
    Sep 22 07:46
    Either that or your in-page anchor with :target selector is a non-js alternative
  52. Peter Krautzberger
    @pkra
    Sep 22 07:46
    Ah, now we go down the rabbit hole -- that has other repercussions due to the surrounding technology in this project...
  53. zakim-robot
    @zakim-robot
    Sep 22 07:47
    [michiel] pkra: you can work around it with <label for=job></> <input type=checkbox id=job/><span>freelance firefighter</span>
  54. Peter Krautzberger
    @pkra
    Sep 22 07:47
    Do you have a link for the problems around "input inside label"?
  55. zakim-robot
    @zakim-robot
    Sep 22 07:47
    [michiel] Input#job:checked + span { display: awesome }
  56. [michiel] I mean, block.
  57. Peter Krautzberger
    @pkra
    Sep 22 07:48
    you mean display:michiel?
  58. zakim-robot
    @zakim-robot
    Sep 22 07:48
    [michiel] 8)
  59. Peter Krautzberger
    @pkra
    Sep 22 07:49
    @michiel I don't know how to visually style that well :(
  60. Job van Achterberg
    @jkva
    Sep 22 07:50
    @pkra I remember @stevefaulkner writing an article on that
  61. Having trouble finding it
  62. zakim-robot
    @zakim-robot
    Sep 22 07:50
    [michiel] What is the problem with styling it pkra?
  63. Peter Krautzberger
    @pkra
    Sep 22 07:51
    I don't want to show a checkbox and I need to provide a target area to toggle it.
  64. I picked this approach from wtfforms (though I also filed mdo/wtf-forms#70 immediately ;-) )
  65. zakim-robot
    @zakim-robot
    Sep 22 07:51
    [michiel] That is the label.
  66. [michiel] You can click the label.
  67. [michiel] Maybe you can do an inline details/summary?
  68. Job van Achterberg
    @jkva
    Sep 22 07:52
    But it also shows the checkbox. Is that what you don't like @pkra? I mean I agree - it makes it look less like a footnote
  69. Peter Krautzberger
    @pkra
    Sep 22 07:52
    @michiel hehe. I need something that works
  70. Job van Achterberg
    @jkva
    Sep 22 07:53
    Otherwise :hover, but that's also a problem
  71. Peter Krautzberger
    @pkra
    Sep 22 07:53
    I added a third example to the pen.
  72. where I split things up.
  73. but now I can't trigger the checkbox.
  74. zakim-robot
    @zakim-robot
    Sep 22 07:53
    [michiel] Button + ARIA expanded
  75. Peter Krautzberger
    @pkra
    Sep 22 07:53
    (by mouse)
  76. Job van Achterberg
    @jkva
    Sep 22 07:53
    But that requires JS
  77. we're trying to not use JS
  78. Peter Krautzberger
    @pkra
    Sep 22 07:53
    @michiel just as jkva said.
  79. I was hoping for a non-JS solution.
  80. Job van Achterberg
    @jkva
    Sep 22 07:53
    So, progressive enhancement
  81. 1) link with in-page anchor to the actual footnote
  82. 2) enhance link into toggle button with JS
  83. Peter Krautzberger
    @pkra
    Sep 22 07:54
    Right.
  84. Job van Achterberg
    @jkva
    Sep 22 07:54
    And have the footnote link have a link [back to reference] for easy nav
  85. so you can easily go to the footnote and back
  86. Everyone wins
  87. Peter Krautzberger
    @pkra
    Sep 22 07:55
    Do you have some references for why this approach is bad though?
  88. Job van Achterberg
    @jkva
    Sep 22 07:55
    Which approach?
  89. Peter Krautzberger
    @pkra
    Sep 22 07:55
    the input+span inside label.
  90. Job van Achterberg
    @jkva
    Sep 22 07:55
    I'm trying to find steve's article on it
  91. Peter Krautzberger
    @pkra
    Sep 22 07:55
    ah.
  92. thanks.
  93. Job van Achterberg
    @jkva
    Sep 22 07:55
    for= is better supported by browsers iirc
  94. ?
  95. 2011 tho
  96. Peter Krautzberger
    @pkra
    Sep 22 07:56
    I was about to say that ;-)
  97. Job van Achterberg
    @jkva
    Sep 22 07:56
    But I also recall @karlgroves using wrapped inputs because of some AT compatibility
  98. is the article for my previous link
  99. Job van Achterberg
    @jkva
    Sep 22 07:57
    Isn't hat the same one?
  100. I ran some tests and found that a control labeled using for and id without placing the control inside the label element is by far the most robust method. I also found use of aria-labelledby is more robust across browsers and AT than the standard HTML method of placing a control inside the label.
  101. Peter Krautzberger
    @pkra
    Sep 22 07:58
    indeed.
  102. Job van Achterberg
    @jkva
    Sep 22 07:58
    I mean, the spec says you can do both
  103. Peter Krautzberger
    @pkra
    Sep 22 07:58
    sorry :D
  104. Job van Achterberg
    @jkva
    Sep 22 07:58
    Nah - it's a good point
  105. Peter Krautzberger
    @pkra
    Sep 22 07:58
    Right. that was the first thing that surprised me -- it was valid HTML :)
  106. Job van Achterberg
    @jkva
    Sep 22 07:59
    "When in doubt, follow the spec. When the spec is ambiguous, do what @stevefaulkner says"
  107. Peter Krautzberger
    @pkra
    Sep 22 07:59
    "When from 2012, maybe run the test again"
  108. :)
  109. I mean IE9 for crying out loud.
  110. (heh, wasn't so long ago that IE9 was bliss)
  111. Job van Achterberg
    @jkva
    Sep 22 08:01
    @pkra I don't know what to tell you, honestly.
  112. Peter Krautzberger
    @pkra
    Sep 22 08:01
    I should test some more.
  113. Job van Achterberg
    @jkva
    Sep 22 08:01
    That's always smart
  114. Peter Krautzberger
    @pkra
    Sep 22 08:01
    And see how this behaves in real life.
  115. Will report back.
  116. Job van Achterberg
    @jkva
    Sep 22 08:01
    Thanks for the good discussion :)
  117. Peter Krautzberger
    @pkra
    Sep 22 08:01
    thanks for your time, @jkva, @michiel!
  118. Peter Krautzberger
    @pkra
    Sep 22 08:25
    Gah. One more question.
  119. opacity:0 hiding.
  120. ChromeVox ignores content with opacity:0 but I think no other AT. amiright?
  121. (and I think ChromeVox might lose the ability to detect opacity in v2 since they're moving out of the DOM)
  122. Job van Achterberg
    @jkva
    Sep 22 09:05
    @pkra not sure. What are you trying to accomplish?
  123. Peter Krautzberger
    @pkra
    Sep 22 09:05
    Accessibly hiding an input checkbox.
  124. I was using a 1px hack but FF and Safari ignore it.
  125. they still show the checkbox.
  126. The opacity:0 hack (e.g., mdo/wtfforms) works visually but ChromeVox then ignores the checkbox input.
  127. thus not accessibly hidden.
  128. Job van Achterberg
    @jkva
    Sep 22 09:07
    So you want to hide it visually but be still available to AT @pkra?
  129. Peter Krautzberger
    @pkra
    Sep 22 09:07
    AFAIK ChromeVox was the only AT that ignores opacity:0 content but I can't test thoroughly right now.
  130. Yup.
  131. To be clear: there's still something there.
  132. Job van Achterberg
    @jkva
    Sep 22 09:08
    have you tried this class: https://www.irccloud.com/pastebin/YFAPUuAj/
  133. Peter Krautzberger
    @pkra
    Sep 22 09:08
    It's just that you can't style checkboxe, right.
  134. Job van Achterberg
    @jkva
    Sep 22 09:08
    I've never tried using that on a checkbox tho
  135. Peter Krautzberger
    @pkra
    Sep 22 09:08
    I tried something similar.
  136. But I'll try that :)
  137. Job van Achterberg
    @jkva
    Sep 22 09:08
    Although I get kinda worried when I hear about controls being hidden
  138. Sounds hackish
  139. Also you'll have to take it out of the focus
  140. otherwise keyboard focus will focus on something that can't be seen
  141. Peter Krautzberger
    @pkra
    Sep 22 09:10
    Again, there's something there.
  142. and I'd like the hidden control to focus on the right area.
  143. Not my fault that browsers don't let us style checkboxes :(
  144. Job van Achterberg
    @jkva
    Sep 22 09:11
    Ah, that's what you mean
  145. Peter Krautzberger
    @pkra
    Sep 22 09:11
    But I'd rather use the native elements and controls.
  146. Job van Achterberg
    @jkva
    Sep 22 09:11
    You have something overlaying the hidden checkbox
  147. Peter Krautzberger
    @pkra
    Sep 22 09:11
    Yeah.
  148. Job van Achterberg
    @jkva
    Sep 22 09:11
    Ah, now I get it
  149. Peter Krautzberger
    @pkra
    Sep 22 09:11
    You'll allow it? ;-)
  150. Yay -- your accessibly-hiding css works better than mine.
  151. Thanks for that.
  152. Peter Krautzberger
    @pkra
    Sep 22 09:30
    Let me correct that. The CSS works but breaks the input control :(
  153. Job van Achterberg
    @jkva
    Sep 22 09:31
    I was wondering how well it'd apply.
  154. When I did something similar before (toggle switch) I used the opacity trick
  155. Peter Krautzberger
    @pkra
    Sep 22 09:31
    Wait a minute...
  156. (But yes, I think the opacity trick is probably better since ChromeVox should stop ignoring that)
  157. Ok. I had broken the input in another way -- but I also had misapplied your CSS example (and it gets ignored on an input on FF)
  158. Blargh.
  159. Job van Achterberg
    @jkva
    Sep 22 09:41
    Blargh indeed.
  160. Peter Krautzberger
    @pkra
    Sep 22 09:46
    Oh, and as to @michiel's suggestion -- I can't use summary/details either since I need something within p's.
  161. Peter Krautzberger
    @pkra
    Sep 22 10:07
    @stevefaulkner 's test needs an update, I think. VoiceOver+Safari seems to have deteriorated (duplicating in more cases)
  162. blergh. Safari does horrible visual things as well.
  163. Mallory
    @StommePoes
    Sep 22 10:15
    Ah, wish I was online earlier
  164. the hidden checkbox with opacity is an old trick
  165. didn't know Chromevox ignored it but then, who the hell uses chromevox? it's like worrying about fireeyes
  166. Opacity should be good to use for this, visible label is clickable (style it like anything you want) and then the :checked+thingie-to-show as michiel had should be great
  167. no JS
  168. it's what we all used when grafixerz wanted us to make "custom" checkboxes and radios-- opacity on the control and a background image (today would be an SVG so works no-images and Windows High-Contrast too) on the label.
  169. Peter Krautzberger
    @pkra
    Sep 22 10:18
    Hey @StommePoes !
  170. Who uses ChromeVox? ChromeOS is growing quickly in US education and thus I have clients worry about it.
  171. Mallory
    @StommePoes
    Sep 22 10:18
    Geen slimme!
  172. That's sad, chromevox was Google's original solution to not making Chrome and Mail and Docs etc work with real screen readers
  173. oh well
  174. Guess we should add that to our testing suite as well if it's popular in the US
  175. Peter Krautzberger
    @pkra
    Sep 22 10:19
    From what I've heard through the grapevine, ChromeVox 2 will be very different.
  176. More like regular screenreaders.
  177. Mallory
    @StommePoes
    Sep 22 10:19
    I don't know any blinks who use it, but then even the youngest is already out of school now
  178. Peter Krautzberger
    @pkra
    Sep 22 10:19
    (i.e. no DOM access)
  179. Mallory
    @StommePoes
    Sep 22 10:20
    Hm then it might work with Edge
  180. I read Serotek's whinge about how Edge doesn't allow DOM access
  181. Peter Krautzberger
    @pkra
    Sep 22 10:20
    Thanks for supporting my original solution though :)
  182. Mallory
    @StommePoes
    Sep 22 10:20
    Jamie said it was an issue too (not breaking, but prevents any hacks to work around author mistakes)
  183. Peter Krautzberger
    @pkra
    Sep 22 10:20
    But VO has declined from 2011, now voices doubles.
  184. Mallory
    @StommePoes
    Sep 22 10:20
    I didn't look at the Pen but the whole idea seems very doable
  185. Peter Krautzberger
    @pkra
    Sep 22 10:20
    NVDA has improved though.
  186. Mallory
    @StommePoes
    Sep 22 10:20
    Well, VO on iOS is good
  187. VO on OSX, ug
  188. Peter Krautzberger
    @pkra
    Sep 22 10:21
    that's good to hear.
  189. Yes, I meant OSX.
  190. Mallory
    @StommePoes
    Sep 22 10:21
    it's as if they moved all their good people to mobile
  191. Peter Krautzberger
    @pkra
    Sep 22 10:21
    hehe
  192. Alright.
  193. I have a green light then.
  194. Mallory
    @StommePoes
    Sep 22 10:21
    yeah people like Bram (who you'll meet at role-drinks) had to switch back to Windows for work
  195. Peter Krautzberger
    @pkra
    Sep 22 10:21
    I think.
  196. Mallory
    @StommePoes
    Sep 22 10:21
    Yeah, do they have a bug tracker, the Chromevox people?
  197. I think the opacity-hiding thing should be considered a bug.
  198. although... I'd have to see if the specs are explicit it what CSS the browser should remove from the tree
  199. Peter Krautzberger
    @pkra
    Sep 22 10:22
    I agree.
  200. But I think it will resolve itself if ChromeVox loses DOM access.
  201. :)
  202. Mallory
    @StommePoes
    Sep 22 10:22
    when's that coming out?
  203. Peter Krautzberger
    @pkra
    Sep 22 10:22
    IIRC v2 is already available in ChromeOS as a beta.
  204. Mallory
    @StommePoes
    Sep 22 10:23
    ok, so prolly soon
  205. Peter Krautzberger
    @pkra
    Sep 22 10:23
    I have no idea if they'll roll it out as an extension.
  206. since it's so different.
  207. Mallory
    @StommePoes
    Sep 22 10:23
    I'll have to ask my testing guy what he's seeing in the wild
  208. Peter Krautzberger
    @pkra
    Sep 22 10:23
    Again, all hear-say here.
  209. Mallory
    @StommePoes
    Sep 22 10:23
    I got a bunch of poewrpoints and guess what they're full of and need to "work with JAWS"??
  210. yup, mathitty math-math. Statistics, trig, calculus. Ug
  211. my math allergies... flaring up again
  212. Peter Krautzberger
    @pkra
    Sep 22 10:24
    hehe.
  213. Mallory
    @StommePoes
    Sep 22 10:24
    I think P should hire some mather to deal with all these vendors so I can go back to bitching about react
  214. Peter Krautzberger
    @pkra
    Sep 22 10:25
    uhm. not sure what's worse ;-)
  215. Mallory
    @StommePoes
    Sep 22 10:25
    geogebra now has... the ability to use Acer webcams to let students turn their hands around in front of the screen to rotate 3d graphs
  216. Peter Krautzberger
    @pkra
    Sep 22 10:25
    sweet.
  217. Mallory
    @StommePoes
    Sep 22 10:25
    math, I think. I have a tab open on my Win machine pointing to a NVDA bug where someone at P couldn't get NVDA to read some math (but Jamie could) and it's last touched Feb 2016
  218. Peter Krautzberger
    @pkra
    Sep 22 10:26
    Where did I recently hear about a blind user realizing that non-blind people can't see a cube from all sides at the same time?
  219. Mallory
    @StommePoes
    Sep 22 10:26
    Maybe me
  220. I read that in the Godfrey paper
  221. Peter Krautzberger
    @pkra
    Sep 22 10:26
    Oh yeah. When we talked on hangouts.
  222. I've used that quite a few times recently.
  223. Mallory
    @StommePoes
    Sep 22 10:26
    yeah you want to peruse that paper? It's a great read
  224. Peter Krautzberger
    @pkra
    Sep 22 10:26
    Yes please!
  225. Mallory
    @StommePoes
    Sep 22 10:26
    from two blind statisticians
  226. Peter Krautzberger
    @pkra
    Sep 22 10:29
    freaky moment was to realize that Safari sometimes does not repaint properly when triggering the checkbox.
  227. Mallory
    @StommePoes
    Sep 22 10:30
    oh?
  228. Peter Krautzberger
    @pkra
    Sep 22 10:32
    in one situation, the revealed content overwrote what followed. In the other, when re-hiding, it looked like only the characters had been removed (leaving whitespace).
  229. switching from inline to inline-block seemed to fix it.
  230. Mallory
    @StommePoes
    Sep 22 10:34
    ug, safari is the new IE
  231. Peter Krautzberger
    @pkra
    Sep 22 10:34
    (Not as bad as a serious Chrome paint bug I ran into but that only happens on some OSX machines, including some testing services but not all)
  232. Mallory
    @StommePoes
    Sep 22 10:35
    bleh
  233. Peter Krautzberger
    @pkra
    Sep 22 10:37
    In a not-too complex setup, setting display:none on a few items left a different element partially invisible and inactive (no selection or links working) -- until you resized the window a tiny bit after which everything was fine.
  234. and if you hid that partially visible element, its size still influenced layout but if you brought it up again, it would still be inactive.
  235. :angry:
  236. anyway. Back to work.
  237. Thanks for your help, @StommePoes !
  238. Mallory
    @StommePoes
    Sep 22 10:41
    "macOS: in 10.12, vo-n brings up a VO menu of all on-screen alert/banner notifications. Vo-space on one to move to it." from @voTips
  239. Peter Krautzberger
    @pkra
    Sep 22 10:41
    @tomoes
  240. Mallory
    @StommePoes
    Sep 22 10:52

    Just saw this on the BBC blog about switching away from Flash:
    "Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of reading a document written on another computer, another word processor, or another network."

    Tim Berners-Lee 1996

  241. The date looks suspicious though
  242. Technology Review (July 1996)
  243. supposedly.
  244. Mallory
    @StommePoes
    Sep 22 11:00
    How many browsers were there in 1996?
  245. looks like 4 big ones
  246. Peter Krautzberger
    @pkra
    Sep 22 11:24
    Just like today then (in terms of engines). That's a little sad.
  247. Mallory
    @StommePoes
    Sep 22 11:32
    I don't want too many
  248. honestly, a handful is good
  249. zomg so someone twotted http://uinames.com/ and the interface is death but now I have the bug to send in a big fat PR
  250. too bad I have to work today :(
  251. zakim-robot
    @zakim-robot
    Sep 22 11:35

    [karlgroves] >uinames.com is a simple tool to generate names for use in designs and mockups. Made by Thom.

    OMG WHAT IS WRONG WITH “JOE SCHMOE”? WHY DO WE NEED A SITE FOR THIS

  252. Mallory
    @StommePoes
    Sep 22 11:42
    joe schoe is too damn short
  253. "Gyöngyösi Sebestyén Dos Santos", the Spanish-Hungarian who logged into your site but their name gets cut off because some american designed the thing :P
  254. Mallory
    @StommePoes
    Sep 22 12:49
    Question, I thought aria-labelledbys/describedbys couldn't be parents/children of the referrer?
  255. in this example, a grandparent element is being referenced as the aria-labelledby (instead of the sibling div with the actual label text in it)
  256. zakim-robot
    @zakim-robot
    Sep 22 13:01
    [karlgroves] Sure, why not
  257. [marcysutton] Isn't that how SVG title got mapped?
  258. Peter Krautzberger
    @pkra
    Sep 22 13:02
    also doing this for SVGs.
  259. Mallory
    @StommePoes
    Sep 22 13:02
    so how does the browser or AT know which text is the labelleing text?
  260. <div id="foo">Some text <div fakelabel> some more text</div> <input aria-labelledby="foo" .../> more random text and whatever else is in this div...<p>copyright bar</p></div>
  261. Peter Krautzberger
    @pkra
    Sep 22 13:09
    Oh I think I misunderstood you.
  262. but the link you posted only has siblings, no?
  263. Mallory
    @StommePoes
    Sep 22 13:12
    happens to.
  264. It seems obvious that we want the box with the label text to label stuff
  265. and not anything else
  266. so I thought for this reason that you couldn't just label yourself with yourself
  267. that you also couldn't
  268. zakim-robot
    @zakim-robot
    Sep 22 13:13
    [karlgroves] Yup. you can.
  269. Mallory
    @StommePoes
    Sep 22 13:13
    <a href="foo" aria-labelledby="bar"><some icon/><span sr-only id="bar">label</span></a>
  270. can it be both ways then?
  271. zakim-robot
    @zakim-robot
    Sep 22 13:14
    [karlgroves] yup
  272. [karlgroves] Wait. No
  273. Mallory
    @StommePoes
    Sep 22 13:14
    ok, just can point to ancestors but not descendents
  274. zakim-robot
    @zakim-robot
    Sep 22 13:14
    [karlgroves] The icon would be ignored
  275. Mallory
    @StommePoes
    Sep 22 13:14
    the icon should be ignored, it's a picture of god knows what
  276. zakim-robot
    @zakim-robot
    Sep 22 13:14
    [karlgroves] ok
  277. Mallory
    @StommePoes
    Sep 22 13:15
    but I saw something like that (except it made more sense) where something deep inside a link was trying to label it
  278. there was lots of stuff in the link I believe
  279. the author only wanted to have one part be the link text
  280. zakim-robot
    @zakim-robot
    Sep 22 13:50
    [michiel] thierryk: the thing you reference is 5 years old. Here is the most recent TR version: https://www.w3.org/TR/wai-aria-1.1/#aria-expanded
  281. [michiel] I’m not sure, but could be tab widget wasn’t around 5 years ago.
  282. Thierry Koblentz
    @thierryk
    Sep 22 14:35
    @MichielBijl yes, thanks, that one shows a new section: "Inherits into Roles" which Steve Faulkner mentioned to me yesterday. I think I need to update many of my a11y bookmarks :(
  283. zakim-robot
    @zakim-robot
    Sep 22 15:25
    [car] https://web-a11y.slack.com/archives/general/p1474539525001928
    In Canada, too. My son's high school just announced their new Chromebook Lending Library.
  284. [karlgroves] My daughter’s entire school has them
  285. zakim-robot
    @zakim-robot
    Sep 22 15:34
    [car] @StommePoes regarding the old "hidden checkbox with opacity" trick, how would you mark up this toggle switch for accessibility?
    http://www.w3schools.com/howto/howto_css_switch.asp
  286. [car] _(man, the examples on the w3schools howto site, while cool and all, seem to be mostly inaccessible. And lots of devs go there to get ideas. Maybe I'll try to find their "suggestion box" and mention that they are leading so many devs astray...)_
  287. zakim-robot
    @zakim-robot
    Sep 22 15:43
    [car] _(for example, the toggle switch example doesn't even work with the keyboard!)_
  288. [car] _(they have a "Report error" link near the bottom of the page. I sent them my suggestion... :)_
  289. zakim-robot
    @zakim-robot
    Sep 22 15:52
    [car] @StommePoes - cool trick! I changed their .switch input {display:none;} to .switch input {opacity:0;} and not only does it still look ok, but as an added bonus it works with keyboard (because of course the checkbox is no longer hidden).
  290. [car] @jkva @pkra @StommePoes Thanks!
  291. [beth] Anyone know if the A11Y Summit 2016 online conference videos have been released yet? I purchased an option that included unlimited replays, but can’t find info on where/when/how they will be released.
  292. Job van Achterberg
    @jkva
    Sep 22 15:57
    I didn't do anything? 😓
  293. zakim-robot
    @zakim-robot
    Sep 22 15:59
    [scottohara] heh, you just reminded me i was going to check on that later @beth, cause i’ve been looking out for a release of them too
  294. [beth] @scottohara If you go to the original event purchase page, the sessions are on sale for download, which leads me to believe they’re out there somewhere… but where?
  295. [scottohara] right.
  296. zakim-robot
    @zakim-robot
    Sep 22 16:11
    [joe-watkins] @beth @scottohara You could try pinging @teleject on Twitter. Usually an email gets blasted when they are ready.
  297. [car] @jkva Yes, you did. You talked it through with @pkra. :)
  298. zakim-robot
    @zakim-robot
    Sep 22 16:27

    [csantos] @Here hi all,
    Using NVDA in Windows 10 (also in Windows 7) with any browser. Navigating using Down/Up arrow key, I'm hearing 'blank' when it reaches elements.
    This is the example
    http://codepen.io/santospro/pen/VKPrOy

    Can anyone give a light with that?

  299. zakim-robot
    @zakim-robot
    Sep 22 16:33
    [patrickfox] The <br/> is read as ‘blank'
  300. [csantos] always?
  301. [patrickfox] not sure why it does that, but having that br there is unnecessary
  302. [csantos] VO doesn’t read <br/> as blank. VO just ignores that tag
  303. [patrickfox] right - that’s the way it should be in NVDA
  304. [patrickfox] I’d report it as an issue with NVDA
  305. [patrickfox] it does the same in Firefox as well, so it’s not just an IE issue
  306. [csantos] I reported that issue nvaccess/nvda#6400
  307. [patrickfox] +1 that’s awesome
  308. [garcialo] waves at @patrickfox
  309. [car] @pkra Maybe you could report the ChromeVox "Should not ignore opacity: 0" bug? https://bugs.chromium.org/p/chromium/issues/list?q=component:UI%3EAccessibility
    Click on "New Issue" button.
  310. zakim-robot
    @zakim-robot
    Sep 22 17:14
    [teleject] @beth the sessions information went out last week.
  311. zakim-robot
    @zakim-robot
    Sep 22 17:34
    [teleject] @beth followed up on your email to E4H. Let me know if you have any more questions.
  312. Mallory
    @StommePoes
    Sep 22 17:43
    @car is that the same team as ChromeVox?
  313. ah scrolling down I do see some ChromeVox issues, however there are also NVDA issues, so still not sure if this is the same team to file the bug with.
  314. unless it's only in Chrome/chromium with ChromeVox.
  315. zakim-robot
    @zakim-robot
    Sep 22 17:44
    [car] I searched, and there seems to be a bunch of ChromeVox bug reports there. The team labels them with a "cvox2" label.
  316. [heidi] @karlgroves re: IAAP membership site, the vendor says: " IAAP was a custom project. We do not have the ability to provide similar WCAG projects at this time. If we can support a non-wcag project, please let me know.” - boo.
  317. James Nurthen
    @jnurthen
    Sep 22 18:12
    @MichielBijl are you around? I hear you were looking for dinner plans.
  318. zakim-robot
    @zakim-robot
    Sep 22 18:17
    [heidi] @karlgroves I also asked if I could make the customizations myself and they said no - there’s no theming, and everything’s hardcoded.
  319. zakim-robot
    @zakim-robot
    Sep 22 18:58
    [heidi] iMIS looks AA...
  320. Mark Sadecki
    @cptvitamin
    Sep 22 18:58
    Wondering if anyone here knows what the future holds for drag and drop. I’ve noticed it is being referred to as deprecated in the aria 1.0 spec and vaguely referenced in 1.1
  321. and what someone who is tasked to build a drag and drop widget should use for a spec
  322. zakim-robot
    @zakim-robot
    Sep 22 19:03

    [csantos] @Here hi guys, more questions/bugs from my test cases heheh

    NVDA is reading clickable bullet for <ul><li> in Google Chrome
    Using NVDA with Google Chrome in Windows 10 (also in Windows 7).
    http://codepen.io/santospro/pen/bwgLLm
    Navigating using Down/Up arrow key, I'm hearing 'clickable bullet first item' and 'clickable bullet second item’.

    Can someone help me, or am I doing something wrong?

    _I created a NVDA issue for that (nvaccess/nvda#6399)_

  323. zakim-robot
    @zakim-robot
    Sep 22 19:14
    [jpdevries] @csantos ya that seems like a bug to me :bug:
  324. Mark Sadecki
    @cptvitamin
    Sep 22 19:37
    @csantos is that happening just in codepen?
  325. Mallory
    @StommePoes
    Sep 22 19:38
    I didn't think a ul could be a child of a p?
  326. meh they probably changed it, they've been changing all sorts of HTML out from under me. U isn't even obsolete anymore... so now our designers are using it for underlined text.
  327. Mark Sadecki
    @cptvitamin
    Sep 22 19:39
    @StommePoes is right, p’s can only have phrasing content: https://www.w3.org/TR/html5/dom.html#phrasing-content-1
  328. zakim-robot
    @zakim-robot
    Sep 22 19:39
    [csantos] I thought the same, I moved <ul> outside the <p> but the issue still happening
  329. Mallory
    @StommePoes
    Sep 22 19:39
    Still, the button's completely closed first
  330. usually, in other browsers, the clickables are because non-clickable things are inside some ancestor who is clickable. but here, the button is a sibling.
  331. I wonder if someone (chrome or NVDA) sees the button's actions as being able to influence the container of them both
  332. Mark Sadecki
    @cptvitamin
    Sep 22 19:40
    whenever a screen reader tells me a non-clickable element is clickable, its almost always because a parent has an event listener on it. that’s why I was wondering if it happened outside of codepen.
  333. codepen likely has all sorts of JS on the page
  334. Mallory
    @StommePoes
    Sep 22 19:41
    Does it change if you add type="button" to the button? since otherwise they could submit J random forms on the page?
  335. ah yeah, could be codepen itself.
  336. zakim-robot
    @zakim-robot
    Sep 22 19:41
    [csantos] It’s not a problem with codepen, I also tested it in a simple .html file
  337. [karlgroves] Yeah, I’d create a test case in its own HTML file. Not in codepen.

    Next, I’d check it in Firefox and IE.

    Finally, I’d use aViewer to find out what NSRV information is being exposed.

    Chances are, this is not an NVDA issue but a chrome issue.

  338. Mallory
    @StommePoes
    Sep 22 19:42
    so when there's no button anywhere, list items are just bullet blah blah...?
  339. zakim-robot
    @zakim-robot
    Sep 22 19:42
    [csantos] oh @karlgroves hell!
  340. StommePoes @StommePoes tries to imagine what a karlgroves hell is like...
  341. Mallory
    @StommePoes
    Sep 22 19:43
    prolly lots of punk music. The really bad stuff with no melody
  342. and bad "singing"
  343. zakim-robot
    @zakim-robot
    Sep 22 19:43
    [karlgroves] Hair metal, actually
  344. [csantos] lol
  345. Mallory
    @StommePoes
    Sep 22 19:44
    edguy!
  346. laaa-va-tory love machiiiiine....
  347. Mark Sadecki
    @cptvitamin
    Sep 22 19:44
    @karlgroves, hair metal? compensating for something?
  348. zakim-robot
    @zakim-robot
    Sep 22 19:44
    [karlgroves] Or, black metal where they try to sing.
  349. Mallory
    @StommePoes
    Sep 22 19:44
    it's when guys who claimed to be metal looked like Stu Robeson's twitter avatar
  350. zakim-robot
    @zakim-robot
    Sep 22 19:45
    [csantos] well, wait haha… so where can I do to fix that chrome issue?
  351. Mallory
    @StommePoes
    Sep 22 19:45
    I think that's david bowie, who isn't hair metal but totally had the hair for hair metal
  352. Follow karl's steps
  353. so we know if it's limited to Chrome
  354. and then bug chrome people
  355. and ask Jamie or Derek
  356. zakim-robot
    @zakim-robot
    Sep 22 19:46
    [csantos] this is not happening with Chrome-Mac-VoiceOver
  357. [karlgroves] TPG has a “Metal Club” Skype room. We have differences of opinion. I’m a bigger fan of yelling and screaming.

    well, wait haha… so where can I do to fix that chrome issue?

    Confirm the issue resides in Chrome

    Then yell at @Sundress

  358. Mallory
    @StommePoes
    Sep 22 19:47
    yelling at her seems mean, but either she gets stuff done, or she knows who to poke, endlessly, with an annoying finger until it's fixed
  359. zakim-robot
    @zakim-robot
    Sep 22 19:47

    [karlgroves] > Chrome-Mac-VoiceOver

    Good lord, man. Don’t use that combo. You’ll be chasing your tail. Safari/VO is the only legitimate combo for VO

  360. Mark Sadecki
    @cptvitamin
    Sep 22 19:47
    nothing happens with Chrome-Mac-Voiceover ;)
  361. Mallory
    @StommePoes
    Sep 22 19:47
    That anything works on VO and Chrome is amazing and the proof that there are supernatural beings among us
  362. zakim-robot
    @zakim-robot
    Sep 22 19:47
    [karlgroves] Yeah, “yell” was a strong term. @sundress is too nice to yell at.
  363. Mallory
    @StommePoes
    Sep 22 19:48
    You just said you were a big fan of yelling and screaming.
  364. zakim-robot
    @zakim-robot
    Sep 22 19:48
    [karlgroves] In a nice way
  365. Mallory
    @StommePoes
    Sep 22 19:48
    Me, I'm a fan of cursing and breaking shit.
  366. zakim-robot
    @zakim-robot
    Sep 22 19:48

    [karlgroves] > poke, endlessly, with an annoying finger until it's fixed

    The Mallory Method ™

  367. Mallory
    @StommePoes
    Sep 22 19:48
    and then drinking my problems away
  368. actually, i'm almost done fixing that uinames thing
  369. it was just such a keyboard abomination
  370. zakim-robot
    @zakim-robot
    Sep 22 19:49
    [karlgroves] Did you add “Joe Schmoe” to the list?
  371. Mallory
    @StommePoes
    Sep 22 19:49
    I'm not adding uselessly-short names to a list I would personally use to encourage designers to stop setting name-placeholder-widths in any limits
  372. zakim-robot
    @zakim-robot
    Sep 22 19:50
    [karlgroves] Fine.
  373. Mallory
    @StommePoes
    Sep 22 19:50
    Before I heard of that, my fake-names-to-show-designs-suck were NSFW and something HR would go after me for
  374. and would break CoCs
  375. and make orphan children weep
  376. etc
  377. "Josephina Henrietta Schmuckenberger-Jones"
  378. zakim-robot
    @zakim-robot
    Sep 22 19:51
    [karlgroves] Nothing NSFW about that
  379. Mallory
    @StommePoes
    Sep 22 19:52
    No, it's what I would add to the list if I were adding names to the list
  380. When P put my full hyphenated name on everything it made my email address so long it didn't fit on the gmail page
  381. but I blame gmail being very terrible with enlarged fonts
  382. icons_suck_most.png
  383. I can only gues 2 of those.
  384. hate icon buttons
  385. developers should get a painful shock every time they do it
  386. so now as I tab around them, I get visible names showing up underneath... with Dragon I'd only have to tab through the things once and then I know what they're called (I don't dare try to change his design because that'll get my PR rejected in no time)
  387. zakim-robot
    @zakim-robot
    Sep 22 20:13
    [beth] @teleject Thanks! I dug around outlook and found the original email hiding in my “email quarantine” folder.
  388. powrsurg
    @powrsurg
    Sep 22 21:27
    Does anyone know if there is an already accessible library for doing one of those drag and drop interfaces for something like a "make your own shirt" interface. Upload a base image, let you move it around, put stuff over it, etc
  389. zakim-robot
    @zakim-robot
    Sep 22 23:39
    [alacker] thats an interesting thought @powrsurg, how would you expect that to work with a screen reader?