Cognitive aspects of navigation in gemini space

[James Tomasino]

On 5/14/20 6:33 PM, solderpunk wrote:
> he new figlet-generated (I assume?) section
> headers look really great, but they're not great for accessibility (a
> screen reader won't know how to read them) and they're not great for
> searchability (a GUS search for words used in one of them won't turn up
> results).

It's a really tough situation and you nailed it on the head. Code
fencing can be used for creative art or for literally preserving
whitespace on indexable content. It would be nice to indicate to both
screen readers and search engines which is which.

I hesitate to even offer a solution because it gets too close to our
heated code fencing & list markup discussion, but... As code fences
currently begin with ```
and end with
```

We could use the starting code fence to indicate whether the content is
art or not, or parseable as text or not.

```text

```art

or some ARIA-esque token.

I was originally thinking that the text following ``` could be a literal
alt text. I dunno. Just throwing out ideas.

solderpunk, please don't shoot me.