Font Awesome Inclusion Confusion

Why is Font Awesome being loaded on the public pages by the WP ADA Compliance Check plugin? I have a client wanting to optimize their website, and they currently have Font Awesome being loaded via the official Font Awesome plugin to then be used site-wide for their specific needs while they then also have the paid version of the accessibility check plugin which then seems unneeded (also seems to be a similar situation with the free plugin version.)

I can understand it being on the admin pages if it’s being used there, but how is it being used on the public pages? If it’s for admin purposes, shouldn’t it check if the visitor is currently logged in & is a sufficient role before including it so people that don’t need it don’t have unnecessary assets being loaded? If it’s for the “open in new tab/window” icon indicator, then shouldn’t it check against the settings to determine if that behavior is actually enabled? I have the site not having the plugin alter any content so the fact it’s loading an icon library for public visitors which is then effectively doing nothing seems like it should be updated. Hopefully this is a quick fix to have the points where Font Awesome is included be wrapped in a sufficient conditional statement (be it checking current user status/role and/or plugin settings) so it’s only included when it should be.

Also, it seems odd that the free & paid versions have Font Awesome being called in via different methods with different assets being loaded (paid version has the JS version of FA while the free version has it loaded via CSS from my initial inspection; seems odd & likely worthwhile to unify how this is done when changing how these are loaded in [only include when actually used] on both.)

Let me know if I should provide any additional information or anything.

Thanks,
Kurt