A scientific safety software platform for research institutions came to Armakuni for embedded engineering pod remediating 27 WCAG 2.1 accessibility defects across a legacy Drupal and PHP platform and a modern Vue.js platform ahead of a regulatory compliance deadline.
The challenge
A scientific safety software platform for research institutions faced 27 accessibility defects across two platforms against a regulatory compliance deadline that its internal engineering team could not absorb without pulling people off the product roadmap. Armakuni deployed an embedded engineering pod of 3 full-stack engineers and 1 QA engineer to remediate every defect in parallel across both platforms, operating inside A scientific safety software platform for research institutions's Jira workflow and sprint cadence as an extension of the internal team.
Scale: Two platforms serving research customers across the U.S., spanning a legacy Drupal and PHP stack and a modern Vue.js stack.
What we built
Armakuni delivered embedded engineering pod remediating 27 WCAG 2.1 accessibility defects across a legacy Drupal and PHP platform and a modern Vue.js platform ahead of a regulatory compliance deadline. The engagement ran as fixed-term embedded pod engagement. 3 full-stack engineers (full-time, 40 hours per week each) and 1 QA engineer (part-time, 20 hours per week). Invoices billed as monthly retainer paid in advance. AWS funded the work at $2,800.
The outcomes
7 measurable outcomes shipped across the engagement. The ones that moved the business the most:
27 accessibility defects on track for remediation across both platforms in parallel. Work runs on a compressed 6-to-8-week timeline against the regulatory deadline, delivered inside the platform's engineering cadence rather than as a last-minute compliance event.
22 high or critical WCAG 2.1 violations closing first. In a severity-ordered sequence, critical navigation and sidebar fixes land in weeks 1 to 3, so the highest-risk defects are resolved in the first half rather than held to the end.
Two stacks covered by a single pod of 3 full-stack engineers and 1 QA engineer. With no handoffs between specialist teams, the legacy Drupal and PHP platform and the modern Vue.js platform reach compliance on one shared timeline.
Component-level fixes propagate across every screen. Rather than one-page-at-a-time patches that leave regression risk on every new feature, future product work built on the same components starts compliant.
Client-tool validation confirms every closed defect. The compliance evidence at audit time matches what the scanner will produce, making the regulatory deadline defensible rather than hopeful.
The internal engineering team ended the engagement stronger on accessibility. Remediation patterns, component-level fixes, and validation approaches are visible inside the Jira tickets and sprint reviews the team runs daily, so the practice is embedded rather than dependent on Armakuni.
The pod operating model is proven as a reusable engineering partnership. It is ready to be restaffed against future modernization, feature engineering, or platform refactoring scope without rebuilding the playbook or re-onboarding a new team.
Built on AWS
Delivered under our AWS DevOps competency.
What's next
Architecture review and modernization roadmap follow-up sessions listed in the SOW as next steps. Pod model available to be restaffed against future engineering scope, whether modernization, feature engineering, or platform refactoring.