[20:17:30] https://www.youtube.com/watch?v=GsE0PpQkBcI [20:17:59] accessibility brownbag session [20:18:18] btw. thanks for doing this, it's been way overdue ! :) [20:18:50] I can help facilitate any questions for for the brownbag [20:19:24] yay [20:22:48] a loupe is an assistive technology. ppl often don't realize this :) [20:23:30] external lenses ftw :D [20:24:44] and outside of visual impairments. alternative input methodologies. which usually piggyback on keyboards (which is why keyboard navigation ability is so much more than about keyboards). [20:25:06] i saw a tweet go by in the last few days from someone pointing out that customizing font *weight* can be very important for visual contrast too, maybe more so than size [20:25:21] yup [20:25:36] esp. with antialiasing these days. [20:26:30] best thing about high-density displays is actually being able to have more than 'too light' and 'way too dark' letter weigths :D [20:27:09] (my pet peeve about 1.5x density is that 1-px strokes are too thin or too thick) [20:27:18] *, 2-px too thick [20:29:04] (re using assistive tech to find elements for tests) clever, but dangerous to rely on hidden data ;) [20:35:25] small addition: "user needs to know HOW to use something" :) [20:35:57] sometimes not obvious with custom interactions yeah ! [20:35:59] move slider left for.. slide right for... [20:36:16] highfives ! :) [20:36:26] o/ [20:36:36] \o [20:36:39] :D [20:40:29] thedj: btw i'm down to ... about 25% of subtitles failing on the conversion after rewriting the srt input processing. (PR submitted) and the rest now report which line they die out on ;) [20:41:08] should be able to accept some more with more liberalization of input, then fix the rest with a combination of linting & manual adjustment [20:41:24] hugs ! [20:41:27] :D [20:41:59] Do we ever actually want to specify a point/pixel size? Or do we instead let the browser set the default, and then only specify percentages of that (to alter the size of headings and such)? [20:42:34] quiddity: i think the main reason to avoid point/pixel sizes is to decouple size of text elements from size of non-text elements [20:42:41] which may, or may not, be a good decoupling to make [20:42:44] s/browser/browser&OS/ [20:42:53] sometimes 5 actually has to mean 5 :) [20:43:01] at least in browser land, you can usually scale everything together [20:43:03] hmm, ok. (I'm out of date on my reading around all that) [20:43:25] on native os yeah sometimes you have to work around a native component size [20:43:34] it's always a balance... usually, you wouldn't want to set specific pixels, but there is always the time where you do need to :) [20:44:36] and most people will then end up abusing the "exception" :) [20:51:19] chrome crashed or something ? [20:52:29] google logged volker out [20:52:43] of course that would happen mid presentation [20:52:48] hehe [20:53:46] i had that with my work account, every single monday morning all-devs meeting. [20:54:28] same time, every week, because every week, i would NEED it during that meeting, and apparently the default remember me was 7 days to the minute... [20:59:54] heh [21:01:06] Also a plug for https://www.mediawiki.org/wiki/Accessibility_and_usability_cleanup [21:01:06] I made that linkdump with the hopes that other people would use it as: [21:01:06] * A starting point, for better organizing ourselves [21:01:06] * A reminder, that "starting a new page" can be detrimental, if other relevant pages already exist. It's harder to update an existing page, but so much more valuable! [21:01:06] So, please please do edit/add/update/overhaul it, however might be helpful. [21:01:29] \o/ [21:04:37] Volker_E: thx a ton for doing that with josh ! [21:04:50] +1 :D [21:05:07] now to get HR to move every new dev into a room and do a required viewing of that video during their onboarding :) [21:17:39] thedj: haha, thanks! [21:17:52] and quiddity [21:18:51] now I have to change my beloved password ;'} [21:20:31] thedj: also, when we incorporate testing into CI they gonna learn it anyways [21:20:49] * Volker_E so embarrassed with the Google logout [21:31:07] Volker_E: i just realized that Apple screwed over VoiceOver users majorly with this new TouchBar... [21:31:40] one of the few groups of people who actually DID use those keys, and that are highly reliant on touch to interact with those buttons. [21:32:49] Volker_E: ah: http://iaccessibility.net/index.php/2016/10/28/voiceover-at-the-bar/ [21:32:59] someone wrote it up already :) [21:33:41] Volker_E: so instead of F2, you now use Fn-2 (since fn button is still there). [21:33:47] it's kinda a compromise to tap three times, but at least aligned [21:33:56] with iPhone [21:34:02] yup [21:35:45] VO+F2 is now Function+Control+Option+2.. [21:37:16] so basically, you need one extra finger.. (which you might not have, if you are unlucky enough to be in this group due to an IED)