Performance & accessibility

Question 1

What are Core Web Vitals and why do they matter?

Accepted Answer

LCP, INP and CLS measure how fast, responsive and stable a page feels. Google uses them in ranking and visitors abandon slow pages. Blanca's Builder optimises for all three by default.

Question 2

How do I improve Largest Contentful Paint (LCP)?

Accepted Answer

Serve hero images as AVIF/WebP, preload critical assets, defer non-critical JS and host on a fast CDN. The platform handles all four out of the box.

Question 3

How do I avoid Cumulative Layout Shift (CLS)?

Accepted Answer

Always set explicit width/height on images and reserve space for ads/embeds. Generated components include CLS-safe defaults.

Question 4

What is INP (Interaction to Next Paint)?

Accepted Answer

INP measures the worst-case responsiveness of UI interactions. Keep JavaScript work short and split heavy logic into Web Workers. The platform's defaults rarely block the main thread.

Question 5

Are images optimised automatically?

Accepted Answer

Yes. Uploads are converted to AVIF/WebP, generated in responsive sizes and served from the edge with lazy loading.

Question 6

Which font loading strategy do you use?

Accepted Answer

System fonts by default; web fonts use font-display: swap with preload for visible-above-fold. Avoid more than two custom font families.

Question 7

How large is the JavaScript bundle?

Accepted Answer

Around 90-120 KB gzipped for a typical marketing site. Split per-route so users only download the code they actually use.

Question 8

Third-party scripts are slowing my site. What can I do?

Accepted Answer

Audit them in Lighthouse, defer non-critical ones (chat widgets, analytics), and use Cloudflare Zaraz to move third-party JS off the main thread.

Question 9

Can I set a performance budget that blocks regressions?

Accepted Answer

Yes. Settings, Performance, Budgets defines thresholds for LCP, INP, CLS and bundle size. The launch checklist enforces them.

Question 10

Which WCAG level do you target?

Accepted Answer

WCAG 2.1 AA. The platform's components meet AA out of the box; the launch checklist runs an automated audit and blocks critical violations.

Question 11

How is colour contrast checked?

Accepted Answer

Every Design DNA theme is validated against WCAG 2.1 AA contrast ratios. Custom palettes are scored in the Design Studio with live warnings.

Question 12

Is every component keyboard-accessible?

Accepted Answer

Yes. Buttons, menus, dialogs, forms and complex widgets follow WAI-ARIA Authoring Practices with tested keyboard interactions.

Question 13

How is keyboard focus shown?

Accepted Answer

A high-contrast focus ring is shown for keyboard users (using :focus-visible) and hidden for mouse users. Disable per component only with strong reason.

Question 14

Are screen readers like NVDA and VoiceOver supported?

Accepted Answer

Yes. Components use semantic HTML, ARIA roles and live regions tested with NVDA, VoiceOver and JAWS.

Question 15

What makes good alt text for accessibility?

Accepted Answer

Describe the purpose of the image in context. Decorative images get alt='' so screen readers skip them. The platform reminds you when alt text is missing.

Question 16

Do you respect prefers-reduced-motion?

Accepted Answer

Yes. All animations have reduced-motion alternatives that disable parallax, autoplay and large transforms when the user prefers it.

Question 17

Are form errors announced to screen readers?

Accepted Answer

Yes. Errors are tied to inputs with aria-describedby and live regions, so screen readers announce them as they appear.

Question 18

Do videos need captions?

Accepted Answer

Yes for WCAG AA. The video block supports VTT captions; the Coach can auto-generate captions in any of the 24 languages.

Question 19

Which tools do you use to test accessibility?

Accepted Answer

axe-core and Pa11y run on every public route in the launch checklist. Manual testing is recommended for complex flows.

Question 20

Should I publish an accessibility statement?

Accepted Answer

Yes — required for public bodies in the EU and recommended for all. Blanca's Builder generates one at /accessibility, translated into all 24 languages.