Accessibility is cheapest when it is part of the foundation rather than a late audit.
Start with semantics
Use the right HTML elements. Buttons, links, headings and landmarks give assistive technology what it needs without extra code.
Build it into components
Accessible components with keyboard handling, focus management and sufficient contrast mean every feature built on them inherits good behavior.
Test continuously
Combine automated checks in CI with manual keyboard and screen-reader testing. Automation finds a portion of issues; people find the rest.
Make it a team habit
Add accessibility acceptance criteria to stories and review designs for color contrast, target size and reading order before development begins.