Legal & trust
Accessibility Statement
Last updated: October 7, 2026
Plain English summary: Folvi uses WCAG 2.2 Level AA as an accessibility reference target, documents current limitations, and provides a channel for reporting barriers.
1. Our commitment
Folvi aims to make the Service usable by people with disabilities and to improve accessibility as the product evolves. We use the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as a reference target for this work and also consider accessibility requirements that apply under applicable law.
2. WCAG accessibility target
WCAG organises accessibility around four principles:
- Perceivable: information and interface components should be available in forms users can perceive
- Operable: interface components and navigation should be operable through supported input methods
- Understandable: information and operation of the interface should be understandable
- Robust: content should work with a range of user agents and assistive technologies
Folvi has implemented accessibility-focused patterns and automated checks in parts of the product, including semantic markup, ARIA attributes, focus handling, and form accessibility helpers. Automated checks can detect some accessibility problems but do not establish full WCAG conformance. Folvi does not currently claim that every Folvi surface fully conforms to WCAG 2.2 Level AA or has been independently certified.
3. Accessibility practices
Semantic structure and ARIA: Folvi uses semantic HTML and ARIA attributes in many application and public-site components to expose names, roles, states, and structure to assistive technologies.
Keyboard and focus support: Folvi includes keyboard-operable controls and visible focus treatment across many core interactions. Accessibility can vary between features, and barriers should be reported if encountered.
Forms and status feedback: Folvi uses labels, descriptions, validation states, and live-region patterns in supported forms and status messages.
Visual presentation: Folvi's design system is intended to support readable contrast, responsive layouts, and visible interaction states. Individual surfaces may still contain defects or regressions.
Media and user content: Folvi provides structures for presenting user content, but accessibility of uploaded files, externally hosted media, SCORM packages, captions, transcripts, and descriptive text depends partly on the content supplied by the user or third party.
4. Known accessibility limitations
User-uploaded SCORM packages: Folvi cannot guarantee the accessibility of SCORM course content uploaded by users. Users are responsible for ensuring their course materials are accessible.
Third-party and user-provided content: Embedded media, uploaded documents, external links, and other content supplied by users or external providers may have accessibility limitations outside Folvi's control.
Folvi interface: Despite accessibility-focused implementation and testing, Folvi may still contain accessibility defects or regressions. A passing automated check does not prove that a page is accessible to every user or assistive technology.
Practical alternatives for some content-related limitations are described in Section 5 below. Please report barriers in Folvi's own interface using Section 6.
5. Workarounds and solutions
SCORM player accessibility: If a SCORM package has accessibility issues, you can:
- Provide alternative course materials (transcripts, documents) on your portfolio
- Note accessibility features in your project description
- Contact the SCORM provider for accessible versions
Embedded video accessibility: If you embed external videos without captions, provide transcripts on your portfolio page.
PDF accessibility: Ensure PDFs you upload are properly formatted with text recognition and structure.
6. Reporting accessibility barriers
If you encounter an accessibility barrier on Folvi, please let us know so we can work to fix it. You can report issues by:
Email: accessibility@folvi.org
Please include:
- Description of the accessibility barrier
- URL of the affected page or feature
- Your assistive technology (screen reader, voice control, etc.) if applicable
- Steps to reproduce the issue
- Your preferred method of contact
Folvi reviews accessibility reports and prioritises remediation based on the nature, severity, affected workflow, and practical impact of the barrier. Unless required by applicable law or separately agreed in writing, Folvi does not promise a fixed acknowledgement or resolution time.
7. Assistive technology support
Folvi is designed to work with standard browser and operating-system accessibility mechanisms, including keyboard input and assistive technologies that consume semantic HTML and ARIA information. Compatibility can vary by browser, operating system, assistive-technology version, feature, and user-provided content.
Folvi does not currently publish a certified compatibility matrix for named screen readers, magnifiers, or voice-control products. If you experience an issue with a particular setup, please report it to accessibility@folvi.org and include the relevant browser, operating system, and assistive technology where possible.
8. Ongoing improvements
Accessibility is an ongoing product-quality concern. Folvi's accessibility work includes:
- maintaining accessibility-oriented component and form patterns
- using automated accessibility checks where they are part of the test suite
- reviewing and repairing accessibility issues found during product work or reported by users
- monitoring relevant accessibility standards and guidance as the product evolves
The scope and frequency of accessibility testing may vary by release and feature. This statement is updated when Folvi's public accessibility position materially changes.
9. Technical standards
Folvi uses web-development practices intended to support accessibility, including:
- Semantic HTML: headings, navigation, forms, and landmark elements where appropriate
- ARIA: accessible names, descriptions, states, and live-region information where native semantics are insufficient
- Keyboard and focus patterns: keyboard-operable controls and visible focus treatment in supported components
- Responsive design: layouts intended to remain usable across supported viewport sizes
- Automated checks: axe-core-based tests for selected accessibility patterns and surfaces
These implementation practices reduce accessibility risk but do not, on their own, establish WCAG conformance for the entire Service.
10. Accessibility statement information
Last updated: October 7, 2026
Contact for accessibility questions: accessibility@folvi.org
Alternative formats: If this statement is not usable in its current form, contact us and describe the format or assistance you need. We will review the request and provide reasonable assistance where practicable and required by applicable law.