[BRLTTY] Clickable links, virtual consoles etc. (Was Re: Footsteps towards better accessibility in Linux)

[Jason J.G. White]

Note also that xdg-open can open a specified URL in the default browser 
as determined by your desktop environment.

On 8/5/25 09:08, Chevelle wrote:
> If you want to click a link from a graphical terminal with ORCA it is 
> possible.  In 'mate-terminal' at least it works.  Make a file like 
> 'junk.txt' with a link in it and cat the file.  Then press the home 
> key to move to the link.  Next press the rightORCA command perform 
> right click on current item.  You should get a menu. Press the down 
> arrow key and select 'Oepn Link' or 'Copy'. Now if BRLTTY can generate 
> the right click it should be possible to press a routing button in 
> combination with another key.  ORCA doesn't have a default key binding 
> for this as far as I can tell. Also when XBRLAPI is running the help 
> key on the Braille display says no help available for what it calls 
> the BRLAPI driver., so it is necessary to use the ORCA key bindings 
> dialogue.  I hope that makes sense.
>
>
> On 5/8/25 04:23, Sébastien Hinderer wrote:
>> Dear Nicolas,
>>
>> Many thanks for your tips and sharing your experience, I find it very
>> interesting and inspiring.
>>
>> To say a bit more about what I am after, I think  I'd like to continue
>> reading my e-mails with Mutt but with the ability, ifit turns out to be
>> necessary, to get a link opened in Firefox as sfiwtly as possible.
>>
>> Of course if that could be achieved from a virtual console (basically an
>> action on a link opens it in Firefox and the screen goes to the GUI)
>> that would probably be my ideal, but I think this may be a bit too high
>> an expectation, so I think I would not mind being able to do the same
>> from a terminal run in graphic mode.
>>
>> I don't know, though, if that is possible and how to reach that. For
>> instance I don't know whether this is something ordinary sighted users
>> can achieve, or if that would be a challenge even for them.
>>
>> I guess one part of the quesiton is to know whether there is an
>> interface between programs and terminals to let program tell to
>> terminals that such and such zone is clickable, and of which Mutt would
>> already be taking advantage when the terminal supports it.
>>
>> Coming back to your workflow, Nicolas, I completely share the feeling
>> that the console is way more efficient even than graphical terminals at
>> the moment, because the responsiveness in virtual consoles is better,
>> for instance.
>>
>> Still a few questions I'd like to ask you. What is the size of
>> yourterminals? Do you stick to the classical 25x80 scheme or do you use
>> way bigger terminals? I am asking because onmy side I continue to use
>> 80x25 but this sometimes creates problems I do not have a good solution
>> for. The bigger one, I think, is copy/pasting links displayed by lynx. I
>> do have the URLs displayed at the bottomof the screen, but if the link
>> is longer than the screen width, then it because quite annoying. Usually
>> I use E to edit the link, copy the beginning of the link to BRLTTY's
>> clipboard, delete it so that the following part fits on the screen, add
>> this part to BRLTTY's clipboard etc. which can be quite tedious and
>> error-prone. If anybody has a better way of doing that in the virtual
>> console and with lynx I am super interested to hear about it.
>>
>> The other question for you Nicolas is could you please elaborate the
>> workflow you mentionned to transfer links from Linux to iOS? I do have
>> an iPhone, too, and I find transferring links cumbersome. Usually I send
>> them to myself by e-mail but I do not find this very convenient.
>>
>> And of course there is also the question of how to efficiently share
>> passwords between Linux and iOS, especially given that in text-mode we
>> do not have (asfar as I know) the possibility tu seu the web browser
>> based plugins to interact with the mainstream password managers.
>>
>> Best wishes,
>>
>> Seb.
>> _______________________________________________
>> This message was sent via the BRLTTY mailing list.
>> To post a message, send an e-mail to: BRLTTY at brltty.app
>> For general information, go to: 
>> http://brltty.app/mailman/listinfo/brltty
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty