WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 5 years ago

#33028 closed defect (bug) (wontfix)

Skip to content: avoid page jump

Reported by: afercia Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.2
Component: Administration Keywords: has-patch
Focuses: ui, accessibility Cc:

Description

Long standing issue, especially for keyboard users: when following the "Skip to main content" link, focus is moved to the #wpbody-content div and in admin screens with a long content, this causes the page to scroll in your browser. See in the screenshot below:

  1. start tabbing in a screen with some long content
  2. the skip to main content link appears, press Enter
  3. focus is moved and the page is scrolled
  4. tab again and the page scrolls again to bring into view the "Help" tab button (there's some JavaScript for this to happen)

https://cldup.com/0sB-GYp4kT.png

Every time keyboard users activate the Skip to main content link, they see this down/up scrolling. I've read the related tickets and to me it's clear why it's done this way, no objections. As a keen keyboard user I find this jump a bit annoying :) and I guess all keyboard users share the same feeling. Yes it's a minor thing, I'd just propose to try to find a simple way (no JavaScript) to improve a bit the users experience.

Attachments (1)

33028.patch (1.1 KB) - added by afercia 5 years ago.

Download all attachments as: .zip

Change History (5)

@afercia
5 years ago

#1 @afercia
5 years ago

  • Keywords has-patch added

In the proposed patch, a simple CSS way to avoid the down/up scroll jump. Tested in latest Chrome, Firefox, IE 8, and Chrome emulator for the responsive view. Should be tested in modern IE and in edge case scenarios, i.e. plugins that modify the admin bar.

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


5 years ago

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


5 years ago

#4 @afercia
5 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Discussed a bit in today's accessibility team chat on Slack and decided to close as wontfix. It's a really minor visual glitch and doesn't impact accessibility.

Note: See TracTickets for help on using tickets.