When you convert text to paths in an SVG, you preserve the visual style exactly — including custom fonts, weights, and spacing — but you lose all the benefits of actual text: it's no longer selectable, searchable, or accessible. This is expected and technically correct behavior.
Your idea of using something like <path text="A" d="..."/> to preserve the appearance and the character meaning is creative, but not supported in SVG. The text attribute doesn't exist on <path> elements, and adding it wouldn't cause browsers or assistive technologies to treat the shape as the letter "A" — it would still just be a vector shape with no semantic meaning.
If your primary goal is visual fidelity (e.g., for print, branding, or static display), converting to paths is the best approach. But if you also need the text to be accessible (e.g., for screen readers or searchable documents), then you should:
Include a <title> and <desc> element in the SVG to describe what it represents.
Optionally add a hidden <text> element or use aria-label or aria-labelledby to preserve the meaning of the outlined text.
Use live text (not converted to paths) for body content or contact info if it should remain selectable.
That way, your SVG works for both perfect visual reproduction and basic accessibility.
This kind of brand consistency is a critical part of identity design — and it ties directly into broader branding strategy. You can explore how a consistent visual language like this contributes to a strong brand in this article: