# Better accessibility on search result highlighting

**URL:** <https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367>\
**Category:** Feature Requests\
**Created:** [12 March 2024 09:56 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367 "2024-03-12T09:56:31Z")\
**Posts on this page:** 14\
**Page:** 2

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [22 March 2024 07:22 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/21 "2024-03-22T07:22:43Z")

</div>

> [@Colin](#):
>
> I thought it does get pulled on screen.

sometimes this does not work especially if two or more nodes are meant to be highlighted.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [22 March 2024 10:42 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/22 "2024-03-22T10:42:55Z")

</div>

When using the select nodes option in status and catch nodes we do dim the whole workspace apart from the selected nodes... maybe we can re-use this capability somehow ? (along with tab switching/centering)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/b/7b22a6ad2f2117c5f392664cecc69ff5c3f81b0e.png)

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [22 March 2024 15:24 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/23 "2024-03-22T15:24:15Z")

</div>

All in for re-use of functionality but TBH, you still have to scan the entire canvas for the _slightly_ more prominent node. And as the OP said, not great for those unfortunate enough to suffer retinitis pigmentosa. But work a look see perhaps.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [22 March 2024 15:27 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/24 "2024-03-22T15:27:21Z")

</div>

oh, actually, you have just reminded me, there is another place we might be able to pick up and re-use some code - the guided tour!

![chrome_itSaZOBRNS](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/5/8524629e3db27aa7841b0001054a71a019d616fb.gif)

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [22 March 2024 21:15 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/25 "2024-03-22T21:15:59Z")

</div>

That's more like a search result :-).... but of course - how would it handle multiple results..

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [22 March 2024 21:24 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/26 "2024-03-22T21:24:13Z")

</div>

You only click on one result at a time?

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [27 March 2024 16:54 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/27 "2024-03-27T16:54:35Z")

</div>

Steve's idea is interesting if we want to highlight just one element.

I rather suggest doing it the other way: we increase the size of the elements which we will gradually reduce to their normal size and at the same time use the flash.

We should also go further for these people by creating accessibility parameters:

- contrast: (darken everything we don't want to highlight)
- text size: (adapt the size of texts/nodes)

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [28 March 2024 09:59 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/28 "2024-03-28T09:59:05Z")

</div>

Any news?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [28 March 2024 10:41 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/29 "2024-03-28T10:41:11Z")

</div>

@GogoVega what news are you looking for?

As it stands there are lots of differ ideas as to what would make the search highlighting more effective. I don't think there is a consensus on what would be a better approach that satisfied everyone's different ideas of what would be better.

There is a much broader topic around accessibliity of the editor in general. I don't want to dismiss that as an important topic, but that could easily snowball into a much larger and complicated set of changes than this one specific request warrants.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [28 March 2024 10:46 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/30 "2024-03-28T10:46:57Z")

</div>

On the suggestion I made above (enlarge the nodes then gradually reduce them).

Yes, accessibility is a delicate subject that will have to be taken step by step - this request being one.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [28 March 2024 10:51 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/31 "2024-03-28T10:51:50Z")

</div>

Personally, I do not like the idea of changing the size of the node.

I do think that movement is a good way to attract the eye. @Steve-Mcl reminded us we have pieces in place already for putting a virtual spot-light on a node as part of the Tour. My instinct says that may be too much, but a slightly toned down version could well work.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [28 March 2024 11:01 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/32 "2024-03-28T11:01:14Z")

</div>

I forgot to mention it yesterday - we could also use "navigator-canvas" like VSCode (bars on the right which indicate where we should scroll)

Another possibility would be to contrast the entire background to highlight only what you want in addition to the flashing and for visually impaired people apply (in addition) Steve's idea.

---

<div class="post-metadata">

**Author:** ![rmwiseman](https://avatars.discourse-cdn.com/v4/letter/r/e47c2d/32.png) [@rmwiseman](https://discourse.nodered.org/u/rmwiseman)\
**Post date:** [2 April 2024 07:35 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/33 "2024-04-02T07:35:10Z")

</div>

I agree that for most people, movement is a good way to attract the eye, but for those with missing peripheral vision, unfortunately movement might as well not be there if it's not significant, as it won't be seen. That's why I think we need (the option to have) a big movement like a (full-screen?) contracting circle that draws the eye to its centre regardless of where you're looking to begin with. I do think it probably needs to be configurable, since what's _needed_ for one person is likely to seem excessive for another person.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [1 June 2024 07:35 UTC](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367/34 "2024-06-01T07:35:55Z")

</div>

Closed on 1 June 2024 07:35 UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/better-accessibility-on-search-result-highlighting/86367.md?page=1)