Accessibility is one of the Cross Functional Requirement(CFR), which I have mostly experienced as being taken care by a 3rd party service or its treated as 'not a must have'.

Ofcourse there are a lot of teams and companies that make accessibility as a part of feature develpment.

From the teams that I have worked on where we followed these 5 simple practices within our teams to make accessiblity practices as part of our ways of working :

1. Test with a screen reader

Screen readers read the text displayed on the website. You can use voice over tools to test if it reads the text and alt text on images if added. I use VoiceOver on Mac to test using screenreader.

2. Check the colour contrast

There are many people who experience colour very differently for example red/green colour blindless. Being red/green colour blind means people with it can easliy confuse any colours which has some red or green as part of the whole colour and so on.

3. Test using only keyboard

Testing by using only keyboard to input, navigate and for button clicks. Many users with motor disabilities will have issues using mouse so they rely on keyboard.

4. Automate accessibility checks

Automated testing is a way to find obvious errors but not enough to cover everything. There are many different tools like Axe-core, Lighthouse, Pa11y that can be integrated as part of pipeline.

5. Test using different user personas

Build different personas with different abilities and goals so you can use this while testing for accessbility.

These are few ways that can help teams to encorporate accessibility testing as part of the ways of working. And accessiblity is a shared responsibility, a teams responsibility.