definitions for new SCs

accessibility-checker-engine/src/v4/rulesets.ts

@@ -69,10 +69,13 @@ const summaries = {
     "3.2.2": "Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.",
     "3.2.3": "Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.",
     "3.2.4": "Components that have the same functionality within a set of Web pages are identified consistently.",
+    "3.2.6": "Make it easier to find help and support. If a Web page contains help mechanisms they occur in the same order relative to other page content, unless a change is initiated by the user.",
     "3.3.1": "If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.",
     "3.3.2": "Labels or instructions are provided when content requires user input.",
     "3.3.3": "If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.",
     "3.3.4": "For content that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, the user can reverse, correct, or confirm the action.",
+    "3.3.7": "Make it easier for users to complete multi-step processes. Don't ask for the same information twice in the same session.",
+    "3.3.8": "Make logins possible with less mental effort. Don't make people solve, recall, or transcribe something to log in.",
     "4.1.1": "(Obsolete and removed) This requirement was originally adopted to address problems that assistive technology (AT) had directly parsing HTML. AT no longer has any need to directly parse HTML. Consequently, these problems either no longer exist or are addressed by other requirements.", 
     "4.1.2": "For all user interface components (including, but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.",
     "4.1.3": "In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.",