I look at Indiana code requiring township trustees to provide insulin to those in need. That part of us is still here.

Went great. Recovering well. Should be out today even

github.com/joeldart/poe...
Talking to myself here. Appendix. They’re saying it’s a very routine surgery. Should be fine. And here we go

Choose your own adventure day lololololol

“Shift left” is prevention over correction. AI magic wands can’t backfill at the end. By educating the team early in the process, however, you will ship more complete work sooner #jsconf

So even with good prompts, copilot made errors. Great a11y is absent from the majority of training data, so you will need to inspect and test rigorously.
Axe-core, playwright, and humans with strong test plans.
Watch YouTube videos, learn how screen readers are used
#jsconf

Be sure you anticipate the errors and test edge cases (demo where a disabled button was ignored and not announced). Letter of the law is often not good enough. Good news was when sharing feedback with copilot, it had good suggestions
#jsconf

General loop
1. “What are some a11y suggestions?”
2. Test
3. Describe to copilot what you experienced
4. Implement next set of suggestions

The more clear you can be in your prompt, the better results you get. Pro tip there is a “foundational accessibility prompt” that Microsoft has shared
#jsconf

WCAG guidelines are very detailed but come down to
1. Perceivable
2. Operable
3. Understandable
4. Robust
#jsconf

This work is about removing barriers for your users. Requiring two hands example and benefits everyone. Example if you require two hands this is a barrier with a broken arm, a mother holding a child, a person holding a grocery bag. Lots of reasons for barriers and removing helps all
#jsconf

Platformatic/flame wraps it all up for you.
In production, you need a flame graph controller. Platformatic/Intelligent-command-center written to be this controller
#jsconf

Data dog has pprof which solves the inspector overhead.

react-pprof visualizes it it in webgl (fast, a11y, responsive, visual regression testing)
#jsconf

Tradeoffs in methods:
- Complex instructions
- overhead (inspector protocol)
- dtrace (requires root doesn’t work in docker)
#jsconf

It’s React/redux loop time, so the amount of time it takes from the Redux store update to all the components maybe re-rendering!

Future: we’re in the early stages. This is an interesting and important area to watch. Lots of big feelings. Lots of big unknowns. Even basic cases have no clear guidance.
Great talk
ryan-roemer.github.io/ai-vs-the-law
#jsconf

Spec-driven development. Generated code also doesn’t have copyright protections?
As developers continue to evolve, teams will need to determine if copyright protections are important
#jsconf