If you choose "Community providers (In VA's network)" from the Facility type filter, the Service type filter become an actionable, selectable search field (A field you can type into and then select one of the suggested options)
However it takes about 2-3 second for this field to become active from it's previous disabled state. Which means that if I am going through and selecting my filters using a keyboard and if I'm doing this quickly (a visual keyboard user), when I select my Facility type, the next tab element is the Search button, because Service Type is still disabled. This causes an form validation error because Service Type is required.
Screenshots
After selecting "Community providers (In VA's network)":
Acceptance Criteria
[ ] I expect that it is determined if this is the behavior across the board
[ ] I expect that it is determined how and where we are tracking the query performance
[ ] I expect that the exact number is documented based on the va.gov tracking
[ ] Reduce the time between when the facility is chosen and when the Service type field becomes active
DEV Note: we can potentially enable the field before getting an API response
Description
If you choose "Community providers (In VA's network)" from the Facility type filter, the Service type filter become an actionable, selectable search field (A field you can type into and then select one of the suggested options)
However it takes about 2-3 second for this field to become active from it's previous disabled state. Which means that if I am going through and selecting my filters using a keyboard and if I'm doing this quickly (a visual keyboard user), when I select my Facility type, the next tab element is the Search button, because Service Type is still disabled. This causes an form validation error because Service Type is required.
Screenshots
After selecting "Community providers (In VA's network)":
Acceptance Criteria
DEV Note: we can potentially enable the field before getting an API response