Throughout my career as a frontend developer, I have constantly seen designers sketch out components without talking to the developers. This will ever so often result in flawed accessibility, shitty code, and a list of bugs in the backlog.
This article will cover how to handle complicated UI componentes, like:
Modals
Carousels
Autosuggests
Date pickers
Custom selects
This article is not a guide how to code these components, it's rather providing real arguments for not implementing them.
The whole team should be aware of the complexity of these components when it comes to:
Keyboard interactions
Audio feedback to AT
Valid and semantic html
Almost anything is possible if you have a lot of time and money. But no client ever said: "we have a lot of time and money".
To save time, developers will use npm packages. I will touch on that too.
Outline
I have Google Docs document and I can send you a link if sounds interesting.
ericwbailey
commented
1 year ago
A brief a11y guide to troublesome UI components
Throughout my career as a frontend developer, I have constantly seen designers sketch out components without talking to the developers. This will ever so often result in flawed accessibility, shitty code, and a list of bugs in the backlog.
This article will cover how to handle complicated UI componentes, like:
This article is not a guide how to code these components, it's rather providing real arguments for not implementing them. The whole team should be aware of the complexity of these components when it comes to:
Almost anything is possible if you have a lot of time and money. But no client ever said: "we have a lot of time and money". To save time, developers will use npm packages. I will touch on that too.
Outline
I have Google Docs document and I can send you a link if sounds interesting.
Terms