Meeting minutes
<jugglinmike> +present
Issues spawned by HTML Range input slider testing
James: In APG there is work to improve slider examples.
One new one is a temperatature slider that using an HTML input type range.
This is basically one that doesn't need all the JS for keyboard because it is HTML input based.
You get a lot of accessibility for free.
In this case, one of the only thing that is done for screen readers is addition of valuetext
This is good for AX to encourage authors to use HTML.
This presents some testing problems for keyboard.
Page Up and Page down in particular.
They move the amount that is larger than up/down arrow.
With HTML range, you can tell the input the increment amount for arrow keys.
But, you can't tell the range input how much or how many steps the page up/page down should change.
Each browser could move a different number of steps
In our aria-at tests, we have so far always included a reference value in the assertion
xample: we would say it should change by 2.8 degrees.
<michael_fairchild> whatwg HTML issues: https://
Discussion of options. Matt made point that we are testing screen reader behavior not browser behavior and sr should just report current value. Sina pointed out that we wouldn't be adding ARIA to the htnml example if we script page up/down.
Conclusion: Rais issue against html that multiple step increment should be specifiable by author.
James: what about other unpredictable situations.
How do we instruct testers to know the correct result.
Mike: the problem is the same for automation and human testing.
You can tell the machine or the hyuman the correct result.
The test runner could query an object for a value and insert it into an assertion.
So, the assertion would have a "empty spot" for an expected value that could be dtermined dynamically.
Sina, James, Matt: +1
Seth: Simon back in second week of August; can advise on raising whatWG issue.
Onboarding experience plan
Hadi: We'd like to iscuss this.
Seth: Next week we'll have more concrete plan for when we can migrate to new experience that includes the allow list that will help with the onboarding process
We have mreged all the non-draft open PRs except for one!!
A few questions have come from this.
Process of merging keys.mjs is really thorny
Maybe we should add keys in main and then merge into feature branch.
James: I'll do some work on keys.mjs to minimize this difficulty.
We should add all possible keys in the file.
Mike: that file and some others use empty space to format code visually.
I assume that is not easily appreciated by screen reader users.
It can effect conflicts.
So, we probably want to remove the extra formatting whitespace.
I'll submit a PR for that.
Seth: there are now 11 new test plans in main.
bring total to 16
Quick question: we need someone to change url in the description of aria-at in the repo.
Seth will send email request to Matt.
Crystal: looking forward to onboarding discussion as newest member of group.
still feeling 1quite lost. would nice to have an orientation or tour.
honestly coming to meetings and I'm super confused.
Hadi: I have been with this team for quite some time, and colleagues helped me get on board, and I don't remember all those details.
I brought Alysa on board , a student of mine, to help with this.
Alysa: I have been trying to onboard without much info and guidance from Hadi.
I started at aria-at.w3.org and signed up to be a tester.
got a dead end because was not registered with a GitHub team so raise an issue.
Seth: although this didn't work when you tried it, we are working on details of how to make that work more smoothly.
weould like some part of this to be automatic.
James: I know we don't want trusted tester access to anyone in the public.
Maybe we could allow anyone to sign up and run a test but we wouldn't accept their results.
until they are approved as a tester.
Alysa: when I tried to join the aria-at community group on the w3c site.
I was asked if joining on behalf of org or as an individual.
it asked me if I owned right of material I would contribute.
Said not sure, so got an email from w3c.
Email asked for a rep of org to approve the membership.
Maybe we can split conversation into two parts.
joining community group and joining repo are separate.
Seth: there is a lot of complexity. we should design what is ideal and then work backward to make that happen.
I can help get people onboarded for now, and then we will work to make this better for the people who follow.
Hadi: to be authroized tester on GitHub. Alysa has not received a response. where does that go?
Seth: I see the request now. I will handle it.