On Wed, Sep 09, 2020 at 10:41:12PM +0100, Luke Emmet wrote:
>
>
> On 09-Sep-2020 18:38, mbays at sdf.org wrote:
> >
> > So, with apologies for hijacking this thread with something totally
> > opposed to its original idea, I'd like to encourage client authors to
> > close this extensibility hole by not suppressing text after the "```" in
> > preformatting toggle lines.
>
> As far as I can see, the spec seems clear enough on this: "5.4.3: Any line
> whose first three characters are "```" (i.e. three consecutive back ticks
> with no leading whitespace) are preformatted toggle lines. These lines
> should NOT be included in the rendered output shown to the user."
This is an interesting detail: 5.4.3 goes on to say,
> Any text following the leading "```" of a preformat toggle line which
toggles preformatted mode on MAY be interpreted by the client as "alt
text" pertaining to the preformatted text lines which follow the toggle
line. Use of alt text is at the client's discretion, and simple clients
may ignore it. Alt text is recommended for ASCII art or similar
non-textual content which, for example, cannot be meaningfully understood
when rendered through a screen reader or usefully indexed by a search engine.
So on one hand, alt text is not to be included in the rendered output of
the preformat block, but alt text is recommended as alternative output
for the preformat block, when the usual rendered output is not useful to
the user.
I think that means clients should probably hide alt text normally, but
to make use of it, might have a way to reveal it. Tooltips or an alt
text visibility toggle function come to mind. Screen readers would want
to read alt text when focusing the preformat block.
---
Previous in thread (15 of 50): 🗣️ Luke Emmet (luke (a) marmaladefoo.com)
Next in thread (17 of 50): 🗣️ mbays (a) sdf.org (mbays (a) sdf.org)