Page 1 of 1
Clicking on a flashing arrow
Posted: Fri Sep 20, 2024 5:08 am
by DMgooner
Is there a way to click on a tab that's in a tease without having to use my mouse? Like when the tease commands you to do something and to let the program know that you've done it you must left-click on a box that says you did. Is there a way to just hit a key on your keyboard, rather than left clicking on it with your mouse?
Re: Clicking on a flashing arrow
Posted: Fri Sep 20, 2024 8:04 am
by Thamrill
DMgooner wrote: Fri Sep 20, 2024 5:08 am
Is there a way to click on a tab that's in a tease without having to use my mouse? Like when the tease commands you to do something and to let the program know that you've done it you must left-click on a box that says you did. Is there a way to just hit a key on your keyboard, rather than left clicking on it with your mouse?
If you mean advance text with the small circle and arrow, then pressing the spacebar should work
Re: Clicking on a flashing arrow
Posted: Fri Sep 20, 2024 11:40 pm
by Evals
It's not possible to navigate to those buttons via keyboard controls and it's actually a major accessibility issue for anybody using an assistive device.
The problem is that the "button" is implemented as a <div> HTML element, and is not a native <input type="button"> or <button> element. It should be a very simple fix for Seraph0x to swap out the element with the click listener on it. He could either replace it with one of the two recommended elements, or decorate it with the appropriate attributes to make it behave more like a native button (i.e. <div tabindex="0" role="button">).
Re: Clicking on a flashing arrow
Posted: Mon Sep 23, 2024 12:58 pm
by indyc
Evals wrote: Fri Sep 20, 2024 11:40 pm
It's not possible to navigate to those buttons via keyboard controls and it's actually a major accessibility issue for anybody using an assistive device.
The problem is that the "button" is implemented as a <div> HTML element, and is not a native <input type="button"> or <button> element. It should be a very simple fix for Seraph0x to swap out the element with the click listener on it. He could either replace it with one of the two recommended elements, or decorate it with the appropriate attributes to make it behave more like a native button (i.e. <div tabindex="0" role="button">).
This would be HUGE for Keystroke if ever implemented. Here's hoping!