(DSNCORE-1335) Problem with Text3

[yceballost]

https://jira.tid.es/browse/DSNCORE-1335

• Update specs
• Design documentation
• Add to mobile library
• Add to desktop library
• Add to UI Kit
• Android ticket
• iOS ticket
• Web ticket

[aweell]

In the ticket the request is to allow tabIndex in text elements, after reading the ticket I'm not able to understand how this property will solve the problem.

TabIndex modifies the tab order, but a text element has no tab order since is interactive.

https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindex#accessibility_concerns

If all the text should be read in one swipe i suggest to use the aria label of the link and hide the text to avoid repetition:

https://mistica-web.vercel.app/playroom/#?code=N4Igxg9gJgpiBcIA8BlALgQzAawAQGcAHLGAXmACYAWAXwD4AdAO11yQBUYAPNAZlwC2MKAEsArgMYtWudiJhMY%2BXFDFQM%2BAPxtOPADIimeABYAnGADNyDEAGIb9AAqGwxjLgwBHMSKQB6XTQDIylWf0DeKWYwiMFhcUlomQ5uNA9TEQwAWmMRKFgmOjkFJRU1DU1w1NDkwOCTcytgG3sQGnTMrIAbDAAjGC7rEGLFZVV1LVxnJld3Lx8HGpkplzcPbxEksIDU%2Bpqqnkjmf3QsbCkQABoQNGMYIXwEAG0QAFkIADcRfExTEABda4Adzyt0e8CeAHYAGwADkuAEZeHD-jQgA

[AnaMontes11]

I agree that tabIndex doesn’t seem like the right solution in this case, as you mentioned, since the text is not interactive.

Regarding your suggestion to use aria-label on the link to unify the reading and hide the redundant text, I think it's a good alternative to avoid repetition. However, I have a question: if we combine the text and the link into a single aria-label, could this affect the experience for users who rely on touch navigation? For example, visually the text and the link appear as separate elements, but functionally they would be treated as one. Could this cause confusion?

One possible alternative could be using aria-labelledby. This would allow them to remain visually and functionally separate, but the screen reader would announce both elements together.

What do you think?