We also made the VoiceOver cursor visible, and made it follow focus. This small, but mighty, patch, enabled us to progress much more rapidly than we had expected. In the process we uncovered a small, but significant, piece we were missing that made us very fast all of a sudden.
#FIREFOX MOZILLA MAC CODE#
Most notably, we learned our way around the Mac code base and the accessibility APIs. What we have so far Firefox 75įirefox 75, released in April, saw the first fruits of this work. It will also include other bits that might turn out missing as more users start testing what we have. This encompasses performance, text editing, live region support, and rotor item support. In the second stage, which we plan to complete by the end of the year, the goal is to improve the user experience for visually impaired VoiceOver users. The output should be good enough so they can feel confident that users visiting their offerings with assistive technology will get an accessible experience. The aim of this first stage is to give web developers the chance to test their web sites with VoiceOver. This is to give VoiceOver and other accessibility features correct information about what is happening inside our web area. For the most part, this means correcting and completing specific properties for various HTML elements and widgets. The first stage, due by the end of June, aims to implement basic VoiceOver support. We agreed to tackle the problem in two stages. There was a lot of old, mostly dysfunctional, code lying around that needs to be modernized and brought up to today’s standards. In January, several members gathered in Berlin during an all-hands to scope out the work.
In late 2019, the accessibility team at Mozilla resourced work on improving MacOS accessibility support over the course of 2020. Here is some insight into what’s happening. In 2020, the team is finally changing that. For several years, Firefox support for the VoiceOver accessibility technology on MacOS was mostly non-existent.
0 kommentar(er)
