

Some low-hanging fruit would be better support for title and desc elements (e.g. outlines how accessibility applies to SVG. Looking back at the full SVG (1.1) spec, is Inkscape already able to claim to be a " Conforming SVG Generator", for which I think lack of animation/filtering features would not be a problem (it seems to me that it doesn't matter what features you support, as long the generated file is valid SVG) but compliance with the Priority 1 accessibility guidelines from the " Authoring Tool Accessibility Guidelines 1.0" would be necessary. We already have the property of not discarding unrecognized elements like foreignObject and its children.) (: I believe we don't need to do anything to support the foreignObject element.



He's still new to inkscape source code, so could use guidance. SVG fonts: font, font-face, font-face-src, font-face-name, missing-glyph, glyph: The layers dialog box may be a good base. Interface for viewing other branches would be nice (perhaps a non-modal dialog box listing the children named by their requiredFeatures, requiredExtensions and systemLanguage attributes. as a viewer would, showing just one child). Minimum requirement is that we render it correctly (e.g.when writing SVG Tiny documents, we must not use style attributes - or at least use only "redundant" style attributes if that's easier to implement.) attributes instead of using style="fill.". Source, I believe we need the following: don't rely on style attributes A number of developers have voiced support for trying to achieve this.Īs a first glance without looking much at either the spec or inkscape It'd be a nice feather in the cap to be able to declare full compliance to one of the SVG specs.
