Add top guides section to a11y intro + a11y content updates

docs/accessibility/core-concepts/run-level-reports.mdx

@@ -91,7 +91,7 @@ Attributes for each rule include:
 You can filter Views and Rules in accessibility reports by:
 
 - **Rule severity**: Critical, serious, moderate, or minor.
-- **Rules**: WCAG 2.1 A, WCAG 2.1AA, or Best practices.
+- **Rules**: WCAG 2.1 A, WCAG 2.1 AA, or Best Practices.
 - **Element status**: Failed, inconclusive, or other (other includes ignored elements and rules, 100% passing views and rules, and inapplicable rules).
 - **Name**: Search for specific URLs or paths to filter the views or specific names to filter rules.
 

docs/accessibility/guides/accessibility-automation.mdx

@@ -17,7 +17,7 @@ Cypress Accessibility runs Axe Core® checks on every significant state and vari
 Accessibility can be thought of as three progressive levels:
 
 - **Basic Usability**: This is the threshold at which a disabled user is likely to be able to make substantial progress through the application, but may still hit major barriers or usability issues. If your contact forms and issue reporting systems are accessible, you will be able to learn about these problems from actual users. Paying attention to issues reported by Cypress and Axe Core® should help you to this point.
-- **WCAG Conformance**: Automated tools like Axe Core® catch up to [57% of accessibility issues that would appear in a manual audit](https://www.deque.com/blog/automated-testing-study-identifies-57-percent-of-digital-accessibility-issues/), but human assessment is essential for validating conformance. Conformance with the WCAG is often the standard set by legislation and regulation related to web accessibility. If your goal is regulatory compliance, this is the bar. No generic automation tool can "prove" compliance with this standard, it **requires** human assessment.
+- **WCAG Conformance**: Automated tools like Axe Core® detect many significant accessibility barriers, but human assessment is essential for validating conformance with the Web Content Accessibility Guidelines (WCAG). This is often the standard set by legislation and regulation related to web accessibility. If your goal is regulatory compliance, this is the bar. No generic automation tool can "prove" compliance with this standard, it **requires** human assessment.
 - **Good User Experience**: This needs to be validated by actual disabled users who are daily users of assistive technology. It's entirely possible to have a website that passes the first two levels, and still offers a poor user experience.
 
 Accessibility is about communicating the nature and structure of the application, and the available actions and information, in a way that allows disabled users to independently understand the interface and complete all tasks. The [POUR principles](https://www.24a11y.com/2019/pour-the-foundation-first/) (Perceivable, Operable, Understandable, Robust) form the foundation for effective accessibility beyond specific tests or checks. While Axe Core® tells us about many genuine accessibility barriers, it's important to leverage that information into making good decisions about accessibility and providing a truly equal experience.