- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Wed, 29 Mar 2023 07:55:00 -0500
- To: "Bradley Montgomery, Rachael L" <rmontgomery@loc.gov>
- Cc: WCAG list <w3c-wai-gl@w3.org>
+1 Kind Regards, Laura On 3/28/23, David MacDonald <david@can-adapt.com> wrote: > +1 > Cheers, > David MacDonald > > > > *Can**Adapt* *Solutions Inc.* > Mobile: 613.806.9005 > > LinkedIn > <http://www.linkedin.com/in/davidmacdonald100> > > twitter.com/davidmacd > > GitHub <https://github.com/DavidMacDonald> > > www.Can-Adapt.com <http://www.can-adapt.com/> > > > > * Adapting the web to all users* > * Including those with disabilities* > > If you are not the intended recipient, please review our privacy policy > <http://www.davidmacd.com/disclaimer.html> > > > On Tue, Mar 28, 2023 at 6:24 PM Bradley Montgomery, Rachael L < > rmontgomery@loc.gov> wrote: > >> Peter, >> >> >> >> That is the proposal being discussed, yes. >> >> >> >> Rachael >> >> >> >> *From: *"Bossley, Peter (TR Product)" <Peter.Bossley@thomsonreuters.com> >> *Date: *Tuesday, March 28, 2023 at 6:19 PM >> *To: *"Bradley Montgomery, Rachael L" <rmontgomery@loc.gov> >> *Cc: *WCAG <w3c-wai-gl@w3.org> >> *Subject: *RE: Focus appearance updates >> >> >> >> *CAUTION:* This email message has been received from an external source. >> Please use caution when opening attachments, or clicking on links. >> >> Confirming that we are still moving this to AAA? If so, +1. >> >> (Just wanted to confirm I was reading the minutes correctly.) >> >> >> >> >> >> *From:* Bradley Montgomery, Rachael L <rmontgomery@loc.gov> >> *Sent:* Tuesday, March 28, 2023 2:29 PM >> *To:* Alastair Campbell <acampbell@nomensa.com>; w3c-waI-gl@w3. org < >> w3c-wai-gl@w3.org> >> *Subject:* [EXT] Re: Focus appearance updates >> >> >> >> *External Email:* Use caution with links and attachments. >> >> >> >> +1 to moving forward with the following at AAA: >> >> >> >> When the keyboard focus indicator >> <https://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-focus-indicator__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDb49gGtA$> >> 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://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-css-pixels__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDAtZW_rA$> >> thick perimeter >> <https://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-perimeter__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDx1Boe9Y$> >> of >> the unfocused component or sub-component, and >> >> o has a contrast ratio of at least 3:1 between the same pixels in the >> focused and unfocused states. >> >> >> >> And to marking it “At Risk” with the fallback option being: >> >> >> >> When the keyboard focus indicator >> <https://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-focus-indicator__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDb49gGtA$> >> is >> visible, an area of the focus indicator meets all the following: >> >> - is at least as large as the area of a 1 CSS pixel >> >> <https://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-css-pixels__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDAtZW_rA$> >> thick perimeter >> >> <https://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-perimeter__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDx1Boe9Y$> >> of >> the unfocused component or sub-component, or is at least as large as >> a 4 >> CSS pixel thick line along the shortest side of the minimum >> bounding box >> >> <https://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-minimum-bounding-box__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDLUNcGzQ$> >> 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, and >> - has a contrast ratio of at least 3:1 against adjacent >> non-focus-indicator colors, or is no thinner than 2 CSS pixels. >> >> >> >> >> >> *From: *Alastair Campbell <acampbell@nomensa.com> >> *Date: *Tuesday, March 28, 2023 at 2:18 PM >> *To: *WCAG <w3c-wai-gl@w3.org> >> *Subject: *Re: Focus appearance updates >> *Resent-From: *WCAG <w3c-wai-gl@w3.org> >> *Resent-Date: *Tuesday, March 28, 2023 at 2:16 PM >> >> >> >> *CAUTION:* This email message has been received from an external source. >> Please use caution when opening attachments, or clicking on links. >> >> Hi everyone, >> >> >> >> We didn’t have quite enough time for the focus-appearance discussion >> today, but I think it helped to clarify the options. >> >> >> >> I think we could proceed with the SC ‘at risk’, with a preferred option, >> and a fall-back option. >> >> >> >> Everyone seemed happy with removing the first part of the SC text, so our >> fallback option now is: >> >> >> >> When the keyboard focus indicator >> <https://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-focus-indicator__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDb49gGtA$> >> is visible, an area of the focus indicator meets all the following: >> >> - is at least as large as the area of a 1 CSS pixel >> >> <https://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-css-pixels__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDAtZW_rA$> >> thick perimeter >> >> <https://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-perimeter__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDx1Boe9Y$> >> of the unfocused component or sub-component, or is at least as large >> as a 4 >> CSS pixel thick line along the shortest side of the minimum >> bounding box >> >> <https://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-minimum-bounding-box__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDLUNcGzQ$> >> 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, and >> - has a contrast ratio of at least 3:1 against adjacent >> non-focus-indicator colors, or is no thinner than 2 CSS pixels. >> >> >> >> (Plus exceptions.) >> >> >> >> From the discussion of the other potential options, I’ve updated the >> document: >> >> >> https://docs.google.com/document/d/1RGQBMvDAhEylflppCAKrF6IW8zjHjqH6DNqXKKzpHyI/edit# >> <https://urldefense.com/v3/__https:/docs.google.com/document/d/1RGQBMvDAhEylflppCAKrF6IW8zjHjqH6DNqXKKzpHyI/edit__;!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDHrCyZeo$> >> >> >> >> If we increase the size requirement, it only makes sense if we also >> remove >> the “4 times shortest side” metric. (We could logically increase that to >> 8 >> times, but I don’t that would be feasible/helpful for the cases we were >> looking at). >> >> >> >> Also, with the increased size requirement I think we can drop the last >> (adjacent contrast) bullet entirely. See the lower part of the doc. >> >> >> >> So the simplest option (readability wise) is: >> >> >> >> >> >> When the keyboard focus indicator >> <https://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-focus-indicator__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDb49gGtA$> >> 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://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-css-pixels__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDAtZW_rA$> >> thick perimeter >> <https://urldefense.com/v3/__https:/www.w3.org/TR/WCAG22/*dfn-perimeter__;Iw!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDx1Boe9Y$> >> of the unfocused component or sub-component, and >> >> o has a contrast ratio of at least 3:1 between the same pixels in the >> focused and unfocused states. >> >> >> >> (Plus exceptions.) >> >> >> >> So, proceeding at risk, can anyone not live with the short option? The >> fallback being very close to the current SC wording. >> >> >> >> >> >> Kind regards, >> >> >> >> -Alastair >> >> >> >> -- >> >> >> >> @alastc / www.nomensa.com >> <https://urldefense.com/v3/__http:/www.nomensa.com__;!!GFN0sa3rsbfR8OLyAw!dHXX5oYfc4UaU_mLfvOsT7lFm-fWZuJmwQcye7_P420DFubbxMomoOlrAz5Zewgk6MuFCqUthE45Ss29cSiexljDL6a5XDE$> >> >> >> >> >> > -- Laura L. Carlson
Received on Wednesday, 29 March 2023 12:55:14 UTC