4 ms·

It most likely needs a smaller team than they used to have, but some dedicated employees are necessary. Accessibility should be part of every design team. Any

It most likely needs a smaller team than they used to have, but some dedicated employees are necessary. Accessibility should be part of every design team. Any new features being developed need accessibility input. This includes all the different mobile apps and integrations with native accessible platforms and accessibility tools. It also needs full internationalisation and language support too, which increases complexity. It needs a few more people than just ticking boxes or building workarounds or ramps after a feature has been developed. Additionally, Twitter also takes in external links from webpages and so can influence the meta markup of these via their API / open graph / social sharing. So it works on the wider web accessibility standards too. I imagine bootstrap and all the other libraries twitter publishes are also part of the teams remit.

exodust 4y ago
> "Accessibility should be part of every design team" Yes but that doesn't mean dedicated people. Accessibility knowledge is already well understood by designers and developers, particularly at the big end of town. The previous team would have presumably written plenty of documents and guidelines and generally fostered a culture of thinking about accessibility. No reason why that will disappear. Patterns and best practice methodologies are common in tech, precisely for efficiency reasons. They belong in standards, and shared knowledge - which is better for the industry as a whole. If every small team needed dedicated accessibility staff, the system is BROKEN.