This is related to #1040.
I'm wondering if the UX would be better if instead of this:
- fill form in a rush, but fail to notice the tiny red asterisks in some fields
- click "save"
- page reloads
- see validation errors
- fix errors
- click save again
...we provided a better UI that guided people to this: 1. fill form in a rush, but still fill in required fields because "required" indicators are bigger and made more prominent -> get a "live" feedback/indication that you've done the right thing 2. save -> win! (at least less chances that you've done something "wrong")
Something like this:
Here's another set of screenshots to demonstrate do's and don't's with regards to accessibility:
Recent comments
This is helpful. When I Googled for suggestions about the error message, I found an old entry in Stack Overflow that suggested increasing max_connections. I passed that along to the hosting...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?
Thanks for the suggestions. All caches have been enabled from the start. I'm not sure what qualifies as a "complex" view. There are 400-500 pages that include EVA fields. But the vast...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?
Also, when we had some problems with the Backdrop sites, this is what the server admin did: I have increased the max_connections for mariadb and increased the child_processes for...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?