Website Redesign & Conversions
Include Accessibility in the Redesign Scope From the Start
Plan keyboard use, contrast, labels and content structure during design. Avoid treating accessibility as a final automated score.
In this guide
Accessibility problems are more expensive to untangle when they are embedded in approved layouts and custom components. A redesign brief should include how people use the website, not only how it looks in a screenshot.
Agree on practical requirements
Review the audience, content and important journeys. Include keyboard access, visible focus, readable contrast, labels and understandable error handling. Relevant legal or contractual commitments need to match the actual project and appropriate professional advice.
Review components in different states
A closed menu may look accessible while its expanded version traps focus. A form may have clear labels but inaccessible errors. Test the states visitors use rather than inspecting only the default design.
- Use a logical heading structure.
- Keep informative image alternatives meaningful.
- Check controls without a mouse.
- Review text enlargement and mobile layouts.
- Include manual checks alongside automated tools.
Ask for evidence at approval
A supplier can show a keyboard walkthrough of the contact journey and the resolved contrast issues. An automated scan is useful supporting evidence, not proof that every requirement or user need has been met. Avoid calling a website certified without a real basis.
Keep maintenance in scope
New content, widgets and third-party embeds can introduce later barriers. Document the authoring practices and testing responsibilities the business should retain. Accessibility is stronger when it is part of ordinary website work rather than a badge added at launch.
Need help putting this into practice?
Tell Nithu what your website needs and which systems are involved. The next step is a review of the requirements and an agreed scope, with any paid tools or ongoing costs explained before work.