After getting fed up with the general neglect of MacOS accessibility from Apple, and having wanted to work on something meaningful for quite some time, I decided to attempt something that for some reason nobody seems to have tried to do before: write a completely new screen-reader for that platform. This isn't an easy task, not only due to the amount of work required to even get close to matching a mature screen-reader in terms of functionality, but also because Apple's documentation for more obscure system services is nigh on non-existent.

After getting fed up with the general neglect of MacOS accessibility from Apple, and having wanted to work on something meaningful for quite some time, I decided to attempt something that for some reason nobody seems to have tried to do before: write a completely new screen-reader for that platform. This isn’t an easy task, not only due to the amount of work required to even get close to matching a mature screen-reader in terms of functionality, but also because Apple’s documentation for more obscure system services is nigh on non-existent.

  • 0x1C3B00DA@kbin.socialOP
    1·
    1 year ago

    I’ve never bought an apple product but I’ve worked at multiple jobs that provided me with a mac so I still want to see improvements in the mac ecosystem.

    Also, I’m not a screenreader user but I am a web developer and screenreader users deserve the same experience as typical screen/keyboard/mouse users. Developing for screenreaders sometimes feels like developing for browsers use to be with inconsistencies and unimplemented standards. For browsers, it was Chromes launch that really spurred competition in the space that drove vendors to implement standards and interoperability so it seems reasonable that a new screenreader could provide the same outcome for screenreaders.