[wp-trac] [WordPress Trac] #51580: Application Passwords: Accessibility Improvements

WordPress Trac noreply at wordpress.org
Fri Oct 30 14:21:40 UTC 2020


#51580: Application Passwords: Accessibility Improvements
------------------------------------+--------------------------------------
 Reporter:  georgestephanis         |       Owner:  georgestephanis
     Type:  defect (bug)            |      Status:  reopened
 Priority:  normal                  |   Milestone:  5.6
Component:  Login and Registration  |     Version:  trunk
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch               |     Focuses:  accessibility, rest-api
------------------------------------+--------------------------------------
Changes (by sabernhardt):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 [https://wordpress.slack.com/archives/C02RP4X03/p1603833439143500?thread_ts=1602742787.172500&cid=C02RP4X03
 more discussion on Slack:]

 alexstine
 > Additional feedback:
 > - Change "Add New" to "Add New Application Password".
 > - The notice is read multiple times, not sure how to fix this. Maybe
 remove role="alert" if focus is being placed on the notice?
 > - I'd still like aria-required="true". This will not effect the main
 form, it only speaks required to screen readers unlike the required HTML
 attribute which will stop the processing unless the field is filled out.
 In a perfect world, change password and application passwords would be on
 sub pages of profile page, it would be much better for accessibility. One
 page doesn't necessarily fit all.

 timothybjacobs
 > Thanks for the additional testing! I can make those changes. Do you
 think it will be clear to screen reader users that the aria-required is
 only applying when creating an app password?

 alexstine
 > I think it would be, but maybe additional feedback from accessibility
 team couldn't hurt. I am of the belief that self-contained forms should
 have these fields indicated as required, however, as I said above, it is
 hard to communicate sub-forms inside a main form. It doesn't make a lot of
 sense to a screen reader user who must explore a bit at a time like it
 would to someone with vision who gets a complete overview of the page.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51580#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list