Flinker aims to make its public website, documentation, and product experiences usable by people with a broad range of abilities, devices, and assistive technologies.
Document precedence: Accessibility is an ongoing product and content responsibility. Report barriers with the affected URL, product, device, and assistive technology where possible.
Design approach
Interfaces use semantic structure, keyboard-operable controls, visible focus, readable contrast, responsive layouts, accessible names, and reduced-motion support where practical.
Known limitations
Complex three-dimensional model interaction, third-party Microsoft surfaces, embedded documents, and customer-authored content may have limitations that differ by browser, device, and assistive technology.
Compatibility
The public website is designed for current standards-based browsers and responsive use. Product compatibility depends on the applicable Microsoft host and documented system requirements.
Feedback and support
Send accessibility feedback to info@flinker.app with the page or product, the problem encountered, and the preferred contact method. Flinker will assess the barrier and respond through the appropriate support process.
Continuous improvement
Accessibility is reviewed as components, content, and products change. Issues are prioritized according to user impact, frequency, and technical feasibility.