I experience Chrome enabling accessibility features even though I am not using accessibility features like magnification and such (a long-standing weirdness/bug), so I am not so surprised this (genuine) DLL is being loaded unintentionally.
I guess it listens to some API that sometimes "lies"/is buggy, or maybe an API that is simply not the definitive API for sniffing accessibility requirements.
You can check what chrome://accessibility/ says - if some of the things there are enabled, disabling them and restarting Chrome might stop that DLL from being loaded (at least until Chrome decides that you do need accessibility enabled again).
So I would say it is only as fishy as a bug, nothing malicious.