What's ridiculous with the accessible keyboard and the generic Windows login is while it's only a couple of clicks to get the accessible keyboard up and running so you can actually login, it then doesn't remember to keep it up once you're logged in. Possibly because the accessible keyboard for login and the accessible keyboard for in a session seem to be different pieces of code - the keyboards are similar, but not identical. Nor is the in-session keyboard one of the things Windows now preserves across sessions.