Voting starts in March for the Drupal Association Board election.
Beta phase evaluation
|Issue category||Task because this is adding accessiblity functionality for accessiblity purposes.|
|Issue priority||Major because it improves the accessibility of the login page, which for many will be the initial experience with Drupal|
|Prioritized changes||The main goal of this accessibility|
"password matches" and "password strength" accessibility could be better. Much of the problem is that to screen readers, the content is not presented in a consistent logical fashion. Furthermore, changes to the page (password strength & password confirmation) are not passed along to the screen reader effectively via ARIA.
"password matches" indicator (label followed up by the value) should be placed after the "confirm password" field, not before.
In addition to this (
I don't know if this is possible this is possible) it would be great that when a user is typing into the "confirm password" field he/she could ear when password and "confirm password" field matches, as it happens for value changes of the "password strength" indicator.
These are really important for drupal accessibility!
Find out if the improvements are possible.
|Task||Novice task?||Contributor instructions||Complete?|
|Update the issue summary||Instructions||yes|
|Update the issue summary noting if allowed during the beta||Instructions|
|Add automated tests||Instructions||we need more|
|Manually test the patch||Novice||Instructions|
|Add steps to reproduce the issue||Novice||Instructions|
|Embed before and after screenshots in the issue summary||Novice||Instructions|
|Review patch to ensure that it fixes the issue, stays within scope, is properly documented, and follows coding standards||Instructions|
User interface changes
None to sighted users.