Frequently asked questions
Wireframes aren't primarily about defining visual style (the design system does that); they're about validating content structure, page layout logic and user flow before investing in full visual design, catching structural problems (like a page trying to do too much, or a form flow that doesn't match how users actually think) while they're still cheap to fix.
After discovery and information architecture have identified what pages/templates are needed and what content each contains, but before full visual design and development. Wireframing that happens too early (before IA is settled) tends to get redone once real content requirements emerge.
Yes. Reviewing designs and wireframes for accessibility before the build phase (rather than testing for it only after launch) is standard practice for an accessibility-first Drupal team, since structural decisions made at wireframe stage (heading hierarchy, form field grouping, navigation patterns) are much cheaper to get right early than to retrofit later.
Insights