Revised Section 508 Standards · WCAG 2.1 Level A and AA
This is a published sample — the same product re-evaluated after remediation. The five Does Not Support findings in the earlier report were corrected on 9 September 2026 and the evaluation was run again from scratch. Seven criteria remain at Partially Supports and are named here rather than quietly dropped: three were outside the scope of that day's fixes, three could not be exercised without completing a live payment, and one covers foreign-language phrases that carry no lang attribute.
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.
WCAG 2.1 Level A and Level AA, as incorporated by the Revised Section 508 Standards (36 CFR Part 1194, Appendix A).
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | Img sample-deliverable.png has descriptive alt text; axe image-alt passes. |
| 1.2.1 Audio-only and Video-only | Not Applicable | Media: [] no audio/video content found. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | Media: [] no video content found. |
| 1.2.3 Audio Description or Media Alternative | Not Applicable | Media: [] no video content found. |
| 1.3.1 Info and Relationships | Supports | Headings, lists and tables are correctly structured, reading order matches visual order, and the upload control's instructions are now programmatically associated with it. |
| 1.3.2 Meaningful Sequence | Supports | SR reading order matches visual order per accessibility tree. |
| 1.3.3 Sensory Characteristics | Supports | No 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 Color | Partially Supports | In-paragraph links are still 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 templates evaluated. Navigation, footer and card links are not affected. Not addressed in this remediation pass. |
| 1.4.2 Audio Control | Not Applicable | No audio auto-play content found. |
| 2.1.1 Keyboard | Supports | The file input is now reachable by keyboard and operable with Enter or Space. Verified on the live pages: the control receives focus on the ninth Tab press from the top of the document, and the upload zone shows a visible focus indicator while it holds focus. The surrounding clickable container remains a mouse convenience; it duplicates an action that is fully available from the keyboard, so it is not a barrier. |
| 2.1.2 No Keyboard Trap | Supports | Keyboard traversal completed without a trap on all ten pages. |
| 2.1.4 Character Key Shortcuts | Not Applicable | No character key shortcuts evidenced. |
| 2.2.1 Timing Adjustable | Not Applicable | No timing limits found. |
| 2.2.2 Pause, Stop, Hide | Not Applicable | Live_regions empty; no auto-updating content. |
| 2.3.1 Three Flashes | Supports | Marquee_blink=0 no flashing content. |
| 2.4.1 Bypass Blocks | Partially Supports | header, nav and footer landmarks and a correct heading hierarchy are present on every template, but there is still no skip link and no main landmark, so there is no direct mechanism to bypass the repeated navigation block. |
| 2.4.2 Page Titled | Supports | Title: Certified Translation Services... present. |
| 2.4.3 Focus Order | Supports | Focus 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) | Supports | Link text, with its surrounding sentence, identifies each destination. |
| 2.5.1 Pointer Gestures | Not Applicable | No gesture-based interactions found. |
| 2.5.2 Pointer Cancellation | Supports | No down-event-only activation. |
| 2.5.3 Label in Name | Supports | Visible labels match accessible names where both exist. |
| 2.5.4 Motion Actuation | Not Applicable | No motion-actuated functions found. |
| 3.1.1 Language of Page | Supports | Html lang='en' valid; axe html-lang-valid passes. |
| 3.2.1 On Focus | Supports | No change of context on focus. |
| 3.2.2 On Input | Supports | Selecting 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 Identification | Partially Supports | Client-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 Instructions | Supports | The file input carries an accessible name ('Upload your document') and its instructions - accepted formats, size limit and price - are associated with the control through aria-describedby. |
| 4.1.1 Parsing | Supports | Reported 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, Value | Supports | The file input exposes a name and role. The contact panel is now marked as role=dialog with aria-modal and an accessible name taken from its heading, and focus returns to the button that opened it when it closes. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | No live media present. |
| 1.2.5 Audio Description | Not Applicable | Media: [] no video content found. |
| 1.3.4 Orientation | Supports | No CSS orientation lock; layout reflows in both orientations. |
| 1.3.5 Identify Input Purpose | Not Applicable | No 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 Supports | Secondary note text set in #6b7280 still falls below the 4.5:1 minimum on 5 of the 10 templates. All primary body text, headings and link text meet the requirement. Not addressed in this pass. |
| 1.4.4 Resize Text | Supports | Viewport meta is 'width=device-width,initial-scale=1'; scaling is not disabled. |
| 1.4.5 Images of Text | Supports | No images of text other than the logo. |
| 1.4.10 Reflow | Supports | Reflow_320_hscroll=0 no horizontal scroll at 320px. |
| 1.4.11 Non-text Contrast | Supports | The upload zone border, the only visual boundary of the primary control, now measures 3.52:1 against its background (rgb(59,130,246) on rgb(248,250,252)) against a 3:1 requirement. The amber check mark in the wordmark measures 2.15:1 but is part of the logotype, which 1.4.3 exempts. |
| 1.4.12 Text Spacing | Supports | No fixed line-height or letter-spacing that would clip text. |
| 1.4.13 Content on Hover or Focus | Not Applicable | No hover or focus triggered additional content. |
| 2.4.5 Multiple Ways | Supports | Two 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 Labels | Supports | Headings describe their sections and every control carries a label, including the upload control that previously had none. |
| 2.4.7 Focus Visible | Supports | Keyboard_traversal shows focus_style_differs true on all tested links/input. |
| 3.1.2 Language of Parts | Partially Supports | The 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 Navigation | Supports | Verified across all ten pages: the first eight tab stops are identical in the same relative order on every page. |
| 3.2.4 Consistent Identification | Supports | Components with the same function carry the same label on every page. |
| 3.3.3 Error Suggestion | Partially Supports | Same scope limitation as 3.3.1. |
| 3.3.4 Error Prevention | Partially Supports | The 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 Messages | Supports | Order and upload status is written into a container marked aria-live=polite, so status changes are announced without moving focus. |
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.