janadiamond

3 ms·

1.
Dashboards show results, not system health(protovate.com)
2 points by janadiamond 7mo ago|0 comments
2.
Why AI Isn't HAL 9000(blog.protovate.ai)
2 points by janadiamond 7mo ago|0 comments
3.
by janadiamond 7mo ago
Exactly. That’s the core of it. Accessibility isn’t really about one perfect design, it’s about whether the system can adapt to different real human needs instead of assuming one “normal” user. High contrast helps some people, hurts others.
4.
When Professional Looking Becomes Evidence(medium.com)
2 points by janadiamond 7mo ago|0 comments
5.
by janadiamond 7mo ago
Nope! Its not you! I'll point that out to the page manager and hopefully they will fix it. GREAT CATCH, thank you!!!
6.
by janadiamond 7mo ago
That makes sense. That “show everything at once” approach probably reduces some of the back-and-forth that hypermedia workflows rely on. It’s interesting that some models can infer structure from hypermedia more easily. That seems like anot
7.
by janadiamond 7mo ago
Interesting point. One thing HTML has going for it is that accessibility info (semantics, ARIA roles, structure, etc.) is embedded. Are you finding that agents can make use of that directly, or are you adding more accessibility metadata on
8.
by janadiamond 7mo ago
That curb cut example is a great example of the pattern. Improvements aimed at a specific accessibility need often end up benefiting more people than expected. While thinking about this, I realized that accessibility often acts like a kind
9.
by janadiamond 7mo ago
That’s a good point. Spelling, grammar, and punctuation can all affect readability. A lot of modern design trends assume perfect reading conditions and typical visual processing. When those assumptions break, accessibility issues start show
10.
Accessibility Issues Are Often Usability Issues(protovate.com)
17 points by janadiamond 7mo ago|18 comments