mudlet buttons and ui's buttons availible in the output window unclickable?

[mohammedradwan2003]

Brief summary of issue / Description of requested feature:

when you go to the UI buttons which other moos download or some other buttons in mudlet such as discord, they show as clickable but you can't click on them

Steps to reproduce the issue / Reasons for adding feature:

1. press contrl tap from input field
2. press tap and listen to the buttons and their names or check boxes
3. press space on a button or a checkbox and it won't click

Error output / Expected result of feature

result that it clicks on the buttons

Extra information, such as the Mudlet version, operating system and ideas for how to solve / implement:

mudlet on windows, solving it by making them clickable using keyboard keys, not just showing up as buttons.

[ironcross32]

If you would please try the following and let us know if this changes the result, also these are assuming NVDA as your screen reader:

• Navigate to a button and press NVDA+Numpad Enter if on desk layout, or NVDA+Enter if on laptop
• Press NVDA + Numpad divide when focused on a button then numpad divide to click or, if on laptop layout, NVDA+Shift+M and then NVDA+[ (left square bracket)
• Simply substitute enter for space when trying to activate the button

[mohammedradwan2003]

like, i can let it work like that, but what i want to happen is that we become able to click the buttons which we can find after pressing tap from the output window, not using this curser.

Edit: Kebap: removed full quote

[ironcross32]

Ultimately, I agree; however, troubleshooting to see if they can be interacted with at all can be useful.

Edit: Kebap: removed full quote

[mohammedradwan2003]

i managed to click on them when i tested yes, i think some of them relate to buffers and mappers, which i think we can convince devs to work on making them accessible,i am sure rojan and tamarindo would be excited about it

[vadi2]

It's not about convincing devs to implement anything - we don't need any convincing, we agree! Better to put that energy to convince more people to contribute to the project. With more people, we'll go further.

[vadi2]

The provided instructions do not work - pressing ctrl+tab switches to the main window, pressing tab then goes back to the input line. NVDA does not read out the buttons.

Provide exact steps to make the problem happen, please.

[vadi2]

@mohammedradwan2003 is this still an issue for you?

[mohammedradwan2003]

they can be, i checked with a combobox once in lotj

On 7/20/22, ironcross32 @.***> wrote:

like, i can let it work like that, but what i want to happen is that we become able to click the buttons which we can find after pressing tap from the output window, not using this curser.

…

On 7/20/22, ironcross32 @.> wrote: If you would please try the following and let us know if this changes the result, also these are assuming NVDA as your screen reader: Navigate to a button and press NVDA+Numpad Enter if on desk layout, or NVDA+Enter if on laptop Press NVDA + Numpad divide when focused on a button then numpad divide to click or, if on laptop layout, NVDA+Shift+M and then NVDA+[ (left square bracket) Simply substitute enter for space when trying to activate the button -- Reply to this email directly or view it on GitHub: #6168 (comment) You are receiving this because you authored the thread. Message ID: **@.***>

Ultimately, I agree; however, troubleshooting to see if they can be interacted with at all can be useful.

--

Reply to this email directly or view it on GitHub:

https://github.com/Mudlet/Mudlet/issues/6168#issuecomment-1190373958

You are receiving this because you authored the thread.

Message ID: @.***>