@JDesign... The problem with tabs on mobile, especially phones is that the WF tabs widget as currently built doesn't allow you to put html content directly underneath each tab button - which can get weird on phones if you have more than just a few tabs. The end user would most likely be clicking on a button & not seeing any changes in content due to screen real estate (which would most likely be filled up with buttons...)
It's more of an aesthetic thing but at the same time there are some seriously computer illiterate people browsing the web on their phones who could simply think it's "broken" or "nothing happened" rather than scrolling down to see the actual content. Then of course, scrolling back up to change the content, etc. Kind of a pain in the ****...
That is essentially what I did for the custom accordion. Go ahead and clone it
The structure has an "acc_section_wrapper" that wraps both the buttons & accordion content, then a "Personnel" section (i.e. buttons - which are actually just pulled in from the original tabs widget from on the desktop", and finally an "acc_content" section. There are two interactions, the first one is set on the "acc_content" section to initially hide it... the second interaction is the actual show/hide functionality - set on the "buttons", affecting "acc_content" - limited to sibling elements.