Sarah L. Fossheim 
tech folks, what are your biggest blockers when it comes to accessibility? 
Noah Liebman@fossheim getting over the hurdle of “learning to use a screen reader sounds daunting” so I try to rely on best practices and dev tools’ representations of the accessibility tree even though I know I should put in the time to get proficient with at least one SR
Christian Niklas@fossheim Having managers or other decision-makers whose first question is when it comes to accessibility: How much would it cost if we were sued for lack of accessibility?
meduz'@fossheim Having someone else than myself to validate that what happens in the browser is decent for people having regular usage of assisting technologies.
Daniel Rotter@fossheim The urge to use frontend frameworks even though a plain HTML returned from the server would also do the job.
Angelika Cathor@fossheim Oh boy, where do I start...
1) Working on "fullstack" teams that are in reality just 3 backend devs in a trench coat that aren't really interested in improving their frontend skills.
@fossheim 2) I don't know what to say to my coworkers that use Linux when they ask how to install and test with a screenreader.
3) I don't have access to a windows device to test with one of the popular windows screenreaders, I only test on VO on a mac.
@fossheim 4) As a dev, negotiating with designers when I notice during development that their designs are making "the right thing" harder to implement (I feel bad for not noticing those things earlier)
@fossheim 5) The prevalence of SPA frameworks and also Phoenix LiveView that make focus management a big problem in apps that don't really need to be a SPA
Virginie@fossheim not having accessibility part of the development process and making accessibility an after-thought of something that will be taken care of when there is some bandwidth (the last week of the year usually) and having the difficulty of testing in real life conditions being used as an excuse for not committing (aka the classic “we can’t be 100% accessible so let’s think for ages about who and what we should prioritize”)
@fossheim I once needed the tables of a datatool I was building being accessible. We reached out to a service to get feedback on our work from employees with disabilities and I learned that the way I was thinking my design and how our design system components were built were not compatible with a really accessible solution. Despite deadlines being tight, we estimated what the changes will represent, prioritized, delivered. Lean UX and CI/CD helped us staying confident and calm.
@fossheim if I was to do it again, I would make the design system components checked/audited for accessibility beforehand and make sure that accessibility concerns are included in the product discovery.
I would also make sure the team can meet and chat with some users who might benefit from an accessible tool to increase empathy (persona are nice but human contact is very impactful)
I would also make sure the team can meet and chat with some users who might benefit from an accessible tool to increase empathy (persona are nice but human contact is very impactful)