Critical accessibility warnings when using axe (a11y checker)

[AElmoznino]

Bug description

Axe devtools complains about critical accessibility issues related to angular-ng-autocomplete.
Notice that Google Chrome's Lighthouse accessibility audit uses axe under the hood and also complains about the same issues.

Expected result

No accessibility issues related to angular-ng-autocomplete. I suggest downloading and using axe devtools when troubleshooting/developing since it provides great suggestions on how to fix the issues.

Actual result

Steps to reproduce

1. Download axe devtools for Chrome.
2. Open it up in Chrome and perform a check on a page that has an <ng-autocomplete> on it. Select "Scan ALL of my page".

Context

We're striving on providing our users a fully accessible app and want to eliminate all accessibility issues. "Friends don't let friends ship inaccessible code" you know 😉

Your Environment

• Version used: 2.0.12
• Browser Name and version: Chrome Version 104.0.5112.79
• Operating System and version: Mac OS Monterey 12.5