Accessibility issue with screen readers (all elements read as clickable)

Need help
1

Hello Bubble team,

I am currently working on a Bubble application and started testing its accessibility using screen readers such as NVDA and VoiceOver.

I noticed an issue that significantly impacts usability: most elements on the page are being announced as “clickable” by the screen reader, even when they are not interactive.

This behavior makes navigation very confusing for visually impaired users, as it becomes difficult to distinguish between actual interactive elements (buttons, links) and static content.

I would like to better understand:

  • How does Bubble define semantic HTML structure for elements?

  • Is there a way to control accessibility attributes such as ARIA roles, labels, or properties within Bubble?

  • Are there recommended best practices to improve accessibility in Bubble apps?

  • Are there known limitations regarding screen reader support?

If needed, I can provide a test page or further details.

2

Have you tried marking the text or button as ‘this element isn’t clickable’? Does that help at all? :thinking:

3

Yes, I have already tried applying it using HTML and even configured it in the editor, but screen readers still insist on reading the elements as clickable.

1 Like
4

Did you get any response on this from bubble?