Equalize Digital released a new report on page builder concerns around accessibility.
You can get the full data download here which features Bricks 2.0
There were several issues that were identified in the report. I’d like to mention two with a specific request for these two:
- Apparently the testers used the default page templates that are magically built into Bricks. They serve a purpose that lessens the “what is going on” for new users hitting those areas and act as placeholders, but either they should have a note in them that says “This is a placeholder”, they should be removed, or they should be made more real.
- In the builder there are old elements that “experts never use anymore” that the testers used. Things like “Tabs” vs “Nestable Tabs” and maybe the default Posts element. The old non-nestable versions were used and found to have accessibility issues. Perhaps those old versions can be hidden from the builder using the Elements Manager.
A number of people commented that “experts know not to use those” but this test shows how easy it is for people to assume they are there to be used. My feature request is, if something really isn’t meant to be used then please remove it, otherwise fix it.
5 Likes
This. Time to deprecate a lot of the early zombie elements and fix up the rest of the stuff.
No need for stuff the posts/products elements or non-nested accordion/slider/tabs to exist.
Every effort should be made to push people towards building their own looped elements, particularly with components coming out of beta.
1 Like
I agree with @David here - let’s either remove or make them legacy and disabled by default (so as not to cause issues with older sites that may still be using them).
Alternatively, for the legacy elements, consider adding a conversion option in the settings, similar to some of the existing conversion tools that autodetect the existence of legacy elements and update them.
2 Likes