Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create an implementations policy #107

Open
WilcoFiers opened this issue May 30, 2022 · 1 comment
Open

Create an implementations policy #107

WilcoFiers opened this issue May 30, 2022 · 1 comment

Comments

@WilcoFiers
Copy link
Collaborator

WilcoFiers commented May 30, 2022

Implementors can do a variety of things to improve their consistency with ACT rules that don't include improving their consistency with ACT Rules. I think it would be useful for us to have a policy that describe what things are, and what things are not acceptable. For example:

  1. Do implementations need to run in their default configuration? Can they turn off certain behaviours such as having stricter reporting on accessibility support?
  2. Can implementors report on beta versions of their product, rather than released versions? If so, how does that relate to Q1?
  3. Can one implementation include results from another. For example, could Accessibility Insights include results from axe-core?
  4. Can implementors report examples with open issues as untested or cantTell?

These aren't things we can really enforce, but I think it's good to have this stuff documented, and ask implementors to agree with it.

@WilcoFiers
Copy link
Collaborator Author

Another topic on this: Can implementors use ACT test cases as training data. This was discussed during TPAC 2023 where we concluded that this would be allowed, but that it is recommended not to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant