Accessibility and Frameworks: Working it out upstream with Vue.js
By Michael Stingl, Team Lead Mobile & Desktop @ownCloud
Making user interfaces accessible to as many people as possible might be a no-brainer to everyone mindful about it. Accessibility should be the default, not an optional extra.
One of our missions at ownCloud is to enable the future of collaboration. This also means delivering on the possibilities that remote work opens up for people with disabilities. When organizations choose ownCloud, its staff should find the overall accessibility of their tool stack enhanced.
All too often, software projects lack awareness and then need to retrofit their code if and when the topic comes up. We’ve been there ourselves. We want to avoid that particular trap in the development of ownCloud’s future web frontend, code-named Phoenix, and our new app for iOS. Both should be inclusive and empathetic environments which can be used by positively everyone, e.g. non-visually or without a pointing device.
We are pleased to have obtained the services of Marcus Herrmann, a Berlin-based accessibility consultant and web developer. He educates our development team by pointing to specific problems in our code, reviews fixes our team makes and contributes code himself.
In a guest post in our blog he explains what he has been doing at ownCloud. For even more detail, look forward to his upcoming book on accessible design with Vue.js.
We still have and maybe always will have room for improvement in making ownCloud fully accessible. But we hope that by addressing the issue head-on in the early stages of its design process, we can make our new interface contribute to a more inclusive workplace – and a more open web for positively everyone.