# Auditing Accessibility of Pavements and Points of Interest in Urban Areas: The 'Seek & Go' Tool +
## 6 User Experience  
One of the primary challenges in completing surveys that require geolocation information is matching questions with identifiable entities on a map correctly. This can be a particularly arduous task when using traditional paper-based surveys. Even with electronic surveys that offer maps, the geolocation capabilities are typically limited to a single point, marked by a pin or, at best, an area defined by a polygon on the map. 'Seek & Go', however, offers a unique solution that significantly improves the user experience and provides increased functionality [48]. Based on usability testing and cognitive walkthrough, the development team identified, in the early stages of the implementation, usability issues that mainly concerned difficulties in handling the UI from small tablets. For this reason,the application focused on a tablet-first design, meaning higher tolerance on tap precision, smart drag and drop of the graphical elements on a map (e.g., pedestrian crossings, obstacles), which allows automatic placement to the correct position (sticky elements), introducing serializable actions for connecting segments only by tapping consequently buttons or graphical elements (such as sockets and plugs) and connecting entrances to segments via a single tap as the application calculates the nearest point and finds the closest element (i.e., pavement or pedestrian road) automatically. Users are provided with clear guidance on selecting the appropriate entity from a range of options, including street segments, POIs, segment connections, and POI/entrance connections. Upon making a selection, users are presented with simplified steps on the screen that facilitate the drawing of the area of interest by tapping on the map. To optimize the user experience, the application utilizes simple trigonometric calculations, leveraging the Turf library to restrict the movement of the drawing elements. This is particularly useful when users are interacting with the UI from a touch screen. The UI is thoughtfully designed to display relevant, simplified information based on the selected entity. To ensure that users adhere to appropriate rules, the application imposes additional restrictions to prevent undesirable actions, such as adding a pedestrian crossing where no two opposite pavements are defined in the working segment. An indicative screenshot of the application is shown in Figure 2 displaying a selected segment entity. The screenshot shows the currently unanswered surveys that correspond to the selected entity on the map, helping users to better identify missing input. In this specific example, the user has to complete surveys for two sidewalks, four obstacles, and three pedestrian crossings. Each entity featured on the map corresponds to a distinct survey, which has been designed to gather pertinent accessibility information. Specifically tailored questionnaires have been developed for each of the four major entities, namely street segments, POIs, segment  
Figure 2: Screenshot of the ‘Seek & Go’ application highlighting a selected segment with its corresponding list of surveys remaining to be completed (marked in red). For better understanding, the text is auto-translated from Greek (except names of the streets which are shown in Greek as provided by Google Maps), and it might contain inconsistencies and grammatical and/or syntactical errors. connections, and POI entrances. The questionnaires capture all requisite accessibility details, including information for obstacles and ramps on pavements, accessibility infrastructure in buildings, slope angles, opening widths, and unique signaling for the visually impaired. From the UI perspective, selecting a survey highlights its corresponding element on the map while emphasizing their relationship. Additionally, dynamic rules are applied within the surveys based on user responses. For example, when a wheelchair ramp is available, supplementary questions relating to the ramp are added.