You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’ve searched for any related issues and avoided creating a duplicate issue.
What happened
<va-search-input> tells the browser to “do something” to autocomplete in two ways - HTML (autocomplete=”off”) and ARIA (aria-autocomplete=”none”).
HTML autocomplete=”off” is picked up by assistive tech (AT) and implements autocomplete behavior. ARIA aria-autocomplete=”none” is picked up by AT, but doesn’t actually implement any behavior.
Since autocomplete="off does what's needed already, you should be able to safely remove aria-autocomplete="none".
What I expected to happen
Only one autocomplete attribute is used to prescribe autocomplete behavior in <va-search-input>
Bug Report
What happened
<va-search-input>
tells the browser to “do something” to autocomplete in two ways - HTML (autocomplete=”off”
) and ARIA (aria-autocomplete=”none”
).HTML
autocomplete=”off”
is picked up by assistive tech (AT) and implements autocomplete behavior. ARIAaria-autocomplete=”none”
is picked up by AT, but doesn’t actually implement any behavior.Since
autocomplete="off
does what's needed already, you should be able to safely removearia-autocomplete="none"
.What I expected to happen
Only one autocomplete attribute is used to prescribe autocomplete behavior in
<va-search-input
>Reproducing
Steps to reproduce:
<va-search-input>
component used under "Search resources and support articles or all of VA>gov"Urgency
How urgent is this request? Please select the appropriate option below and/or provide details
Details
This is a minor issue and isn't affecting AT users. Fixing this will simply tidy up the component.
The text was updated successfully, but these errors were encountered: