VPAT Version: 2.4 | Applicable Standards: WCAG 2.1 Level A & AA, Revised Section 508
WCAG 2.1 Level A — Conformance Results
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | The upload SVG icon in the dropzone does not have an aria-label or <title> element providing a text alternative. All other non-text content (file type hints, slider values) is conveyed in text. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | The application does not contain any audio or video content. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | No prerecorded audio or video content is present. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | No prerecorded video content is present. |
| 1.3.1 Info and Relationships | Supports | The page uses semantic HTML: proper heading hierarchy (h1, h2), landmark elements (header, main, footer), form labels associated with inputs via <label for>, and list markup for the file list. |
| 1.3.2 Meaningful Sequence | Supports | DOM order matches the visual reading order. No CSS reordering is used. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely solely on shape, size, visual location, or orientation. The upload prompt uses text ("Drop files here or browse"). |
| 1.4.1 Use of Color | Supports | Color is not the sole means of conveying information. Error states include text messages, links are underlined, and the browse link uses underline decoration alongside the accent color. |
| 1.4.2 Audio Control | Not Applicable | The application does not play audio. |
| 2.1.1 Keyboard | Does Not Support | The dropzone area is a <div> with only a click handler. It is not focusable via keyboard (tabindex is absent) and does not respond to Enter or Space key events. Users can still access the hidden file input via the "browse" label, but the primary drag-and-drop area is mouse-only. |
| 2.1.2 No Keyboard Trap | Supports | No keyboard traps exist. Focus can always be moved away from any element. The application does not use modals or focus-trapping overlays. |
| 2.1.4 Character Key Shortcuts | Not Applicable | The application does not implement any single-character keyboard shortcuts. |
| 2.2.1 Timing Adjustable | Not Applicable | No time limits are imposed on user interaction. The processing step waits indefinitely for a server response. |
| 2.2.2 Pause, Stop, Hide | Supports | The only animation is a CSS spinner shown during processing, which is an essential loading indicator and does not auto-update content. No prefers-reduced-motion media query is implemented, though the spinner is purely functional. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No content flashes more than three times per second. |
| 2.4.1 Bypass Blocks | Does Not Support | No skip-to-content link is provided on the main application page. The single-page layout has a header and settings section before the primary action area. (Note: this ACR page itself includes a skip link.) |
| 2.4.2 Page Titled | Supports | The page has a descriptive <title> element: "Reducto". |
| 2.4.3 Focus Order | Supports | Tab order follows the logical reading order of the document. No positive tabindex values are used. |
| 2.4.4 Link Purpose (In Context) | Supports | Link text is descriptive. The "browse" link clearly indicates its purpose in the context of the upload prompt. |
| 2.5.1 Pointer Gestures | Not Applicable | No multipoint or path-based gestures are required. Drag-and-drop has a click alternative via the browse link. |
| 2.5.2 Pointer Cancellation | Supports | Click actions use standard browser click events (mouseup completion). No actions fire on pointer down. |
| 2.5.3 Label in Name | Supports | Visible labels match accessible names for all form controls. Slider labels include the visible text. |
| 2.5.4 Motion Actuation | Not Applicable | No device motion or user motion features are used. |
| 3.1.1 Language of Page | Supports | The <html> element has lang="en". |
| 3.2.1 On Focus | Supports | Focusing any element does not trigger a context change. No auto-navigation or auto-submission occurs on focus. |
| 3.2.2 On Input | Supports | Changing form controls (sliders, file input) does not trigger unexpected context changes. Processing requires an explicit button click. |
| 3.3.1 Error Identification | Supports | Errors from the API are displayed as text in the status area with "Error:" prefix. The submit button is disabled when no files are selected, preventing empty submissions. |
| 3.3.2 Labels or Instructions | Supports | All form controls have visible labels. Sliders include tooltip help text (?) explaining each setting. File type restrictions are indicated ("PDF, DOCX, or HTML files"). |
| 4.1.2 Name, Role, Value | Partially Supports | Most elements use correct native semantics. However, file remove buttons use title="Remove" for their accessible name with an × entity as visible text — screen readers may announce this as "multiplication sign" rather than "Remove". An aria-label="Remove" would be more reliable. |
WCAG 2.1 Level AA — Conformance Results
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | No live audio or video content is present. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | No prerecorded video content is present. |
| 1.3.4 Orientation | Supports | No CSS or JavaScript restricts the display to a particular orientation. The layout adapts to both portrait and landscape viewports. |
| 1.3.5 Identify Input Purpose | Partially Supports | The file input has an appropriate accept attribute. However, no autocomplete attributes are used, though the application's inputs (sliders, file upload) do not map to standard autocomplete tokens. |
| 1.4.3 Contrast (Minimum) | Supports | Text contrast ratios meet or exceed 4.5:1 in both light mode (#2a2622 on #f8f5f1 ≈ 11.6:1) and dark mode (#e8e0d6 on #1a1a1a ≈ 12.8:1). Dim text (#706456 on #f8f5f1 ≈ 4.8:1) meets the minimum. Accent color on both backgrounds meets the 3:1 threshold for large text. |
| 1.4.4 Resize Text | Supports | The layout uses rem units for typography and a flexible max-width container. Text resizes to 200% without clipping or loss of content. |
| 1.4.5 Images of Text | Supports | No images of text are used. All text is rendered as HTML. |
| 1.4.10 Reflow | Supports | The single-column layout with max-width: 720px and responsive padding reflows correctly at 320px width without horizontal scrolling. The JSON output area uses overflow-x: auto for long lines. |
| 1.4.11 Non-text Contrast | Supports | UI components (buttons, inputs, dropzone border) have at least 3:1 contrast against adjacent backgrounds. The accent-colored submit button (#c38822 on #f8f5f1) provides clear visibility. |
| 1.4.12 Text Spacing | Supports | No !important declarations restrict line-height, letter-spacing, word-spacing, or paragraph spacing. User style sheet overrides for text spacing do not cause content loss. |
| 1.4.13 Content on Hover or Focus | Partially Supports | Tooltip help icons show content on hover and focus. The tooltip content is hoverable and persistent. However, there is no explicit dismiss mechanism (Escape key) for the tooltips — they rely on moving focus or pointer away. |
| 2.4.7 Focus Visible | Does Not Support | The stylesheet does not define any custom :focus or :focus-visible styles. While browsers provide default focus outlines, these may be suppressed or insufficient in some browsers. No explicit focus indicators are styled for buttons, links, sliders, or the browse label. |
| 2.5.8 Target Size (Minimum) | Supports | Interactive targets meet the 24×24 CSS pixel minimum. The submit button is full-width, slider handles use native sizing, and the tooltip triggers (16×16) are spaced sufficiently from adjacent targets. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | The application does not involve legal commitments, financial transactions, or modification of user-controlled data in a data store. |
| 4.1.3 Status Messages | Does Not Support | Processing status updates ("Uploading and processing…", "Error: …") and result summaries ("12 Q&A pairs from 2 file(s)") are displayed visually but lack aria-live regions. Screen reader users are not notified of these state changes. |
Revised Section 508 — Chapter 3: Functional Performance Criteria
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Partially Supports | Semantic HTML supports screen reader navigation. Heading structure and form labels are present. However, the dropzone lacks keyboard access and status messages lack aria-live announcements. |
| 302.2 With Limited Vision | Supports | The application supports browser zoom to 200%+ without content loss. Both light and dark modes maintain adequate contrast ratios. Layout reflows at narrow widths. |
| 302.3 Without Perception of Color | Supports | Information is not conveyed by color alone. Error messages use text, status indicators use text labels, and links use underline styling. |
| 302.4 Without Hearing | Not Applicable | The application contains no audio content. |
| 302.5 With Limited Hearing | Not Applicable | The application contains no audio content. |
| 302.6 Without Speech | Not Applicable | The application does not require speech input. |
| 302.7 With Limited Manipulation | Partially Supports | Most controls (buttons, sliders) are operable with limited fine motor control. However, the dropzone requires mouse interaction for drag-and-drop. The alternative browse link is available but the primary interaction path is not keyboard-accessible. |
| 302.8 With Limited Reach and Strength | Not Applicable | As a web application, physical reach and strength are not applicable. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | The interface uses clear, concise language. Navigation is consistent and predictable. Settings include help tooltips. The single-page layout presents a linear workflow: upload → configure → process → download. |
Revised Section 508 — Chapter 4: Hardware
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| All Chapter 4 Criteria (402–415) | Not Applicable | This product is a web application and does not include hardware components. |
Revised Section 508 — Chapter 5: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| All Chapter 5 Criteria (501–504) | Not Applicable | This product is a web application accessed through standard web browsers. It is not native platform software. |
Revised Section 508 — Chapter 6: Support Documentation and Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 602.2 Accessibility and Compatibility Features | Partially Supports | This Accessibility Conformance Report documents the current accessibility status. No separate end-user documentation describing accessibility features is provided. |
| 602.3 Electronic Support Documentation | Supports | This conformance report is provided as an accessible HTML page with semantic markup, proper heading structure, and table captions. |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | No printed or non-electronic documentation is provided. |
| 603.2 Information on Accessibility and Compatibility Features | Supports | Accessibility information is available via the footer link on the main application page and through direct contact at ngoldbla@kennesaw.edu. |
| 603.3 Accommodation of Communication Needs | Supports | Support is available via email, which accommodates users with a range of communication needs. |
Legal Disclaimer: This report covers the accessibility conformance of Reducto as evaluated in April 2026. Conformance may change as the product is updated. This document is informational and does not constitute a legal guarantee.
Generated using VPAT® 2.4 template. VPAT is a registered trademark of the Information Technology Industry Council (ITI).