Try not to inherit accessibility debt when reusing code

Note: This post is older than two years. It may still be totally valid, but things change and technology moves fast. Code based posts may be especially prone to changes...

(Loaded 745 times)

Technical debt is also possible in accessibility and can easily grow when re-using code or components.

I have seen it (too) many times – new page / feature is required and it needs to be done fast. So what to do? Well couldn’t we just use existing code / component, tweak it a bit and deploy?

Works great with tight budgets, works great with short deadlines. Can also work great in general.

If…

If the initial code / component was accessible, that is.

Otherwise – the more you re-use inaccessible code / components, the more accessibility debt you introduce to your website / product.

So make sure – I can not emphasize this enough – that the original code / component is accessible, tested and verified – before you re-use it in new contexts. And in case you are maybe forced to go against common sense and copy & paste it instead of import from central source, then beware even more. If you had one inaccessible component before you now have two and the more they differ, the more debt you have inherited.

So – accessibility from start, test early and do not forget about the neighboring code / components as well.

Author: Bogdan Cerovac

I am IAAP certified Web Accessibility Specialist (from 2020) and was Google certified Mobile Web Specialist.

Work as digital agency co-owner web developer and accessibility lead.

Sole entrepreneur behind IDEA-lab Cerovac (Inclusion, Diversity, Equity and Accessibility lab) after work. Check out my Accessibility Services if you want me to help your with digital accessibility.

Also head of the expert council at Institute for Digital Accessibility A11Y.si (in Slovenian).

Living and working in Norway (🇳🇴), originally from Slovenia (🇸🇮), loves exploring the globe (🌐).

Nurturing the web from 1999, this blog from 2019.

More about me and how to contact me: