Hi there, @user19339 
First of all, a huge thank you for taking the time to share such detailed feedback and for suggesting possible solutions. We really appreciate the effort you put into testing the widgets and documenting your ideas!
One quick note regarding the CSS adjustments: the reason custom CSS may stop working after widget updates is that temporary classes are being used. For more reliable customizations, we recommend using stable classes, as they are designed to remain consistent across updates. You can find more details about stable classes and CSS customization here: Guide to CSS Codes
Regarding your accessibility suggestions — I’ve discussed them with our developers, and they’ve created tasks to implement the 1st, 2nd, and 4th ideas. We’ll keep you updated as soon as there are any changes available 
The 3rd suggestion requires a more complex product-level update, so it will take more time to explore. For now, the recommended workaround is to use custom CSS to address this case. We’ll also keep it in mind as a potential global improvement in the future.
Thanks again for helping us make the widgets more accessible! Your feedback is really valuable 