<Jemma> https://github.com/w3c/aria-practices/wiki/May-5%2C-2020-Meeting
<Jemma> Chair: Matt King
<scribe> scribe: carmacleod
<Jemma> jon: aria-hidden can be one
<Jemma> car: I like your table, it seem to be easy to follow
<Jemma> jon: we can wait ARIA group's work as Carolyn mentioned.
<Jemma> jon and car: this can be new agenda in a couple of week, not necessarily next week new agenda.
<Jemma> james: we need to be careful of scope creep for 'aria-hidden'
<Jemma> mck: let's put this as new agenda three weeks from now.
<Jemma> car: current discussion is more on remediation of browser side
<Jemma> car: so aria-hidden may not be ready for APG yet.
<Jemma> mck: how about not having the APG meeting on the week of Global Disability Awareness ?
<Jemma> group: yes
mck: we'll meet next week, but not the following week, due to GAAD events
github: https://github.com/w3c/aria-practices/pull/1356
<Jemma> last comment for 1356 is https://github.com/w3c/aria-practices/pull/1356#issuecomment-622416191
carmacleod: I think it looks ok - I want to do a bit more testing before final approval, i.e. WHCM, etc
<Jemma> "Looks like the extra awaits fixed the issue with the regression test not working in the CI process for the menubar editor updates."
<Jemma> sarah: I will help
sarah_higley: I can rebase some of the tests to incorporate the t.plan changes
<Jemma> sarah: take out t.plan
<Jemma> t,plan is not the best way, rather using test helper will be better option.
sarah_higley: linting should catch some stuff in tests now - you no longer need t.plan, so lint will flag, and you can remove it and use query elements test helper instead
<Jemma> sarah: simon added linting check for that, I think.
sarah_higley: theoretically, you should get an error if you use findElements
siri: question about editor
menubar - last week I had problem on mobile
... on android
... it seemed to lose my focus and I couldn't select a second
item
jemma: I tried it on my android phone, and it was functional (it had problems with responsiveness, but functionally ok)
github: https://github.com/w3c/aria-practices/issues/1017
mck: simon started working on this, there are still tests
carmacleod: github has 158 hidden comments
<Jemma> may be "readme" section for Sarah's workflow document?
<Jemma> or separate doc like https://github.com/w3c/aria-practices/wiki/Pull-Request-Review-Process#design_review
<jamesn> /
<Jemma> Topic?
github: https://github.com/w3c/aria-practices/issues/1362
github: https://github.com/w3c/aria-practices/issues/1026
sarah_higley: still adding
tests
... doc changes are still rough
... ready for functional and accessibility review of example
itself
mck: anxious to get this in and tested
jongund_: simon had feedback on
datepicker high contrast mode - is it ok to not have a border
in HCM and just have border for date that has focus?
... if anybody has any ideas for this, please let me know
carmacleod: the Windows date picker doesn't have grid lines - there's a border only on the current date
sarah_higley: sina had a comment on the down arrow behavior on the select-only combobox
<Jemma> https://github.com/w3c/aria-practices/issues/1026#issuecomment-588023657
<Jemma> https://github.com/w3c/aria-practices/issues/1026#issuecomment-610575881
mck: right now, down arrow - if
you don't automatically select - just makes it possible to
navigate the list without changing the value
... if you press Esc, it goes back to the previous value
sarah_higley: the windows
combobox doesn't do that, but I added that behavior because
people prefer it in usability studies
... if you press down arrow and then tab, it changes the
value
mck: it would be good to add a
"Choose a value" option as the first option
... I will respond to comment 2 in 1026
jamesn: was just playing with it - the typeahead seems ok until you hit a wrong letter
sarah_higley: I was trying to decide what to do there - if you type 2 letters and the second one is wrong, you don't want to jump somewhere else
mck: maybe try cancelling the timeout
sarah_higley: that might work
mck: and making an "error" sound
sarah_higley: not sure if that's possible?
carmacleod: you used to be able to print ^G to do system beep
sarah_higley: would be better to trigger an error or notifications api event or something
<Jemma> mck: I wish I could work on aria-live
<Jemma> james: I wished the screen magnifier developers would work on this error alert on top with aria-live.
<Jemma> the solution for James testing is ...
sarah_higley: I still have to add tests
mck: simon can review tests when you say they are ready
<Jemma> https://github.com/w3c/aria-practices/issues/1392#issuecomment-623282227
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/creek/creep/ Succeeded: s/two/three/ Succeeded: s/it/aria-hidden/ Succeeded: s/nto/not/ Succeeded: s/me are you ok carolyn?// Succeeded: s/of aria-live/with aria-live/ Present: Matt_King carmacleod Jemma jongund BGaraventa siri sarah_higley jamesn Regrets: Mark_McCarthy Found Scribe: carmacleod Inferring ScribeNick: carmacleod Agenda: https://github.com/w3c/aria-practices/wiki/May-5%2C-2020-Meeting WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]