Obviously, it is not 508-compliant to acquire an input area of type " password. " The key reason why
God Bless The usa… land that MY PARTNER AND I laugh at.
Certainly, I don’t realize that much about the main 508 thing given that I’m Canadian and since it may not be a big matter yet here, nonetheless I can’t view " password" becoming non-508-compliant. http: //www. section508. gov does it right there in their website (although they also have a ridiculous Javascript alert field that pops up every time you click with an external website link. )
The encryption of the actual visible characters inhibits readers from examining them back, and that is considered a problem Needless to say, I would think it might be MORE of a challenge for a reader that they are shouting out your password in a big office, so I don’t really understand why from a stability perspective. I think that readers need to be spec’d to require reading the quantity of characters in your pwd field alternatively. Would make additional sense, and would give a similar usability that the remaining of us possess with pwd fields.
Was hoping to create the WDF webpage 508-compliant, but prop that, then… there’s compliance and you will find usability, as a person say.