Performance, accessibility, i18n and security as design concerns
Comes up in: Frontend system design
This concept is being written. It gets the full five steps — explanation, predict, interview angle, practice with tests, and review cards. Here is exactly what it will cover, so you can study it elsewhere in the meantime.
What it covers
- performance budgets per page
- virtualisation
- image strategy
- a11y architecture (design system, focus management)
- i18n architecture (locale routing, message loading)
- security architecture (CSP, auth flows, XSS surfaces)
- observability (RUM, error tracking)
Words you will know
What you will practise
- checklist applied to one design
Interview questions this answers
- How do you bake accessibility into a design rather than adding it later?