On Tue, 19 Jul 2016 14:32:28 +, rcorre wrote:
> It's a small thing and I'm probably in a minority who work like this,
Things that are difficult with your keyboard-mode browser are probably
difficult for people who use screen readers. It's definitely worth
bringing up.
On Tuesday, 19 July 2016 at 13:33:28 UTC, Jack Stouffer wrote:
On Tuesday, 19 July 2016 at 13:27:37 UTC, qznc wrote:
I don't understand, the anchor link doesn't go anywhere. It's
to provide a perma-link to that piece of documentation so you
can direct link to it somewhere else.
My guess:
On Tuesday, 19 July 2016 at 13:27:37 UTC, qznc wrote:
I don't understand, the anchor link doesn't go anywhere. It's
to provide a perma-link to that piece of documentation so you
can direct link to it somewhere else.
My guess: "every clickable element has a series of keys shown
above it". The
On Tuesday, 19 July 2016 at 13:16:52 UTC, Jack Stouffer wrote:
On Tuesday, 19 July 2016 at 11:38:20 UTC, rcorre wrote:
Keyboard-centric browsers (e.g. qutebrowser [1], dwb [2],
ect.) generally let you click on links via 'hinting'. You
press a button (e.g. 'f' for 'follow'), every clickable
On Tuesday, 19 July 2016 at 11:38:20 UTC, rcorre wrote:
Keyboard-centric browsers (e.g. qutebrowser [1], dwb [2], ect.)
generally let you click on links via 'hinting'. You press a
button (e.g. 'f' for 'follow'), every clickable element has a
series of keys shown above it, and you press those
