Content
View differences
Updated by Alexander Coles over 1 year ago
In order to make good choices about the tools we develop and test with, we should first find out more about:
* what AT tools our current users (paid and community) are using.
* what AT tooling might be recommended (or even required) to ensure OpenProject is compliant with legislation (e.g. Barrierefreiheitsstärkungsgesetz, European Accessibility Act, Section 508\*\*)\*\*
* what AT tooling may be recommended or required by our partners and customers, e.g. ZenDIS' 508**)**
* find data on AT tooling market share - globally and in our core markets.
We may also want to do a brief analysis of the level of support in individual AT tools for WCAG 2.1, 2.2 and other applicable standards (a11ysupport.io provides useful matrices for support of individual ARIA attributes, e.g. [`aria-controls`](https://a11ysupport.io/tech/aria/aria-controls_attribute))
* what AT tools our current users (paid and community) are using.
* what AT tooling might be recommended (or even required) to ensure OpenProject is compliant with legislation (e.g. Barrierefreiheitsstärkungsgesetz, European Accessibility Act, Section 508\*\*)\*\*
* what AT tooling may be recommended or required by our partners and customers, e.g. ZenDIS'
* find data on AT tooling market share - globally and in our core markets.
We may also want to do a brief analysis of the level of support in individual AT tools for WCAG 2.1, 2.2 and other applicable standards (a11ysupport.io provides useful matrices for support of individual ARIA attributes, e.g. [`aria-controls`](https://a11ysupport.io/tech/aria/aria-controls_attribute))