BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20250507T081832Z
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-MICROSOFT-CDO-TZID:13
BEGIN:STANDARD
DTSTART:20241103T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:STANDARD
DTSTART:20251102T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20250309T100000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:c0109ce5-a813-4455-be1d-8080adcc357a
DTSTAMP:20250507T081832Z
SUMMARY:ARIA and Assistive Technologies Community Group Weekly Teleconferen
 ce
DTSTART;TZID=America/Los_Angeles:20250507T100000
DTEND;TZID=America/Los_Angeles:20250507T110000
DESCRIPTION:https://www.w3.org/events/meetings/c0109ce5-a813-4455-be1d-8080
 adcc357a/20250507T100000/\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/May-7%2C-2025-Agenda\n\nAgenda\n\n### Review agen
 da and next meeting dates\n\n* Requests for changes to agenda?\n* Next AT 
 Driver Subgroup meeting: Monday May 12\n* Potentially cancel meeting on Th
 ursday May 15\n* Following Community Group Meeting would be: Wednesday May
  21\n\n### Current status\n\n* Goal for June 30\, 2025: 23 total candidate
  and recommended plans\n* Current status: 15 candidate plans\n* [Test plan
  update tracker in Google Sheets](https://docs.google.com/spreadsheets/d/1
 4QIhQB9ufdUdZNhb3TNZzoZkGBq0oHawft-S5pm0ioY/edit?gid=0#gid=0)\n\n#### 3 pl
 ans in draft review\n\n1. In progress: [Rating Radio Group Example](https:
 //www.w3.org/WAI/ARIA/apg/patterns/radio/examples/radio-rating/)\n1. On ho
 ld: [Vertical Temperature Slider](https://aria-at.w3.org/data-management/v
 ertical-temperature-slider):\n    * NVDA results blocked by [app issue 135
 2](https://github.com/w3c/aria-at-app/issues/1352)\n    * Test plan will n
 eed to be revised after resolution of [APG issue 3257](https://github.com/
 w3c/aria-practices/issues/3257)\, which is planned for May 29.\n1. On hold
 : [Disclosure Navigation Menu Example V25.03.06](https://aria-at.w3.org/te
 st-review/163641):\n    * Completed revisions to assertions for activate l
 ink test.\n    * Re-run with JAWS after JAWS July update is released to ca
 pture accurate output.\n\n#### Coming next to draft review\n\n* May 16 tar
 get: [Accordion](https://www.w3.org/WAI/ARIA/apg/patterns/accordion/exampl
 es/accordion/)\n* Delayed to July (previously April 25 target): [Disclosur
 e (Show/Hide) of Answers to Frequently Asked Questions](https://www.w3.org
 /WAI/ARIA/apg/patterns/disclosure/examples/disclosure-faq/)\n* Delayed to 
 July (previously May 2 target): [Disclosure (Show/Hide) of Image Descripti
 on](https://www.w3.org/WAI/ARIA/apg/patterns/disclosure/examples/disclosur
 e-image-description/)\n* Delayed to July (previously May 16 target): [Disc
 losure (Show/Hide) Navigation Menu with Top-Level Links](https://www.w3.or
 g/WAI/ARIA/apg/patterns/disclosure/examples/disclosure-navigation-hybrid/)
 \n\n#### 15 plans in candidate review\n\nPlan | Vispero | Apple\n--- | ---
  | ---\n[Action Menu Button Example Using aria-activedescendant](https://a
 ria-at.w3.org/data-management/menu-button-actions-active-descendant) | In 
 Review | In Review\n[Action Menu Button Example Using element.focus](https
 ://aria-at.w3.org/data-management/menu-button-actions) | Not Started | Not
  Started\n[Alert](https://aria-at.w3.org/data-management/alert)| Approved 
 | In Review\n[Color Viewer Slider](https://aria-at.w3.org/data-management/
 horizontal-slider) | in review | Not started\n[Command Button](https://ari
 a-at.w3.org/data-management/command-button)| Approved | In review\n[Disclo
 sure Navigation Menu Example](https://aria-at.w3.org/data-management/discl
 osure-navigation) | In Review | Not Started\n[Link Example 1 (span element
  with text content)](https://aria-at.w3.org/data-management/link-span-text
 )| Approved | In review\n[Link Example 2 (img element with alt attribute)]
 (https://aria-at.w3.org/data-management/link-img-alt) | In Review | Not st
 arted\n[Link Example 3 (CSS :before content property on a span element)](h
 ttps://aria-at.w3.org/data-management/link-css) | In Review | Not started\
 n[Media Seek Slider](https://aria-at.w3.org/data-management/seek-slider) |
  In Review | Not started\n[Modal Dialog](https://aria-at.w3.org/data-manag
 ement/modal-dialog) | Approved | Not started\n[Navigation Menu Button](htt
 ps://aria-at.w3.org/data-management/menu-button-navigation) | Not Started 
 | Not started\n[Radio Group Example Using aria-activedescendant](https://a
 ria-at.w3.org/data-management/radiogroup-aria-activedescendant)| in Review
 | Not started\n[Radio Group Example Using Roving tabindex](https://aria-at
 .w3.org/data-management/radiogroup-roving-tabindex)|Not Started|Not starte
 d\n[Toggle Button](https://aria-at.w3.org/data-management/toggle-button)| 
 approved | In review\n\n### Re-run of JAWS for color viewer slider\n\n* [4
  conflicts in JAWS results for Color Viewer Slider V24.12.04](https://aria
 -at.w3.org/test-queue/383/conflicts)\n* Related to min and max announcemen
 t.\n* Need to validate Hadi's results.\n\n### Arrow keys in NVDA test plan
 s\n\n* [Issue 1242: NVDA Feedback: missing arrow key commands in tests 7 t
 hrough 10 in Radio Group Example Using Roving tabindex\, V25.02.12](https:
 //github.com/w3c/aria-at/issues/1242)\n* [Issue 1243: NVDA Feedback: Missi
 ng arrow key commands in test 7 through 10 in Radio Group Example Using ar
 ia-activedescendant\, V25.02.12](https://github.com/w3c/aria-at/issues/124
 3)\n\nConsider: [Conflicts in NVDA results for Rating Radio Group V25.04.2
 2](https://aria-at.w3.org/test-queue/393/conflicts#main):\n* Should we kee
 p insert+up in the plan?\n* NVDA behavior in rating radio group is inconsi
 stent with how NVDA behaves in other semantically equivalent scenarios.\n*
  Should we consider adding arrow keys to tests 7 through 10 like in other 
 radio test plans?\n\n### App issue 1298 about VO bot inconsistencies\n\n[V
 oiceOver Bot / any browser - Expected button states are inconsistent in Di
 sclosure Nav tests · Issue #1298 · w3c/aria-at-app](https://github.com/w
 3c/aria-at-app/issues/1298)
STATUS:CONFIRMED
CREATED:20250507T081830Z
LAST-MODIFIED:20250507T081832Z
SEQUENCE:3
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:20250507T100000
END:VEVENT
END:VCALENDAR
