Event Updated: ARIA and Assistive Technologies Community Group Weekly Teleconference

[View this event in your browser](https://www.w3.org/events/meetings/e72b4a73-43d7-4854-a0ed-d9fde0148f02/20241114T120000/)

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

 14 November 2024, 12:00 -13:00 America/Los\_Angeles

 Event is recurring every other week on Thursday, starting from 2024-11-14, until 2025-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/November-14%2C-2024-Agenda)### Review agenda and next meeting dates

- Requests for changes to agenda?
- Next Community Group Meeting: Wednesday November 20
- No meeting Thursday November 28
- Next AT Driver Subgroup meeting: Monday December 9

### Current status

Goals:

- 6 recommended plans by September 30.
- Total of 10 Recommended + 10 in Candidate Review by December 31.

Status: Behind schedule

#### 8 refactored plans in candidate review

PlanVisperoApple[Alert](https://aria-at.w3.org/data-management/alert)ApprovedIn Review[Action Menu Button Example Using aria-activedescendant](https://aria-at.w3.org/data-management/menu-button-actions-active-descendant)In ReviewIn Review[Color Viewer Slider](https://aria-at.w3.org/data-management/horizontal-slider)in reviewNot started[Command Button](https://aria-at.w3.org/data-management/command-button)ApprovedIn review[Link Example 1 (span element with text content)](https://aria-at.w3.org/data-management/link-span-text)ApprovedIn review[Modal Dialog](https://aria-at.w3.org/data-management/modal-dialog)ApprovedNot started[Radio Group Example Using aria-activedescendant](https://aria-at.w3.org/data-management/radiogroup-aria-activedescendant)in ReviewNot started[Toggle Button](https://aria-at.w3.org/data-management/toggle-button)approvedIn review#### Three refactored plans in draft review

1. [Disclosure Navigation Menu Example](https://aria-at.w3.org/data-management/disclosure-navigation)
2. [Navigation Menu Button](https://aria-at.w3.org/data-management/menu-button-navigation)
3. [Action Menu Button Example Using element.focus](https://aria-at.w3.org/data-management/menu-button-actions)

#### Refactor in progress

1. [Radio Group Example Using Roving tabindex](https://aria-at.w3.org/data-management/radiogroup-roving-tabindex)

### Issue 365: Impact of hints on testing

[Impact of hint text/help messages on test results · Issue #365 · w3c/aria-at](https://github.com/w3c/aria-at/issues/365)

Proposal for discussion (included as comment in issue):

#### Define hint in the glossary

Hint: Supplemental output provided by a screen reader that is intended to help users understand an element or how to use it. Hints are distinct from base output that includes required information, such as name, role, value, state, and properties. Hints may repeat information that is included in base output. hints that are conveyed with speech are spoken after base output.

#### Update Testing guidance

Why AARIA-AT does not test hints, i.e., test assertions do not apply to hints?

1. Hints are supplemental output. While it is very important that hints do not interfere with interoperability, hints are not essential functionality. The scope of ARIA-AT is limited to fostering interoperability of essential functionality.
2. Because users of certain screen readers commonly disable hints, base output must satisfy interoperability requirements. If a hint could satisfy an interoperability requirement, hints would have to be consider essential instead of supplemental.

why leave hints on during testing?

1. Testing with default settings is an important principle.
2. It is important to capture negative side effects caused by hints, e.g., a hint conflicts with base output.

testing requirements:

1. Because hints are sometimes part of an AT response, they are included in the AT response recorded for a command. The goal is for response collection to be comprehensive; it must include both positive and negative side effects of the command. Good hints an be considered a positive side effect while inaccurate hints can be considered a negative side effect.
2. Hint output is not analyzed to determine an assertion verdict. Thus, testers must have the skills and knowledge necessary to distinguish hints from base output.

### Testing Action menu button with element.focus

[Test plan for Action Menu Button Example Using element.focus](https://aria-at.w3.org/data-management/menu-button-actions)

### Testing Disclosure Navigation Menu

[Test plan for Disclosure Navigation Menu Example](https://aria-at.w3.org/data-management/disclosure-navigation)

Issues to resolve:

- [Conflicts in Disclosure Navigation Menu Example V24.10.10 | ARIA-AT](https://aria-at.w3.org/test-queue/300/conflicts)
- [Conflicting results for test 11 "Navigate to an expanded disclosure button from a link in the associated dropdown" (Disclosure Navigation Menu Example, V24.07.31) · Issue #1100 · w3c/aria-at](https://github.com/w3c/aria-at/issues/1100)
- [Conflicting VoiceOver results for test 12 "Navigate from a collapsed disclosure button to a link in a dropdown" (Disclosure Navigation Menu Example, V24.08.12) · Issue #1116 · w3c/aria-at](https://github.com/w3c/aria-at/issues/1116)
- [Conflicting results for test 15 "Activate a link in a dropdown" (Disclosure Navigation Menu Example, V24.07.31) · Issue #1101 · w3c/aria-at](https://github.com/w3c/aria-at/issues/1101)

### Testing navigation menu button

[Test Plan for Navigation Menu Button](https://aria-at.w3.org/data-management/menu-button-navigation)

Issues to resolve:

- [Conflicting VoiceOver results for test 5 "Open a menu to the last item" (Navigation Menu Button, V24.10.12) · Issue #1137 · w3c/aria-at](https://github.com/w3c/aria-at/issues/1137)
- [VoiceOver test result Conflicts Navigation Menu Button V24.10.12 | ARIA-AT](https://aria-at.w3.org/test-queue/306/conflicts)
- [JAWS test result Conflicts Navigation Menu Button V24.10.12 | ARIA-AT](https://aria-at.w3.org/test-queue/304/conflicts)

 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%2Fe72b4a73-43d7-4854-a0ed-d9fde0148f02%2F%3FrecurrenceId%3D20241114T120000) 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").