Accessibility: which builder output passes an audit

Accessibility: which builder output passes an audit
Rarely reviewed, increasingly a legal issue. The question: does the builder emit semantic, keyboard-navigable markup by default?

Gutenberg leans on core block semantics and generally does well. Bricks lets you set the HTML tag per element, so a card can be a real article element. Elementor improved with its accessibility-focused releases but still wraps interactive widgets in generic divs that need ARIA patching. Older Divi/WPBakery output is div-heavy and weak on focus states.

Pros (Bricks / Gutenberg):
— Control over semantic tags, cleaner heading order
Cons:
— You still own ARIA on custom interactive widgets
Cons (legacy builders):
— Generic div wrappers, poor keyboard focus by default

Verdict: semantic-tag control is the differentiator — Bricks and Gutenberg lead.

Best for: sites with WCAG/ADA obligations where div-soup output is a liability.