Treat accessibility as continuing website work
Accessibility should remain part of website maintenance, with redevelopment when the existing implementation needs improvement. The Frameworks refreshed the Estorick Collection website in 2017 to keep pace with changing technology, making it more accessible and responsive than its predecessor. The Frameworks subsequently continued to provide website maintenance for Estorick, rather than treating the refresh as the end of the work.
For teams managing a website, the practical approach is to keep designers and developers collaborating beyond launch and alert to technical changes. The Frameworks argues that more powerful browsers do not make inclusion automatic: accessibility and usability still require deliberate attention throughout design, development and execution.
A 2025 article in Smashing Magazine describes teams integrating automated accessibility scanners into continuous integration and using semantic roles and accessible names in UI tests to help prevent regressions. Incorporating accessibility checks into ongoing development helps teams protect access as a website evolves.
Sources: The Estorick Collection at 25, Designing and developing web experiences for everyone