Accessibility needs to be part of the
conversation too.
You don't need to become an accessibility expert, but you should feel confident asking your web agency how they've considered and tested accessibility.
These 10 questions are a good place to start.
QUESTION 1
How has accessibility been considered throughout the project?
Accessibility should not suddenly appear in the final week before launch. Ask how it has been considered during planning, design, development and content creation.
You are looking for evidence that it has been part of the project from the start, rather than something added at the end.
QUESTION 2
What accessibility testing have you carried out?
Ask what testing has taken place.
Has the agency used only automated tools, or has it also done manual testing?
Automated tools are useful, but they only find some accessibility problems. They cannot tell you whether someone can use the website successfully.
QUESTION 3
Has the website been tested using assistive technology?
This is an important one.
Ask whether anyone has tested the site using technology such as screen readers, magnification or keyboard navigation.
I use screen readers and magnification myself, and this kind of testing can uncover problems that are very easy to miss when you are simply looking at a page on screen.
QUESTION 4
Have the most important user journeys been tested from start to finish?
Think about what people need to do on your website.
For a charity, that might include finding support, completing an application form, donating, applying for a job, volunteering, or contacting the organisation.
Ask whether those journeys have been tested all the way through. A homepage can work well, but a form at the end of the journey can create a barrier.
QUESTION 5
Have forms been tested properly?
Forms are often where people get stuck. Ask whether the agency has tested things like labels, instructions, error messages and what happens when someone misses a required field.
It is not enough for the form to technically submit.
Someone needs to understand what is being asked, know when something has gone wrong and be able to fix it.
QUESTION 6
Have third-party systems been included?
Many websites send people onto other platforms.
That might include donation systems, recruitment websites, booking systems, CRM forms, event platforms, or payment systems.
Ask whether those parts of the journey have been considered too. Your organisation might see them as separate systems, but the person using the website does not.
QUESTION 7
Have downloadable documents been considered?
If your website includes PDFs, Word documents, reports, application packs, or guidance, ask whether they’ve considered accessibility there as well.
An accessible website can still lead someone to an inaccessible document.
For charities, that can matter a lot if the document contains information about support, eligibility, services or what somebody needs to do next.
QUESTION 8
Are there any known accessibility issues at launch?
This is a useful question because the honest answer may not be "none".
No website is perfect. What matters is whether the agency knows about any remaining issues, understands their impact and has a plan for dealing with them.
I would be more comfortable with a clear answer about known problems than a vague claim that the website is "100% accessible".
QUESTION 9
Who is responsible for fixing accessibility issues after launch?
Accessibility does not stop on launch day.
Websites change. New pages are added. Forms are updated. Documents are uploaded. New systems are introduced.
Ask who is responsible for fixing any accessibility problems found later and how those changes will be managed.
QUESTION 10
What happens when the website changes in the future?
This is the question that often gets missed.
A website may be tested before launch, but six months later it could contain new pages, new campaigns, new PDFs and new functionality.
Ask how accessibility will continue to be considered after launch. That might include internal checks, staff guidance, ongoing specialist support or testing when bigger changes are made.

This is not about catching your agency out!
A good web agency should be happy to have this conversation. The aim is not to turn the project into a test of whether they know every accessibility standard.
It is about making sure everyone is clear about what has been considered, what has been tested and where specialist input might still be needed.
Accessibility works best when the web agency, the organisation and accessibility specialists all understand where their responsibilities sit.

