I need to cite them in a sales pitch for a web app that will have applets in it.
As someone who deploys both free floating (JWS) and embedded (conventional applet) rich client apps. from a web site, I would advise avoiding applets wherever practical.
They are an odd mix of thin and rich client that makes moving around the page using the keyboard difficult, if not impossible.
They are not easily resizable.
There is a new browser/JRE/applet interaction bug every other week, and they are a constant source of maintenance trying to work around the bugs that nobody seems to want to fix. Sun/Oracle points to the browser manufacturer, while the makers of the browser either say it is Sun's problem, or flag it as low priority.
In the few cases where I deploy embedded applets, there is either:
No other solution immediately obvious. This usually only applies to applets intended to support other applets - Java minimum version checking, applet wrappers etc.
A JWS based alternative.
And in the case of 2, when I hear from users of bugs in the applet, I advise them to use the JWS version.
Is there any reason this web app. would be better served by embedded applet(s) rather than an app. deployed using JWS?
You might try: http://www.javafx.com/ (although this is based on JavaFx, it's still some kind of applet)
Old-school applets are very rare. More visitors have Flash and it is easier to create good-looking sites. If you only are going to use the old-style applets (so not JavaFx): please think it over again. You might be better of choosing a more simpler solution with HTML and (some) Javascript.
Or is it actually Java Webstart.