Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Accessibility - new icons only 34 px high vs. WCAG standard of 48 px - SAF-696

  • “FAQ” and “Report an issue” links don’t do anything when clicked on .- SAF-691

  • Problems with feature flags

    • Export e2e - when turned off no longer gives the ability to export JSON data - the interface still goes to the new sharing with HA flow. - SAF-692

    • Exposure mode still puts the home screen into dark mode, but does not populate any fake data for the Exposure History page - which I believe it used to do. Now the Exposure History page says “no known contact”.

      • Actually this looks a bit more complex: behaviour depends on whether you have configured an HA already, whether you restart the app etc. - Needs more investigation

  • When I move context away from the app & back, “Exposure History” and “Your Healthcare Authority” titles end up too high up, off the top of the screen . - SAF-694

  • “About” screen can be scrolled up.down a short way, even though there is no content to scroll to.. - SAF-693

  • Privacy policy links to a file in Google Docs, which has the title “Mobile Application Privacy Policy (obsolete).” - SAF-695

  • I managed to make the App Hang playing around with Feature Flags, Exposure History etc. (also with some HAs configured). When I then restarted the app, it hung on the title screen. Every time I restarted it hung, so eventually I had to re-install it. This happened around 12:40pm local time (CET) I have not yet managed to reproduce this, but will try. I have adb logcat logsm logs but didn’t spt spot anything interesting yet. - needs more investigation

Existing bugs that are highly conspicuous:

...

Other observations

  • HA news pages have gone. I assume this is intentional? But Is that intentional? Is this coming back? - I will ask on Slack.

  • We still don’t have any way of telling what build we have installed (no build ID in the About page; no build identifiers in the filenames of the APKs we distribute). Have discussed with Tim before, but we need to address this. Tracked as SAF-520 already - have asked Jen about prioritizing this

  • I’ve not been able to generate an exposure notification with real JSON data yet. Not sure if this is a problem with my tools & data or the app. - to investigate


Various screenshots below.

Accessibility feedback on Touch Targets from Google Accessibility Scanner.

...