Post #2907432
2024-12-02 23:35 UTC
@philsherry@mstdn.social
> react dev uses spans instead of buttons "because then no css has to be overwritten"
> I point out during development it should be a button
> PM tells me there's no time to fix it
> repeat for a while with similar issues
> months later I'm asked to "make the product accessible now"
> every small fix has to go through sprint planning, development, two code reviews, QA, release notes
> management: "wow accessibility is expensive, let's pause this for a while"
> repeat
:elmo_fire:
Replies (1)
-
@philsherry@mstdn.social 2024-12-02 23:56
@fossheim@front-end.social Sigh. Very yes. As I say to people I work with: “If I’ve ended up on your team, it probably means you’ve done a lot of things badly and we’re at the wrong end of a deadline. But the good news for you is all the pressure’s on me now—not you—because I’ll be getting the blame—by management—for anything I label as an accessibility issue.“