Ignore readonly autocomplete field

[eddie0329]

<< Describe the changes >>

Closes: #4708

adding feature that autocomplete-valid rule should not fail on readonly fields.

[WilcoFiers]

Hey @eddie0329 Thank you so much for the contribution. While This addresses the issue, I don't think this is quite the right way to do this. The way you've done this will result in the rule passing. What I think we'd want here is for the rule to be inapplicable on readonly input elements. The way to do that is to move the check to the matches function in lib/rules/autocomplete-matches.js.

You'd then need to put a test for it in test/rule-matches/autocomplete-matches.js. We'll also want at least one E2E test to validate the result, which you can add to test/integration/rules/autocomplete-valid/autocomplete-valid.html.

[WilcoFiers]

LGTM, just need a couple integration tests in test/integration/rules/autocomplete-valid/autocomplete-valid.html.

[eddie0329]

@WilcoFiers Thanks for review.
I was trying to add some integration test,, but have little problem.

Command , npm run test:integration, leads me error below:

SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 131

My current chrome version is 134. Instead of down garde my original chrome version, is there any way using like virtual environment?

[straker]

@eddie0329 if you run the command npx browser-driver-manager install chromedriver from the root of the axe-core directory, that should install a compatible version of chromedriver for you so you can run the integration tests.