W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2019

Re: Code in Pre should not be a failure at this time.

From: Wayne Dick <wayneedick@gmail.com>
Date: Fri, 1 Feb 2019 17:03:43 -0800
Message-ID: <CAJeQ8SBOsQn3wL9tQg7MjeRD5_N5VbErE1rZPEo1zmMLdZnYeg@mail.gmail.com>
To: Jonathan Avila <jon.avila@levelaccess.com>
Cc: GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
I'm workin' on it.

On Fri, Feb 1, 2019 at 1:51 PM Jonathan Avila <jon.avila@levelaccess.com>
wrote:

> Editor like Notepad++ show line numbers and then have no line number for
> lines that wrap.  So some sort of indicator would do the job for wrapped
> text that is not a line break.
>
>
>
> Jon
>
>
>
> *From:* Wayne Dick <wayneedick@gmail.com>
> *Sent:* Friday, February 1, 2019 3:31 PM
> *To:* GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
> *Subject:* Code in Pre should not be a failure at this time.
>
>
>
> *CAUTION:* This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
>
> In my final note on crowd sourcing Pre I outlined the difficulties with
> code. However, we do not have an alternative html construct that does the
> job.
>
>
>
> I think we should work on some basic format rules to enable formatting
> that does not obscure block structure when it word wraps.  I can pull down
> some examples to see what we can do. BUT this should be WCAG 2.1 only.
>
>
>
> We need a bridge until suitable semantic code for developed for HTML.
>
>
>
> Best, Wayne
>
Received on Saturday, 2 February 2019 01:04:41 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:29 UTC