Can anyone provide feedback on how accessible is Gopher using a screen reader? Any quirks worth knowing about?

Thanks.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Accessibility Test wrote:

Can anyone provide feedback on how accessible is Gopher using a screen reader?
Any quirks worth knowing about?

Thanks.

I'm not sure how accessible gopher is by design, but gopher sites
mostly deal in text, which should be easy on a screen reader. I can't
comment too much beyond, that, however, because I don't know how
much a screen reader depends on the underlying protocol (for example
if it is geared towards HTTP for browsers, or if it really does just
read text on a screen. If the latter, I think things should mostly
be fine unless a file download is involved.)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 28 Apr 2019 03:41:27 -0700 (PDT), Accessibility Test <[email protected]> wrote:

Can anyone provide feedback on how accessible is Gopher using a screen reader? >Any quirks worth knowing about?

Thanks.

If I am not mistaken, there is only one Gopher-specific thing - the
Gopher menus. The other type of content (text files, binaries) you can
get through HTTP as well. (eg. using Lynx.) So I guess if a Gopher
menu ("gophermap") is easy to understand if you read it aloud, it
should be okay... I believe that huge ASCII multi-line banners can be
very annoying if read it characer by character.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 28 Apr 2019 03:41:27 -0700, Accessibility Test wrote:

Can anyone provide feedback on how accessible is Gopher using a screen reader?
Any quirks worth knowing about?

Thanks.

I see no reason why screen readers wouldn't work. Don't have experience
with them though. I think gopherholes are even more accessible than
webpages since there isn't anything but the content, which is always good.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 29 Apr 2019, Grant Hedson wrote:

I'm not sure how accessible gopher is by design, but gopher sites
mostly deal in text, which should be easy on a screen reader. I can't
comment too much beyond, that, however, because I don't know how
much a screen reader depends on the underlying protocol (for example
if it is geared towards HTTP for browsers, or if it really does just
read text on a screen. If the latter, I think things should mostly
be fine unless a file download is involved.)

When I did some web-design work, more than ten years ago now, the standard
for determining if a page/site would work well in a screen reader was to
view it in Lynx.

As another poster said, ASCII art is bad, and anything involving columns
is probably bad, but otherwise Gopher ought to be quite accessible for the visually-impaired.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Saw this today, and was reminded of this thread:

gopher://gopher.black:70/1/phlog/20190502-asmr

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, 2 May 2019 20:27:28 +0000
lkosov <[email protected]space> wrote:

Saw this today, and was reminded of this thread:

gopher://gopher.black:70/1/phlog/20190502-asmr

I think a "LOL!" is required here :)
(How does screen readers deal with ASCII smileys btw?)

--

/ Pinku

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)