Re: [External] : Incorporated style changes for CFC

They are all within the “guidelines” folder, which is a set of includes that gets pulled into the main doc.

That shouldn’t cause conflicts as we have very few PRs on the normative parts of the docs.

-Alastair


From: Lori Oakley <lori.oakley@oracle.com>
Date: Monday, 23 September 2024 at 13:36
To: Michael Gower <michael.gower@ca.ibm.com>, WCAG2 Backlog <public-wcag2-issues@w3.org>
Subject: RE: [External] : Incorporated style changes for CFC
Hi Mike,

It looks good to me. The only question I have is changing this many files, doesn't this cause conflicts?

Thanks,
Lori

From: Michael Gower <michael.gower@ca.ibm.com>
Sent: Monday, September 23, 2024 8:04 AM
To: WCAG2 Backlog <public-wcag2-issues@w3.org>
Subject: [External] : Incorporated style changes for CFC

Hello everyone,
Since we’re about to do a CFC, I’ve generated a PR that is entirely about matching W3C style in our technical document.

https://github.com/w3c/wcag/pull/4080<https://urldefense.com/v3/__https:/github.com/w3c/wcag/pull/4080__;!!ACWV5N9M2RV99hQ!PUQW8j2dGThDoq_SHiT-vTGeYKPSRzO89LGFW8fJ70m78n47GMZaS8oB6KruAeIXH8_b1cF7TBseleVIl-j_WNqqgw$>

All of these style changes have been discussed before (and are part of our own style guide as well as in place for the wider W3C and EO guides), but I had been delaying implementing in order to avoid conflicts with other omnibus changes.

There is no content altered as part of this beyond setting some initial capitals to lower case, and the altering of “website” into one word (unlike web page).

It will go through as part of the CFC, but I thought I would flag to members of the TF for a quick review. Apologies for not having it ready for last Friday.

Thanks!
Mike

PS The matching changes in the non-normative docs are still forthcoming; they obviously do not have the publishing constraints of the technical document.