Accessibility: New Topic/Reply form not accessible to screen reader

A screen reader user on iOS reported that several buttons on the New Topic/Reply form are not correctly labelled.


  • The reply button in the bottom-left is being read as “Or press Ctrl+Enter”, not “Reply” as expected
  • The hamburger button in the top-right is not labelled
  • The upload image button in the bottom-right is read as “link”

Is this specific to mobile?

Of the buttons listed, I think only the Reply button appears on the desktop version but it’s still labelled “Or press Ctrl+Enter”

1 Like

@owlish I would love to get this sorted, can you provide us with a quick start of how to test this? What software do we install locally?


The Chrome Vox screenreader was recommended for accessibility testing.

NVDA is another free option for Windows.


Just wanted to check in to see if there’s been any movement on this or if you need any more information

Hi @sam, is there any other information you need for this?

I think we have what we need, its just a question of resources at the moment.

I am adding a #pr-welcome on this in case someone from the community wants to help out.


The issue with the reply button was fixed by commit 31ffcf989ce63e. I just tested this on iOS with VoiceOver.

Now I’ll investigate the other two issues.


I verified that the hamburger button in the composer isn’t labeled. Specifically, this is the toggle-toolbar button in the composer-toggles component. This button is only rendered in the mobile view.

What would be a reasonable label for this button? Maybe “Formatting”, since many of the toolbar options are formatting related? Not all of them are, though. Maybe the more generic “Tools” would be better.


It occurred to me that, to enable accessibility fixes to reach Discourse’s worldwide user base without imposing too much on translators, we should use existing strings for unlabeled controls when it makes sense. So, for the hamburger button, would it make sense to use “show more” as the title? We could use “options”, and I think that would be a better fit, except that there’s already an “options” button in the toolbar itself. I think that would be confusing.