Re: WAI-Adapt CR Exit Criteria Draft

This is excellent and practical feedback. We are following up on all
your comments.
[image: Lionel Wolberger]
<https://userway.org/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>

Lionel Wolberger
COO, UserWay Inc.
[image: UserWay.org]
<https://userway.org/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
[image: Phone Icon] +1 (415) 800-4557 <+14158004557>
[image: Envelope Icon]
lionel@userway.org <lionel@userway.org>
[image: Schedule with Me]
<https://userway.org/s/lionel?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>




On Fri, Aug 19, 2022 at 3:37 PM Michael Cooper <cooper@w3.org> wrote:

> Hi - I made some comments and suggestions in the google doc version. In
> summary:
>
>    - Exit criteria section itself should be an appendix, and I added
>    content about the 2-CR plan;
>    - Conformance section should be a normal section, and I suggested
>    using the Respec conformance section as a starting point. I clarified
>    wording of MUST statements to avoid passive voice and to be explict about
>    subject and predicate.
>    - Implementation I suggest be part of the CR testing resource, not
>    part of the spec.
>
> Michael
> On 2022-08-18 7:10 a.m., Lionel Wolberger wrote:
>
> Dear all,
>
> Below please find the draft Exit Criteria that Matt and I drafted. Thanks
> to Matt for his share of the work!
>
> Feel free to comment on list, and we will discuss next meeting
>
> - Lionel
>
> Candidate Recommendation Exit Criteria
>
> The WAI Adapt Content Module 1.0 specification consists of attributes that
> may be added to a page’s HTML at the website’s discretion. A user-agent may
> take suitable rendering decisions based on these attributes.
>
> For example, a user agent may have a rendering mode for
> data-simplification=”critical”. In such a rendering mode, elements marked
> up with WAI Adapt  data-simplification=”low” would not be rendered.
>
> For the specification to exit Candidate Review status: each
> attribute-value pair in the specification has at least two user agents (or
> extensions to existing user agents) that provide an appropriate rendering.
>
> For clarity, we note:
>
>    -
>
>    While the WAI-Adapt standard stipulates HTML value/attribute markup
>    codes for use by page authors, implementations to meet exit criteria are
>    focused on rendering of the markup.
>    -
>
>    For user agents (or extensions) rendering a given attribute, all
>    values for that attribute must be supported.
>    -
>
>    The results of testing are made available in a separate implementation
>    report.
>
> Conformance
>
> The main content of WAI-Adapt is sets of attribute/value pairs that MAY be
> used by authors. The sections may contain examples of recommended practice,
> but it is not required to follow such recommendations in order to conform
> to this specification.
>
> User agents MAY implement any attributes they wish. If a user agent
> implements an attribute, it MUST provide support for all possible values of
> that attribute.
>
> [image: Lionel Wolberger]
> <https://userway.org/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
>
> Lionel Wolberger
> COO, UserWay Inc.
> [image: UserWay.org]
> <https://userway.org/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
> [image: Phone Icon] +1 (415) 800-4557 <+14158004557>
> [image: Envelope Icon]
> lionel@userway.org <lionel@userway.org>
> [image: Schedule with Me]
> <https://userway.org/s/lionel?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
> Important Reads: Accessibility and SEO Impact
> <https://userway.org/blog/the-impact-of-accessibility-on-seo/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
>  & Accessibility Tax Credits
> <https://userway.org/blog/everything-you-need-to-know-about-web-accessibility-tax-benefits/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
>
>