💾 Archived View for rawtext.club › ~sloum › geminilist › 005661.gmi captured on 2023-11-14 at 09:56:51. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Devin Prater r.d.t.prater at gmail.com
Fri Feb 26 02:57:56 GMT 2021
- - - - - - - - - - - - - - - - - - -
Thanks for your interest. Frames are the one thing I've seen that screenreaders most treat as a "container" that can be skipped. So, have theblocks with a roll of frame, that is, the <iframe> roll if possible, orjust make them <iframe> if possible. I'm more of a user than adeveloper, sorry. Other than that, GemiNaut, as far as I've used it,works great. I'll stress test it more in the coming weeks and get backto you if I find anything else.
On 2/25/21 3:52 PM, Luke Emmet wrote:
On 25-Feb-2021 19:42, Devin Prater wrote:
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.
Hello - GemiNaut author here. I'd be interested to understand further
how to make GemiNaut more accessible. As you have seen it uses an
HTML renderer for the GUI layer, so in theory I'd expect it would be
possible to have good accessibility to allow skipping over the
preformatted areas.
How is this done for well behaved websites, where you want to specify
an area that the user can skip over? Is there a standard way this is
done?
An initial search suggests to use |aria-hidden="true" as an element
attribute to hide it from screen readers.|
This is not my area of expertise, so I'm happy to follow up any
pointers or take pull requests. Feel free to write to me off the list
if you prefer.
- Luke