[wp-trac] [WordPress Trac] #43412: Comments: row action links and forms accessibility improvements
WordPress Trac
noreply at wordpress.org
Mon Jan 7 18:46:03 UTC 2019
#43412: Comments: row action links and forms accessibility improvements
-------------------------------------+-------------------------------------
Reporter: afercia | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: 5.1
Component: Comments | Version:
Severity: normal | Resolution:
Keywords: semantic-buttons has- | Focuses: accessibility,
screenshots needs-refresh has- | javascript
patch ui-feedback ux-feedback |
-------------------------------------+-------------------------------------
Comment (by afercia):
Re: the buttons, worth reminding placing related UI controls at the
opposite sides of the screen is a huge accessibility barrier for low
vision users. Person with a limited viewing field are able to view just a
small portion of the screen at any time. Sometimes they use screen
magnifiers at a very high zoom level. A button at the opposite side of the
screen is basically invisible.
Also, worth reminding the discussion and design feedback given on the
tracking ticket for the proximity of controls:
https://core.trac.wordpress.org/ticket/40822#comment:9
> Based on https://www.lukew.com/ff/entry.asp?571, I think we should:
> - Have the primary action (like update, etc.) on the left, as a primary
button.
> - If relevant, list secondary actions immediately to the right of the
primary action, as secondary buttons.
> - List all negative action (cancel, delete) next, as links.
>
> In most cases, the actions should be left aligned, to line up with the
forms. This would happen on Settings, bulk edit screens, edit term
screens, etc.
>
> In the case of things like the theme modal, actions should remain
centered (since the content within the modal doesn't follow the same left-
aligned linear path as forms do).
These are the patterns I'd strongly recommend for better accessibility. If
the concern is about avoiding clicks on the wrong button, then increasing
the clickable area of the buttons would probably be a better option, as
for example some mobile operating systems do (see screenshot below).
--
Ticket URL: <https://core.trac.wordpress.org/ticket/43412#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list