BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20251107T152834Z
BEGIN:VTIMEZONE
TZID:Asia/Tokyo
X-MICROSOFT-CDO-TZID:20
BEGIN:STANDARD
DTSTART:20241116T004500
TZOFFSETFROM:+0900
TZOFFSETTO:+0900
TZNAME:JST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:7c7e68a1-2d98-4b85-b812-a9c3d2f6f50c
DTSTAMP:20251107T152834Z
SUMMARY:Accessibility Guidelines Working Group
DTSTART;TZID=Asia/Tokyo:20251111T094500
DTEND;TZID=Asia/Tokyo:20251111T180000
DESCRIPTION:https://www.w3.org/events/meetings/7c7e68a1-2d98-4b85-b812-a9c3
 d2f6f50c/\n\n\n\nAgenda\n\nMorning: WCAG 2 updates\n* Proposal\;\n  * Clea
 n up of existing content\n  * Internationalization \n  * Possible algorith
 m updates\n  * Normative errata\n  * Deduplication?\n  * Fixing audio desc
 ription\n  * Timing adjustable\n  * NOT: Adding new requirements\n* Discus
 sion Questions\n  * Which of the changes above raise risks of breaking bac
 kwards compatibility?\n  * Can we address items above WITHOUT breaking bac
 kwards compatibility?\n* What do we call it?\n  * WCAG 2.3\n  * WCAG 2026\
 n  * WCAG 2.final\n  * WCAG 2.3 (Not backwards compatible)\n\nAfternoon: W
 hat would a policy document with WCAG 3 look like?\n* Input of [info from 
 editors week](https://docs.google.com/presentation/d/1DlDxp8MCYXj3RWnFCCz1
 3zsmM2fV4Wf8NbECKogdul8/edit?slide=id.g39fd5db5083_2_5#slide=id.g39fd5db50
 83_2_5)\n* Desired outcome:  Resolution to do such a document (in charter)
 \, and desired outline (not in charter)
STATUS:CONFIRMED
CREATED:20250716T142447Z
LAST-MODIFIED:20251107T152834Z
SEQUENCE:9
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessibility Guid
 elines Working Group:mailto:public-ag-admin@w3.org
LOCATION:Floor 4 - 402
CATEGORIES:TPAC 2025,Group Meetings
END:VEVENT
END:VCALENDAR