Re: CFC - Two editorial Errata

+1 to both

JF

On Wed, Sep 26, 2018 at 9:50 AM, Detlev Fischer <detlev.fischer@testkreis.de
> wrote:

> +1
>
> Am 26.09.2018 um 15:28 schrieb Andrew Kirkpatrick:
>
> Call For Consensus — ends Friday September 28 at 9am Boston time.
>
>
>
> The Working Group has discussed one editorial errata during the working
> group call (https://github.com/w3c/wcag/issues/460 and
> https://www.w3.org/2018/09/25-ag-minutes.html#item07) and another was
> just reported that is so straightforward that this chair estimates 100%
> support for (https://github.com/w3c/wcag/issues/488).
>
>
>
> Errata #1:
>
> The text under the Understandable principle is currently “Information and
> the operation of user interface must be understandable.” There is a small
> grammatical issue which the group proposes to resolve by changing the text
> to “Information and operation of the user interface must be
> understandable.” (adding “the” before “user interface”).
>
> Reference: https://www.w3.org/TR/WCAG21/#understandable
>
>
>
> Errata #2:
>
> An issue was submitted this morning (https://github.com/w3c/wcag/
> issues/488) that pointed out that the text immediately following the
> “Robust” principle is “Content must be robust enough that it can be
> interpreted by by a wide variety of user agents, including assistive
> technologies.” (note the “by by”). As this is different from the WCAG 2.0
> text and the group intended to not make any change, the proposal for this
> Editorial Errata is to indicate that this text should match the WCAG 2.0
> version, which is “Content must be robust enough that it can be interpreted
> reliably by a wide variety of user agents, including assistive
> technologies.” (uses “reliably by” instead of “by by”).
>
> Reference: https://www.w3.org/TR/WCAG21/#robust
>
>
>
> In accepting this CFC, you are agreeing to mark issues 460 and 488 as
> editorial errata per the W3C’s process for indicating Errata to a published
> specification.
>
>
>
> If you have concerns about this proposed consensus position that have not
> been discussed already and feel that those concerns result in you “not
> being able to live with” this decision, please let the group know before
> the CfC deadline.
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Head of Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C54093524ef264326424008d51cd66c05%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446629619786436&sdata=c5UP0xiniJIppvd6Esu1XA%2FbX1ykpABkhgCCmBp%2Fht8%3D&reserved=0>
>
>
>
>
>
>
> --
> Detlev Fischer
> TestkreisWerderstr. 34, 20144 Hamburg <https://maps.google.com/?q=Werderstr.+34,+20144+Hamburg&entry=gmail&source=g>
>
> Mobil +49 (0)157 57 57 57 45
> http://www.testkreis.de
> Beratung, Tests und Schulungen für barrierefreie Websites
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virenfrei.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> <#m_7574634516275178059_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>



-- 
*​John Foliot* | Principal Accessibility Strategist
Deque Systems - Accessibility for Good
deque.com