Software
Software
Durable Task in the Real World: What Problems Does It Actually Solve?
12 Oct 2026
Open the thinkingSoftware
Updated Candidate Recommendation: Scalable Vector Graphics (SVG) 2
THE CONTEXTEvidence for
Evidence for
Question raised by “Updated Candidate Recommendation: Scalable Vector Graphics (SVG) 2”.
How this was reviewed: Article-level review.
W3C has published an updated SVG 2 Candidate Recommendation Snapshot, inviting implementations and feedback. The announcement describes corrections and clarifications intended to improve interoperability. SVG combines scalable two-dimensional graphics with styling and dynamic behaviour, making it relevant to interactive diagrams and artwork. The document's candidate status matters: publication is a standards-development milestone, not proof that every feature behaves identically in every browser.
Candidate Recommendation status is not a universal browser-support promise. The announcement describes the specification's direction, without certifying a project's accessibility or performance. Individual features need compatibility checks, and the best rendering may vary with device capability, user settings and the purpose of the drawing.
OUR EDITORIAL CONNECTION
Beautiful graphics should survive the device change
Page & Process makes information visual, and a visual explanation should stay sharp and useful on the visitor's device. This source belongs here because expressive graphics and dependable interaction need to develop together. Standards work gives us a place to examine compatibility rather than treating one impressive desktop demonstration as the finished experience.
The buyer question we would begin with
Will this visual explanation still work on my phone, with a keyboard or at high zoom?
Look closer at
Question raised by “Updated Candidate Recommendation: Scalable Vector Graphics (SVG) 2”.
A vector graphic can explain a relationship without fixing it to one screen size. The layers below ask how that explanation would remain readable, navigable and maintainable, then connect the design to checks on the devices and access methods a project agrees to support.
The PageWhat someone encounters.
A bespoke product explainer could unfold an SVG drawing as the visitor explores a service, with each shape connected to a real question and an equivalent text description. Tapping a component would reveal its role without forcing a long animation. The drawing would adapt to narrow screens while retaining meaningful labels. A static view would remain available for visitors who prefer less motion or need to print the explanation.
The ProcessWhat happens behind it.
The team would identify which drawing and animation features the actual design needs, then check those features across the supported browsers. Assets would have clear ownership and a controlled export process, preventing inaccessible text outlines or accidental external dependencies. An animation budget would limit expensive effects. The release checklist would include focus order, alternative descriptions and a reduced-motion version alongside the usual visual inspection of the artwork.
The ResearchWhat we need to understand.
We would compare a conventional explanatory page with an interactive diagram built around the same buyer questions. Participants would be asked to explain the service back in their own words and identify the next relevant step. The research would distinguish attraction from understanding: an effect earns its place when it helps people locate or retain useful information, rather than merely increasing the time they spend watching the page.
The TestHow we would find out.
The candidate diagram would be tested at narrow mobile widths, enlarged text and high browser zoom, with keyboard navigation and motion reduction enabled. Every important component must remain reachable and understandable without relying on animation or colour alone. Screenshot comparisons would detect clipped labels; task observations would check whether users can identify a requested component and its meaning. A failed effect would receive a simpler compatible rendering before release.
Draw the relationship.
Keep the meaning accessible.
Choose a process or relationship your buyers find difficult to understand. We can prototype a visual explanation and inspect its reading order, scaling and alternative route before it becomes part of the website.