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
SciSure 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 SciSure'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 on a compressed 6-to-8-week timeline against the regulatory compliance deadline with the pod delivering inside SciSure's engineering cadence rather than producing a last-minute compliance event.
22 high or critical WCAG 2.1 violations closing first in the severity-ordered delivery sequence with critical navigation and sidebar fixes landing in weeks 1 to 3 so the highest-risk customer-facing defects are resolved in the first half of the engagement 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 and no split between legacy. and modern platform compliance timelines, so the legacy Drupal and PHP platform and the modern Vue.js platform reach compliance together.
Component-level fixes propagating across every screen, rather than one-page-at-a-time patches that would have left regression risk on every new feature. so future product work built on the same components starts compliant rather than generating new defects.
Client-tool validation confirming every closed defect. so the compliance evidence at audit time matches what the scanner will produce and the regulatory deadline is defensible rather than hopeful.
SciSure engineering team ending the engagement stronger on accessibility. with remediation patterns, component-level fixes, and validation approaches visible inside the same Jira tickets, sprint reviews, and knowledge-transfer sessions the internal team runs every day, so accessibility practice is embedded rather than dependent on Armakuni.
Pod operating model proven as a reusable engineering partnership, ready to be restaffed against future modernization, feature engineering, or. platform refactoring scope without rebuilding the playbook or re-onboarding a new team from scratch.
Built on AWS
Delivered under our AWS Application Development, DevOps Services (confirm with delivery team before publishing) competencies.
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.