Meeting minutes
Announcements
This week - a big request. The mobile accessibility task force is hoping to publish 1st public working draft of their guidance for mobile.
It would be helpful if members of the WCAG2ICT can review - to check consistency with WCAG2ICT - as there may be modifications.
This is “pre-CFC”, i.e. a good (but last) chance to comment before we go into a CFC.
This publication will mark the first step towards the process of publishing a Group Note.
This is your last chance to comment for changes, either at:
https://
Or to public-mobile-a11y-tf@w3.org
Email sent out on Tuesday 25 Feb from Alastair Campbell
1 week to review the mobile task force working draft
Does anyone have any time to review this doc in the next week?
<ChrisLoiselle> I have no bandwidth :( I suggest comment would be to hold off and put under WCAG2ICT
<bruce_bailey> i agree it is missed opportunity not too coordinate more closely
We may need to provide comment during the 30-day public comment period.
ChrisLoiselle: Think there is still some discussion to have about how it relates to other W3C - where it is published and how it is organised is an open question. e.g. Is it a subset of WCAG2ICT?
<ChrisLoiselle> +1 to Bruce. I had that same idea
<Zakim> bruce_bailey, you wanted to ask if we could ask MATF to identify any areas of friction between their work and ours?
bruce_bailey: Shame we don]t have more time to coordinate. But suggest we ask them for input on where they think there might be areas of friction or challenges, so we can focus on those specific areas.
maryjom: To meet up with JJ after CSUN - will discuss matters then
Recap for shadi: This week - a big request. The mobile accessibility task force is hoping to publish 1st public working draft of their guidance for mobile.
It would be helpful if members of the WCAG2ICT can review - to check consistency with WCAG2ICT - as there may be modifications.
<Zakim> bruce_bailey, you wanted to mention that MATF might be of more utility to recent DOJ ADA web rule than WCAG2ICT
bruce_bailey: MATF might be of more utility to recent DOJ ADA web rule than WCAG2ICT - as this references primarily mobile, but points to WCAG2ICT at the moment
maryjom: Need to consider inconsistencies with WCAG2ICT and also new EN 301 549 draft.
… And some ideas might only apply to mobile, not to all software.
Develop WCAG2ICT "Explainer" Content
<PhilDay> +1 to reviewing draft comment
<ChrisLoiselle> +1
<loicmn6> +1
<bruce_bailey> +1 that guidance to U.S. states needs to be harmonized with guidance to Europe.
maryjom: to work on drafting an initial comment on mobile TF.
<bruce_bailey> +1 to reviewing draft maryjom draft comment
maryjom: Cleaned up comments, accepted suggested changes etc to make it easier to review.
[maryjom sharing screen˙
Proposed edit: WCAG2ICT is the acronym used for the W3C Guidance on Applying WCAG 2 to Non-web Information and Communication Technology Group Note.
<bruce_bailey> sometimes WCAG2ICT is the doc sometimes its the TF
maryjom: Add TF when we refer to the task force later to differentiate between document and task force
And refer to group note when we refer to the doc
Latest version "who develops"
Who develops WCAG2ICT
The WCAG2ICT Group Note is developed by a Task Force (TF) of the Accessibility Guidelines Working Group (AG WG). The work statement defines the objectives, scope, approach, and so on for the WCAG2ICT Group Note. The participants of the WCAG2ICT TF are volunteers drawn from W3C member organizations and invited experts and are supported by WAI staff.
Version being reviewed: Background and Development History for WCAG2ICT
This document 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. Because WCAG 2 was developed for the Web, addressing accessibility for non-web documents and non-web software may involve requirements beyond those included in this document.
Authors and developers are encouraged to seek 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.
<bruce_bailey> I had originally intended to reference the Access Board second ANPRM and suggesting WCAG incorporation by reference for software, and industry had concerns.
<bruce_bailey> +1 to shadi
shadi: Good summary of what the document is -maybe the title should be changed. Sentences 2 & 3 removed or moved to end. (Addressing accessibility... and Although this document...)
<loicmn6> +1 to shadi proposal to delete sentences 2 & 3.
shadi: Another minor comment. "relevant advice" - is this document irrelevant? Maybe change to "additional advice"
maryjom: Maybe worth talking about previous attempts to use WCAG outside of the web, so this document was created to provide that guidance.
<Zakim> PhilDay, you wanted to say Web or web
<ChrisLoiselle> Phil, I think we could move to intent and usage
PhilDay: suggest sentences 2-3 move to intent & usage.
maryjom: Other sentences to go into introduction
<maryjom> loicmn
loicmn6: "This document" - should "The WCAG2ICT group note is intended to"
<bruce_bailey> Again, I started from 2013 https://
<shadi> +1 good point!
shadi: Could be a section called "Why this was created"
explain intent to apply WCAG to non-web software - mention US Access Board etc.
[Now looking at Goals]
Goals
Brief description of the main goal for WCAG2ICT - in a sentence or two.
This document is a companion “explainer” for the WCAG2ICT W3C Group Note. It is meant to be…..
Addition for Background & dev history: This section should cover need for WCAG2ICT Group Note and how it was developed to provide the interpretation for use with regulatory standards (508, EN 301549).
There was a version from 2013 which covered WCAG 2.0 and the latest version of WCAG2ICT covers all WCAG 2 versions.
shadi: This document doesn't provide "the interpretation".
… provides guidance or clarification from a W3C perspective to help those who wish to apply WCAG to non-web...
Latest rough draft: This section should cover need for WCAG2ICT Group Note and how it was developed to provide guidance and considerations for applying WCAG in non-web contexts. This helped regulatory standards (508, EN 301549) adopt WCAG criteria for non-web documents and software. There was a version from 2013 which covered WCAG 2.0 and the
latest version of WCAG2ICT covers all WCAG 2 versions.
We may not need a Goal section
If it ends up being too repetitive...
Still more work to do later in the doc
References have been cleaned up
Feel free to add to the document during the week, ready for next week
Analysis spreadsheet - SC that could use more extensive language changes
Google sheet for analysis: https://
Friday meeting has not worked - nobody has been able to attend.
So we will try and do some of the work in this Thursday session
Assign yourself to a few SCs, then go away and suggest if we need any changes
(e.g. CSS pixels)
Latest editor's draft for ref: https://
<maryjom> Group worked the remainder of the meeting on filling in the spreadsheet and discussing comments entered into the spreadsheet.
shadi: Why would consistent navigation be applied to elements with the same functionality repeated **on the same page**?
loic: This can happen where at the top of the page you have "Previous" and "Next" and may be the opposite order at the bottom of the page.
… will provide additional examples for us to discuss next time.