Replies
There is something else that confuses me. When I post an anonymous reply, the user’s real name is still visible in notifications. On the plugin page it says
If you have bbPress to BuddyPress group forums integration enabled, it won’t support recording of anonymous activity of the anonymous forum topics/replies. The activity will show the actual user’s detail.
As far as I understand, we do not have bbPress to BuddyPress group forums integration enabled. If you mean the checkbox at the bottom of the bbPress settings page (just above the Akismet integration setting), that option is not enabled on our site. Group forums should therefore not be active. I cannot find any other related setting.
Still, the real username of the anonymous poster appears in notifications (for example, to the topic starter).
Am I misunderstanding something here? We do not want to disable all forum activity recording.
We are still not sure about whether we should offer anonymous posting to our users. However, if we do, at the very least bbPress Keymasters need to be able to see who the actual author is. It would be enough if only Keymasters (not regular bbPress moderators) could see the real username.
Yes, exactly—the ability for users to report comments in the same way as posts, bbPress topics and replies, and updates and comments in the activity stream.
For us, comments are very central, and it would be extremely convenient to have everything managed in a single plugin. 🙂
I wanted to add some additional details.
The modal popup does actually open and overlay the page content, but it does not receive focus for the screen reader. This means that when navigating with a screen reader, the user remains in the underlying page content and cannot locate the form fields within the modal. The behavior seems to vary slightly depending on the OS when using VoiceOver, and I haven’t yet tested with other screen readers such as JAWS, NVDA, or ZoomText.
What would be needed is for the modal to be treated as a dialog, with the rest of the page marked as inactive while the modal is open. The screen reader / keyboard focus should be set to the first interactive element (in this case, the subject field), and keyboard navigation should be trapped within the modal, looping through its elements until it is closed.
I’m not able to code this myself, but these practices are clearly outlined in WCAG guidelines.
Would this be something you could consider looking into? Otherwise, we’ll continue using the Popover version for now.
Here is an example:
https://erotopia.se/forum/topic/forumfeedback-och-buggar/#post-13624