1.3.1 minimum semantics for groups of details / summary elements #5193

The quirks of details/ summary have been well described by @scottaohara in his articles The details and summary elements and The details and summary elements, again. My question concerns the overall semantics when several details/ summary elements are used in content (think of a list of FAQs). Then the question arises what semantics we can expect authors to implement above the disclosure functionality, i.e. above the output as a series of buttons with expanded state. Since summary maps in many browsers to button, it will flatten / remove any headings semantics we would want to use inside summary. Would you expect or even mandate list markup for a group of several details/summary elements to provide info on the number of elements in the group and a way to jump past that section? My hunch is no, not using markup beyond details/ summary wouldn't fail 1.3.1, but I'd like to hear other folks' opinions.