Meeting minutes
Review Agend and Next Meeting Date
View agenda at https://
No meeting on May 4 or May 18.
AT Support Table Launch Follow UP
Discussion of feedback.
Anything we should change based on feedback?
Anything constructive?
Reading it closely, more of a distraction than constructive.
Some on APG rather than aria-at.
Should we change what we have done or what we are about to do?
based on feedback.
Consensus: The feedback does not include anything that would suggest we have corrections to make to existing work or future plans. Group discussed future plans for ability to report by specific attribute, e.g., aria-modal, so it has more of a "Can I use" type of functionality. That is a future objective. Scope of current work is continuing reporting on patterns until we have sufficient success on that front.
Current Testing Progress
James: NVDA/FF for command buttons is ready to publish. JAWS/FF same, also ready to publish.
VO/Chrome is also ready for command button.
Toggle button: VO/Chrome not ready. NVDA/FF complete. JAWS/FF complete.
Alert: NVDA/FF and JAWS/FF complete. ready to publish. VO/Chrome complete and ready to publish.
Radio group: NVDA/FF complete, JAWS/FF has 6 conflicts. We know how to resolve them.
James will prioritize resolving JAWS radio group conflicts.
We published Firefox results for alert, toggle button, and command button during meeting.
… attribute level vs a pattern level. That is in future scope. However, near term, focus is on reporting on patterns./