FOSDEM is a free event for developers of free and open software, held in Brussels each year. With 30 tracks to choose from, it’s an intense two days of ideas, knowledge and collaboration.
I gave a short talk in the Open Source Design Room (hosted by the Open Source Design project), looking at four open projects that together represent the different layers of the accessibility stack: the screen reader (NVDA), the code (HTML), the browser (Firefox), and the accessibility API (Accessibility Object Model(AOM)).
There was time for a couple of questions at the end:
- What is the difference in capability between NVDA and the propriatary screen readers?
- All screen readers are slightly different in their capabilities, but NVDA is as fully featured and capable as those developed by closed software teams.
- We’re trying to make our products accessible, but where do we go for help?
- There is a Slack channel called A11y Slackers where many accessibility specialists gather (and can answer your questions), and two email-based forums where you can post questions: WebAIM and WAI-IG.
- What extensions and tools are available for testing accessibility?
ChromeVox is a browser-based screen reader, and there are integrated screen readers available on all platforms (Narrator on Windows 10, VoiceOver on Mac OS and iOS, TalkBack on Android and Orca on Linux).