“I’ve been told we need to be accessible.”
We help clarify the requirement, assess your application and work out what needs to happen next.
Make sense of the requirement
Accessibility for financial applications & portals
Accessibility is on your agenda.
Accessibility is on your agenda.
Let’s make the next step clear.
Whether you’re building a financial application or improving an existing portal, we help you understand the requirements, plan the work and make the changes in your code.
Trusted by financial services leaders
Selected work / Federated Hermes
Full accessibility. Required from day one.
Selected work / Federated Hermes
Full accessibility.
Required from day one.
A new Money Market Portal. An existing delivery team. We brought the accessibility expertise to help carry the work through.
6months
Delivery time
THE STARTING POINT
0Dedicated
accessibility owners
accessibility owners
0Accessibility specialists
in the client’s team
in the client’s team
Our expertise. Embedded in their team.
From the first assessment to the work that keeps accessibility on track.
Audit
- Assess the application
- Identify the gaps
- Set the baseline
Resource analysis
- Review skills & capacity
- Fill specialist gaps
- Agree ownership
Plan
- Define requirements
- Prioritize the work
- Plan delivery & tests
Implementation
- Join the delivery team
- Build & test changes
- Re-audit the results
Documentation
- Record test results
- Prepare the ACR using VPAT
- Support acceptance
Monitoring
- Check new releases
- Catch regressions
- Keep accessibility on track
01
(hidden)
Hidden placeholder step required by the CMS; the content above is rendered from Section text.
Find your starting point
What brought accessibility onto your agenda?
Find your starting point
What brought accessibility
onto your agenda?
You don’t need to know the terminology.
Start with the situation that sounds familiar.
“Can you join my delivery team?”
We bring accessibility expertise into your build or rebuild, while the application is taking shape.
Bring us into the project“I’ve been asked to get an audit.”
We assess the agreed journeys, identify barriers and explain what the findings mean for your team.
Start with an assessment“I already have an audit. Can you fix the issues?”
Yes. We can turn the findings into a delivery plan, then implement and test the changes in your code.
Turn findings into changes“They’ve asked me for a VPAT. Or Section 508.”
We help establish what your customer is asking for, what your product needs and what evidence to provide.
Understand what’s needed“I’ve received an accessibility claim.”
We can work with your team and legal advisers to assess the barriers and carry out technical remediation.
Plan the technical response01
(hidden)
Hidden placeholder step required by the CMS; the content above is rendered from Section text.
Choose how we work together
We can lead the work. Or join your team.
Choose the support that fits your situation.
We help you establish what is needed, plan the work and carry it through implementation and testing.
- 01
Understand what is needed.
We review the requirement and the evidence you already have. Where testing is needed, we assess the agreed journeys and documents.
You get: a clear view of the gaps and scope.
- 02
Make a plan your team can use.
We agree priorities, responsibilities, dependencies and release steps, including how the result will be checked.
You get: a delivery plan with clear ownership.
- 03
Build or fix the application.
Our specialists implement changes in your codebase, working with your developers and delivery process.
You get: changes made in your application.
- 04
Check the result and hand it over.
We retest the agreed scope, document the outcomes and establish how accessibility will be maintained.
You get: verification results and an agreed handover.
You have a delivery team. We bring the accessibility expertise.
First, we get aligned.
We review your requirements, existing findings, roadmap and responsibilities. We use what is already in place and flag any gaps before starting the changes.
- 03
Work inside your delivery team.
Our specialists join the work in your codebase, support implementation decisions and build accessibility into the application alongside your developers.
Our focus: specialist capacity for implementation.
- 04
Test the work. Support the release.
We test the agreed journeys, help resolve defects and document the results. Reporting and handover fit the project’s acceptance requirements.
Our focus: verification, evidence and handover.
01
(hidden)
Hidden placeholder step required by the CMS; the content above is rendered from Section text.
When your customer asks for more
Your customer’s requirements can become part of your delivery brief.
When your customer asks for more
Your customer’s requirements can become part of your delivery brief.
Whether you provide a financial platform or operate one for your customers, public-sector accessibility requirements can become part of your delivery brief through procurement or a contract.
Let’s clarify the requirement ↗What gets evaluated
Web Content Accessibility Guidelines: technical criteria used to assess digital accessibility.
508
Why it’s being requested
The Americans with Disabilities Act and Section 508 are different frameworks. Section 508 concerns federal technology and can appear in supplier requirements.
ACR
How results are reported
A Voluntary Product Accessibility Template becomes an Accessibility Conformance Report when completed with evaluation results. It reports what was found; it doesn’t replace the fixes.
01
(hidden)
Hidden placeholder step required by the CMS; the content above is rendered from Section text.
Technical support for accessibility claims
A claim to address? We can help with the work.
Facts
Assess the reported barriers and give your legal team a clear view of the findings, scope and gaps.
Plan
Define priorities, owners and milestones for your counsel to review and use in the response.
Remediation
Implement the agreed changes and retest the affected journeys.
Evidence
Prepare testing records, remediation updates and agreed conformance reporting.
Your legal team leads the response. We support them with technical expertise and delivery.
01
(hidden)
Hidden placeholder step required by the CMS; the content above is rendered from Section text.
You don’t need a finished brief to have a useful conversation.
Let’s work out the next step. Tell us what you’ve been asked to deliver, where the project stands and what your team needs help with.
"They are authentic and always go above and beyond to deliver for us".
A few practical questions
How would you work with my team?Keep the strengths you already have. Bring us in where you need support.
-
Can we do this internally?
Yes, if your team has the specialist knowledge, time and ownership to implement and test the work. We help where expertise, capacity or coordination is missing. AI and automated tools can support the work; the team still needs to verify the results.
-
Do we need another audit?
Not automatically. We review the findings and evidence you already have. If they provide a useful basis for delivery, we use them and assess any remaining gaps.
-
Will we have to rebuild the application?
Not necessarily. We assess the product and the changes it needs. A rebuild should follow a technical and commercial decision, not an assumption that every accessibility issue requires one.
-
What do we have at the end?
The agreed implementation, verification results and a handover explaining the scope, outcomes and ongoing responsibilities. Reporting and acceptance requirements are agreed at the start.
-
Can you deliver our project in six months?
The FHI accessibility phase took six months. Your schedule depends on scope, access, dependencies and the release process. We establish those before committing to a delivery date.
-
What happens after launch?
We agree who owns ongoing accessibility, how changes will be checked and what support is needed to catch regressions as the application evolves.