StatusGator Accessibility Conformance Report (VPAT)
Product Information
Product Name: StatusGator
Version: Deployed version as of April 19, 2026
Report Date: April 19, 2026
Contact: support@statusgator.com
Scope: Public status pages and embeddable widgets used by customers, including K-12 institutions
Evaluation Methods:
- Automated testing (axe DevTools, Lighthouse)
- Manual keyboard navigation testing
- Screen reader testing (VoiceOver)
- Color contrast analysis (WebAIM tools)
Conformance Legend
- Supports: We have verified are fully compliant with WCAG guidelines
- Partially Supports: We have verified some compliance but there are minor gaps or future improvements needed.
- Does Not Support: Areas we are not yet compliant with.
- Not Applicable: Does not apply because we do not utilize the item in question.
WCAG 2.1 Level A
| Criteria | Conformance | Remarks |
|---|---|---|
| 1.1.1 Non-text Content | Supports | Images and icons include appropriate alternative text. Decorative images use null alt attributes. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | Product does not include prerecorded audio-only or video-only content. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | Product does not include prerecorded video content requiring captions. |
| 1.3.1 Info and Relationships | Supports | Semantic HTML is used to convey structure and relationships between elements. |
| 1.3.2 Meaningful Sequence | Supports | Content order is logical and preserved across responsive layouts. |
| 1.3.3 Sensory Characteristics | Supports | Instructions and status indicators do not rely solely on sensory characteristics such as color or position. |
| 1.4.1 Use of Color | Supports | Status indicators use both color and text labels to convey meaning. |
| 1.4.2 Audio Control | Not Applicable | No audio content is present. |
| 2.1.1 Keyboard | Partially supported | All interactive elements are accessible via keyboard navigation except for Modal Windows . |
| 2.1.2 No Keyboard Trap | Supports | Users can navigate away from all components using standard keyboard controls. |
| 2.2.1 Timing Adjustable | Supports | No time-based interactions require user adjustment. |
| 2.2.2 Pause, Stop, Hide | Supports | Automatically updating content does not interfere with user interaction. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No content flashes more than three times per second. |
| 2.4.1 Bypass Blocks | Supports | A skip navigation mechanism is in place. |
| 2.4.2 Page Titled | Supports | Pages include descriptive and meaningful titles. |
| 2.4.3 Focus Order | Supports | Focus order follows a logical and intuitive sequence. |
| 2.4.4 Link Purpose (In Context) | Supports | Link text is descriptive and provides clear context. |
| 3.1.1 Language of Page | Supports | The primary language of each page is programmatically defined. |
| 3.2.1 On Focus | Supports | Elements do not trigger unexpected changes when receiving focus. |
| 3.2.2 On Input | Supports | Changes of context are not triggered unexpectedly on user input. |
| 3.3.1 Error Identification | Supports | Form inputs display accessible error messages |
| 3.3.2 Labels or Instructions | Supports | Form inputs display accessible labels |
| 4.1.2 Name, Role, Value | Supports | UI components expose appropriate roles, names, and values to assistive technologies. |
? WCAG 2.1 Level AA
| Criteria | Conformance | Remarks |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | Product does not include live video content. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | Product does not include prerecorded video content. |
| 1.3.4 Orientation | Supports | Content is usable in both portrait and landscape orientations. |
| 1.3.5 Identify Input Purpose | Supports | Product does not include user input fields within scope. |
| 1.4.3 Contrast (Minimum) | Supports | Text and UI elements meet minimum contrast ratios. |
| 1.4.4 Resize Text | Supports | Content can be resized up to 200% without loss of functionality. |
| 1.4.5 Images of Text | Supports | Text is presented using HTML rather than images wherever possible. |
| 1.4.10 Reflow | Supports | Content reflows appropriately at smaller screen sizes without horizontal scrolling. |
| 1.4.11 Non-text Contrast | Supports | All UI components meet contrast requirements |
| 1.4.12 Text Spacing | Supports | Content remains readable and functional when user-defined text spacing is applied. |
| 1.4.13 Content on Hover or Focus | Supports | Hover and focus-triggered content is dismissible and does not obstruct interaction. |
| 2.4.5 Multiple Ways | Supports | Users can navigate content via multiple methods including direct links and navigation structures. |
| 2.4.6 Headings and Labels | Supports | Headings and labels are descriptive and structured logically. |
| 2.4.7 Focus Visible | Supports | Visible focus indicators are present for all interactive elements. |
| 3.1.2 Language of Parts | Supports | Language changes within content are programmatically identified when applicable. |
| 3.2.3 Consistent Navigation | Partially supports | Navigation elements are consistent across pages except for Modal Windows . |
| 3.2.4 Consistent Identification | Supports | Components are consistently labeled and behave predictably. |
| 3.3.3 Error Suggestion | Supports | |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | Product does not include critical form submissions. |
| 4.1.3 Status Messages | Supports |