4 ms·
Applications don't have to implement this, the toolkit is supposed to handle it. It happens at the layer above Vulkan/DirectX, because those APIs are too low le
by zxzax 5y ago
Applications don't have to implement this, the toolkit is supposed to handle it. It happens at the layer above Vulkan/DirectX, because those APIs are too low level and don't know anything window controls, text, etc. When applications disregard the platform's toolkit and use another toolkit that is not at feature parity with the one provided by the platform, they'll lose functionality. That's always been the case.
- politician 5y agoWhat I'm saying is that there should be a cross-platform standard like Vulkan or like the Document Object Model for accessibility. Toolkits should use implementations of that standard to enable accessibility like they use implementations of Vulkan or OpenGL to render graphics. In turn, applications should use the toolkits, as you've said. I don't know if there is a "Khronos Group" for Accessibility Standards. Maybe there is.
- zxzax 5y agoIMO the closest thing to that is WAI-ARIA, the concepts apply anywhere.
- mwcampbell 5y agoI think you're right. Unfortunately, that isn't very helpful for developers not using the web platform.