tabindex ＝“ 0”的替代方案是什么？是否存在可以按顺序浏览页面内容而又不会丢失元素的内容？ [英] What alternative to tabindex="0" exists that makes page content browsable in sequential order without missing elements?

问题描述

我有一个包含几个HTML元素的页面，当用户使用Tab键和屏幕阅读器从上到下浏览页面时，这些元素将被忽略和跳过。通过将属性tabindex = 0添加到包含需要屏幕阅读器读取的文本的div中，可以解决此问题。一些评论说这不是正确的方法。

I have a page that has several HTML elements, that are ignored and skipped when the user is navigating the page from top to bottom using tab key and a screen reader. This is something that I was able to fix by adding the attribute tabindex="0" to the divs that contain the text that needs to be read by the screen reader. some comments say that it is not the right approach to make this. Which is the recommended alternative?

我在android上使用话语提示来导航页面，而在Jaws和Narrator上，它们都具有相同的行为，元素没有tabindex被忽略，它直接跳转到< a> 元素，跳过< a> 周围的标题和文本标记。

I´m using Talkback on android to navigate the page and on windows both Jaws and Narrator, they all have the same behaviour, elements without tabindex are ignored, it jumps straight to <a> elements skipping the titles and texto that surrounds the <a> tag.

推荐答案

具有屏幕阅读器的用户使用 tab 键转到可激活的元素。对于标准元素（例如文本），他们可以使用其他导航快捷方式，具体取决于其导航模式（浏览或焦点模式），屏幕阅读器以及自己的首选项，例如箭头（← ↑ → ↓）

Users with screenreaders use the tab key to go to activable elements. For standard elements (like text) they can use other navigation shortcuts which depends on their navigation mode (browse or focus mode), their screenreader, and their own preferences, for instance arrows (←↑→↓)

这篇关于tabindex ＝“ 0”的替代方案是什么？是否存在可以按顺序浏览页面内容而又不会丢失元素的内容？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！