# Accessibility.build - Sample Statement of Work Outline

This outline demonstrates the information used to scope an Accessibility.build professional-services engagement. It is not a signed agreement or legal advice.

## 1. Parties and contacts

- Client legal name and authorized contact
- Service provider: KHUSHWANT PARIHAR, sole proprietor operating Accessibility.build
- Service-provider GSTIN: 08FGIPP1206G1ZH
- Project, billing, security, and accessibility contacts

## 2. Objective

State the product, release, procurement, remediation, training, or documentation outcome the engagement is intended to support.

## 3. Scope

- Target standard and conformance level
- Websites, applications, documents, designs, or codebases
- Representative pages, templates, flows, states, and user roles
- Browser, operating-system, device, and assistive-technology matrix
- Test accounts and data supplied by the client
- Explicit exclusions

## 4. Method

- Automated checks used as supporting evidence
- Keyboard and manual interaction testing
- Screen-reader and responsive review
- Design, code, content, or document inspection
- Finding validation and severity approach

## 5. Deliverables

- Executive summary
- Finding register with reproducible evidence
- WCAG or other standards mapping
- Remediation guidance
- Readout, workshop, code review, or retest deliverables
- File formats and accessible delivery requirements

## 6. Schedule and dependencies

- Kickoff and access deadline
- Testing window
- Draft and final delivery dates
- Client review period
- Retest window
- Effect of delayed access or material product changes

## 7. Fees and payment

- Fixed package and approved add-ons
- Currency and applicable taxes
- Deposit and milestone schedule
- Payment method and invoice details
- Cancellation, rescheduling, and refund terms

## 8. Acceptance and change control

- Deliverable acceptance criteria
- Process for reporting an omission or factual error
- Written approval required for scope changes
- Additional pages, findings, flows, or retest cycles

## 9. Confidentiality, data, and security

- Applicable NDA or confidentiality terms
- Data categories and permitted processing
- Prohibited sensitive data
- Approved service providers
- Retention, return, and deletion expectations
- Security-incident contact process

## 10. Limitations

- The audit represents the agreed scope, version, environment, standard, and date.
- Automated testing alone does not establish conformance.
- The engagement is not legal advice.
- Product changes after testing may create new barriers.