I am not at all fussy about case, but technically Denise is uppercase (as it is my Wallet Name) while all my other usernames are lowercase. :)
I'm glad that the access compromise works for you! Please do always feel free to let us know if you notice an accessibility need not being met; I can't promise we'll always be able to make a specific change (between dueling access needs, "is it technically impossible", "is it technically possible but would require a lot of work that we don't have the time/resources to do right now", etc) but we'll always give it a good hard think and see what we can come up with, and we are Very Cross if people are rude in comments to official journals to someone just for asking about access needs. (And I'm always happy to explain the reasoning behind a particular decision or the reason why we can't make a specific change, if the answer is "sorry, can't do that right now", to see if we can get something that will work after a few back-and-forth tries.)
Totally understood about the draft saving thing, yes! Just to be absolutely on the safe side: I will caution that the autosave on the old update page is a "best effort" thing, done in your own browser and not on the server side, that works in 95% of cases but breaks terribly in the other 5%. (It's why we haven't just implemented that version of autosave in the new update page yet, since when it goes wrong, it really goes wrong.) If your current browser supports extensions, you may want to install an extension like Lazarus that will autosave the information that you put in forms like the update page so it can be restored in case of a crash, just for more peace of mind.
Re: accessibility feedback (does this go here?)
I'm glad that the access compromise works for you! Please do always feel free to let us know if you notice an accessibility need not being met; I can't promise we'll always be able to make a specific change (between dueling access needs, "is it technically impossible", "is it technically possible but would require a lot of work that we don't have the time/resources to do right now", etc) but we'll always give it a good hard think and see what we can come up with, and we are Very Cross if people are rude in comments to official journals to someone just for asking about access needs. (And I'm always happy to explain the reasoning behind a particular decision or the reason why we can't make a specific change, if the answer is "sorry, can't do that right now", to see if we can get something that will work after a few back-and-forth tries.)
Totally understood about the draft saving thing, yes! Just to be absolutely on the safe side: I will caution that the autosave on the old update page is a "best effort" thing, done in your own browser and not on the server side, that works in 95% of cases but breaks terribly in the other 5%. (It's why we haven't just implemented that version of autosave in the new update page yet, since when it goes wrong, it really goes wrong.) If your current browser supports extensions, you may want to install an extension like Lazarus that will autosave the information that you put in forms like the update page so it can be restored in case of a crash, just for more peace of mind.