Forum Documentation Showcase Pricing Learn more

Bubble Websites and Accessibility

Is it possible to create a Bubble website that conforms to accessibility standards? Has anyone had that as a requirement for any of their projects?

My sense is that Bubble is seen primarily as a tool for entrepreneurs and start-ups, but as it grows in popularity, its appeal will broaden, and its potential applications [and website audiences] will become more diverse; and accessibility might become more of an issue.

Generating semantic mark-up is not currently one of Bubble’s strongest suits, although I have noticed that for some elements, the HTML tag can be specified in the property editor; but that’s actually identified as an SEO feature.

Anyway, just curious if others have given this any thought, and I’d be interested to know if it’s even on @Bubble’s radar.

1 Like

That’s a good question. I’m really curious about this too, especially as it pertains to inputs (and labels and ESPECIALLY tabbing index). I haven’t seen anything about it and don’t necessarily see how it could work necessarily given the way pages are assembled, but +1 from me.

It is on our list of things to investigate and improve on, but not for the near future, unfortunately.

We’ll keep you guys updated on this thread.

1 Like

Great to know it’s on the radar, @emmanuel. I’d be more proactive in approaching local gov’t orgs and businesses if accessibility wasn’t an issue. (Gotta fund my own entrepreneurial endeavors somehow. :wink:)

Thanks for letting us know!

I have to agree with you on the inputs and definitely the tabbing index. I’ve read through all the threads regarding the tab index and while testing different options people tried, I actually found two bugs which I reported. The tab index is a very important issue to resolve and a manual override is needed.

1 Like

You can use Javascript to update the tab order. Just FYI in case it’s worth the complexity.

1 Like

@sridharan.s - Yeah, I’ve definitely thought about that, but it’s a pretty sloppy process currently to make that work on a page that has complex forms or dynamic forms. Ultimately, it doesn’t actually address the accessibility/screen-readability of the page, but it can work. For simpler forms I’ve found that by curating how forms and their parent groups are themselves grouped can produce decent results for tab-index, but definitely not a long-term solution.

Just circling back on this as I’m curious where this is on priority list now that we’re 10 months further down the road.

Being able to conform to accessibility standards – even just being able to label inputs – would be very helpful.