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

Update Accessibility Support Section #200

Merged
merged 4 commits into from May 31, 2018
Merged

Conversation

anthonyFer
Copy link
Contributor

  1. The sentence "to test accessible uses of a web technology" is confusing.
  2. The word "that" was missing?

1. The sentence "to test accessible uses of a web technology" is confusing. 
2. The word "that" was missing?
@moekraft
Copy link
Collaborator

moekraft commented May 3, 2018

Reviewed at 5/3 meeting. Anthony will continue to work on the wording. Take a look at definition of Accessibility Supported for inspiration: https://www.w3.org/TR/WCAG20/#accessibility-supporteddef

@@ -80,7 +80,7 @@ An ACT Rule MUST list any limitations, assumptions or any exceptions for the tes
Accessibility Support {#acc-support}
===========================

ACT Rules are designed to test accessible uses of a web technology. However, not every part of a web technology is implemented in all assistive technologies a website may need to support. The concept of [accessibility supported](https://www.w3.org/TR/WCAG20/#accessibility-supporteddef) use of a Web technology is defined in [[WCAG20]]. Because of this, ACT Rules are not necessarily applicable in all test scenarios. For instance, a web page that has to work in assistive technologies that have no WAI-ARIA support, wouldn’t be tested with an ACT Rule that relies on WAI-ARIA support, since this could lead to false positive results.
ACT Rules are designed to test the accessibility conformance in applications of web technologies. However, not every part of a web technology is implemented in all assistive technologies that a website may need to support. The concept of [accessibility supported](https://www.w3.org/TR/WCAG20/#accessibility-supporteddef) use of a Web technology is defined in [[WCAG20]]. Because of this, ACT Rules are not necessarily applicable in all test scenarios. For instance, a web page that has to work in assistive technologies that have no WAI-ARIA support, wouldn’t be tested with an ACT Rule that relies on WAI-ARIA support, since this could lead to false positive results.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The casing of "web technology" is not entirely consistent.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It isn't just about the implementation in assistive technology for accessibility support. Per the WCAG definition, it's also about user agent support of the accessibility features in the technology. For example, use of technically sound WAI-ARIA may not be fully supported in older user agents or older assistive technology. In either case, the accessibility support isn't there. So are rules expected to always have defined the parameters (AT type, version and browser type, version) where there is accessibility support? Or for the user agent support can they simply point to the documented test results (as an example, the ARIA 1.1 support results).

@@ -80,7 +80,7 @@ An ACT Rule MUST list any limitations, assumptions or any exceptions for the tes
Accessibility Support {#acc-support}
===========================

ACT Rules are designed to test accessible uses of a web technology. However, not every part of a web technology is implemented in all assistive technologies a website may need to support. The concept of [accessibility supported](https://www.w3.org/TR/WCAG20/#accessibility-supporteddef) use of a Web technology is defined in [[WCAG20]]. Because of this, ACT Rules are not necessarily applicable in all test scenarios. For instance, a web page that has to work in assistive technologies that have no WAI-ARIA support, wouldn’t be tested with an ACT Rule that relies on WAI-ARIA support, since this could lead to false positive results.
ACT Rules are designed to test the accessibility conformance in applications of web technologies. However, not every part of a web technology is implemented in all assistive technologies that a website may need to support. The concept of [accessibility supported](https://www.w3.org/TR/WCAG20/#accessibility-supporteddef) use of a Web technology is defined in [[WCAG20]]. Because of this, ACT Rules are not necessarily applicable in all test scenarios. For instance, a web page that has to work in assistive technologies that have no WAI-ARIA support, wouldn’t be tested with an ACT Rule that relies on WAI-ARIA support, since this could lead to false positive results.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is still saying that rules test conformance of web technologies. That's not correct. Rules test conformance of applications built with web technologies.

@WilcoFiers WilcoFiers merged commit 3c8623e into w3c:master May 31, 2018
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

Successfully merging this pull request may close these issues.

None yet

6 participants