Diaries of Senior UI/UX Designer Desarae Veit who loves to read, write, travel, and so much more. Hobbies include aviation, yoga, scuba diving, barre, and art or craft projects. Blog includes Book Reviews and Gadget Reviews.
Secure and Accessible: Where Accessibility and Security Intersect — Oct 22 at 2 PM ET, from Accessible Web.
This tension is real in government work: CAPTCHAs, short timeouts, and login rules that block password managers can improve security on paper while locking actual users out.
Worth attending for teams building services everyone has to use.
https://accessibleweb.com/category/accessible-web-events/accessibility-webinars/
An error message that only says 'invalid input' is not helpful. It is a dead end.
Actual users know something went wrong. What they do not know is where, why, or how to fix it without starting over.
WCAG in plain English: identify the field in error, describe the problem in text, and suggest a correction when one is known. Do not rely on color alone. Do not clear the form. Do not move focus somewhere confusing and hope people find their way back.
We test it this way: submit an incomplete form on purpose, with a keyboard and with a screen reader. Can someone find every error, understand each one, fix it, and resubmit without re-entering good data?
If not, the error handling is not finished.
Clear errors are not polish. They are how a service respects people's time.
Painting teaches restraint that interface design usually has to learn the hard way.
On a canvas, every extra color competes. Add one more and the whole piece gets louder, muddier, harder to read. The painting does not need more. It needs a decision about what matters most, and everything else placed in service of that.
Interfaces fail the same way. Every extra button, badge, banner, and pop-up competes for attention. Nothing stands out when everything is shouting. Actual users pay the price in scanning, confusion, and missed next steps.
So the craft question is the same in both places: what is the one thing this surface is for?
Cut what competes with it. Keep what supports it. Leave enough quiet space for the important thing to be found quickly.
Restraint is not minimalism for its own sake. It is respect for the person on the other side.
The 42nd CSUN Assistive Technology Conference is March 8-12, 2027, in Anaheim — and 2027 adds a new Innovation Track for emerging ideas and early-stage technology.
That track matters. Accessibility innovation needs testing by actual users and experts before it becomes a product claim, not after.
Worth planning for now, especially for public-sector teams building at scale.
https://conference.csun.at/event/2027/summary
Flexibility is not a virtue in a component library.
Give a team twenty ways to build a modal, and twenty different focus behaviors ship with it. One traps focus correctly. One loses it behind the page. One never returns it at all.
That is why we build highly opinionated components.
A modal in our system has one job and one pattern: focus moves in on open, stays inside while it is open, returns to the trigger on close, and the close control has a real, visible label. No toggles for any of that. No advanced settings that turn it off.
Designers still get room where room matters — content, layout, hierarchy. They do not get room to break keyboard access by accident.
Constraints are not the opposite of good design. Handled well, they are how good design ships the same way, every time, for actual users.
