[x] Modify label text to Include State Route ramps, spurs, couplets.
[x] Change warning text to WARNING! Local roads and streets under state routes are not available.
[x] Make warning visible at all times (instead of only being visible when the checkbox is checked).
[x] Make checkbox label's style match the other labels. Currently is not bolded, etc.
“Also include non-mainline routes” was either not used or confused participants (severe issue)
Only the second participant check the “Also include non-mainline routes” option and fully read the warning message. The other did not check and use the information provided. Participant 2, however, felt the option told her the feature was not yet available and did not use if for applicable tasks.
All participants expected that the website was already displaying information for exits and local roads. Therefore, they were confused when restrictions they knew existed on ramps or local roads did not display on the map. This is a severe issue for usability. Based on participant behavior, most users will use the website with the impression that ramp and local road restriction details are available regardless to whether or not they check the “Also include non-mainline routes” option.
Four of the eight tasks required the use of the “Also include non-mainline routes” option. Of those tasks, 100 percent failed tasks 2, 5 and 6 because they did not use this feature. On task 7, 75 percent failed because they did not use this feature.
Proposed Solutions
Make it clear that ramp data is only available if they check the “Also include non-mainlines” option. Change the label to “include ramps” or something similar. Users did not associate “non-mainline routes” with ramps, even with the clarifiers of ‘ramps, spurs, alt., etc’ listed after the option label.
Long-term
The best solution is to postpone the launch until local road data is available, such as data for under a state highway. All participants expected this information to be available. When they did not see colored dots indicating restrictions on the map, some users misinterpret the lack of restriction dots as meaning there were no local road or state highway ramp restrictions. The majority of users either do not notice the local agency contact link in the left navigation (results list) or the results list does not appear during the search, which leaves users without a way to navigate to the local agency contact list if needed.
Cannot postpone
Short-term
As data for these roads may not be available until next spring, users need to know that local road information is not available. Add a message on the site that appears at all times (not conditionally displayed when an option is selected) warning users that only data for state highways and interstates will be displayed, and to contact a local agency contact to plan a trip on local roads. However, user may still miss this information and expect to see local restrictions on the map.
“Also include non-mainline routes” was either not used or confused participants (severe issue)
Only the second participant check the “Also include non-mainline routes” option and fully read the warning message. The other did not check and use the information provided. Participant 2, however, felt the option told her the feature was not yet available and did not use if for applicable tasks.
All participants expected that the website was already displaying information for exits and local roads. Therefore, they were confused when restrictions they knew existed on ramps or local roads did not display on the map. This is a severe issue for usability. Based on participant behavior, most users will use the website with the impression that ramp and local road restriction details are available regardless to whether or not they check the “Also include non-mainline routes” option.
Four of the eight tasks required the use of the “Also include non-mainline routes” option. Of those tasks, 100 percent failed tasks 2, 5 and 6 because they did not use this feature. On task 7, 75 percent failed because they did not use this feature.
Proposed Solutions
Make it clear that ramp data is only available if they check the “Also include non-mainlines” option. Change the label to “include ramps” or something similar. Users did not associate “non-mainline routes” with ramps, even with the clarifiers of ‘ramps, spurs, alt., etc’ listed after the option label.
Long-termThe best solution is to postpone the launch until local road data is available, such as data for under a state highway. All participants expected this information to be available. When they did not see colored dots indicating restrictions on the map, some users misinterpret the lack of restriction dots as meaning there were no local road or state highway ramp restrictions. The majority of users either do not notice the local agency contact link in the left navigation (results list) or the results list does not appear during the search, which leaves users without a way to navigate to the local agency contact list if needed.Cannot postpone
Short-term
As data for these roads may not be available until next spring, users need to know that local road information is not available. Add a message on the site that appears at all times (not conditionally displayed when an option is selected) warning users that only data for state highways and interstates will be displayed, and to contact a local agency contact to plan a trip on local roads. However, user may still miss this information and expect to see local restrictions on the map.