You'd have to do that by adding some custom CSS. Normally, you'd do that with a custom_css.php in our template folder. But of course in an article created using this plugin, there's no "Fabrik" running, and our CSS doesn't get included.
So I think your best bet would be to use the built in J! template override feature (Extensions, Template Manager, Tmplates, <edit your template>, Create Overrides). Create the override, edit the default.css it creates, and add a class in there to style the 'li' however you want it, and in your Fabrik 'article' plugin template, wrap the placeholder for your photos in a div with that class.
So something like ...
Code:
My pics: <div class="myPicsClass">{yourtable___your_pics}</div>
... and then in the com_content default.css template override, add ...
Code:
.myPicsClass ul li {
# whatever CSS you need goes here
}
There's probably a simpler way of getting an extra class in to a content page, I'm just having trouble thinking of how to do it. Heck, you may just be able to add it as a static style sheet tag in your template.
EXTRA RAMBLING
I recall trying to add a way of solving this a while back ... a long while back, in the Fabrik 2.1 days ... and I think what I came up with was adding a "form_css" view option to our regular {fabrik ...} content plugin, and adding an option to the the original 2.1 form2article plugin so it insertes {fabrik view=form_css id=X layout=foo} at the top of the article.
That allowed you to include all our usual classes and styling, by having a plugin that ran in the article, which included our normal form CSS. I just looked, and that code is still in our article plugin. However, I strongly suspect that it has suffered from bitrot over the years. You could however try that, and add the above {fabrik ...} incantation by hand to your 'article' plugin template, as the first line, replacing X with the form ID, and foo with a valid Fabrik form tmeplate name (like 'default'). If that works, you should then be able to add a custom CSS to the template.
I may well have a hack at resurecting that code / option in the 3.x article plugin, as it proved to be quite useful in 2.1. It just never made it in to 3.x, as I added it in 2.1 after we forked the first cut of 3.x.[/code]