Meeting minutes
<maryjom> https://
Issue 473: https://
ISSUE: w3c/
Issue 473 - Definitions and explanations for “Set of Documents” and “Set of Software Programs” produces strange corner cases that should be addressed or explained
Issue 473, working ideas in Google doc: https://
ISSUE: w3c/
Proposal 1: No change to the content, with the following proposed answer
Thank you for your question regarding WCAG2ICT. The Task Force considered making the advisory content regarding “sets of software” and “sets of documents” more formal, but decided against making any changes. While overlapping sets could occur, we do not foresee a problem in evaluating each overlapping set as a set.
<maryjom> Add proposal 1 to a survey for the coming week
<ChrisLoiselle> +1 to proposal 1
Issue 466 - Closed functionality list - suggested additions
ISSUE: w3c/
Proposal 1: No change to examples of closed functionality
[Examples excerpt from the Key Terms section on “closed functionality (as used by WCAG2ICT)”]
Example: Examples of technology that may have closed functionality include:
self-service transaction machines or kiosks — examples include machines used for retail self-checkout, point of sales (POS) terminals, ticketing and self-check-in, and Automated Teller Machines (ATMs).
telephony devices such as internet phones, feature phones, smartphones, and phone-enabled tablets
entertainment technologies including smart TVs, set-top boxes, smart displays, smart speakers, smart watches, and tablets
an ebook reader or standalone ebook software that allows assistive technologies to access all of the user interface controls of the ebook program (open functionality) but does not allow the assistive technologies to access the actual content of book (closed functionality).
an operating system that makes the user provide login credentials before it allows any assistive technologies to be loaded. The login portion would be closed functionality.
other technology devices, such as printers, displays, and Internet of Things (IoT) devices.
[Examples excerpt from the Comments on Closed Functionality section]
Example: In developing guidance for closed functionality, the task force has considered examples of ICT that historically have been partially or fully closed to assistive technologies:
self-service transaction machines or kiosks (e.g. retail self-checkout, point of sales (POS) terminals, and Automated Teller Machines (ATMs))
telephony devices (e.g. internet phones, feature phones, and smartphones)
entertainment technologies (e.g. smart TV, set-top box, smart watches)
ebook reader
computer that is locked down due to a policy so that users may not adjust settings or install software
other technology devices (e.g. printers, displays, and Internet of Things (IoT) devices).
Proposal 2: Incorporate suggested examples from Issue 466
[Examples excerpt from the Key Terms section on “closed functionality (as used by WCAG2ICT)”]
Example: Examples of technology that may have closed functionality include but are not limited to:
self-service transaction machines or kiosks — examples include machines used for retail self-checkout, point of sales (POS) terminals, ticketing and self-check-in, and Automated Teller Machines (ATMs).
telephony devices such as internet phones, feature phones, smartphones, and phone-enabled tablets
educational devices such as interactive whiteboards and smart boards
entertainment technologies including gaming platforms or consoles, smart TVs, set-top boxes, smart displays, smart speakers, smart watches, and tablets
an ebook reader or standalone ebook software that allows assistive technologies to access all of the user interface controls of the ebook program (open functionality) but does not allow the assistive technologies to access the actual content of the book (closed functionality).
medical devices such as digital blood pressure monitors, glucose meters, or other wearable devices
an operating system that makes the user provide login credentials before it allows any assistive technologies to be loaded. The login portion would be closed functionality.
other technology devices, such as printers, displays, and Internet of Things (IoT) devices.
[Examples excerpt from the Comments on Closed Functionality section]
Example: In developing guidance for closed functionality, the task force has considered examples of ICT that historically have been partially or fully closed to assistive technologies:
self-service transaction machines or kiosks (e.g. retail self-checkout, point of sales (POS) terminals, and Automated Teller Machines (ATMs))
telephony devices (e.g. internet phones, feature phones, and smartphones)
educational devices such as interactive whiteboards and smart boards
entertainment technologies (e.g. gaming platforms or consoles, smart TV, set-top box, smart watches)
ebook reader
medical devices such as digital blood pressure monitors, glucose meters, or other wearable devices
computer that is locked down due to a policy so that users may not adjust settings or install software
other technology devices (e.g. printers, displays, and Internet of Things (IoT) devices).
2 lists of closed functionality examples. First is a full list of systems that may be closed.
Second list is specifically those technologies that the TF has considered
After discussion - add new examples only to the definitions section, not to the Comments on Closed Functionality list
Proposal 2 modified as follows:
Proposal 2: Incorporate suggested examples from Issue 466
[Examples excerpt from the Key Terms section on “closed functionality (as used by WCAG2ICT)”]
Example: Examples of technology that may have closed functionality include but are not limited to:
self-service transaction machines or kiosks — examples include machines used for retail self-checkout, point of sales (POS) terminals, ticketing and self-check-in, and Automated Teller Machines (ATMs).
telephony devices such as internet phones, feature phones, smartphones, and phone-enabled tablets
educational devices such as interactive whiteboards and smart boards
entertainment technologies including gaming platforms or consoles, smart TVs, set-top boxes, smart displays, smart speakers, smart watches, and tablets
an ebook reader or standalone ebook software that allows assistive technologies to access all of the user interface controls of the ebook program (open functionality) but does not allow the assistive technologies to access the actual content of the book (closed functionality).
medical devices such as digital blood pressure monitors, glucose meters, or other wearable devices
an operating system that makes the user provide login credentials before it allows any assistive technologies to be loaded. The login portion would be closed functionality.
other technology devices, such as printers, displays, and Internet of Things (IoT) devices.
[Examples excerpt from the Comments on Closed Functionality section]
Example: In developing guidance for closed functionality, the task force has considered specific examples of ICT that historically have been partially or fully closed to assistive technologies:
self-service transaction machines or kiosks (e.g. retail self-checkout, point of sales (POS) terminals, and Automated Teller Machines (ATMs))
telephony devices (e.g. internet phones, feature phones, and smartphones)
entertainment technologies (e.g. smart TV, set-top box, smart watches)
ebook reader
computer that is locked down due to a policy so that users may not adjust settings or install software
other technology devices (e.g. printers, displays, and Internet of Things (IoT) devices).
Issue 465 - Seeking clarity for key term 'underlying platform software'
ISSUE: w3c/
<maryjom> Issue 465: w3c/
Google doc: https://
Decision yesterday was to not change SCs
Correct Google doc: https://
No change to SCs 2.5.1, 2.5.2 and 2.5.7
Accessible authentication also has "underlying" platform software
So SC 3.3.8 should leave as is, to keep consistent with SCs 2.5.1, 2.5.2, 2.5.7
Only things we will change are removing "Underlying" from Note 1 in the Glossary entry 'keyboard interface' and from SC 2.1.1 Keyboard
Issue 464 - Suggest slight clarification of audience and outcomes #464
Google doc: https://
ISSUE: w3c/
Decision made yesterday - just needs a PR to be created
Issue 463 - Programmatically determine the language of text #463
ISSUE: w3c/
Google doc: https://
Question is regarding the quote from WCAG - not how we apply it.
https://
Our application: https://
Only change from WCAG is word substitution - content replaced with non-web document and software
Definition of programmatically determined - https://
Looks like this is just a question on the original WCAG language, not our word substitutions for ICT
Chris to draft reply
Draft reply to go in google doc for others to give input
(Now moved to horizontal review google doc)
w3c/wcag2ict#427
Needs 2 proposals to be added to survey - one version with, one version without
Mary Jo to work on this one, add options to google doc, then put in survey
Issue 421 - In definition of 'keyboard interface' and in 2.1.1, "would satisfy the success criterion" is incomplete #421
Mary Jo to propose 2 options and survey
Issue 383 - Adjust links in Guidance Section to link to all taskforce and AG publications #383
If we point to an evergreen link, then the current link points to lots of documents. Only a few are relevant to WCAG2ICT, and are difficult to identify!
Categories make it difficult to search
<ChrisLoiselle> https://
We could point to the general TF page - and suggest people refer to specific guidance from these areas that may be helpful...
<ChrisLoiselle> https://
Refer to the publications from these various groups
Mary Jo to draft PR on this and add to survey
Daniel has worked on a few PRs. Editors to review and give input