Sorry. This sat here far longer than it should have, and you asked a fair question. Both are yes, in the next release. I built them after reading this.
There’s a no-code path and a code path, whichever suits you.
From the settings screen (Settings → Widewalk → “The launcher”):
- Your own image: paste an image address into “Your own button image.” It replaces the default icon on the corner button.
- Drop the floating button: choose “Open from a link.” The corner button goes away.
- Open it from your footer: give any link or button the class widewalk-open, or the attribute data-widewalk-open. For example: Accessibility options That works anywhere in your markup, footer included. If you want to point at some other element, there’s a field for your own CSS selector in the same panel.
If you would rather do it in code:
- Your own icon: add_filter( ‘widewalk_launcher_icon’, function () { return ‘…’; } );
- Drop the floating button: add_filter( ‘widewalk_hide_launcher’, ‘__return_true’ );
- There is a small script API as well: Widewalk.open(), Widewalk.close(), Widewalk.toggle() and Widewalk.isOpen().
Two details worth knowing. Your trigger’s aria-expanded stays in step, and focus returns to it when the panel closes, so keyboard and screen reader users get a clean path in and out. And when the floating button is hidden, it is not removed outright. It stays as a single focusable pixel that reappears when focused, so if a trigger ever goes missing from a template, keyboard and screen reader people can still reach the panel.
Thanks for the nudge on this one.
We will marked this as solved, but check it out, as we as well release compatibility with RTL