Right now, when we test drop-downs in Rails applications, we use a custom method to interact with the drop-down. This method behaves unreliably and does not seem to wait for Javascript to render, as Capybara matchers do.
I am not sure what makes it so that Capybara does not recognize the select, but I worry that this also means that people using screen readers and other assistive technology would have a difficult time using the select menus.
Acceptance criteria
[ ] The visual appearance of the select stays the same
[ ] You can use the select with a screen reader
[ ] Capybara's .select method recognizes the element as a select and can choose an option from it
What maintenance needs to be done?
Update the LuxInputSelect so that Capybara's "select" method works on it.
Level of urgency
Why is this maintenance needed?
Right now, when we test drop-downs in Rails applications, we use a custom method to interact with the drop-down. This method behaves unreliably and does not seem to wait for Javascript to render, as Capybara matchers do.
I am not sure what makes it so that Capybara does not recognize the select, but I worry that this also means that people using screen readers and other assistive technology would have a difficult time using the select menus.
Acceptance criteria
Implementation notes, if any
This ticket blocks https://github.com/pulibrary/approvals/issues/1165