[Clients] Gemini and accessibility regarding preformatted code blocks


25 f?vrier 2021 21:29 "Devin Prater" <r.d.t.prater at gmail.com> a ?crit:
>> Is that because "slash" has one syllable and "asterisk" has three? 
>> Just guessing here, but please
>> tell us what works/doesn't work for you, or point to a suitable 
>> "accessibility 101" site.
> 
> Nah, slash is just easier to press than Shift + 8. I meant ergonomic as 
> in easy to type. Although,
> ?slash" is spoken more quickly than ?asterisk", but most TTS engines 
> say ?star? anyway. It?s not
> significant, and is definitely up to the writer?s choice of style.
> 
>>> So, this is where client creators come in. Gemini clients should have 
>>> a way to hide preformatted
>>> blocks, or fold them, or if they are a GUI client, like GemiNaut, 
>>> which shows the Gemini text in n
>>> HTML-like area, map the blocks to a frame, so that screen readers can 
>>> skip them.
>> 
>> I think that most preformatted blocks are meant to be readable. How 
>> about an option to hide
>> preformatted blocks if and only if they have alt text? That, plus 
>> social pressure to actually
>> *provide* alt text, even if it's just "ascii art" or "ascii art 
>> kittens", should do it.
> The problem is that screen readers *cannot* read Ascii art in any 
> meaningful way, so having the
> option to hide those blocks by default would really help. If clients 
> really wanted to be smart,
> grab a list of language short codes from Github or something and show 
> blocks with those language
> ID?s, like:
> 
> ``` Python
> ?
> ```
> 
> Would be shown, but:
> 
> ``` Best widdle kitten ever
> ?
> ```
> 
> wouldn?t. But that?s just something I?ve thought of when thinking about 
> how to work around
> preformatted blocks that would be meaningful to a screen reader user, 
> like code, and those which
> wouldn?t be, like Ascii art.

Is the reader reading line by line? So depending on the alternative text 
the user could decide
to explore the content or skip it?

Thank you very much for your email! There is definitely a need to 
improve the accessibility and
it better to do it know than trying to change things once the protocol 
and formats are carved
in stone.

I wonder if the alternative texts (better renamed "description"?) should 
be mandatory
for such pre-formated blocks?

---

Previous in thread (3 of 51): 🗣️ Devin Prater (r.d.t.prater (a) gmail.com)

Next in thread (5 of 51): 🗣️ ew.gemini (ew.gemini (a) nassur.net)

View entire thread.