🌻 accessibility:
✅ check focus state on the first item
alt text:
✅ clear button clear address finder
✅ received translations
✅ edit button: use 'edit address'
focus:
✅ on error after clicking an item in address finder/typing
✅ on results after clicking an item in address finder/typing
❌ on manual address fields after clicking that button (autofocus)
❌ on input after pressing clear
- don't want user to tab through everything before getting to the clear button - what if they have 60+ results?
If you need to alert your user to something urgently — for example to display an error message — use negative integers as your value. http://coop-design-manual.herokuapp.com/accessibility.html
UX input:
✅ annouce grey box- to indicate successful select address (decided to focus before)
✅ you have selected: xyzv hidden text on grey box
✅ confirm copy, ask for translations
⛔️ translations
✅ PROBLEM: it reads out everything. that feels like a lot...
⛔️ annouce: 'Keep typing your address to display more results' but change to be more... alerty?
✅ CLEAR button: bottom of tabbing order
✅ EDIT button: bottom of tabbing order
generally:
✅ check HTML for addressFinderItems list of buttons - accessibility
✅ grey background on hover items
✅ don't supress focus state
✅ breadcrumbs make no sense
✅ make the whole thing a button
✅ read: londonderry Remove
-
the user should know it's loading
-
the user should know results have appeared
-
the user should be able to select results
-
the user should know if there's been an error
steps taken:
-
good HTML (importance of lists)
-
annouces errors
-
focus state shows (was hidden by overflow-hidden before)
-
***aria-live: on the loading results
-
aria-label on edit button
- there was an alt tag on the img, but was ignored as a presentational thing