Completion target
A versioned responsive release candidate whose content behavior, layout rules, component patterns, test matrix, known limitations, support and acceptance scope are traceable.
Responsive Interface Decision Record
Coordinate one responsive interface through real content and people, layout requirements, bounded CSS/unit scenarios, representative reflow and interaction testing, controlled implementation, and named acceptance.
Before you begin
- • Current product, design-system, analytics/support and code ownership records available
- • Critical inaccessible task or data-loss issue routed to responsible owners
Risks to control
- • Device categories and screen-resolution lists can erase zoom, windowing, orientation, input, language, assistive-technology and real-content differences.
- • Responsive telemetry or session recordings can collect sensitive behavior and content when minimum-data boundaries are absent.
- • A viewport screenshot cannot prove DOM order, keyboard sequence, programmatic relationships, zoom/reflow or assistive-technology behavior.
- • Browser emulation does not reproduce every device, input, viewport, browser chrome, font, network, preference or virtual-keyboard condition.
Choose your path
Built around the job you need to finish
Carry one interface layout from real content, task order, affected-user needs and supported environments through bounded layout Tools, controlled implementation, representative reflow/interaction tests, performance evidence, rollback and named acceptance.
Product designer or content owner
Preserve task hierarchy and readable content across available space without choosing device widths as universal truth.
Inventory representative content and states, approve component constraints and review task order at narrow, wide, zoomed and localized conditions.
The layout preserves meaning and task completion without arbitrary page counts, breakpoints or text ratios.
Frontend engineer or QA owner
Implement responsive components with exact grid, flex, container and typography behavior plus reproducible boundary tests.
Use connected Tools as bounded code/measurement aids, document support assumptions, test adjacent widths and failure states, and retain rollback evidence.
Can reproduce layout behavior, failures and fixes without a one-score performance or deployment-ready claim.
Keyboard, screen-reader, zoom, reflow or motor-affected user and reviewer
Complete representative tasks with coherent reading/focus order, visible focus, usable targets and no two-dimensional scrolling where not essential.
Exercise navigation, forms, tables, dialogs, validation and dynamic content across zoom, text spacing, orientation and input methods.
Accepts or reports exact task/state failures with affected-user evidence and correction ownership.
Authoritative checks for this workflow
Outputs and checklists are planning aids. Review the linked current authorities and the records, terms, instructions, and requirements that apply to your exact situation before a consequential decision.
- Web Content Accessibility Guidelines 2.2World Wide Web Consortium · Current reflow, orientation, text spacing, focus, target size and interaction criteria; one viewport or breakpoint list cannot establish accessible responsiveness.
- Evaluating Web Accessibility OverviewW3C Web Accessibility Initiative · Current combined automated, human, assistive-technology and affected-user evaluation route across representative pages, content and states.
- CSS Grid Layout Module Level 2World Wide Web Consortium · Current grid track, placement, alignment, subgrid and accessibility-order context for an implementation-specific responsive layout.
- CSS Flexible Box Layout Module Level 1World Wide Web Consortium · Current flexible layout and ordering behavior supporting exact component tests without treating visual reordering as correct reading or focus order.
- CSS Containment Module Level 3World Wide Web Consortium · Current containment and container-query context supporting component-boundary tests beyond universal device breakpoints.
- Web VitalsGoogle web.dev · Current stable LCP, INP and CLS field-quality context; a single Lighthouse run or score is not deployment, usability or performance acceptance.