Throughout web view, the UI has a deficiency which I feel detracts from the usefulness and user experience. My issue is with what happens (or, rather, doesn't happen) when the user clicks a "button".

To be more specific, throughout the web view experience, when one clicks a button to perform an action or task in the system, there is no visual response from that button. In my experience, throughout a broad range or web browser applications, pages, and systems, there is generally some responsiveness a user comes to expect when clicking a button. This observation includes BOTH the initial HOVERING over a button (some of them respond to a hover, but many vital buttons throughout the system do not), AND the visual 'depression' response one expects when clicking the button.

Again, this is a pretty universal experience throughout all of web view, but I will give some concrete examples:

• Logging in! The initial user name page has a "Continue" button, which IS responsive, but the next page in which you enter your password has a "Sign In" button, which is not responsive in any way. Why would these two buttons behave differently? Seems like a simple oversight.

• Approving a batch. When an approver is in a batch, there is an "Approve" button at the top of the page. After review is completed, I scroll back to the top and click the "Approve" button. There is usually an extended latency period after doing this, but there is no indication whatsoever that the system is working to register the approval. No signature Blackbaud spinning wheel in screen's center OR lower right corner job status pop up. This is quite confusing for the user, and I often don't know how long I'm supposed to wait before either re-attempting to click or leaving the page to move on to my next task.

• Reporting and exporting. An especially challenging case is when one has run the initial report, but then selects "Export Excel data". From here, the signature lower right job status pop up happens. When it's completed, the user gets a "Download" button. This button DOES respond to hover, but when actually clicked, there is no depression. This gets pretty confusing when you have an especially 'heavy' report, because it can take a long time to download, and again there is absolutely no indicator to let the user know it did in fact register the click and you just need to be patient. Many times, I have waited a while, then clicked again, then later realize I ran it multiple times and that just contributed to the latency.

This may sound petty or insignificant, but I will argue that is matters more than you may think. A user needs to know they have actually accomplished the "click" as desired. I was a very early adopter of web view, so I have a lot of experience here, and I can't tell you how many times I've had the experience of clicking to perform an action (for example, running a report, exporting the results, Approving a batch), and, after waiting a few seconds, having no idea whether or not the click actually registered. At times I've caused glitches because I try to perform the process again, but it turns out it was already attempting to run, and by inducing a second click I have caused an error.

This seems like it could be an 'easy win' for Blackbaud to improve the user experience - especially as you continue to build up RE web view and the same code features can be applied to both systems. Thanks for thinking about this!