Show that accessibility is part of your development process, not a separate phase. Mention specific tools you use and WCAG levels you target.
Strong answers include: semantic HTML, ARIA attributes when needed, keyboard navigation, colour contrast, screen reader testing, alt text for images, and testing with tools like axe or Lighthouse. Best candidates treat accessibility as a core requirement, not an afterthought, and mention WCAG guidelines and legal requirements.
Increasingly expected of frontend developers. Candidates who dismiss accessibility or have never considered it are missing a fundamental skill. Ask for a specific example of an accessibility issue they found and fixed.