WordPress.org

Make WordPress Core

Opened 14 months ago

Last modified 5 months ago

#40470 new defect (bug)

WordPress installation steps - button press differences

Reported by: xavortm Owned by:
Milestone: 5.0 Priority: normal
Severity: normal Version:
Component: Upgrade/Install Keywords: has-patch has-screenshots
Focuses: ui, accessibility Cc:

Description

Something that has been bothering me for every single WP install I do - the first two buttons in the step - Begin WP Installation, Input settings and Update wp-config.php are happening by typing, pressing tab and space to click the "next" buttons, but once I get to the "All done, now you can login" screen I can't use space to go next.

This is closely related to #26504 , as well as some older tickets that were closed in favor of the mentioned one, but since the login screen is not discussed there but the inner dashboard, I thought that this can be separated in a new ticket. (maybe "good first ticket"?)

http://i.imgur.com/VSzBXvC.png

As mentioned above, to replicate: Clone WP core in new folder and install it through the browser, follow all steps and go to the next by pressing "space" on the final action buttons. Only the last step doesn't work with space but with enter instead.

Attachments (5)

40470.patch (939 bytes) - added by menakas 13 months ago.
Removed button classes for Log In - 2 cases - Already installed & just installed
NewInstallBefore.png (17.1 KB) - added by menakas 13 months ago.
Before pic for New installation
NewInstallAfter.png (17.0 KB) - added by menakas 13 months ago.
After pic for New installation
AlreadyInstallBefore.png (13.5 KB) - added by menakas 13 months ago.
Before pic for Existing installation
AlreadyInstallAfter.png (13.2 KB) - added by menakas 13 months ago.
After pic for Existing installation

Download all attachments as: .zip

Change History (14)

#1 @swissspidy
14 months ago

  • Component changed from General to Upgrade/Install
  • Keywords needs-patch added
  • Version trunk deleted

#2 @afercia
14 months ago

That's because it's actually a link that looks like a button: <a href="<?php echo esc_url( wp_login_url() ); ?>" class="button button-large"><?php _e( 'Log In' ); ?></a>

There are a lot of such links in the admin, also in the context of the installation process, e.g.: <a href="<?php echo $install; ?>" class="button button-large"><?php _e( 'Run the install' ); ?></a>

Links can be activated pressing Enter, while real buttons can be activated pressing either Enter or Spacebar, that's native behaviour in all browsers. Regardless, I share the concern about potential confusion resulting for the design, as basically the current styling makes controls that behave differently, look the same.

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


14 months ago

#4 @rianrietveld
14 months ago

  • Milestone changed from Awaiting Review to Future Release

Discussed this in the wpa11y meeting:

  • Using a link is correct, but the design should be changed.
  • "Log in" one in the final step could be changed to look like a link. It's the final step. No need to be consistent.
  • There are no form fields on the page, so there's no reason to include any implication that this is "form-like".

@menakas
13 months ago

Removed button classes for Log In - 2 cases - Already installed & just installed

#6 @menakas
13 months ago

  • Keywords has-patch needs-unit-tests added; needs-patch removed

#7 @swissspidy
13 months ago

  • Keywords needs-screenshots added; needs-unit-tests removed

This isn't really something we do/should have unit tests for.

However, screenshots highlighting before / after state would be nice.

@menakas
13 months ago

Before pic for New installation

@menakas
13 months ago

After pic for New installation

@menakas
13 months ago

Before pic for Existing installation

@menakas
13 months ago

After pic for Existing installation

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


5 months ago

#9 @afercia
5 months ago

  • Focuses ui added
  • Keywords has-screenshots added; needs-screenshots removed
  • Milestone changed from Future Release to 5.0
Note: See TracTickets for help on using tickets.