What does 'Clickable' mean

By PaulMartz, 21 February, 2025

Forum
macOS and Mac Apps

While browsing the web, I often hear VoiceOver read an HTML element, then say the word "clickable". It's usually not on a button or link. More often, it's on static text. I've tried the various VoiceOver click equivalents, including VO+Space, VO+Shift+Space, and bringing the mouse pointer to the control and physically clicking the mouse. Most of the time, nothing happens.

Sometimes I'm surprised, though. When creating an AppleVis post, for example, there is a static text label just before the forum pulldown menu. VoiceOver reads the static text as, "forum, clickable". And if I press VO+Space on that text, it activates the adjacent pulldown menu. But even this behavior isn't consistent. Again using AppleVis posts as an example, I can navigate to the subscribe checkbox, interact, and navigate to the static text label. VoiceOver does not read this as clickable, but nonetheless, clicking it checks the checkbox. So it's confusing, to say the least.

I'd love to turn it off, but, much like WTA, the clickable announcement does not obey the general verbosity setting, and there are no speech hints to control it.

Any insights into why this announcement exists, ideas for turning it off, or even a pointer to where it might be mentioned in Apple's documentation would be appreciated.

Options

Comments

By PaulMartz on Friday, February 21, 2025 - 16:59

As I navigate through the text of my post above using VO+right arrow, the word "clickable" is announced at the end of each paragraph. Interestingly, if I use VO+A to read the article, VoiceOver does not announce clickable after every paragraph.

By PaulMartz on Friday, February 21, 2025 - 21:08

Happens in Google Chrome but not in Safari. Huh.

By Brian on Friday, February 21, 2025 - 21:42

Way back when computers used floppy disks, the sighted people used a mouse to navigate their operating systems, and dinosaurs roamed the Earth ...
someone decided that the "clickable" element would be an amazing idea. I want to say it was back in the days of.dhtml (dynamic HTML) content. You could add elements to a webpage where, upon a mouse click, the content would change/expand.
Let's take a look at the AppleVis mobile website, for example. About three swipes from the top left corner, we get a, "Main Menu, button, collapsed", element. This kind of control is what the clickable element used to be used for.
As far as I can tell, people still utilize the clickable element primarily for aesthetic purposes. Since visually speaking, it's not really something you would necessarily know you click on it, with the exception that your mouse pointer would likely change when you mouse over that particular element.
Does this make sense?

By Brian on Friday, February 21, 2025 - 21:44

Before you ask why you're getting the clickable feedback on just about everything, my best, most educated and experience answer for you would be simply, because macOS VoiceOver is all kinds of broken.

By TheBlindGuy07 on Friday, February 21, 2025 - 23:39

Seriously? I thought we'd need a 100 page academic paper for that :)
I'm getting this clickable thing in chrome as well but I only use chrome for web apps like teams where this doesn't seem to happen, only regular text like on applevis for example.

By Dave Nason on Saturday, February 22, 2025 - 00:36

Member of the AppleVis Editorial Team

It’s weird and annoying alright.
The thing is that this is one thing I’m not sure we can blame Apple for, as I’m sure I’ve encountered it on Windows too. I think more with NVDA than Jaws though. Plus as mentioned, on Mac, it seems to be on Chrome but not Safari.
I stand to be corrected though 🤷‍♂️
Dave

By TheBlindGuy07 on Saturday, February 22, 2025 - 00:47

With NVDA you have a toggle since a while to disable clickable announcement. I doesn't happen everywhere only on elements that are actually clickable and I leave it off for personal preference but it's a very useful attribute to know sometimes. The thing is that it seems to be new on mac either due to a chrome update or a macos one.

By Maldalain on Saturday, February 22, 2025 - 03:02

I am having the same issue with Brave browser. It is annoying but I can do with it.

By Brian on Saturday, February 22, 2025 - 03:19

Agree with TheBlindGuy07. NVDA has an element toggle that is simply glorious. I too have clickable disabled. Along with Article, and a few choice others. 😉

By PaulMartz on Saturday, February 22, 2025 - 14:52

If NVDA can provide a toggle for this on Windows, then it seems like VoiceOver could do the same on MacOS.

The similarities with the Writing Tools announcement are uncanny. Both clickable and WTA are announced via VoiceOver with no visual equivalent that would distract sighted users. Both are incapable of being toggled off. And both are pointless and provide no tangible information.

I'd lobby Apple to put clickable under control of general verbosity, but I've gotten nowhere with my attempts to similarly control WTA, and I'm out of energy.

By mr grieves on Saturday, February 22, 2025 - 16:48

It just started happening in Chromium browsers (Ege, Chrome and Brave) recently and it drives me mad. It seems to happen on every single bit of plain text that isn't marked up with anything special. It drives me mad.

I wonder if there is some new Chrome feature that lets you interact with text somehow. Didn't they add something wher eyou could circle text and ask questions or something like that? I wonder if there is some weird feature that means you can do stuff with this if you have a mouse. But for us it seems to just be irritating. If you read a long article it says clickable after pretty much everything. And not to mention the times when it reads the same line twice. I'm really upset how bad Chrome has become recently.

By PaulMartz on Saturday, February 22, 2025 - 17:33

Agreed. After about a year of more or less problem-free Chrome usage, I'd like to find an alternative. As usual, I'm busy with other projects, and I'll have to make do with Safari and Chrome, whatever is least painful.

By Icosa on Sunday, February 23, 2025 - 02:09

Definitely see it regularly with NVDA. It's usually where someone used something like a javascript event to trigger code on a click instead of using a link or a button. I find it often does something but it isn't uncommon for it to not register no matter what I do, particularly annoying when the occasional site requires the clickable element to be used.

By mr grieves on Sunday, February 23, 2025 - 16:28

Firefox is also suffering from the clickables at the moment. On the whole I find it is in third place - it works and there are some on here using it with VoiceOver. But I'm not sure it does much better than the others.

As for Opera, I used to love it back in the day - only browser I ever paid for. No idea about accessibility back then. But once it hit version 10, I think, it became just another Chromium browser. I switched to Vivaldi at that point, but moved away from that when I started using VoiceOver as it had a few issues. Not been back to either since so don't know if they are any better. But I don't think they are going to be much different to Chrome in terms of rendering.

By mr grieves on Saturday, March 8, 2025 - 17:43

I updated Brave and it has also been cured.

Firefox, however, is still telling me clickable at every opportunity.

By Icosa on Saturday, March 8, 2025 - 20:11

Probably a chromium thing, with firefox having its own rendering engine.

By PaulMartz on Thursday, October 1, 2026 - 13:13

Some time after I posted this, a release of Google Chrome addressed the issue, and reading websites was pleasantly "clickable"-free.

A recent update to Google Chrome has brought clickable back. Because, apparently, even a $400 billion company can't be bothered to implement regression testing.

By mr grieves on Thursday, October 1, 2026 - 14:24

In reply to by PaulMartz

I was noticing this earlier in the ChatGPT app, and now I've checked Chrome and you are right, it is back. I can't put into words how much I hate this.

By AbleTec on Thursday, October 1, 2026 - 15:10

Subject says it all, I guess. You can't control what these companies do, but the speech dictionary can be used to make the experience better. Sometimes it's all we've got lol.

Loving greetings to my spiritual brother-from-another-mother Paul. Pray you're doing amazing!

By PaulMartz on Thursday, October 1, 2026 - 15:19

I used the VO Utility pronunciation table. For the pronunciation of clickable, I used a period. Space didn't work.

I'm back to being clickable-free, even in the heading for this forum topic. Good enough for now.

You mean add a pronunciation rule for clickable to make it disappear? The thought had occurred to me, but switching to Safari except in emergency seemed like the better option. I hate things like that - maybe that shows a lack of blind person credentials on my part. Just imagine reading this topic if clickable was blanked out. We'd think Paul had gone nuts.

By Brian on Thursday, October 1, 2026 - 18:07

It used to be, that you could enable/disable certain elements from being read aloud by voiceover. You could also choose the order in which things were addressed. For example, you could have a link spoken aloud as the link name, followed by it status, etc. Or buy it status first, followed by the name, etc.
Is this still the case? And if so, is clickable items not within this list?

Disclaimer, genuinely asking here. Not trying to speak negatively on VoiceOver.

By Mohammad Suliman on Thursday, October 1, 2026 - 18:34

I also can confirm the bug. Yes, that's true. If you go to the "Verbosity" > "Speech", and change the verbosity of the "Text" control to low, the clickable will go away. It's the status in VO's terms for text. Not sure if this will make other places more confusing, I was curious so have only tested that.

Thank you again, Brian.

By PaulMartz on Thursday, October 1, 2026 - 18:56

I have default verbosity set to low all the time, so I didn't think there would be a way to make it any lower. It turned out I had set custom verbosity to Medium for text elements, for some unknown reason. Changing it to Default made clickable go away.

Good tip, thanks.

By Brian on Thursday, October 1, 2026 - 18:59

Glad my outdated knowledge could still be useful. 😊