Replies: 2 comments
-
I am still immersing myself in the repository and ARIA guidelines, but here is a possible example with more actions, based on combining code from #10 with the initial key-access-test commit: https://github.com/christineiym/OS-DPI/tree/access/thinking/method-key-access-test |
Beta Was this translation helpful? Give feedback.
0 replies
-
Interesting discussion here: mar10/fancytree#709
…On Tue, Aug 23, 2022 at 11:04 AM Christine Mendoza ***@***.***> wrote:
I am still immersing myself in the repository and ARIA guidelines, but
here is a possible example with more actions, based on combining code from
#10 <#10> with the initial
key-access-test commit:
https://github.com/christineiym/OS-DPI/tree/access/thinking/method-key-access-test
It does not completely work, as I need to allow input normally controlled
with up/down arrows to be entered/edited, but it seems to work well with
the keyboard focus control bindings.
—
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABQK7CZDUY2LO7VHBFQQQDV2TSA3ANCNFSM57IMDRDA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm just trying ideas. Check it out here: https://github.com/gbishop/OS-DPI/tree/access/thinking/key-access-test.
It only supports Tab for moving between components, F2 for entering and exiting a component and arrows for moving inside a component.
It would be neat if the actions could be broken down more. One function per is not that interesting...
Beta Was this translation helpful? Give feedback.
All reactions