Re: Success Criteria Best Practice Guidelines

        

        
            That depends on the list. We went over some of the proposed sc on the call two weeks ago so that the group could see why sometimes lists are needed. There seemed to be full agreement that in practice they are neededAll the bestLisa SeemanLinkedIn, Twitter---- On Wed, 03 Aug 2016 00:59:52 +0300  Gregg Vanderheiden<gregg@raisingthefloor.org> wrote ----very niceone more thought.     SC should not use lists for what to include or exclude.  They should have descriptions that allow a person to determine what they apply to or not if at all possible.  New things come up every day that need to be included or excluded.   And lists in SC won’t address them.   gregg   On Aug 2, 2016, at 3:48 PM, Andrew Kirkpatrick <akirkpat@adobe.com> wrote:        On Tuesday’s call the Working Group did not get to discuss the best practice guidelines, but we wanted to get discussion going on the list.  The survey where we started the discussion on this is https://www.w3.org/2002/09/wbs/35422/reqsWCAG21/results.     ==start== Success Criteria Best Practice Guidelines   For the Working Group to accept a candidate success criterion, they need to fit within the overall structure. The following are guidelines that will help the Working Group efficiently process suggested SC:  Ensure that the criteria is written as simply as possible. SC are better when they:  Are short in length  Minimize the use of lists and when necessary numbered lists are preferred to more easily allow referencing specific items  Do not require the use of "notes" (Notes are regarded as Normative in WCAG 2.0 and 2.1)  Avoid jargon and unnecesarily complex language. When utilizing a glossary term (or adding a glossary term) the SC needs to make sense when the defined term is replaced with the full glossary definition.The SC can be summarized into a simple language sentence that describes its theme  ==end==   Please provide any comments/suggestions.     Thanks, AWK   Andrew Kirkpatrick Group Product Manager, Standards and Accessibility Adobe    akirkpat@adobe.com http://twitter.com/awkawk