Thanks for the heads-up, Ralph.
JAWS and NVDA will read out the values fine, and like VoiceOver they'll offer you to edit-type-in-text. I'd call myself an Orca beginner: while when there are no labels and just values, I hear the values first and then "text" (Orca tells you what kind of input box it is when you focus on it) so I could start typing fine, but I didn't realise the old value stuff was still in there. Maybe a more regular Orca user would know (since when there is a label and no value things are read out slightly differently). So in my Change Password form, I could have potentially entered something like
aw3s0mep455w0rdNew Password (again)
and then I suppose I'd get an error saying that wasn't my old password, and my new passwords don't match.
Besides, any input type=passwords can't use values at all: every screen reader I've ever used reads out "star" or "asterisk", so I guess you'd be asking people to guess that the "star star star star star star star star star star star" input must be asking for a password... or not use that input type (it has been argued they are not great for usability, tho without that input type, if you're not using headphones everyone can hear your password lawlz).
Checkboxes and radio buttons shouldn't rely on values... should have labels.
Now if I bothered to go back and read the inputs, sure, I'd notice right away there was text in there. But why should I have to? There's a reason readers read back what you type to you.
Be aware that any reset button resets the value of the inputs that's in the HTML, not blank. Which in this case would be your values. If your back-ender cares.
Title is often an option if you're ONLY thinking about screen readers, but without anything else that's super-obviously a label for everyone else, I wouldn't use it (no mouse, no title; not accessible).