- From: <kerscher@montana.com>
- Date: Tue, 16 Aug 2022 20:29:21 -0600
- To: <public-epub3@w3.org>, <public-publishingcg@w3.org>
- Message-ID: <004001d8b1e1$38a31740$a9e945c0$@montana.com>
Dear Accessibility Summary sub-TF, Date: Thursday August 18, 2022 Time: 14 UTC, 7:00 a.m. Pacific, 10:00 a.m. East Coast, 15:00 London, 16:00 Milan Location: see zoom below IRC channel: #pcg-a11y server: irc.w3.org port: 6665 or 6667 Agenda 1. Scribe 2. Accessibility Summary is now a recommendation (should) not a requirement (must) in the EPUB Accessibility Conformance and Discoverability Specification 1.1 in CR. The change happened last week. 3. Background 3.1 official definition of accessibilitySummary in schema.org https://schema.org/accessibilitySummary "A human-readable summary of specific accessibility features or deficiencies, consistent with the other accessibility metadata but expressing subtleties such as "short descriptions are present but long descriptions will be needed for non-visual users" or "short descriptions are present and no long descriptions are needed." 3.2 There has been a change to the conformance section 3.5.2 of the EPUB Accessibility Conformance and Discoverability specification 1.1. Now the metadata is clearly understandable as a natural language description of conformance. The strings are required and can be parsed to align with specific statements. https://www.w3.org/TR/epub-a11y-11/ Here is the text: To indicate conformance to the accessibility requirements of this specification, an EPUB publication [epub-3] MUST specify in its metadata section a conformsTo property [dcterms] exactly matching (i.e., both in case and spacing) the following pattern: EPUB-A11Y-A11Y-VER_WCAG-WCAG-VER-WCAG-LVL where: A11Y-VER Specifies the version number of the EPUB Accessibility specification the publication conforms to. The value MUST NOT include decimal points (e.g., the value 11 indicates this version of this specification). WCAG-VER Specifies the version number of WCAG the publication conforms to. The value MUST NOT include decimal points (e.g., 20 for WCAG 2.0 or 21 for WCAG 2.1). WCAG-LVL Specifies the WCAG conformance level the publication conforms to (e.g., A or AA). EXAMPLE 1: A basic conformance statement In this example, the EPUB creator is stating that their publication conforms to the EPUB Accessibility 1.1 specification at WCAG 2.1 Level AA. <package .> <metadata .> . <meta property="dcterms:conformsTo" id="conf"> EPUB-A11Y-11_WCAG-21-AA </meta> . </metadata> . </package> The following conformance strings are valid as of publication of this specification: . EPUB-A11Y-11_WCAG-20-A . EPUB-A11Y-11_WCAG-20-AA . EPUB-A11Y-11_WCAG-20-AAA . EPUB-A11Y-11_WCAG-21-A . EPUB-A11Y-11_WCAG-21-AA . EPUB-A11Y-11_WCAG-21-AAA NOTE The list of valid conformance strings will increase as W3C releases new versions of WCAG. In addition, WCAG 3.0 is set to introduce new level names (currently Bronze, Silver and Gold). Those names will likely replace A, AA, and AAA in the string pattern, but conformance will be addressed after that specification becomes a W3C Recommendation. 4. Outline of our Accessibility Summary Begin Outline Abstract Status of this document Table of Contents (automatically generated) Introduction Note: Reference to the User Experience guide. Principles 1: - I was thinking this would be a restatement/pointer to the Schema.org definition of the accessibility Summary Principles 2: I thought this would be a description of the presentation of the accessibility metadata presented through the User Experience Guide, i.e., this is all the accessibility metadata that is normally identified. Principle 3: This would reference the conformance metadata statements referenced above, e.g. <meta property="dcterms:conformsTo" id="conf"> EPUB-A11Y-11_WCAG-21-AA </meta> Before you start writing Some High-level Considerations What to include in the Accessibility Summary Guide Examples End of outline George Kerscher is inviting you to a scheduled Zoom meeting. Topic: George Kerscher's Personal Meeting Room Join Zoom Meeting https://us02web.zoom.us/j/4065494687 Meeting ID: 406 549 4687 Passcode: 123456 One tap mobile +13462487799,,4065494687# US (Houston) +16699006833,,4065494687# US (San Jose) Dial by your location +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 253 215 8782 US (Tacoma) +1 312 626 6799 US (Chicago) +1 929 436 2866 US (New York) +1 301 715 8592 US (Germantown) Meeting ID: 406 549 4687 Find your local number: https://us02web.zoom.us/u/kcidE9pCDH Telephone numbers outside the USA: Australia: +61 (0) 2 8015 2088 or +61 (0) 8 7150 1149 Brazil: +55 11 4680 6788 or +55 21 3958 7888 France: +33 (0) 1 8288 0188 Germany +49 (0) 30 3080 6188 or +49 (0) 30 5679 5800 Italy: +39 069 480 6488 Japan +81 (0) 3 4578 1488 or +81 524 564 439 Spain: +34 84 368 5025 or +34 91 198 0188 Sweden: +46 (0) 7 6692 0434 or +46 (0) 8 4468 2488 Switzerland: +41 (0) 31 528 0988 Netherlands: +31 (0) 20 241 0288 United Kingdom: +44 20 3051 2874 or +44 (0) 20 3695 0088 Other international numbers available: https://zoom.us/zoomconference A full list of keyboard shortcut keys can be found at: https://support.zoom.us/hc/en-us/articles/205683899-Hot-Keys-and-Keyboard-Sh ortcuts-for-Zoom Some Keyboard Shortcuts for Windows . F6: Navigate among Zoom popup windows. . Ctrl+Alt+Shift: Move focus to Zoom's meeting controls . Alt+U:Display/hide Participants panel . Alt+Y: Raise/lower hand . Alt+A: Mute/unmute audio . Alt+V: Start/Stop Video . Alt+H: Display/hide In-Meeting Chat panel . Alt+N: Switch camera Alt+F: Enter or exit full screen
Received on Wednesday, 17 August 2022 02:30:05 UTC