BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20220330T222935Z
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-MICROSOFT-CDO-TZID:13
BEGIN:STANDARD
DTSTART:20211107T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:STANDARD
DTSTART:20221106T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20220313T100000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:56afb63c-c19d-4883-9e6c-ca8f5db72ff0
DTSTAMP:20220330T222935Z
SUMMARY:ARIA Deep Dive - Dialogs
DTSTART;TZID=America/Los_Angeles:20220407T090000
DTEND;TZID=America/Los_Angeles:20220407T100000
DESCRIPTION:https://www.w3.org/events/meetings/56afb63c-c19d-4883-9e6c-ca8f
 5db72ff0/\n\nPostponing this until 07 April as multiple folks can't make M
 arch 31.\n\nhttps://github.com/w3c/aria/issues/1708\n\nAgenda\n\nhttps://g
 ithub.com/whatwg/html/wiki/dialog--initial-focus\,-a-proposal\n\nThe discu
 ssion has been very valuable. Our end goal is to pull improvements from th
 is discussion into HTML and ARIA specs and and implementations. ARIA and H
 TML should be aligned\, such that <dialog> and role=dialog result in simil
 iar behavior.\n\nAll browsers are currently shipping some form of initial 
 focus in dialog\, using some version/concept of "first focusable descendan
 t". Firefox was satisfied with the direction of the discussion\, in terms 
 of improving existing behavior\, and as a result\, they started shipping i
 n Firefox 98. Safari 15.4 and Chrome/Edge already ship as well.\n\nThe dis
 cussion needs to continue on these issues we uncovered:\n\n### AT support:
 \n* Should modeless dialogs be treated as a landmark\n* Should platform AP
 Is provide a dialog open event\n* Should platform APIs provide a means to 
 determine whether a dialog is modal or non-modal? HTML-AAM 377\n* Should g
 uidance be provided on what screen readers should announce when a dialog o
 pens (they tend to read up to the current focus\, but have slightly differ
 ent heuristics)\n### Improving keyboard accessibility of non-modal dialogs
 :\n* Tab trapping Should <dialog> actually create a "control group" for fo
 cus? whatwg/html#2171\n* Dialog closing keystrokes such as Escape: Enable 
 support for<dialog> to be dismissed using the back button whatwg/html#5667
 \n* Pane switching keystrokes such as F6 (or Ctrl+F6 on Mac): Clarify UX (
 keyboard) and further a11y expectations for modeless dialogs whatwg/html#7
 707
STATUS:CONFIRMED
CREATED:20220330T161006Z
LAST-MODIFIED:20220330T222935Z
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=Accessible Rich In
 ternet Applications Working Group:mailto:public-aria@w3.org
END:VEVENT
END:VCALENDAR