The wider ILF Tech Team rolled up their sleeves to help us unearth bugs 🐞🔍 and issues for the Web Monetization publisher tools, and the revamped website. The most common issues were about accessibility and the user experience.
🧰 For publishers
For a quick intro or refresher about the publisher tools, check out July’s blog.
Improvements and fixes for the Banner and Widget tools:
- Accessibility improved such that:
- The close button is clearly visible on any background.
- The custom builder is fully responsive on mobile and desktop, supporting screen readers and keyboard navigation.
- Text customization is now consistent on both mobile and desktop, including unlimited text resizing.
- The text visibility toggle and the thumbnail toggle now work as expected.
- Banner customization allows multiple types of animation.
- Editing the name of a config tab now restricts the use of spaces and special characters.
- The correct message is shown before overriding current with a previously saved config.
- Users now receive visual feedback when copying a script.
- Editing an existing banner that is on a publisher's website now immediately applies the changes to the website.
Highlighting improvements and fixes to the RevShare tool:
- Security checks now confirm that wallet addresses are valid, and only resolve with a valid wallet address response.
- Improved navigation in the Tools drop-down on mobile—focus now moves to a specific menu item instead of the entire list.
- When configuring the table of sharing recipients:
- The percentage field is now read-only.
- Table resizing is now consistent on desktop and mobile, with the table maintaining a minimum of 2 rows.
A notable enhancement to the WordPress plug-in was:
- Allowing a user to add multiple wallet addresses across the entire website, where previously only one could be added.
For supporters
The browser extension now includes minor bug fixes and an enhancement, released in 0.9.2.1 to 0.10.0.0. The most notable were:
Disconnecting from a wallet now offers the option to force a disconnect, useful if a wallet has since become inactive.
A consent screen that new users will immediately see after installing the extension. Existing users will be required to give their approval when there is a change in the policy. The reason for this work is that we want to be clear and upfront with users about which information is collected and how it is used. This complements the existing consent screen where users can optionally agree to automate key addition, when connecting a wallet.
💻 Ready for Hacktoberfest?
Before you go, are you, or anyone you know, participating in Hacktoberfest? We’d love for you to help us improve the Web Monetization project by tackling issues at:
Every contribution makes a difference—let's build something great together!
Join our community meetings
Web Monetization community calls are open to the public, and you’re invited! The next one is on October 9th, 2025.
Find your timezone ▶️ Add to your Google Calendar ▶️ Join the meeting
Until next time, come back soon!
Top comments (0)