Meeting minutes
Setup and Reset for Test Case
<Matt_King> James: Decided there will always be a setup button
<Matt_King> Z: If there is no script, should the button be on the page
<Matt_King> James: we could hide button if there is no script
<Matt_King> z: During test generation, we will make a copy of the reference example pages, one for each unique setup script.
<Matt_King> Rich: This sprint will wrap up full deployment of the new schema
<Matt_King> will be able to move to more agile approach after Oct 1, last day of this sprint
<AlyssaG> +present
Feedback from testers running tests
Matt_King: i saw an email from Alyssa Vo regarding feedback.
Matt_King: AlyssaG were you able to get any testing this week?
AlyssaG: yes, I did 6 and have a completed a total of 8.
Matt_King: do you have any feedback?
AlyssaG: one of the tests references from interactive and focus mode.
James: I wasn't aware we had reached a conclusion.
Matt_King: I thought we had reached a conclusion. We were going to have a terms listing somewhere, different than the working mode.
Matt_King: we are assuming a certain amount of knowledge but certain things can be confusing. Have you seen the raise an issue button AlyssaG?
AlyssaG: no I have not looked for it.
Matt_King: it is down at the bottom and gives you a form. Ass much feedback as possible. Thank you.
AlyssaG: I shall do that
Matt_King: Jongund you had raised some issues while testing. Your issue about radio buttons
jongund: It would be nice if we used the radio buttons for sighted users, no line breaks. Maybe some visual styling.
Matt_King: Issue 505 can be retitled and retagged.
James: I will do some work on this.
jongund: when you open the test you can't see the script window.
James: It is a comment on 502.
Z: this is in that ARIA-AT repo, there is a current call that specifies and size.
Matt_King: I believe we need a separate issue for this.
James: I will create this.
Z: we just need to specify the size or remove it.
Matt_King: is there anything else jongund?
Hadi: Sorry for joining late
Hadi: I think screen reader navigation and keyboard navigation should be separate.
Matt_King: we have not defined any assertions related to landmark regions yet.
jongund: I think there needs to be information on if they can ignore it or not.
Matt_King: we need to think about what we want the screen readers do but what we want the tests to tests
Priorities for next sprint
<jongund> MK: IN the last ten minutes, we can talk about the next ???, any other development of the app
MK: Previous meetings about the way we work
MK: We have been talking about our draft tests, what should or should not be in them
MK: Then we want to change the draft tests are ready for screen reader companies
MK: This process is working well for everybody, we identified some issues today
MK: We need to record browser and screen reader versions, and identified some accessibility issues
MK: We have a crisp list to burn down
MK: What are the things that are absolutely critical between now and the end of the year
MK: What priorties of the group members
MK: This is an opportunity for working group input to priorties
ST: We have received issues related to radio buttons, so it might a high priority
MK: That is a design one
ST: I would be happy to talk about the issues with the design team
ST: There are some additional issues for visual design
ST: Radio is first suggestion
ST: The difference between NEXT and SAVE, not sure we have an issue for that
MK: I thought you were suppose to raise an issue
RN: That was n the accessibility audit
MK: I think there needs to be consensus on a solution that can be implemented
MK: I welcome an issue, think it through, please provide a proposal and we can talk through the proposal
MK: We can then have the solution float to the top
MK: We need to talk about it soon for the ..
ST: Something like the radio buttons fits under dedicated time, and we don't have to carve out right now
MK: We will not be able to get all the fixes and the production issues
JS: Is that more important than screen reader and browse version issues
MK: The tests status is needed to make test available to screen reader developers, the SR and browser version is important too
ST: We are feeling pressure, can we use email today to figure out the radio button, we need to do it in the next week
MK: We will revisit this next week