FAQ Library
Performance & accessibility
Core Web Vitals, image optimisation and WCAG 2.1 AA accessibility patterns.
- What are Core Web Vitals and why do they matter?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.
- How do I improve Largest Contentful Paint (LCP)?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.
- How do I avoid Cumulative Layout Shift (CLS)?Always set explicit width/height on images and reserve space for ads/embeds. Generated components include CLS-safe defaults.
- What is INP (Interaction to Next Paint)?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.
- Are images optimised automatically?Yes. Uploads are converted to AVIF/WebP, generated in responsive sizes and served from the edge with lazy loading.
- Which font loading strategy do you use?System fonts by default; web fonts use font-display: swap with preload for visible-above-fold. Avoid more than two custom font families.
- How large is the JavaScript bundle?Around 90-120 KB gzipped for a typical marketing site. Split per-route so users only download the code they actually use.
- Third-party scripts are slowing my site. What can I do?Audit them in Lighthouse, defer non-critical ones (chat widgets, analytics), and use Cloudflare Zaraz to move third-party JS off the main thread.
- Can I set a performance budget that blocks regressions?Yes. Settings, Performance, Budgets defines thresholds for LCP, INP, CLS and bundle size. The launch checklist enforces them.
- Which WCAG level do you target?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.
- How is colour contrast checked?Every Design DNA theme is validated against WCAG 2.1 AA contrast ratios. Custom palettes are scored in the Design Studio with live warnings.
- Is every component keyboard-accessible?Yes. Buttons, menus, dialogs, forms and complex widgets follow WAI-ARIA Authoring Practices with tested keyboard interactions.
- How is keyboard focus shown?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.
- Are screen readers like NVDA and VoiceOver supported?Yes. Components use semantic HTML, ARIA roles and live regions tested with NVDA, VoiceOver and JAWS.
- What makes good alt text for accessibility?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.
- Do you respect prefers-reduced-motion?Yes. All animations have reduced-motion alternatives that disable parallax, autoplay and large transforms when the user prefers it.
- Are form errors announced to screen readers?Yes. Errors are tied to inputs with aria-describedby and live regions, so screen readers announce them as they appear.
- Do videos need captions?Yes for WCAG AA. The video block supports VTT captions; the Coach can auto-generate captions in any of the 24 languages.
- Which tools do you use to test accessibility?axe-core and Pa11y run on every public route in the launch checklist. Manual testing is recommended for complex flows.
- Should I publish an accessibility statement?Yes — required for public bodies in the EU and recommended for all. Blanca's Builder generates one at /accessibility, translated into all 24 languages.