Since the underlying tool seems to be named something like "widget," I found I can nudge it into this embedded interactive output instead of artifacts by saying, "show me a widget that..."
One of the problems with this approach (one-way sync/extract from org-mode files to Anki database) is losing out the context (imagine org file notes from a technical books). I use org-drill in combination with org-sticky-header, which show the path of headings to that particular node. Normally in Anki, this requires to add some extra descriptions or tags for this purpose. In org-mode, we get this for free.
But on the other hand, org-drill will fill your org file with scheduling and metadata drawers (I did some hacks to hide them but not able to make it work without messing the org-ellipsis).
Another drawback with org-drill is it manages schedules for one "card" per heading, hence cloze items are not scheduled individually. So, either you remember entirely "Alfred North Whitehead wrote [Principia Mathematica] in [1910]" or not at all. In Anki, not only the book title "[Principia Mathematica]" and the written year "[1910]" are tested separately (same as org-drill), but also scheduled/scored separately too (where org-drill falls short).
I use both, org-drill mostly for books, Anki for "standalone" facts. But I'm always wishing for some kind of a system that hit the sweet spot between them two.