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?
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.
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 (←↑→↓)