Event Updated: ARIA and Assistive Technologies Community Group Weekly Teleconference

[View this event in your browser](https://www.w3.org/events/meetings/8b398afb-04d4-4e27-81ed-fa5cd11d9a4a/20240228T100000/)

 ARIA and Assistive Technologies Community Group Weekly Teleconference Upcoming Confirmed
=========================================================================================

 28 February 2024, 10:00 -11:00 America/Los\_Angeles

 Event is recurring every other week on Wednesday, starting from 2024-02-28, until 2024-12-31

[ ARIA and Assistive Technologies Community Group ](https://www.w3.org/groups/cg/aria-at/calendar/)Weekly meeting focused primarily on generating ARIA-AT reports via manual testing. Alternates between an earlier Wednesday time one week and later Thursday time the next.

 Agenda
------

[Agenda](https://github.com/w3c/aria-at/wiki/February-28%2C-2024-Agenda)### Review agenda and next meeting dates

- Next meeting: March 7
- Requests for changes to agenda?

### Automation subgroup meeting planning

1. Review pole results
2. Make automation meeting time decision

### Command and toggle button test plans

1. Fix complete for toggle button role issue, [issue 1031](https://github.com/w3c/aria-at/issues/1031)
2. Questions related to [feedback issue 1030](https://github.com/w3c/aria-at/issues/1030): 
  1. Should 'b' quick nav command be added to [first 4 toggle button VoiceOver tests](https://deploy-preview-1041--aria-at.netlify.app/review/toggle-button)?
  2. Should 'b' quick nav command be added to [first 3 VoiceOver tests in button test plan](https://aria-at.w3.org/report/62353/targets/232)?
3. To preserve as much existing manual test data as possible, waiting on deployment of new app code before advancing new test plan versions to draft review.
4. Discuss target date for resolving app deployment blockers and deploying app update: 
  1. [Feedback on unexpected behaviors functionality in issue 738](https://github.com/w3c/aria-at-app/issues/738#issuecomment-1965711069)
      to be resolved by [PR 939](https://github.com/w3c/aria-at-app/pull/939)
      and [PR 1016](https://github.com/w3c/aria-at/pull/1016)
  2. [Feedback about incorrect content on test plan view page in issue 745](https://github.com/w3c/aria-at-app/issues/745#issuecomment-1965638839)

### Radio test plan

1. Radio test plan refactor on hold until resolution of [issue 1039](https://github.com/w3c/aria-at/issues/1039))
2. Will be resolved by [PR 1042: Update tests.csv to override priority in assertions column by howard-e](https://github.com/w3c/aria-at/pull/1042#pullrequestreview-1905198701)
3. Discuss time table.

### Assertion priority definitions

[Define meaning of assertion priorities: "MUST", "SHOULD", and "MAY" · Issue #1033 · w3c/aria-at](https://github.com/w3c/aria-at/issues/1033)

### Response to Vispero alert test plan feedback

Based on previously discussed assertion priority definitions, discuss how to resolve Vispero Feedback:
[JAWS Changes Requested: "Trigger an alert" (Alert Example, Test 3, V23.12.06) · Issue #1032 · w3c/aria-at](https://github.com/w3c/aria-at/issues/1032)

### Proposal to change terminology used for undesirable behaviors

[Proposal for new terminology for the phenomena we currently call "undesirable behaviors" or "Other behaviors with negative impact" · Issue #1043 · w3c/aria-at](https://github.com/w3c/aria-at/issues/1043)

 Joining Instructions
--------------------

 Instructions are restricted to meeting participants. You need to [ log in](https://auth.w3.org/?url=https%3A%2F%2Fwww.w3.org%2Fevents%2Fmeetings%2F8b398afb-04d4-4e27-81ed-fa5cd11d9a4a%2F%3FrecurrenceId%3D20240228T100000) to see them.

 Participants
------------

### Groups

- [ARIA and Assistive Technologies Community Group](https://www.w3.org/groups/cg/aria-at/) ([View Calendar](https://www.w3.org/groups/cg/aria-at/calendar/))

 Report feedback and issues on [ GitHub](https://github.com/w3c/calendar "W3C Calendar GitHub repository").