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 makes accessibility part of the Basker baseline rather than leaving every detail to each theme. The right markup structure is in place before a theme developer or editor opens a block. These defaults reduce repeated remedial work, but teams should still test each page and theme with assistive technology.