Improved Accessibility Defaults for Builder Sites

Accessibility used to depend on per-theme work. Public sites now get stronger accessibility defaults across landmarks, ARIA labels, and carousel announcements, so the baseline for any Website Builder page is raised without requiring custom theme work to achieve it.

What improved

Builder-produced pages are easier for screen-reader users to navigate. Interactive components communicate their state more clearly. Carousel elements now announce transitions correctly to assistive technologies.

Accessibility as a Basker contract

This shifts accessibility from being a per-theme responsibility to part of the Basker contract. The right markup structure is in place before a theme developer or editor opens a block, so teams do not need to audit accessibility separately for every new page they build.