Put a simple demo into the mobile showcase. I had similar problems as found with the tabset component. Only the first contentPanel seems to be properly inserted into the DOM.

For both the accordion title bar and the tabset tab, I think we need another way to specify content other then just the title attribute on contentPane.

For accordian a users will likely want to change the arrow character used to indicate the visiblity of the panel.

For tabset in the mobile space icons are often used with text or instead of text. Sometimes an icon can say more then a few words which is important on a screen with limited room.

for the first issue, I think that's probably due to the use of findComponent in the current trunk version (which I have since changed). Am waiting for Mark's checkin before updating it, but I have taken findComponent out of the ability of the panel to find out if it is selected as a complicated layout may not locate it properly with findComponent.

no problem to add another attribute. Please suggest a name (icon?) whatever....as that's a very simple thing to do.

If you look at the Accordion class, you can see a few other options for using a character (rather than having to load an icon). Since the original premise for this product was to try and use as little resource loading as possible, the use of icons can be supported, but assumption was made to try and have defaults that did not rely on extra weight to be brought over from server.
We can have a default value (the arrow...there are a few others in the class if we want an option), that can be overridden if an icon is present. At least then, we can show it as light as possible.

accordion component completed in 1.1 Beta. Any new improvements or issues should be a new jira