BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20241114T195328Z
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-MICROSOFT-CDO-TZID:13
BEGIN:DAYLIGHT
DTSTART:20240310T100000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20250309T100000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20241103T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:e72b4a73-43d7-4854-a0ed-d9fde0148f02
DTSTAMP:20241114T195328Z
SUMMARY:ARIA and Assistive Technologies Community Group Weekly Teleconferen
 ce
DTSTART;TZID=America/Los_Angeles:20241114T120000
DTEND;TZID=America/Los_Angeles:20241114T130000
DESCRIPTION:https://www.w3.org/events/meetings/e72b4a73-43d7-4854-a0ed-d9fd
 e0148f02/20241114T120000/\n\nWeekly meeting focused primarily on generatin
 g ARIA-AT reports via manual testing. Alternates between an earlier Wednes
 day time one week and later Thursday time the next.\n\nAgenda: https://git
 hub.com/w3c/aria-at/wiki/November-14%2C-2024-Agenda\n\nAgenda\n\n### Revie
 w agenda and next meeting dates\n\n* Requests for changes to agenda?\n* Ne
 xt Community Group Meeting: Wednesday November 20\n* No meeting Thursday N
 ovember 28\n* Next AT Driver Subgroup meeting: Monday December 9\n\n### Cu
 rrent status\n\nGoals:\n* 6 recommended plans by September 30.\n* Total of
  10 Recommended + 10 in Candidate Review by December 31.\n\nStatus: Behind
  schedule\n\n#### 8 refactored plans in candidate review\n\nPlan | Vispero
  | Apple\n--- | --- | ---\n[Alert](https://aria-at.w3.org/data-management/
 alert)| Approved | In Review\n[Action Menu Button Example Using aria-activ
 edescendant](https://aria-at.w3.org/data-management/menu-button-actions-ac
 tive-descendant) | In Review | In Review\n[Color Viewer Slider](https://ar
 ia-at.w3.org/data-management/horizontal-slider) | in review | Not started\
 n[Command Button](https://aria-at.w3.org/data-management/command-button)| 
 Approved | In review\n[Link Example 1 (span element with text content)](ht
 tps://aria-at.w3.org/data-management/link-span-text)| Approved | In review
 \n[Modal Dialog](https://aria-at.w3.org/data-management/modal-dialog) | Ap
 proved | Not started\n[Radio Group Example Using aria-activedescendant](ht
 tps://aria-at.w3.org/data-management/radiogroup-aria-activedescendant)| in
  Review| Not started\n[Toggle Button](https://aria-at.w3.org/data-manageme
 nt/toggle-button)| approved | In review\n\n#### Three refactored plans in 
 draft review\n\n1. [Disclosure Navigation Menu Example](https://aria-at.w3
 .org/data-management/disclosure-navigation)\n1. [Navigation Menu Button](h
 ttps://aria-at.w3.org/data-management/menu-button-navigation)\n1. [Action 
 Menu Button Example Using element.focus](https://aria-at.w3.org/data-manag
 ement/menu-button-actions)\n\n#### Refactor in progress\n\n1. [Radio Group
  Example Using Roving tabindex](https://aria-at.w3.org/data-management/rad
 iogroup-roving-tabindex)\n\n### Issue 365: Impact of hints on testing\n\n[
 Impact of hint text/help messages on test results · Issue #365 · w3c/ari
 a-at](https://github.com/w3c/aria-at/issues/365)\n\nProposal for discussio
 n (included as comment in issue):\n\n#### Define hint in the glossary\n\nH
 int: Supplemental output provided by a screen reader that is intended to h
 elp users understand an element or how to use it. Hints are distinct from 
 base output that includes required information\, such as name\, role\, val
 ue\, state\, and properties. Hints may repeat information that is included
  in base output. hints that are conveyed with speech are spoken after base
  output. \n\n#### Update Testing guidance\n\nWhy AARIA-AT does not test hi
 nts\, i.e.\, test assertions do not apply to hints?\n1. Hints are suppleme
 ntal output. While it is very important that hints do not interfere with i
 nteroperability\, hints are not essential functionality. The scope of ARIA
 -AT is limited to fostering interoperability of essential functionality.\n
 2. Because users of certain screen readers commonly disable hints\, base o
 utput must satisfy interoperability requirements. If a hint could satisfy 
 an interoperability requirement\, hints would have to be consider essentia
 l instead of supplemental.\n\nwhy leave hints on during testing?\n1. Testi
 ng with default settings is an important principle.\n2. It is important to
  capture negative side effects caused by hints\, e.g.\, a hint conflicts w
 ith base output.\n\ntesting requirements:\n1. 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 m
 ust include both positive and negative side effects of the command. Good h
 ints an be considered a positive side effect while inaccurate hints can be
  considered a negative side effect.\n2. Hint output is not analyzed to det
 ermine an assertion verdict. Thus\, testers must have the skills and knowl
 edge necessary to distinguish hints from base output.\n\n### Testing Actio
 n menu button with element.focus\n\n[Test plan for Action Menu Button Exam
 ple Using element.focus](https://aria-at.w3.org/data-management/menu-butto
 n-actions)\n\n### Testing Disclosure Navigation Menu\n\n[Test plan for Dis
 closure Navigation Menu Example](https://aria-at.w3.org/data-management/di
 sclosure-navigation)\n\nIssues to resolve:\n* [Conflicts in Disclosure Nav
 igation Menu Example V24.10.10 | ARIA-AT](https://aria-at.w3.org/test-queu
 e/300/conflicts)\n* [Conflicting results for test 11 "Navigate to an expan
 ded 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)\n* [Conflicting VoiceOver results fo
 r test 12 "Navigate from a collapsed disclosure button to a link in a drop
 down" (Disclosure Navigation Menu Example\, V24.08.12) · Issue #1116 · w
 3c/aria-at](https://github.com/w3c/aria-at/issues/1116)\n* [Conflicting re
 sults for test 15 "Activate a link in a dropdown" (Disclosure Navigation M
 enu Example\, V24.07.31) · Issue #1101 · w3c/aria-at](https://github.com
 /w3c/aria-at/issues/1101)\n\n### Testing navigation menu button\n\n[Test P
 lan for Navigation Menu Button](https://aria-at.w3.org/data-management/men
 u-button-navigation)\n\nIssues to resolve:\n* [Conflicting VoiceOver resul
 ts 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/issu
 es/1137)\n* [VoiceOver test result Conflicts Navigation Menu Button V24.10
 .12 | ARIA-AT](https://aria-at.w3.org/test-queue/306/conflicts)\n* [JAWS t
 est result Conflicts Navigation Menu Button V24.10.12 | ARIA-AT](https://a
 ria-at.w3.org/test-queue/304/conflicts)
STATUS:CONFIRMED
CREATED:20241114T195327Z
LAST-MODIFIED:20241114T195328Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=ARIA and Assistive
  Technologies Community Group:mailto:public-aria-at@w3.org
RECURRENCE-ID;TZID=America/Los_Angeles:20241114T120000
END:VEVENT
END:VCALENDAR