-
Notifications
You must be signed in to change notification settings - Fork 11
Views
Entry-point with links to the important sections of the site. Main tool will be the search field from which users will look for data.
Address view shows data divided into 2 sections with tabs.
- Services for current address which shows most integral services (like schools, hospital etc) for people living in this address.
- Close-by - which shows a list of all units close to current address
We are using tabs to divide information to give best browsing experience for screen readers.
- Area tab will be moved to it's own view and address view will offer a link to it
- Add most common services tab for address view similar to old UI version
- Make markers and clusters same size so clusters don't overshadow markers. Also both need to be bigger than transit markers since we want unit markers to be more recognizable on map. 07.02.2020
Search view is the primary way for browsing data.
- We decided to remove Close-button from settings snackbar because people assumed it closed whole settings window rather than snackbar itself. Also we decided that this wouldn't cause problems since user at this point would be leaving settings or if they decide to change settings snackbar would disappear. 07.02.2020
Unit view lists the following details of a unit:
- Image
- Highlights
- Contact information
- Address
- Opening hours
- Phone numbers
- Contact persons
- E-services
- Unit description
- Service categories
- Accessibility shortcomings and information
- Events
- Reservable objects
Main concern when creating unit view was how to divide unit data in more digestible chunks. After going through different iterations with the help of accessibility consultants we've decided on using tabs for dividing content. This gives screen readers good preview to incoming content by first selecting desired tab. Tabs also remove need for dynamic elements like accordion-elements. For accessibility's sake we want to keep the content as static as possible in order to avoid confusion for screen reader users.
Events and reservable objects required a new page for browsing data. Initially we tried using dynamic loading for these information sets. But it ended up becoming unusable for screen readers. We decided that a paginated listing was the best solution. Having 2 paginated lists within a single tab made the page hard to navigate with screen readers. In the end we decided the best solution would be showing only small amount of data and giving user option to start browsing data in a separate page.
- Clicking "show more events/reservable objects"-button should take user to new browsing page and place focus on back button for easy navigation back. Browsing page's back button click should place focus back to relative "show more..." button so navigation can continue easily and screen reader user doesn't lose sense of direction
Checklist
- Ensure headings are in correct level orders
Unit page sticky elements should have only tabs-element. This because on devices with smaller heights usable area get too small. 07.02.2020
Unit's events moved to own page. Events were originally loaded gradually (10 at a time) by pressing button. This caused problems with screen readers and moving user's focus back to last list item was problematic especially with long fetch times.
- We decided to move unit's events to their own page. 20.01.2020