After a bit of noodleing, here are some thoughts on this:
1. Since the content is actually being hidden by javascript screen-readers will still be able to read the content.
2. Navigation can still be handled by placing a standard anchor before the collapse elements, for example:
<a name="#monkey" tabindex="7" title="All about monkeys" alt="All about monkeys" class="screen-reader-text">All About Monkeys</a>
[expand id="monkey" title="All About Monkeys"]...[/expand]
The only area that still remains is how best to activate the expand via keyboard.
But we do have this feature in that the id of the expand can be used as an anchor in the url to auto-expand that section. Please view the documentation regarding the ID attribute for an example.
In our view, this fills all aspects of accessibility. Happy to hear your thoughts on this. If you would like to continue the discussion, you can create a feature request at: https://ideas.twinpictures.de
This issue is marked as resolved.
