Re: WCAG 2.x Editorial updates

That described the problem (that the PR fixed). The fix in the PR was to 
then use <ul> ... c'mon, have a little faith in my PRs...

Patrick

On 30/08/2023 13:02, John Foliot wrote:
> Alastair writes:
>  >  <ol> used instead of <ul> when no order is intended/necessary
> 
> Errmm... isn't that the other way around? That *<ul>* is used when no 
> order is intended? (It may just be the way this was written, but 
> noting it just in case...)
> 
> JF
> 
> On Wed, Aug 30, 2023 at 7:21 AM Alastair Campbell <acampbell@nomensa.com 
> <mailto:acampbell@nomensa.com>> wrote:
> 
>     Hi everyone,____
> 
>     __ __
> 
>     These have been merged.____
> 
>     __ __
> 
>     *From: *Alastair Campbell
>     *Date: *Tuesday, 22 August 2023 at 15:22
>     *To: *WCAG list
>     *Subject: *WCAG 2.x Editorial updates____
> 
>     Hi everyone,____
> 
>     ____
> 
>     A while back we discussed doing asynchronous approvals of minor
>     changes to the informative WCAG 2.x documents.____
> 
>     ____
> 
>     We’ll refine this process when the new Task Force is started, but in
>     the meantime, I thought we could beta-test this process.____
> 
>     ____
> 
>     This is a short list of a few backlog items:____
> 
>     https://github.com/w3c/wcag/pulls?q=is%3Aopen+is%3Apr+label%3AAsync-Approval <https://github.com/w3c/wcag/pulls?q=is%3Aopen+is%3Apr+label%3AAsync-Approval>+____
> 
>     ____
> 
>     If any of these appear to create problems, or you think should not
>     be merged: Please reply in the github thread or to this email by the
>     30^th August.____
> 
>     +1s are not required for this type of (largely editorial) changes to
>     informative documents. We will default to merging unless problems
>     are spotted. ____
> 
>     ____
> 
>     If you don’t respond by then we will merge it, but if you later
>     spot/discover a problem, that’s ok, we can do a similar update in
>     future.____
> 
>     ____
> 
>     *Overview of PRs / Changes*____
> 
>     **____
> 
>     Reformat definition lists, ordered lists, fix Reading Level
>     understanding <https://github.com/w3c/wcag/pull/3296> #3296 ____
> 
>       * seems back in the WCAG 2.0 days, definition lists weren't used.
>         This retrospectively fixes it____
>       * <ol> used instead of <ul> when no order is intended/necessary____
>       * fix the completely broken listing of education levels for
>         Reading Level understanding____
> 
>     ____
> 
>     Tweak 2.4.6 Headings and Labels understanding
>     <https://github.com/w3c/wcag/pull/3295> #3295 ____
> 
>     Remove incorrect suggestion that headings/labels should make sense
>     out of context, reformat lists (particularly what seemed to be a
>     definition list, but marked up with <strong>?)____
> 
>     ____
> 
>     Follow-up changes to 1.4.3 and 1.4.6 understanding documents
>     <https://github.com/w3c/wcag/pull/3216> #3216 ____
> 
>       * corrects a mistake where the text about focus/hover in 1.4.6
>         understanding talks about 1.4.3 applying also to focus/hover,
>         when it actually means to say that THIS SC applies here as well.
>         this PR now generalises that text to just say "This Success
>         Criterion"____
>       * adds a <code> block that was missed out for the contrast formula____
>       * reformats the contrast formula rationale part for enhanced
>         contrast, to bring it in line with the same text in the minimum
>         contrast understanding____
>       * tweaks the rationale to mention 1.4.6 in relation to 7:1 ratio____
> 
>     ____
> 
>     ____
> 
>     Update text alternative for target size (minimum) understanding
>     illustrations <https://github.com/w3c/wcag/pull/3190> #3190 ____
> 
>       * corrects the incomplete alt for the target-spacing-toolbar
>         example____
>       * expands the alt for a few of the following illustrations____
> 
>     ____
> 
>     Kind regards,____
> 
>     ____
> 
>     -Alastair____
> 
>     ____
> 
>     -- ____
> 
>     ____
> 
>     @alastc / www.nomensa.com <http://www.nomensa.com/>____
> 
>     ____
> 
> 
> 
> -- 
> *John Foliot* |
> Senior Industry Specialist, Digital Accessibility |
> W3C Accessibility Standards Contributor |
> 
> "I made this so long because I did not have time to make it shorter." - 
> Pascal "links go places, buttons do things"

-- 
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
https://mastodon.social/@patrick_h_lauke | skype: patrick_h_lauke

Received on Wednesday, 30 August 2023 12:54:35 UTC