Note that there's discussion in WP/GB via WordPress/gutenberg#16391 on overall accessibility of the snackbar, so we might perhaps review the consensus from a11y folks there and ensure we utilize the snackbar for error & success states in a solid a11y manner.

Looks like WordPress/gutenberg#67662 is an updated proposal in WP/GB that we might consider here as well.

@dkotter I have added a scroll-to-top to make error notices more visible. Regarding the Snackbar notice, as @jeffpaul pointed out, it has open accessibility issues. Since we have already added the scroll-to-top, I think we can replace it with a standard success notice combined with the scroll-to-top. However, I am not too concerned about this since the message we are displaying is not high priority. Additionally, the core itself uses Snackbar notices, and I have seen some plugins, such as ElasticPress, doing the same. what do you think?

Additionally, the core itself uses Snackbar notices, and I have seen some plugins, such as ElasticPress, doing the same. what do you think?

I'm fine with using the Snackbar here. We can always change this once there's a better option in Core.

I have added a scroll-to-top to make error notices more visible.

Thanks, this works great.

One last thing is how long the snackbar shows. If we can't reduce the time that shows (not sure if that's a setting that is supported by Core) I think we should at least remove the snackbar (if this is easy enough) anytime the screen changes.

As an example, if I enable a Feature, the snackbar shows. If I then click in to configure the settings for that Feature, ideally we remove the snackbar at that point.

Then when settings are saved, we show the snackbar again. If I go back to the main screen, that snackbar should be removed again.