Accessibility Conformance Report

Revised Section 508 Standards · WCAG 2.1 Level A and AA

This is a published sample — the report as it stood before remediation. RENDUN LIMITED produced it for its own service, CertMyTranslation, and published it unedited. Five criteria came out at Does Not Support, including one that meant keyboard-only and screen reader users could not place an order at all. All five were corrected the same day.

The report produced after the fixes · About these reports

Product

Name
CertMyTranslation (certmytranslation.com)
Description
Public web application for ordering certified document translations.
Version
Evaluated 2026-09-09 (before remediation)
Report date
2026-09-09
Evaluated by
RENDUN LIMITED (third party)
Contact
support@rendun.co

Evaluation methods used

Ten pages covering every distinct page template were evaluated: the home page and order tool, the primary service page, a document-type page, a language page, the photo-check tool, the multi-page document page, the article index, a long-form article and two legal-text pages.

Each page was tested with axe-core 4.13, a deterministic evidence pass (heading and landmark structure, language, image alternatives, link text, form labelling, 320 px reflow), a 40-step keyboard traversal, keyboard interaction and form-submission probes, and a virtual screen reader reading-order capture. Every criterion reported as Does Not Support or Partially Supports was then verified by hand against the live pages before being entered here.

Applicable standards

WCAG 2.1 Level A and Level AA, as incorporated by the Revised Section 508 Standards (36 CFR Part 1194, Appendix A).

Terms

Supports
The functionality of the product has at least one method that meets the criterion without known defects.
Partially Supports
Some functionality of the product does not meet the criterion.
Does Not Support
The majority of product functionality does not meet the criterion.
Not Applicable
The criterion is not relevant to the product.

Summary

Supports
23 criteria
Partially Supports
9 criteria
Does Not Support
5 criteria
Not Applicable
13 criteria

Report

Table 1: Success Criteria, Level A
CriteriaConformance LevelRemarks and Explanations
1.1.1 Non-text ContentSupportsImg has proper alt text; sample-deliverable.png alt descriptive.
1.2.1 Audio-only and Video-onlyNot ApplicableNo audio/video media found on page.
1.2.2 Captions (Prerecorded)Not ApplicableNo media elements present.
1.2.3 Audio Description or Media AlternativeNot ApplicableNo media elements present.
1.3.1 Info and RelationshipsPartially SupportsHeadings, lists and tables are correctly structured and the reading order matches the visual order. However the upload control's instructions are not programmatically associated with the control (see 3.3.2). Affects the 6 pages carrying the upload tool.
1.3.2 Meaningful SequenceSupportsReading order matches visual/logical order per SR announcements.
1.3.3 Sensory CharacteristicsSupportsNo instruction relies solely on shape, size, visual location or sound. The evidence the automated layer attached here (colour-only links) belongs to 1.4.1 and is reported there; it is not counted twice.
1.4.1 Use of ColorPartially SupportsIn-paragraph links are distinguished from surrounding body text by colour alone (axe-core 'link-in-text-block'), 2 to 4 occurrences on each of 7 of the 10 pages evaluated. Navigation, footer and card links are not affected.
1.4.2 Audio ControlNot ApplicableNo audio content present.
2.1.1 KeyboardDoes Not SupportThe document upload control cannot be operated by keyboard. The file input is set to display:none and the .upload-zone container that receives the click has no tabindex and no role, so it is not focusable. Verified by traversing the live page: 80 consecutive Tab presses never reach the control, and the container cannot be focused programmatically. A keyboard-only user cannot start an order. Affects all 6 pages that carry the upload tool.
2.1.2 No Keyboard TrapSupportsKeyboard traversal completed without a trap on all ten pages.
2.1.4 Character Key ShortcutsNot ApplicableNo custom single-key shortcuts evidenced.
2.2.1 Timing AdjustableNot ApplicableNo time limits found on page.
2.2.2 Pause, Stop, HideNot ApplicableNo moving/auto-updating content found.
2.3.1 Three FlashesSupportsMarquee_blink=0, no flashing content.
2.4.1 Bypass BlocksPartially Supportsheader, nav and footer landmarks and a correct heading hierarchy are present on every page, but there is no skip link and no main landmark, so there is no direct mechanism to bypass the repeated navigation block.
2.4.2 Page TitledSupportsDescriptive title: Certified Translation Services....
2.4.3 Focus OrderSupportsFocus order follows DOM order on all ten pages and no focus is moved unexpectedly. The items the automated layer flagged referred to a dialog that does not exist in the DOM (dialogs_in_dom = 0 on every page).
2.4.4 Link Purpose (In Context)SupportsLink text, with its surrounding sentence, identifies each destination.
2.5.1 Pointer GesturesNot ApplicableNo path-based/multipoint gestures present.
2.5.2 Pointer CancellationSupportsNo down-event-only activation.
2.5.3 Label in NameSupportsVisible labels match accessible names where both exist.
2.5.4 Motion ActuationNot ApplicableNo motion-actuated features present.
3.1.1 Language of PageSupportsHtml lang=en; axe html-has-lang/lang-valid pass.
3.2.1 On FocusSupportsNo change of context on focus.
3.2.2 On InputSupportsSelecting a file starts the upload and reveals a price in place. This changes content but not context: focus is not moved, no new window opens and no navigation occurs.
3.3.1 Error IdentificationPartially SupportsClient-side validation of accepted file types and size is present. The error paths of the upload and payment flow were not exercised in this evaluation because doing so requires completing a live financial transaction; this is a stated limitation of scope.
3.3.2 Labels or InstructionsDoes Not SupportThe file input has no associated label element, no aria-label and is not wrapped in a label. The surrounding instructional text ('Upload your document', accepted formats, price) is presented visually but is not programmatically associated with the control, so it is not conveyed when the control receives focus.
4.1.1 ParsingSupportsReported as Supports in line with the September 2023 WCAG 2.1 erratum, which records this criterion as always satisfied for content using HTML parsers.
4.1.2 Name, Role, ValueDoes Not SupportThe file input exposes no accessible name. The .upload-zone div that acts as the visible control has neither a role nor an accessible name, so assistive technology cannot determine what it is or that it is operable.
Table 2: Success Criteria, Level AA
CriteriaConformance LevelRemarks and Explanations
1.2.4 Captions (Live)Not ApplicableNo live media present.
1.2.5 Audio DescriptionNot ApplicableNo media elements present.
1.3.4 OrientationSupportsNo CSS orientation lock; layout reflows in both orientations.
1.3.5 Identify Input PurposeNot ApplicableNo input field collects information about the user. The only control is a file input, and payment fields are rendered inside the payment provider's own frame.
1.4.3 Contrast (Minimum)Partially SupportsSecondary note text set in #6b7280 falls below the 4.5:1 minimum on 5 of the 10 pages evaluated. All primary body text, headings and link text meet the requirement.
1.4.4 Resize TextSupportsViewport meta is 'width=device-width,initial-scale=1'; scaling is not disabled.
1.4.5 Images of TextSupportsNo images of text other than the logo.
1.4.10 ReflowSupportsReflow_320_hscroll=0 at 320px width.
1.4.11 Non-text ContrastDoes Not SupportThe upload zone border, which is the only visual boundary of the primary control, measures 1.36:1 against its background (rgb(191,219,254) on rgb(248,250,252)) against a 3:1 requirement.
1.4.12 Text SpacingSupportsNo fixed line-height or letter-spacing that would clip text.
1.4.13 Content on Hover or FocusNot ApplicableNo hover or focus triggered additional content.
2.4.5 Multiple WaysSupportsTwo mechanisms are available on every page: the global navigation and the footer link lists, plus related-document links within the content.
2.4.6 Headings and LabelsPartially SupportsHeadings describe their sections throughout. The upload control has no label at all, which is the labels half of this criterion (see 3.3.2).
2.4.7 Focus VisibleSupportsFocus_style_differs true on nearly all tested links.
3.1.2 Language of PartsPartially SupportsThe language pages carry Spanish document names in running English text - 'Acta de nacimiento', 'Registro Civil' - with no lang attribute on those phrases, so a screen reader pronounces them with English phonetics. The document element is correctly marked lang='en' throughout. Unchanged by the remediation pass; it appears in both reports.
3.2.3 Consistent NavigationSupportsVerified across all ten pages: the first eight tab stops are identical in the same relative order on every page.
3.2.4 Consistent IdentificationSupportsComponents with the same function carry the same label on every page.
3.3.3 Error SuggestionPartially SupportsSame scope limitation as 3.3.1.
3.3.4 Error PreventionPartially SupportsThe order is a financial transaction. Price and page count are shown before payment and the published policy allows refunds, but the review-and-correct step could not be exercised without completing a live transaction; stated limitation of scope.
4.1.3 Status MessagesDoes Not SupportNo live region is present on any of the ten pages evaluated. Order and upload status is written into a static container, so status changes are not announced to assistive technology.

Limitations of scope

Error handling in the upload and payment flow was not exercised, because doing so requires completing a live financial transaction. Criteria 3.3.1, 3.3.3 and 3.3.4 are reported on the basis of the code paths visible without submitting an order, and are marked Partially Supports for that reason rather than because a defect was observed.