Technology

Audits and fixes for websites, web applications and documents. We test against WCAG 2.2 and check what ADA and Section 508 require for your situation. That covers keyboard navigation, screen reader behaviour, colour contrast, forms, captions and more. We also remediate PDFs to PDF/UA and help you prepare a VPAT or ACR if a buyer asks for one.

WCAG 2.2 is the technical standard, a published checklist of what accessible content looks like. ADA is the US law that lawsuits cite; it does not name a standard, but courts generally expect WCAG conformance. Section 508 applies to US federal agencies and their suppliers, and it references WCAG directly. Meet WCAG 2.2 AA and you are in reasonable shape for all three.

We agree a scope first: usually key pages or screens, templates, and the main user journeys like sign-up, search and checkout. Each is tested with automated tools, then manually with a keyboard and screen readers. You get a report listing every issue, where it occurs, which WCAG criterion it fails, and how to fix it, ranked by severity.

Both, your choice. Some clients want the audit report and fix things with their own developers; we answer their questions while they work. Others hand us the codebase and we do the remediation through Squash Apps. Document fixes we almost always do ourselves, since PDF remediation needs specific tooling.

Making PDFs work with screen readers and other assistive technology. That means proper tagging, a logical reading order, alt text on images, marked-up tables and form fields, and correct document metadata. PDF/UA is the ISO standard for accessible PDFs. We handle single documents and large batches: reports, forms, brochures, textbooks. Send a sample file and we will quote per document.

Yes. A VPAT is the template; the filled-in result is an Accessibility Conformance Report, which US government and many enterprise buyers ask for before purchase. We test your product against the relevant criteria, document conformance honestly, including partial support and known gaps, and produce the ACR. We do not write 'supports' where the product does not.

Yes. A retest pass is included in remediation projects, and we offer it separately if your own team did the fixes. We verify each reported issue, flag anything still failing, and update the report. Many clients also book a periodic recheck, every release or every quarter, because new code tends to reintroduce issues.

Emayyam is your point of contact; Squash Apps builds. They are our parent company, a custom software and AI firm with 500+ projects delivered and CTO-led teams. Typical flow: a scoping call, a written proposal with milestones, then development in sprints with a demo at the end of each. You deal with one team throughout.

For large or long-running builds: a full product, a dedicated team, or anything with heavy AI work. In those cases it is often simpler to contract Squash Apps directly at squashapps.com; they have offices in Coimbatore, Dubai and the US. For smaller builds, accessibility work, or projects bundled with localization or publishing, work through us. We will tell you honestly which route fits.

Web applications, portals, dashboards and APIs, mostly on current JavaScript and TypeScript stacks, with the usual databases and cloud platforms behind them. The honest answer is it depends on the project. Tell us what you run today and we will confirm whether the team has built with it before. If they have not, we say so.

No. A ten-page accessibility audit, a batch of twenty PDFs, a landing page fix: all normal jobs. Small projects are often how clients try us out before committing to bigger work. If a job is too small to need a formal proposal, we just quote it by email and get on with it.

Wireframes, screen designs, prototypes and design systems, plus reviews of existing products. The work is done with Squash Apps designers. It can be standalone, for example redesigning a portal your own team will build, or part of a development project. We factor accessibility into the design stage, which is cheaper than fixing it in code later.

Yes. Options range from a small monthly retainer for bug fixes and updates to ongoing feature development with a part-time or full-time team. Because operations run 24/7, we can also cover monitoring and out-of-hours issues. Maintenance is quoted separately at the end of a build, so you are not locked in upfront.

Fixed price for well-defined scope: audits, document batches, small builds. Time and materials where requirements will move. Retainers for ongoing maintenance. Every quote is itemised so you can see what each part costs, and the first consultation is free. We will not give a number before scoping, because guesses are how projects go wrong.

It depends on scope, so honest ranges: an accessibility audit of a typical site takes two to four weeks. PDF remediation runs days to weeks depending on volume. A small web application is usually two to three months. Larger builds are broken into milestones so you see working software early. The proposal includes a dated plan.

Email contact@emayyaminfotech.com or call +91 95008 89800. Tell us roughly what you need; a link to your site or a short description is enough. We set up a free consultation call, ask questions, and follow up with a written scope and quote. Nothing is billed until you approve the proposal.

Yes, on request and before you send anything sensitive. We can sign yours or provide a simple mutual NDA. Day to day, project files are restricted to the people working on your job, and we do not name clients or show their work without written permission.