- do you need to support high DPI monitors? If "yes" then you need a) something capable to render on GPU and b) to use scalable vector image formats like SVG and others.
- Do you need adjustable styling? Like today it is a flat UI and tomorrow they will return back to skeumorphism. Material design for example is step in that direction. What about UI branding, when the same UI is used for different brands with their own color schemes, etc? What is expectation for the lifetime of your application? Just for the note: http://sciter.com/from-skeuomorph-to-flat-ui-evolution-of-on...
- What about UI accessibility? "Section 508" and the like.
- So called "richtext" WYSIWYG editing - yes/no?
- Printing and print preview?
- Dynamic UI composition? When UI is composed from actual data structure. In some cases simple flat property lists may work but not always.
- UI animations and transitions ?
- What about UI internationalization?
As of "No HTML, no CSS"...
HTML is just a serialization form of tree of UI elements. Not more not less. Any library has this (serialization) in one form or another.
CSS is simply the way to define things like: "this element in that state has to be rendered te following way". Any good library has that in one form or another.
You do not need full scale browser for HTML/CSS, and actually should not use solutions based on browsers for the UI. Primary goal of a browser is to provide safe browsing experience, UI rendering is only next function after the first...