Accessibility Conformance Report (VPAT)
Report Information
- Product Name: MyConferenceTime
- Product Description: Web-based parent-teacher conference scheduling platform, including authenticated application and public marketing website.
- Report Date: March 2026
- Product Version: Current production version as of March 2026
- Evaluation Standard: WCAG 2.1 Level A and AA
- VPAT Version: VPAT® 2.5
- Conformance Level: Partially Supports WCAG 2.1 Level A and AA
Accessibility Statement
MyConferenceTime maintains a public Accessibility Statement outlining our commitment to digital accessibility and continuous improvement. The statement is available at https://www.myconferencetime.com/info/accessibility/.
Scope of Evaluation
This report covers the MyConferenceTime authenticated web application, public marketing website pages hosted under MyConferenceTime control, and help documentation hosted directly within those properties. Some help documentation is hosted on a third-party support platform (Freshdesk). Accessibility conformance of the Freshdesk platform itself is subject to documentation provided by the third-party vendor. MyConferenceTime does not control the internal accessibility architecture of that platform.
Evaluation Methods Used
- Automated accessibility scanning (e.g., WAVE and similar tools)
- Manual keyboard-only testing
- Manual screen reader spot testing on representative workflows
- Color contrast evaluation of UI components
- Responsive layout testing for reflow and zoom
Definitions of Conformance Terms
- Supports: The functionality meets the success criterion.
- Partially Supports: Some functionality meets the criterion; improvements are ongoing.
- Does Not Support: The functionality does not meet the criterion.
- Not Applicable: The criterion does not apply.
WCAG 2.1 Level A and AA Success Criteria
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (A) | Partially Supports | Core UI icons and images include text alternatives. User-uploaded images and legacy content may lack descriptive alternative text. |
| 1.3.1 Info and Relationships (A) | Partially Supports | Semantic structure is implemented in core templates. Some legacy administrative pages may require additional structural refinement. |
| 1.4.1 Use of Color (A) | Partially Supports | Core UI does not rely solely on color. User-selected themes or formatting may introduce exceptions. |
| 2.1.1 Keyboard (A) | Partially Supports | Primary workflows are operable by keyboard. Some legacy components and certain third-party widgets may require refinement. |
| 2.4.1 Bypass Blocks (A) | Partially Supports | Skip links are implemented in primary templates. Ongoing work aligns older templates to consistent patterns. |
| 3.3.1 Error Identification (A) | Partially Supports | Forms identify errors with text. Improvements continue for consistent inline and programmatic associations. |
| 4.1.2 Name, Role, Value (A) | Partially Supports | Most interactive elements expose accessible names and roles. Some custom widgets require additional refinement. |
| 1.4.3 Contrast (Minimum) (AA) | Partially Supports | Core interface components meet contrast requirements. User-generated formatting and theme customization may result in lower contrast combinations. |
| 1.4.4 Resize Text (AA) | Partially Supports | Content supports 200% text resizing in most workflows. Dense tables and legacy layouts may require further improvements. |
| 1.4.10 Reflow (AA) | Partially Supports | Responsive layouts are broadly implemented. Some complex data tables may require horizontal scrolling at narrow widths. |
| 1.4.11 Non-text Contrast (AA) | Partially Supports | Focus indicators and UI boundaries are implemented in primary templates; improvements are ongoing in legacy components. |
| 2.4.6 Headings and Labels (AA) | Partially Supports | Heading structure is standardized in primary templates; some older pages may contain skipped heading levels. |
| 2.4.7 Focus Visible (AA) | Partially Supports | Visible focus styling is present in core UI. Certain third-party or legacy components may require enhancements. |
| 3.3.3 Error Suggestion (AA) | Partially Supports | Error guidance is provided in many workflows; consistency improvements are ongoing. |
| 3.3.4 Error Prevention (AA) | Partially Supports | Confirmation steps are present for many administrative actions. Enhancements continue for improved prevention and undo patterns. |
| Remaining WCAG 2.1 Level A and AA Criteria | Supports or Not Applicable | Remaining success criteria are supported or not applicable based on product functionality and media usage. |
Accessibility Limitations and User-Generated Content
MyConferenceTime allows administrators to configure themes, formatting, and content. Accessibility of user-generated content may vary depending on color selections, formatting choices, or externally embedded materials. The platform provides accessible defaults and guidance; however, accessibility outcomes for administrator-created content cannot be fully guaranteed.
Ongoing Accessibility Improvements
Accessibility evaluation and remediation are ongoing. Updates are prioritized based on user impact and frequency of use. Improvements are incorporated into regular development cycles.
Contact Information
If you encounter an accessibility barrier, please contact us through our support page and include the page URL, task being performed, and any assistive technology used.