StatusGator Accessibility Conformance Report (VPAT)

StatusGator Accessibility Conformance Report (VPAT)

StatusGator Accessibility Conformance Report VPAT

Yellow highlighting identifies additions and revised wording compared with the published report.

Product information

Product Name: StatusGator

Version: Deployed version as of October 13, 2026

Report Date: October 13, 2026

Contact: support@statusgator.com

Scope: Public status pages, embeddable status page widgets, and the StatusGator mobile app for iOS and Android used by end-users.

Evaluation methods

• Automated testing (axe DevTools, Lighthouse)
• Manual keyboard navigation testing
• Screen reader testing (VoiceOver)
• Color contrast analysis (WebAIM tools)
• Mobile app accessibility testing on iOS and Android

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, icons, and controls include appropriate text alternatives or accessible labels. Decorative content is excluded from assistive technology output where appropriate.
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	Web content uses semantic HTML to convey structure and relationships. Mobile app controls expose structure and relationships to assistive technologies.
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	Supports	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	Web status pages provide a skip navigation mechanism. Applicability to mobile app software is assessed using the relevant non-web guidance.
2.4.2 Page Titled	Supports	Web pages and mobile app screens have descriptive titles or labels identifying their purpose.
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 web pages and mobile app content is programmatically identified where applicable.
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	Web and mobile app controls expose appropriate accessible names, roles, values, and states 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, including in the mobile app.
1.3.5 Identify Input Purpose	Supports	The purpose of applicable input fields is programmatically identified where required.
1.4.3 Contrast (Minimum)	Supports	Text and UI elements meet minimum contrast ratios.
1.4.4 Resize Text	Supports	Web content can be resized up to 200% without loss of functionality. Mobile app content supports text scaling without loss of content or functionality.
1.4.5 Images of Text	Supports	Text is presented as text rather than images of text wherever possible across web content and the mobile app.
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	Supports	Navigation elements are consistent across pages.
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

If you have any questions or problems, please email hi@statusgator.com or submit a support ticket.