Is It Out of Scope? — Web design
Is supporting an additional browser or device beyond the agreed matrix out of scope for a web design project?
Depends. Designing for a broader viewport range is usually included; a genuinely new device class (e.g., a specific kiosk display) often isn't.
The design was approved against an agreed set of breakpoints and browsers. Requests to also cover something specific and unusual — an older browser version, a kiosk-style display, a niche device — go beyond the standard responsive range that set was meant to cover.
Is it out of scope?
Depends on what's being asked. A slightly wider standard viewport range is usually a small adjustment within the existing design. A genuinely different device class or an unusually old browser is real added design consideration beyond the agreed matrix.
Clause typically implicated
Clause typically implicated
Out-of-scope clause→ — The agreed compatibility matrix defines the range the design covers; a genuinely new device class or unusual browser target exceeds that agreed scope.
Example contract wording
Example contract wording (illustrative, not legal advice)
The design was approved against the agreed browser/device matrix — supporting [the new target] wasn't part of that range, so I'd want to scope the added design consideration separately.
How MarginFlow flags it
MarginFlow flags requests to support a device or browser genuinely outside the agreed matrix outside_scope on design contracts, while treating minor viewport adjustments as included.