News for hackers. Stuff that matters.
Re:Phoenix.new – The Remote AI Runtime for Phoenix by miki123211 on Friday June 20, 2025 @01:46PM (#44330099)
1. What's your approach to accessibility? Do you test accessibility of the phoenix.new UI? Considering that many people effectively use Phoenix to write front-ends, have you conducted any evals on how accessible those frontends come out?

2. How do you handle 3rd party libraries? Can the agent access library docs somehow? Considering that Elixir is less popular than more mainstream languages, and hence has less training data available, this seems like an important problem to solve.

Re:Phoenix.new – The Remote AI Runtime for Phoenix by chickensong on Friday June 20, 2025 @04:06PM (#44331554)
It seems like they're giving you lower level building building blocks here. It's up to the developer to address these things. Instruct the agent to build/test for accessibility, feed it docs via MCP or by other means.
Re:Phoenix.new – The Remote AI Runtime for Phoenix by rramon on Saturday June 21, 2025 @01:16AM (#44334723)
They use the Daisy UI component library in 1.8+ Phoenix versions which should have basic accessibility baked in.