Accessibility Conformance Report
Voluntary Product Accessibility Template documenting how SentraCheck and its Accessible Document Viewer conform to WCAG 2.1 Level AA and Revised Section 508 standards.
Product Information
Covered Components
This report covers two primary components of the SentraCheck product:
- SentraCheck Platform — The web application used by agency staff to upload documents, run accessibility scans, manage VPAT reports, and view compliance dashboards (
sentracheck.com/app/). - SentraCheck Accessible Document Viewer — A publicly accessible, token-authenticated viewer that renders AI-converted, WCAG-compliant HTML versions of agency documents for the public (
sentracheck.com/viewer.html).
Evaluation Method: This report is based on a self-assessment conducted by SentraCheck developers using manual testing, keyboard navigation testing, screen reader testing (NVDA + Chrome, VoiceOver + Safari), and automated tooling (axe-core). An independent third-party audit is planned for Q3 2026.
Terms Used in This Report
The functionality of the product meets the criterion without any known deficiencies.
Some functionality does not meet the criterion. Known exceptions are described in the remarks.
The majority of product functionality does not meet the criterion.
The criterion is not relevant to this product.
The product has not been evaluated against this criterion.
WCAG 2.1 Success Criteria — Level A
Table 1: Perceivable
| Criteria | Conformance | Remarks |
|---|---|---|
| 1.1.1 Non-text Content | Supports | Images within accessible document output include AI-generated alternative text. UI icons use aria-hidden or descriptive aria-label. Viewer toolbar buttons all have programmatic labels. |
| 1.2.1 Audio-only and Video-only | Not Applicable | SentraCheck does not produce or embed audio-only or video-only content. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | No prerecorded audio content is present. |
| 1.2.3 Audio Description or Media Alternative | Not Applicable | No synchronized media is present. |
| 1.3.1 Info and Relationships | Supports | The Document Viewer outputs semantic HTML5: headings (h1–h6), lists, data tables with thead/tbody, paragraphs, and definition lists. The platform uses ARIA landmarks (main, nav, banner, contentinfo) throughout. |
| 1.3.2 Meaningful Sequence | Supports | DOM order in converted documents reflects the logical reading sequence of the source. AI conversion preserves document structure and reading order. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely on shape, color, size, visual location, orientation, or sound as the sole means of identification. |
| 1.4.1 Use of Color | Supports | Color is never the sole means of conveying information. Status indicators and compliance badges include text labels alongside color coding. |
| 1.4.2 Audio Control | Not Applicable | No audio plays automatically. |
Table 2: Operable
| Criteria | Conformance | Remarks |
|---|---|---|
| 2.1.1 Keyboard | Supports | All viewer controls (font size, print, translate, download) are keyboard accessible via Tab and Enter/Space. Converted document content — headings, links, and tables — is fully keyboard navigable. |
| 2.1.2 No Keyboard Trap | Supports | No keyboard traps exist. Modal dialogs and dropdowns release focus via the Escape key. |
| 2.1.4 Character Key Shortcuts | Not Applicable | No single-character keyboard shortcuts are implemented. |
| 2.2.1 Timing Adjustable | Not Applicable | No time limits are set on viewer content or document interaction. |
| 2.2.2 Pause, Stop, Hide | Not Applicable | No auto-updating, blinking, scrolling, or moving content is present. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No flashing or strobing content exists anywhere in the product. |
| 2.4.1 Bypass Blocks | Supports | The Document Viewer includes a visually hidden "Skip to main content" link as the first focusable element, allowing keyboard users to bypass the toolbar and go directly to document content. |
| 2.4.2 Page Titled | Supports | The viewer page title is set dynamically to the document filename (e.g., "Budget-Report-2026.pdf — SentraCheck"). All platform pages have descriptive, unique titles. |
| 2.4.3 Focus Order | Supports | Focus order follows a logical, meaningful sequence matching the visual presentation throughout the viewer and platform. |
| 2.4.4 Link Purpose (In Context) | Supports | All links have descriptive text or accessible names via aria-label. Ambiguous link text includes surrounding context or an explicit aria-label. |
| 2.5.1 Pointer Gestures | Supports | No multi-point or path-based gestures are required. All functionality is operable with a single pointer. |
| 2.5.2 Pointer Cancellation | Supports | Actions are triggered on the up-event, allowing users to cancel accidental activations by moving the pointer away. |
| 2.5.3 Label in Name | Supports | Accessible names for interactive components contain or begin with the visible text label. |
| 2.5.4 Motion Actuation | Not Applicable | No functionality is triggered by device motion or user movement. |
Table 3: Understandable
| Criteria | Conformance | Remarks |
|---|---|---|
| 3.1.1 Language of Page | Supports | The viewer sets lang="en" by default. When the conversion process detects a non-English document, the lang attribute is updated accordingly (e.g., lang="es" for Spanish). |
| 3.2.1 On Focus | Supports | No context changes are initiated solely by a component receiving focus. |
| 3.2.2 On Input | Supports | No unexpected context changes occur on input. Form submissions require explicit user action. |
| 3.3.1 Error Identification | Supports | Input errors are identified in text and described specifically. Error messages are associated with their fields via aria-describedby. |
| 3.3.2 Labels or Instructions | Supports | All form inputs have visible labels. Required fields are marked. Format requirements are stated before submission. |
Table 4: Robust
| Criteria | Conformance | Remarks |
|---|---|---|
| 4.1.1 Parsing | Supports | HTML output from the Document Viewer is valid HTML5. Elements have complete start and end tags, are correctly nested, and IDs are unique within each page. |
| 4.1.2 Name, Role, Value | Supports | All interactive components expose accessible names, roles, and states to assistive technologies via native HTML semantics or ARIA. Custom controls use appropriate ARIA roles with aria-expanded/aria-selected states. |
WCAG 2.1 Success Criteria — Level AA
Table 5: Perceivable
| Criteria | Conformance | Remarks |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | No live audio content is present. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | No prerecorded video with audio is present. |
| 1.3.4 Orientation | Supports | The viewer and platform function in both portrait and landscape orientations. Content is not restricted to a single display orientation. |
| 1.3.5 Identify Input Purpose | Supports | Input fields collecting personal information include appropriate autocomplete attribute values to assist users and assistive technologies. |
| 1.4.3 Contrast (Minimum) | Supports | Document Viewer body text meets a minimum 4.5:1 contrast ratio. The dark toolbar (navy background) uses white text at >7:1. Platform UI meets minimum contrast requirements throughout. |
| 1.4.4 Resize Text | Supports | The viewer includes built-in font size controls (Small, Medium, Large, X-Large). Text can also be resized to 200% via browser zoom without loss of content or functionality. |
| 1.4.5 Images of Text | Supports | The Document Viewer converts source PDFs to real HTML text, not images. Scanned image PDFs are OCR-processed to extract actual text before conversion. No document content is presented as an image of text. |
| 1.4.10 Reflow | Supports | Content reflows at 320 CSS pixels width without horizontal scrolling. The viewer uses a fluid single-column layout. Wide tables in converted documents are wrapped in scrollable containers. |
| 1.4.11 Non-text Contrast | Supports | UI components (buttons, form inputs, focus indicators) meet the 3:1 minimum contrast ratio against adjacent colors. |
| 1.4.12 Text Spacing | Supports | No loss of content or functionality occurs when letter spacing, word spacing, line height, and paragraph spacing are overridden to WCAG 2.1 SC 1.4.12 values. |
| 1.4.13 Content on Hover or Focus | Supports | Tooltips and dropdowns triggered by hover or focus are persistent, hoverable, and dismissable via Escape without moving focus. |
Table 6: Operable
| Criteria | Conformance | Remarks |
|---|---|---|
| 2.4.5 Multiple Ways | Supports | The platform provides multiple ways to locate content: navigation sidebar, search, and direct links. The Document Viewer is a single-purpose page and is exempt from this requirement. |
| 2.4.6 Headings and Labels | Supports | All page sections and form controls have descriptive headings and labels. Converted document headings reflect the source document's hierarchy (h1–h6). |
| 2.4.7 Focus Visible | Supports | Keyboard focus is visible at all times. A clearly visible focus ring (blue outline, minimum 2px) is displayed on all interactive elements. |
Table 7: Understandable
| Criteria | Conformance | Remarks |
|---|---|---|
| 3.1.2 Language of Parts | Partially Supports | Page language is always set correctly. Inline language changes within converted documents are marked with lang attributes when detected by the AI conversion engine, but detection may not be complete for all mixed-language content. |
| 3.2.3 Consistent Navigation | Supports | Navigation mechanisms appear in the same location and order across all platform pages. The sidebar navigation is consistent throughout the application. |
| 3.2.4 Consistent Identification | Supports | Components with the same function across pages are consistently identified with the same name, label, or accessible name. |
| 3.3.3 Error Suggestion | Supports | When input errors are detected, specific correction suggestions are provided where feasible and security permits (e.g., "Password must be at least 8 characters and include a number"). |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Destructive actions require confirmation. Submissions can be reviewed before final confirmation. Users can cancel before committing. |
Table 8: Robust
| Criteria | Conformance | Remarks |
|---|---|---|
| 4.1.3 Status Messages | Supports | Status messages (conversion progress, upload success/failure, scan completion) are implemented as aria-live regions, announced by screen readers without requiring focus to move. Loading states use aria-busy where appropriate. |
Revised Section 508 — Chapter 5: Software
The Revised Section 508 Technical Standards incorporate WCAG 2.0 Level A and AA by reference for web-based software. SentraCheck’s conformance to WCAG 2.1 Level A and AA (detailed above) addresses the Section 508 web accessibility requirements.
| Criteria | Conformance | Remarks |
|---|---|---|
| 501.1 Scope | Supports | SentraCheck is web-based software covered under Chapter 5. Requirements are addressed via WCAG 2.1 Level AA conformance documented above. |
| 502 Interoperability with Assistive Technology | Supports | Tested with NVDA + Chrome (Windows) and VoiceOver + Safari (macOS/iOS). The viewer and platform are operable with standard screen readers without special configuration. |
| 503 Applications | Supports | SentraCheck does not override user preferences for platform display settings. User-set font sizes, high-contrast modes, and color inversion settings are respected. |
| 504 Authoring Tools | Supports | SentraCheck functions as an authoring tool for accessible documents. The Document Viewer output is WCAG 2.1 Level AA conformant HTML, enabling agencies to publish accessible content to the public. |
Chapter 6: Support Documentation and Services
| Criteria | Conformance | Remarks |
|---|---|---|
| 602 Support Documentation | Supports | Product documentation describes accessibility features, keyboard shortcuts, and how to use the product with assistive technologies. Available at sentracheck.com/support.html. |
| 603 Support Services | Supports | Technical support is available via email (support@sentracheck.com) and by phone (559-251-7767). Support staff can assist users with assistive technology needs. |
Contact & Legal Disclaimer
This report was completed by SentraCheck development staff. The information provided reflects the state of the product as of the report date. We welcome feedback from users and procurement teams.
If you experience any accessibility barriers while using SentraCheck, please contact us at support@sentracheck.com with a description of the issue and the assistive technology you are using. We will respond within 2 business days.
Legal Disclaimer: This accessibility conformance report is provided for informational purposes only. It represents a good-faith self-assessment and does not constitute a legal warranty or guarantee of accessibility. SentraCheck continually works to improve accessibility and will update this report as the product evolves. Government agencies requiring formal third-party audits should contact us to discuss assessment options.