A11y Slacker archive 2015-10-07

zakim-robot

Oct 07 00:35

[Faruk Ateş, a11y] Amusingly, the Polymer project 1.0 documentation is closer to explaining what I'm describing than what FB or ms.com do :smile:
zakim-robot

Oct 07 00:38

[Faruk Ateş, a11y] @car: Aha, yes, that's a very closely approximate idea, except I was envisioning it with Tab being the main forward/backward (with Shift) method still, and an "enter/exit" mechanism via Enter (and optionally some other key close to Tab) and Esc
StommePoes

11:49

test
MichielBijl

12:19

@StommePoes roger
StommePoes

12:19

ja, saw it on the website, just set up this copy of pidgin
zakim-robot

12:21

[Carolyn MacLeod, a11y] @kurafire: That sounds interesting, too, but I was trying to solve a slightly different problem, which is that it often takes too many Tab keys at the top level to get anywhere. So I thought F6 could be a "mega-Tab" to skip larger areas.
powrsurg

13:23

I have slides from a presentation for something that has buttons to move the slide forward or backward in the presentation. For proper focus management should the focus stay on the button that was pressed for that slide, or should it stay as the back/forward button for slide X? So if I was on slide 2 and hit the forward button should it be what is now slide 3's forward button (since 2 moved to 3 and this would be the same actual element) or should it stay at slide 2's forward button, which would be a different element.
zakim-robot

13:51

[Pontus Horn af Rantzien, a11y] I may be misunderstanding the scenario, but why does each slide have its own back/forward buttons? It seems to me that back/forward should logically be its own UI independent of the slides
MichielBijl

13:58

Anybody have any input on this: https://twitter.com/MichielBijl/status/651755038780604417
MichielBijl

13:59

More information in the minutes near the end: http://www.w3.org/2015/10/01-aria-minutes.html
MichielBijl

14:01

And it would technically be for the PFWG meeting, mixed that up with APG :X
powrsurg

14:01

@Pontus This is for the administrative ability, not for a person viewing the presentation. Sorry for not making tha tclear
zakim-robot

14:07

[jitendra, a11y] going to meet ted drake today
zakim-robot

14:07

[jitendra, a11y] he is in my town
MichielBijl

14:29

Nice :)
zakim-robot

14:30

[jitendra, a11y] do u know him
stevefaulkner

14:42

@jitendra ted is a great guy
zakim-robot

14:42

[jitendra, a11y] yes
MichielBijl

14:43

I've seen some of his work, yes.
zakim-robot

14:44

[jitendra, a11y] https://mobile.twitter.com/mpnkhan/status/651764452694495232
zakim-robot

15:13

[Claire Ryberg, a11y] Can anyone take a look at this https://jsfiddle.net/cryberg/u6458d66/ and tell me what your screenreaders announce?
I was trying to figure out if it was helpful to use aria-pressed with a button that toggles an expand/collapse panel, and have come across some weird behavior. I think I will not be using aria-pressed, because aria-expanded seems to be descriptive enough, but can anyone explain to me why adding aria-pressed to an accordion button reverses what is announced when the button is pressed?
This is what I mean: Using JAWS in IE11, with aria-expanded on a button that triggers an accordion, "expanded" is announced when the accordion opens, and "collapsed" is announced when it is closed, as expected.
When I add aria-pressed to the same button, it instead announces "collapsed" when the accordion opens, and "expanded" when it is closed, the reverse of what I would expect.
garcialo

15:16

Filter
button
Filter
toggle button collapsed
pressed expanded
Filter by title edit has auto complete
blank
garcialo

15:17

ah, I guess I didn't properly hit enter on the first button =p
garcialo

15:19

Here we go...
garcialo

15:19

Filter
button collapsed
expanded
Filter by title edit has auto complete
blank
Filter
toggle button collapsed
pressed expanded
Filter by title edit has auto complete
blank
zakim-robot

15:21

[Claire Ryberg, a11y] So the second button is reading as expected for you. Hm. What screen reader are you using?
garcialo

15:21

NVDA + Firefox + Windows 10
zakim-robot

15:22

[Claire Ryberg, a11y] Alright, thanks! Also, if it helps, I was navigating with tabs only
garcialo

15:23

yup, same here
zakim-robot

15:23

[Claire Ryberg, a11y] I wonder why I'm hearing the reverse in JAWS
garcialo

15:24

they act differently =p
MichielBijl

15:31

So apparently I totally forgot that Fronteers jamsessions are tonight :(
MichielBijl

15:34

Might still make it to meet with @StommePoes :D
zakim-robot

18:49

[Greg Tarnoff, a11y] Does anyone have any experience with refreshable braille displays? I’m wondering if we make a form accessible by keyboard navigation/screen reader, have we done enough to make the braille display usable?
garcialo

18:52

That's the impression I've always gotten.
garcialo

18:54

When you make it screen reader accessible, you're really just making sure there is text data. Screen reader reads it; braille display...brailles it? Braillificates? Make it into braille.
zakim-robot

18:57

[Greg Tarnoff, a11y] That’s my understanding. We’re looking at standardized testing for schools and we know we can’t put a picture on a screen for analysis and know they can’t figure it out. But I’m wondering if there is something more than replicating all mouse interactions via keyboard.
zakim-robot

22:52

[Matt May, a11y] OS X has a virtual braille display in VO preferences, if you want to visualize how it works. It's under Visuals, Braille Panel tab. Set "show braille panel" to On and you'll see it when you run VO.
zakim-robot

22:54

[Matt May, a11y] There are some braille abbreviations for roles (btn, tbl, etc.) but by and large, the interaction model is very similar to running a screen reader with TTS.

Gitter Channel Archive 7th of October 2015