No focus with internal page linking with the screen reader

Created on 17 August 2021, over 3 years ago
Updated 30 March 2024, 9 months ago

Problem/Motivation

The accessibility of the internal links or the read more link is not optimal. When you click on the link, you have no focus on the new page with the screen reader. It would be better if the focus were automatically on the title field. This way, screen reader users do not have to navigate around the page.

Steps to reproduce

Download a screen reader, e.g. nvda (free). Run NVDA and navigate to the website and tab through the page. Click on an internal link and then click Tab on the new page. Now you see that you have to press Tab a few times until you reach the content.

Proposed resolution

It would be better to have the title field in focus first on every page, so that you can read the page content directly.

πŸ› Bug report
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component
BaseΒ  β†’

Last updated 1 day ago

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡©πŸ‡ͺGermany rkoller NΓΌrnberg, Germany

    This issue was raised as the issue of the day in the #bugsmash channel yesterday. At first thank you for raising the issue @zeroplexer! I've read through the issues summary but a few details are not clear to me. Could you perhaps elaborate what you are exactly referring to and what your point of reference is, meaning in which theme you've noticed those issues? If the issue is just about saving the amount of tab key presses until one reaches the main content as mentioned in the steps to reproduce section then Claro as well as Olivero already provide that kind functionality - on the first tab press the user gets the Skip to main content link. On the other hand you refer to " have the title field in focus" in the proposed resolution section, which might be a more reasonable request. if you take for example node creation pages there is no focus at all after the initial page load and it might be helpful and speed up the interaction if the first field in the form gets into focus which is the title field most of the time (at least in the context of content types). a similar pattern is recommended for dialog modals where it is a good practice in the a11y context to either bring the close or the first input element into focus. If you could clarify your points that would be fantastic. I'll change the status to Postponed (Maintainer needs more information) aka PMNMI for now based on the recommendation of @quiteone on the thread (i am not that familiar with the process). after updating the issue summary, clarifying the points in question, the issue can be set back to active again. thank you!

  • πŸ‡³πŸ‡ΏNew Zealand quietone

    @rkoller, thank you!

    I am also adding that if we do not have the information needed to work on this issue it may be closed in 3 months.

  • Status changed to Closed: cannot reproduce about 1 month ago
  • πŸ‡¦πŸ‡ΊAustralia griffynh Sydney

    Closing, no update for > 3 months.

    Please reopen this if it is relevant in the future.

Production build 0.71.5 2024