Meeting minutes
<maryjom> Analysis spreadsheet - SC that could use more extensive language changes
Announcements
Remember to "present+" yourself
Brief discussion about v012 of EN 301 549 - incorporation of WCAG2ICT - some changes suggested in public draft comments via ITI
<GreggVan> PRESETN+
Announcements. There was an email from Mary Jo. US daylight savings changes this Sunday, so there will be a mismatch for the next 3 weeks.
W3C calendar should handle the time change - just make sure - meeting will be an hour earlier for those in non-US timezones
Thinking that we might just cancel next week because of CSUN
<bruce_bailey> i will not be at CSUN, but will be offline for most of the next two weeks.
Next week (13th March) WCAG2ICT call will be cancelled.
Mary Jo will send email reminder about next week being cancelled
Develop WCAG2ICT "Explainer" Content
[maryjom sharing screen]
<Zakim> bruce_bailey, you wanted to note light editing before call
bruce_bailey: has done some light editing on the document just before the call
Working through edits from last week, accepting changes...
Text moved into "what is" section
What is this document
The WCAG2ICT Group Note is intended to help clarify how to use WCAG 2 to make non-web documents and non-web software more accessible to people with disabilities. Addressing accessibility involves addressing the needs of people with auditory, cognitive, neurological, physical, speech, and visual disabilities, and the needs of people with
accessibility requirements due to the effects of aging. Although this document covers a wide range of issues, it is not able to address all the needs of all people with disabilities.
Background with accepted changes
Background and Development History for WCAG2ICT
WCAG 2 was developed for the Web. Addressing accessibility for non-web documents and non-web software involves requirements beyond those included in WCAG 2 and the WCAG2ICT Group Note. Authors and developers are encouraged to seek other relevant advice about current best practices to ensure that non-web documents and non-web software are
accessible, as far as possible, to people with disabilities.
The 2013 WCAG2ICT Group Note helped regulatory bodies develop standards (i.e., 508, EN 301549) adopt WCAG criteria for non-web documents and non-web software. The 2013 Group Note covered WCAG 2.0 (level A and AA, only) and the latest version of WCAG2ICT Group Note covers all WCAG 2 versions.
GreggVan: question if we have AAA.
maryjom: Clarified that this may be coming later
After Gregg's minor changes: Background and Development History for WCAG2ICT
WCAG 2 was developed for the Web. Addressing accessibility for non-web documents and non-web software involves requirements beyond those included in WCAG 2 and the WCAG2ICT Group Note. Authors and developers are encouraged to seek other relevant advice about current best practices to ensure that non-web documents and non-web software are
accessible, as far as possible, to people with disabilities.
The 2013 WCAG2ICT Group Note helped regulatory bodies develop standards (i.e., 508, EN 301549) adopt WCAG criteria for non-web documents and non-web software. The 2013 Group Note covered WCAG 2.0 (level A and AA) and the latest version of WCAG2ICT Group Note covers all WCAG 2 versions (level A and AA).
GreggVan: Suggest we pull the goals from our charter or work statement
Revised: Goals
The objective of the WCAG2ICT Task Force is to develop documentation describing how WCAG 2.x and its principles, guidelines, and success criteria could apply to non-Web Information and Communications Technologies (ICT).
Now working on Intent & usage
Current: Intent and Usage of the WCAG2ICT Note
Will look into DoJ references to WCAG2ICT to point out specific expectations there that aren’t actually covered in WCAG2ICT to inform some of this content.
WCAG2ICT is a W3C Group Note that is informative — it is not normative and does not set requirements. It provides guidance on the application of WCAG 2 principles, guidelines, and success criteria to non-web documents and software. WCAG2ICT was developed to provide an authoritative interpretation of how WCAG 2 can apply in different contexts.
The main focus of the WCAG2ICT Note is to provide verbiage replacements for web-based language in the WCAG success criteria and definitions as well as provide additional insights into where WCAG criteria may make assumptions of the presence and functionality of a user agent and assistive technology. This is because not all software has a user agent
or platform software with accessibility APIs and services, nor do all technologies have or support assistive technology that acts on programmatic information.
GreggVan: suggest we may want to avoid commenting on 3rd parties interpretation
<Zakim> bruce_bailey, you wanted to DOJ reference is opportunity to fullfil their expectations
bruce_bailey: This is an opportunity to make sure WCAG2ICT does what DOJ or other bodies expected it would do.
… so we can do things that were not in our charter when it was originally done
Sam: Thought one issue was the applicability of criteria.
Now working on "who is WCAG2ICT for"
Who is WCAG2ICT for?
WCAG2ICT is for standard developers, ICT managers, ICT developers, policy makers, and any others wanting to understand how WCAG 2 can be applied to non-web documents and software.
Accessibility standards organizations - to provide non-web language in the success criteria and definitions and to provide interpretation notes to help the organization make any potential adjustments or notes needed for specific technologies, if needed.
ICT managers - who are familiar with WCAG to quickly get an overview of using WCAG as an accessibility benchmark for non-web ICT.
Technology developers - to provide the language substitutions for non-web language in WCAG success criteria where existing accessibility standards don’t contain an interpretation.
Policy makers (which includes legislators, regulators) - to inform policy makers how WCAG2ICT is being used to influence standards requirements where WCAG is being applied to non-web ICT.
Others include auditors, educators, litigation, marking, the curious, and individuals looking to learn more about digital accessibility.
Daniel: suggest we focus on primary audience. Marketers may not be primary
Revised version...
Who is WCAG2ICT for?
WCAG2ICT is for standard developers, ICT managers, ICT developers, policy makers, and any others wanting to understand how WCAG 2 can be applied to non-web documents and software.
Accessibility standards organizations - to provide non-web language in the success criteria and definitions and to provide interpretation notes to help the organization make any potential adjustments or notes needed for specific technologies, if needed.
ICT managers - who are familiar with WCAG to quickly get an overview of using WCAG as an accessibility benchmark for non-web ICT.
Technology developers - to provide the language substitutions for non-web language in WCAG success criteria where existing accessibility standards don’t contain an interpretation.
Policy makers (which includes legislators, regulators) - to inform policy makers how WCAG2ICT is being used to influence standards requirements where WCAG is being applied to non-web ICT.
Others include auditors, educators, litigators, vendors, and individuals looking to learn more about digital accessibility.
Nearly finished with this doc. Think about how we should deliver it.
Analysis for SC language changes
Google doc: https://
maryjom: Would like people to add comments on any of the SCs
If you have any thoughts you want to discuss just speak up
Now going to work on SCs individually
Pick any you want - just put your name on it so somebody else doesn't edit at the same time
Google doc: https://
bruce_bailey: If we think the standard SC works - do we just write "No" in the first & 2nd columns?
maryjom: Correct - the vast majority are likely to be No, No, in the 1st 2 columns
Sam: Question. Our charter is not to change based on EN. Is that correct?
GreggVan: No - EN should follow us, we shouldn't need to change to follow EN.
Sam: Not sure on Loic's comments on consistent navigation - pulled content from EN.
loicmn: Not because of the changes in EN - it's because we couldn't change the language in the original WCAG. We can change the language in WCAG2ICT.
maryjom: We can also suggest changes for WCAG3
GreggVan: We should focus on non-web content
… We shouldn't be commenting on web content in WCAG - just comment on applying it outside of the web
… But we can bring information from the working on EN - to inform the working here to improve language
Sam: Think we cannot add to requirements
GreggVan: We can change wording when outside the web - we are interpreting non-web
Sam: looking rows 46-47
loicmn: I misunderstood the purpose of this table. I thought we were giving feedback to WCAG. So forget my earlier input - loicmn will then give to WCAG3 team
<Daniel> What counts as consistent identification
<Daniel> Open by Eric Eggert
Daniel: Chances are low for WCAG2 to have new items added. But it is theoretically possible.
… It would then be 2.2.1 or 2.3 or whatever
Daniel: Open issue from Eric which might be relevant - see above.
maryjom: 5 minutes left. Made good progress on the SCs
We can wrap up here - just finish whichever line you are working on.
If you have time please continue to work on incomplete lines in this spreadsheet.
You can also propose improvements for WCAG3 if needed
But we should focus on what work we need to do in our document
Spreadsheet link: https://
See you in 2 weeks, apart from those who will meet in person at CSUN.