the accelStepper library drives the acceleration based on the number of steps in a movement.
if you ask the library to move 1000 steps Clockwise and provide some max speed and acceleration value, the library can calculate the acceleration phase and also decide at what steps it needs to start decelerating to arrive at destination with a close to null speed.
In your use case scenario, the number of steps is unknown upfront as you don't know when the user will release de button.
For the acceleration part, you could provide a very far target and the ramp up will happen but when you release the button you need to define what you want to happen - how long (how many steps) should be the slow down phase based on the current speed. You could ask the library what is the current position and speed and set a new target position ( moveTo()) which will recalculate the speed for the next step.
you might benefit from studying state machines. Here is a small introduction to the topic: Yet another Finite State Machine introduction
I'd suggest you use one of the numerous button library for the buttons, such as Button in easyRun or OneButton or Toggle or EasyButton or Bounce2, ... (Toggle would be "easy")