Hi there,
I am working on making our application that is made with the JS API keyboard accessible. I see that there are some built in keyboard commands for adding vertices when sketching but I noticed some issues with it.
To replicate:
Are there any plans to make this fully keyboard accessible?
Solved! Go to Solution.
@Anonymous User ,
This is a bug that was introduced at version 4.21. This was just unfortunately not caught earlier, so I apologize for that. I have logged an internal bug, so hope we can get this resolved in our next release. If you change the version to version 4.20 in the sandbox link you provided, you can see it working.
Thanks,
Jose
@Anonymous User Steps 3-4 seem to be as-designed in the sandbox app. Perhaps there are additional properties to set keyboard navigation that works alongside the sketch tools.
@Anonymous User ,
This is a bug that was introduced at version 4.21. This was just unfortunately not caught earlier, so I apologize for that. I have logged an internal bug, so hope we can get this resolved in our next release. If you change the version to version 4.20 in the sandbox link you provided, you can see it working.
Thanks,
Jose
Thanks Jose, that's great to hear
@JoseBanuelos Quick follow up question - do you know if there are plans to make editing more keyboard accessible as well, e.g. being able to select vertices and move them etc?
@Anonymous User ,
This is a great question. Unfortunately, selecting and updating vertices is not very keyboard accessible with our API at the moment. This is good feedback for us to to explore this avenue further. Do you happen to have a use case for this enhancement request that you could share with us? Are you developing an application that would really benefit from this? I understand the accessibility need, we just like to also have real life scenarios to tie to these enhancement requests.
Appreciate your feedback,
Jose
@JoseBanuelos thanks for the update! We are creating a product that we want to meet accessibility guidelines so that anyone can use and benefit it. I am currently exploring building my own keyboard shortcuts but it would be even better if this was available out of the box.
Hi @JoseBanuelos just wondering if you knew if this bug was going to be resolved in 4.26?
Thanks,
Alex
This has been resolved in 4.27!