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

DIFI: 6.1. Applicability #203

Closed
WilcoFiers opened this issue Apr 25, 2018 · 2 comments
Closed

DIFI: 6.1. Applicability #203

WilcoFiers opened this issue Apr 25, 2018 · 2 comments

Comments

@WilcoFiers
Copy link
Collaborator

We support that applicability must be described objectively, unambiguously and in plain language.

Definitions of terms that are used in more than one test rule, must be described consistently and have the same meaning wherever they are used.

Applicability must take into consideration all kinds of content on a web page and not be limited to only one specific technology, such as HTML.

@kasperisager
Copy link

The ACT format describes how to write individual rules and should not define how to deal with aspects that span multiple rules. I think this is best left to specific implementations of ACT rules, such as Auto-WCAG, that can then define how to write rules within a specific context.

@WilcoFiers
Copy link
Collaborator Author

Conclusion: Rules should be tied to technologies, so that they remain unambiguous. Open ended rules lead to differences of interpretation. If a technology should be added, either the rule should be updated or a new rule should be created.

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

No branches or pull requests

3 participants