Re: Editorial updates in WCAG 2.1 publication prep

>I don't know of an orange that passes without getting into brown territory.

Then that would pose a challenge to others which we need to consider.

Jon

Sent from my iPhone

On Feb 24, 2017, at 7:20 PM, David MacDonald <david100@sympatico.ca<mailto:david100@sympatico.ca>> wrote:

I don't know of an orange that passes without getting into brown territory.


Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd<http://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 Fri, Feb 24, 2017 at 4:44 PM, Jonathan Avila <jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>> wrote:

>   The orange borders for proposals are now red and pass the color contrast test;

Red says something different to me than orange.  Were we not able to find an orange that had sufficient contrast?


>  Nobody complained about this, but the "Principle", "Guideline", and "Success Criterion" at the start of headers, and the "Level" in the conformance level indicator, are no longer CSS generated content. However, in the TOC those

I’ve noticed this in other W3C documents.  I had noticed a lot of other content was missing when viewed in IE as well – but then I read Github was no longer supporting IE so I assumed it must have been me.  But we should consider how people might view the document in different browsers like IE.

Jonathan

From: Michael Cooper [mailto:cooper@w3.org<mailto:cooper@w3.org>]
Sent: Friday, February 24, 2017 2:48 PM
To: AG WG
Subject: Editorial updates in WCAG 2.1 publication prep


A couple editorial issues that people raised on the list and I changed for the publication:

  *   The orange borders for proposals are now red and pass the color contrast test;
  *   The instructions in the intro more clearly indicate that they are indicated as "[Proposed]" with brackets, which now works as a search term for people wanting to find them that way;
  *   There's a brief clause pointing out that there are also proposed definitions to look at;
  *   Nobody complained about this, but the "Principle", "Guideline", and "Success Criterion" at the start of headers, and the "Level" in the conformance level indicator, are no longer CSS generated content. However, in the TOC those words are not used (just the section numbers) because of how the W3C stylesheets rendered it. I'll work on solving that for future publications.

Some of these changes are not in the rawgit because they required manual edits to the snapshot that will be published. I'll try to get the github versions up to snuff soon, it will require a little script work.

Michael