-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to move AMP story block using keyboard #3325
Comments
It's not trivial, but here's a great guide to best practice expected behaviour. |
Previously suggested in #2454. Will close it as a duplicate. |
As a talking point, I have created a WIP pull request in #3400. It is still discovery stages at this point, but it is a workable solution. |
Screencast of the tabbing and arrows in use. |
@MackenzieHartung @pbakaus A lot of work and discussion has taken place on #3400 . This ticket is not just a simple bug, it has lots of moving parts and is a fundamental change on how blocks are moved. This PR will effect other on going such as #3060 #3311 #3416 . This ticket needs to go through the new process, so we can capture all requirements |
Hey @jasti I only added the one AC for now. Based on @spacedmonkey's comments I'm not sure if that is too high level and if more is needed. I will wait for you to move this to the IB column... |
In #3400 I left a comment for a new feature that could be its own AC:
So just arrow keys: move by single pixels |
Bug Description
When using keyboard navigation, users are unable to move movable blocks in the AMP Story interface. For accessible reasons, this should be possible.
Expected Behaviour
Steps to reproduce
Screenshots
Additional context
Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
Implementation brief
QA testing instructions
Demo
Changelog entry
The text was updated successfully, but these errors were encountered: