RE: CFC - WCAG 2.2 Redundant entry

Without the same session limitation, I’m not sure if the security exception is broad enough to cover situations where saving the data is problematic for privacy reasons.  In some ways we are encouraging people to store a lot of information about users across sessions that they may not be aware of that is being saved.

Jonathan

From: Alastair Campbell <acampbell@nomensa.com>
Sent: Monday, June 6, 2022 1:00 PM
To: Michael Gower <michael.gower@ca.ibm.com>; WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: Re: CFC - WCAG 2.2 Redundant entry

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi Michael,

> I believe a prior version had a note (or even normative wording) explaining that the process is constrained to the current user session.

That was removed last august: https://github.com/w3c/wcag/commit/45f7815e0cb484540e6d362244c35acea89e7bd3


> I also thought the search results example had been critiqued and decided to be removed?

We can check that, but the CFC is for the normative text. Understanding doc updates can be done separately.


> Finally, shouldn’t the 2 editor’s notes  beginning “Are there…” be removed before CFC?

All the “editor’s notes” will be removed prior to CR, but shouldn’t impact this CFC.

Kind regards,

-Alastair


From: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>
Date: Monday, June 6, 2022 at 8:20 AM
To: WCAG list (w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>) <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: [EXTERNAL] CFC - WCAG 2.2 Redundant entry
Call For Consensus — ends Friday June 10th at midday Boston time. The Working Group has previously discussed the WCAG 2.2 SC Redundant Entry and it needs to be approved by CFC. It can be previewed in the editor’s draft: ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Call For Consensus — ends Friday June 10th at midday Boston time.

The Working Group has previously discussed the WCAG 2.2 SC Redundant Entry and it needs to be approved by CFC.

It can be previewed in the editor’s draft:
https://w3c.github.io/wcag/understanding/redundant-entry.html<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwcag%2Funderstanding%2Fredundant-entry.html&data=05%7C01%7Cacampbell%40nomensa.com%7C44120b34848142cca16b08da47dace2c%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C637901302330585015%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4bfTbcNio6Q3SeRl0V%2FkSGvw3xua%2B%2Bmw%2F2MafaJOzjA%3D&reserved=0>

The SC was last discussed Dec 3rd:
https://www.w3.org/2021/12/03-ag-minutes#t24

The change history is here:
https://github.com/w3c/wcag/commits/main/guidelines/sc/22/redundant-entry.html<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag%2Fcommits%2Fmain%2Fguidelines%2Fsc%2F22%2Fredundant-entry.html&data=05%7C01%7Cacampbell%40nomensa.com%7C44120b34848142cca16b08da47dace2c%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C637901302330585015%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jMqdjww97hy1oWtcDcdTf3tC5I0vBFBOwrDWE2cTT8E%3D&reserved=0>

The surveys are available here:
https://www.w3.org/2002/09/wbs/35422/wcag22-redundant-entry/results and
https://www.w3.org/2002/09/wbs/35422/wcag22-redundant-entry-updates/results

The github issues (all closed) are listed here:
https://github.com/w3c/wcag/issues?q=is%3Aissue+label%3A%223.3.8+Redundant+Entry%22<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag%2Fissues%3Fq%3Dis%253Aissue%2Blabel%253A%25223.3.8%2BRedundant%2BEntry%2522&data=05%7C01%7Cacampbell%40nomensa.com%7C44120b34848142cca16b08da47dace2c%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C637901302330585015%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JT9pnNiJGZrODiRzcrVvAFJU02ujL5YhObd%2B3ltXnjo%3D&reserved=0>+

If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.

Kind regards,
-Alastair
--

@alastc / www.nomensa.com<http://www.nomensa.com>