Content
View differences
Updated by Henriette Darge over 1 year ago
# Current
Discuss whether we need licenses for commercial AT tools, e.g.:
* [JAWS](https://www.freedomscientific.com/products/software/jaws/) (Windows only) - Screenreader and Braille output
* [JAWS Inspect](https://www.tpgi.com/arc-platform/jaws-inspect/) (Windows only) - testing tool for the above
* [Dolphin Screenreader](https://yourdolphin.com/ScreenReader) (Windows only) - Screenreader and Braille output
We may want to consider scheduling demos with their sales teams before requesting the budget for licenses.
Additionally, for macOS and Linux devs we may need:
* a commercial VM solution (e.g. Parallels) and Windows 10/11 Licenses
* OR Cloud Virtual Desktop (e.g. [Azure Virtual Desktop](https://azure.microsoft.com/en-us/products/virtual-desktop)) subscriptions
# Decision made in [**this meeting**](https://community.openproject.org/meetings/4436#item-10035)
* **Standard:**
* WCAG 2.1
* **Tools (taken from the GitHub list)**
* Recommended tools (takem from Primer and [WebAIM](https://webaim.org/projects/screenreadersurvey10/), August 2023):
* NVDA (Windows)
* ~~JAWS (Windows)~~
* VoiceOver (Mac)
* Orca (Linux)
* Top three screen readers for mobile devices ([data from WebAIM](https://webaim.org/projects/screenreadersurvey8/), August 2019):
* VoiceOver (iOS)
* TalkBack for Android (Android)
* Voice Assistant (Android)
* Alex will add a patterns page about "Accessibility" including this list of tools, basic checklist, patterns that we already implemened
<br>
## **Open**
* Will we need Windows licenses for developers as most impaired users are working in Windows?
Discuss whether we need licenses for commercial AT tools, e.g.:
* [JAWS](https://www.freedomscientific.com/products/software/jaws/) (Windows only) - Screenreader and Braille output
* [JAWS Inspect](https://www.tpgi.com/arc-platform/jaws-inspect/) (Windows only) - testing tool for the above
* [Dolphin Screenreader](https://yourdolphin.com/ScreenReader) (Windows only) - Screenreader and Braille output
We may want to consider scheduling demos with their sales teams before requesting the budget for licenses.
Additionally, for macOS and Linux devs we may need:
* a commercial VM solution (e.g. Parallels) and Windows 10/11 Licenses
* OR Cloud Virtual Desktop (e.g. [Azure Virtual Desktop](https://azure.microsoft.com/en-us/products/virtual-desktop)) subscriptions
# Decision made in [**this meeting**](https://community.openproject.org/meetings/4436#item-10035)
* **Standard:**
* WCAG 2.1
* **Tools (taken from the GitHub list)**
* Recommended tools (takem from Primer and [WebAIM](https://webaim.org/projects/screenreadersurvey10/), August 2023):
* NVDA (Windows)
* ~~JAWS (Windows)~~
* VoiceOver (Mac)
* Orca (Linux)
* Top three screen readers for mobile devices ([data from WebAIM](https://webaim.org/projects/screenreadersurvey8/), August 2019):
* VoiceOver (iOS)
* TalkBack for Android (Android)
* Voice Assistant (Android)
* Alex will add a patterns page about "Accessibility" including this list of tools, basic checklist, patterns that we already implemened
<br>
## **Open**
* Will we need Windows licenses for developers as most impaired users are working in Windows?