Move accessibility impact into Accessibility Considerations section.

Author: msporny

index.html

@@ -2559,6 +2559,18 @@ <h2>Accessibility Considerations</h2>
 
       <em>This section is non-normative.</em>
 
+      <p>
+There are a number of accessibility considerations of which implementors
+should be aware when processing data described in this specification.
+As with any implementation of web standards or protocols, ignoring
+accessibility issues will make this information unusable to a large
+subset of the population. It is important to follow accessiblity
+guidelines and standards such as [[WCAG21]] to ensure that all people,
+regardless of ability, can make use of this data. This is especially
+important when establishing systems that utilize cryptography and encryption,
+which, historically, have created problems for assistive technologies.
+      </p>
+
       <p>
 This section details the general accessibility considerations that should be
 taken into account when utilizing this data model.
@@ -2571,8 +2583,9 @@ <h3>Data First Approaches</h3>
 cards, have poor accessibility characteristics. Some of these poor
 characteristics include, but are not limited to, small print,
 reliance on small, high resolution images, and no affordances for people with
-vision disabilities.
+vision impairments.
         </p>
+
         <p>
 When utilizing this data model to create verifiable credentials, it is
 suggested that data model designers use a "data first" approach. For example,
@@ -2582,7 +2595,7 @@ <h3>Data First Approaches</h3>
 machine readable way rather than solely relying on the image to convey this
 information. This approach is preferred because a "data first" approach
 provides the foundational elements of building different interfaces for
-people with disabilities.
+people with varying abilities.
         </p>
       </section>
     </section>
@@ -3384,9 +3397,6 @@ <h3>Device Theft and Impersonation</h3>
         </ul>
 
     </section>
-      <section>
-        <h2>Accessibility Impact</h2>
-        <p>There are a number of accessibility considerations of which implementors should be aware when processing data described in this specification. As with any implementation of web standards or protocols, ignoring accessibility issues will make this information unusable to a large subset of the population. It is important to follow accessiblity guidelines and standards such as [WCAG21] to ensure that all people, regardless of ability can make use of this data. This is especially important when establishing cryptography and encryption which historically have created problems for assistive technologies.
 
   </body>
 </html>