nextcloud / nextcloud/server

[Bug]: More "Recently edited" files are accessible via keyboard than by mouse

Open
#34,088 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop accessibility feature: accessibility feature: files technical debt
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
  • This is a bug, not a question or a configuration/webserver/proxy issue.
  • This issue is not already reported on Github (I've searched it).
  • Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
  • Nextcloud Server is running on 64bit capable CPU, PHP and OS.
  • I agree to follow Nextcloud's Code of Conduct.
Bug description

When you are tabbing through Files, on reaching the "Recently edited" files, only 3 files are visible and accessible via mouse but there more files (at least 4 more in my case) that can be reached by tabbing with the keyboard

Steps to reproduce
  1. Open Files
  2. Tab through main content until "Recently edited" files are reached
  3. Keep tabbing
  4. Even though there are only 3 files visible, on tabbing you find that there are more files below but hidden
    image
Expected behavior

After the 3 visible files are focused, the focus shifts to the checkbox on the file list header row.

Installation method

No response

Operating system

No response

PHP engine version

No response

Web server

No response

Database engine version

No response

Is this bug present after an update or on a fresh install?

No response

Are you using the Nextcloud Server Encryption module?

No response

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

No response

List of activated Apps
/
Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named; first reproduce the issue in Files by tabbing through the "Recently edited" files and compare the visible items with the focus order. Trace the Files UI responsible for that section, and consider the issue done when focus moves from the three visible files to the file-list header checkbox without reaching hidden files.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
accessibility, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.