Instructions on how to create and use a bookmark can help as far as the domain/getting to log in goes. I know nobody RTFMs but if they've got instructions they can follow for that, they'll only need to read it once (hopefully). Hopefully, that will reduce the level of frustration before they try to log in.
Is your product a simple TODO list? Is it a health diary with loads of sensitive information? Is it for storing nuclear codes? Is this something users typically use on shared computers? On their phones? When you consider whether or not some of the other commenters' suggestions for reducing complexity of authc and potentially account recovery are reasonable, you need to keep that context in mind. It's hard to make decent suggestions without that context, imo.
Check WCAG's recommendations around accessibility. Start with cognitive and vision, and make sure to check out sections around designing and interacting with forms, but make sure to have a browse around broadly.
The UK government's style guides have some thoughtful advice around usability and accessibility. [0][1]
Is your product a simple TODO list? Is it a health diary with loads of sensitive information? Is it for storing nuclear codes? Is this something users typically use on shared computers? On their phones? When you consider whether or not some of the other commenters' suggestions for reducing complexity of authc and potentially account recovery are reasonable, you need to keep that context in mind. It's hard to make decent suggestions without that context, imo.
Check WCAG's recommendations around accessibility. Start with cognitive and vision, and make sure to check out sections around designing and interacting with forms, but make sure to have a browse around broadly.
The UK government's style guides have some thoughtful advice around usability and accessibility. [0][1]
[0]: https://www.gov.uk/guidance/style-guide [1]: https://design-system.service.gov.uk/