Summary

  • W3C’s 6 October Candidate Recommendation Snapshot asks implementers to test SVG 2; it is not yet a W3C Recommendation or an endorsement by W3C Members.
  • The snapshot leaves three features at risk of removal, including multiple title or desc elements for localization, while a test-based implementation report and public comments are still ahead.

Scalable Vector Graphics 2 has returned to a formal W3C Candidate Recommendation Snapshot. The publication history makes the timing notable: its previous recorded snapshot was dated 4 October 2018. That is an eight-year gap between published snapshots, not evidence that the Working Group stopped work in the intervening years.

The new document is a decision point, not a finish line. The SVG Working Group invites implementations and says the Candidate Recommendation period is intended to collect implementation experience. The snapshot says an implementation report will be produced from the SVG test suite in Web Platform Tests. It also says that Candidate Recommendation publication does not mean W3C or its Members have endorsed the document as a final standard. Advancement to Recommendation is expected no earlier than 1 December 2026.

That distinction matters because the group has put specific features on the record as “at risk.” More than one title or desc element to provide localization may be dropped, as may nested links and vector-effect options other than non-scaling-stroke. The label does not mean any of these features has already been removed, nor that browsers uniformly fail to implement them. It means their continued place in this version can be affected during the Candidate Recommendation period.

Localization is the less visible but consequential item in that list. A single description can serve one audience; multiple localized titles or descriptions can let the same graphic present suitable descriptive text to readers using different languages. The snapshot does not claim that all SVG accessibility depends on this one mechanism. It does, however, make the future of this particular authoring option an open implementation question rather than a settled feature of the next status.

The process now has observable inputs. Implementers can test the listed features against the SVG suite, report differences, and contribute to the implementation evidence. Authors, accessibility practitioners and localization specialists can file comments through the stated 1 December deadline. The Working Group will then have to decide whether the evidence supports retaining, narrowing or removing each at-risk item. The published report is not yet available, so neither support levels nor the final disposition can be assumed.

The group’s 29 September minutes record that participants had no objection to a Snapshot CR and proceeding with the transition. The minutes also discuss an internal “white review” that had not yet taken place, while saying the group did not think it blocked the transition. That is not evidence of a process breach: the published 6 October snapshot says it has received wide review, and the terms should not be conflated.

For implementers, the immediate task is not to treat the snapshot as frozen or to market every listed feature as guaranteed. It is to test the behaviors they rely on and make the results visible while the status can still change. For standards users, the record to watch is the implementation report, the comment disposition and any later update to the at-risk list. The renewed publication puts SVG 2 back before the web platform, but the evidence phase—not the date on the cover—will determine which disputed capabilities advance with it. Primary records: the 6 October snapshot and W3C publication history; the 29 September SVG Working Group minutes record the transition discussion, while W3C Process defines the Recommendation track.