__What should we do?__
Simplify the connect icon from
![]()
to
![]()
__Why should we do it?__
Improve the icons accessibility :arrow_down:.
Please, change the sequence/message flow icon
From:
![]()
By the single version of both sequence line + arrow, like
![]()
and
![]()
I think that by default can be the first image, and change it on demand later (with a context menu similar when you switch from task types ) to dotted arrow.
There are some people (like me) that have a weird eye condition where with icons like that,

It causes that the brain thinks that the image is not focused and it tries to focus but since the image is ok and will not change the brain tries to focus all time causing a fatal tiredness and even headache.
I'm pretty sure that I'm not the only one with this problem since the doctor told me that is a normal issue for some people with certain age.
Best Regards, and congrats for all you awesome work.
Thanks for opening this issue.
What the icon should transport is _make a connection_. We want to avoid that users think only a single connection type is possible. We also want to avoid to show more than one entry in the context pad and in the palette.
Do you have a suggestion how we could improve the icon with regards to your issue while continuing to transport that message?
Would be interesting to get your feedback on :arrow_up: @eriknyk.
Thanks for you answer @nikku, I was thinking a way to try minimize the effect, and something like this can help.

I didn't try other colors, but yeah it minimize the effect, not at 100% but at least about 75% what is acceptable helpful.
This symbol does not only represent (a standard) connection but also message flow, conditional flow, and default flow. It is a symbol that represents an entire group like most of our other symbols in the palette and context pad do (gateway, task, end event, etc.).
So my argument would be that one representative symbol is enough. In this case, I would choose the standard connection:

Your rationale @andreasgeier makes absolute sense.
I've updated the issue description accordingly. We'll give the simplified connection symbol (sequence flow style only) a try.
Most helpful comment
This symbol does not only represent (a standard) connection but also message flow, conditional flow, and default flow. It is a symbol that represents an entire group like most of our other symbols in the palette and context pad do (gateway, task, end event, etc.).
So my argument would be that one representative symbol is enough. In this case, I would choose the standard connection:
