RE: Decision to Restart CR or Not (Please review and reply by March 30th)

+1 to restarting CR

Regards
Stefan

From: Melanie Philipp <melanie.philipp@deque.com>
Sent: Wednesday, 29 March 2023 19:31
To: Bradley Montgomery, Rachael L <rmontgomery@loc.gov>
Cc: WCAG <w3c-wai-gl@w3.org>
Subject: Re: Decision to Restart CR or Not (Please review and reply by March 30th)

+1 to restarting CR to move some form of Focus Appearance to AAA and rework Target Size to make it simpler (circle approach).

I can also go with continuing on with this CR, but only if that means dropping the at-risk Focus Appearance.

Melanie Philipp, CPACC, WAS | Director, Services Methodology | 540-848-5220
Deque Systems - Accessibility for Good
www.deque.com<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.deque.com%2F&data=05%7C01%7Cstefan.schnabel%40sap.com%7Caabf4b291cf444a2468608db307b744f%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638157079019891423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TFgP7znEMpW8zqxkjge6xo5X99F%2F2qIShKIIf%2FW5h1s%3D&reserved=0>



On Wed, Mar 29, 2023 at 10:38 AM Michael Gower <michael.gower@ca.ibm.com<mailto:michael.gower@ca.ibm.com>> wrote:
+1 Restart.
I do think there is another option which is:
3) Remove Focus Appearance entirely  and leave Target Size as is.

If something be discovered in the next couple days that shows we simply cannot return to CR, we may want to keep that in mind, as some may prefer that to leaving Focus Appearance at AA.

Mike

From: Bradley Montgomery, Rachael L <rmontgomery@loc.gov<mailto:rmontgomery@loc.gov>>
Date: Tuesday, March 28, 2023 at 3:58 PM
To: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: [EXTERNAL] Decision to Restart CR or Not (Please review and reply by March 30th)
Hello, At this point we have several suggested changes to Focus Appearance and Target Size to address concerns raised during Candidate Review (CR). Making these normative changes will require we reenter CR and slip publication to June. We need
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Hello,

At this point we have several suggested changes to Focus Appearance and Target Size to address concerns raised during Candidate Review (CR). Making these normative changes will require we reenter CR and slip publication to June.

We need to make a decision about whether those changes are worth restarting CR and slipping publication to the June timeframe.  This is a straw poll to get a sense from the group where everyone stands.

Do you believe we should:


1.       Leave Focus Appearance and Target Size text as is in the current draft,<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2FWCAG22%2F&data=05%7C01%7Cstefan.schnabel%40sap.com%7Caabf4b291cf444a2468608db307b744f%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638157079019891423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=UkjreqTetFEOM%2BZAp0rGwRlOEZsI16Jx9YGdkZeaUh0%3D&reserved=0> transition to PR, and publish on schedule, or

2.       Update the text and restart CR, publishing in the June timeframe?


The changes discussed at today’s meeting and in other email threads are:



•         Target Size Pull Request<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag%2Fpull%2F3123%2Ffiles%23diff-a30d6476d02e45a066c55e8e174fe5381088cb0a3862e9c2e4eb3bbdf695c007&data=05%7C01%7Cstefan.schnabel%40sap.com%7Caabf4b291cf444a2468608db307b744f%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638157079019891423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=elhh0R4N%2FY1rpVKpiEH%2FBr824Mvh3rcnTfmevHOl2to%3D&reserved=0>

•         Change Focus Appearance to:

When the keyboard focus indicator<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2FWCAG22%2F%23dfn-focus-indicator&data=05%7C01%7Cstefan.schnabel%40sap.com%7Caabf4b291cf444a2468608db307b744f%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638157079019891423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZLNGJie%2BxeBFnSPm8Wva9Hln9LCJgP6jW%2BwY7UBiFTM%3D&reserved=0> is visible, an area of the focus indicator meets all the following:
o    is at least as large as the area of a 2 CSS pixel<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2FWCAG22%2F%23dfn-css-pixels&data=05%7C01%7Cstefan.schnabel%40sap.com%7Caabf4b291cf444a2468608db307b744f%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638157079019891423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9ieXhiuSGzClWTundvjmIM3D7M9tNptoyYYdshzWB14%3D&reserved=0> thick perimeter<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2FWCAG22%2F%23dfn-perimeter&data=05%7C01%7Cstefan.schnabel%40sap.com%7Caabf4b291cf444a2468608db307b744f%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638157079020047665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZjLOz%2BCrf2%2Bz1aZ3Xo4t1KdPiDj5vExTBnD5Weg7mdM%3D&reserved=0> of the unfocused component or sub-component, and

·     has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states.
I’ve included the changes above to simplify hunting but please limit your response on this thread to whether you think the changes are worth slipping the schedule.
Kind regards,

Rachael



---
Rachael Bradley Montgomery, PhD
Digital Accessibility Architect
Library of Congress
Email: rmontgomery@loc.gov<mailto:rmontgomery@loc.gov>