Specify the accessible deliverable before work starts

What happened: In July 2025, a language-services buyer returned delivered material after reporting missing alternative text and an accessibility failure. MoniSa asked for translated alternative text and source files. In April 2026, the accessibility step was agreed, but the cost was not confirmed because the total page count was not defined. The record shows neither a corrected deliverable nor buyer acceptance.

Dated outside evidence: The World Wide Web Consortium's Web Content Accessibility Guidelines (WCAG) 2.2, Recommendation of 5 October 2023, includes criterion 1.1.1 on text alternatives for non-text content, with defined exceptions. It concerns web content; citing it does not establish compliance of a delivered workbook or document. The US Access Board's final rule, Information and Communication Technology (ICT) Standards and Guidelines, published in the Federal Register on January 18, 2017, sets the Revised Section 508 Standards. These Standards bind federal agencies and incorporate WCAG 2.0 Level AA by reference for covered web content and electronic documents, subject to stated exceptions. A buyer may apply them by contract; the return record does not establish that the end client was a federal agency. For WCAG 2.2 criterion 1.1.1: W3C, Web Content Accessibility Guidelines (WCAG) 2.2 (5 October 2023).

What it suggests (inference): Translation of visible text and preparation of an accessible deliverable are different scope questions. The record does not prove whether accessibility had been agreed at the outset. The public guidance supplies a concrete question about non-text content rather than proof of the cause of this return.

What to check: Attach the intended output format and applicable accessibility requirements to the quote request. Identify who supplies, translates and checks alternative text, and which editable source files are available. Record any unresolved source-file or volume assumptions and the approval needed if those assumptions change. Agree how the actual output will be checked.

Separate correction work from evidence of acceptance

What happened: In February 2022, a language-services buyer reported that edits were not visible in reworked files and referred to a similar problem in an earlier delivery. The record establishes the buyer's report, not the cause of the missing edits or a later successful correction.

Dated outside evidence: The International Organization for Standardization's ISO 17100:2015, Translation services — Requirements for translation services, published May 2015, describes core processes and resources for meeting applicable translation specifications, including client specifications. Its public abstract does not prescribe a particular file-verification method. For the ISO 17100 abstract: ISO 17100:2015 — Requirements for translation services (2015).

What it suggests (inference): A promise to correct and a checked deliverable are different milestones. The operating record makes the handoff worth specifying; the standard's focus on applicable specifications supports agreeing the required output, without proving why the reported edits were absent.

What to check: Have the quote identify the delivered file version, the person responsible for applying corrections, the review handoff and the acceptance evidence. Distinguish correction of an agreed requirement from a new request that changes scope. Ask for verification in the delivered file, not an acknowledgement alone.

Prepare the translation requirement

Continue with the MoniSa pages relevant to the deliverable being quoted:

Define the deliverable and correction handoff

Advice drawn from the accessibility return and rework observations above:

  • Specify the intended file format and applicable accessibility requirements.
  • State who supplies, translates and checks alternative text.
  • Record source-file and volume assumptions that still need confirmation.
  • Identify the file version, correction owner, review handoff and acceptance evidence.

Claims without deliverable evidence

The cited records support caution about these conclusions:

  • A return for accessibility problems does not prove what scope had originally been agreed.
  • A report that edits are missing does not establish the cause.
  • An acknowledgement does not show that the corrected file was checked or accepted.

Make a scope change reviewable

Advice for approving the work and reviewing a returned deliverable:

  • Keep the agreed output requirements with the file version submitted for review.
  • Separate correction of an agreed requirement from an additional request.
  • Record who approves changed assumptions and who verifies the delivered correction.