Merge pull request #2236 from TejasAmle-Lambdatest/stage

accessibility web score

Author: Ishavyas9

docs/accessibility-web-score.md

@@ -0,0 +1,119 @@
+---
+id: accessibility-web-score
+title: Accessibility Web Score
+hide_title: false
+sidebar_label: Accessibility Web Score
+description: Learn about LambdaTest's Accessibility Score - a unified metric that measures the accessibility health of your website or application workflow through severity-weighted calculations.
+keywords:
+- accessibility score
+- accessibility testing
+- wcag compliance
+- accessibility metrics
+- accessibility health
+url: https://www.lambdatest.com/support/docs/accessibility-web-score/
+site_name: LambdaTest
+slug: accessibility-web-score/
+---
+
+The Accessibility Score is a unified metric that represents the accessibility health of your website or application workflow.
+Gone are the days of sifting through lengthy accessibility reports trying to figure out what matters most. The Accessibility Score gives you a clear, actionable number that tells you exactly where your product stands on accessibility compliance.
+Use this score to track your progress over time, compare releases, and demonstrate tangible improvements to stakeholders.
+
+## Who needs this?
+
+The Accessibility Score helps:
+
+- **Product Managers** who need to quantify accessibility health and present progress to leadership
+- **QA Engineers** tracking accessibility improvements across sprints
+- **Accessibility Teams** monitoring compliance and identifying problem areas
+- **Developers** who want quick feedback on whether their changes improve or hurt accessibility
+
+If you're building digital products that real people use, this score matters.
+
+## Where to find it
+
+Navigate to any completed accessibility test in your LambdaTest dashboard. The Accessibility Score appears prominently in the test report, giving you an instant read on how that specific scan performed.
+
+---
+
+## How the score is calculated
+
+The Accessibility Score reflects both **how many** accessibility issues exist and **how severe** those issues are. A site with 100 minor issues scores differently than one with 10 critical blockers, and our formula accounts for that reality.
+
+### Step 1: Weight issues by severity
+
+Not all accessibility violations carry equal impact. A missing form label (critical) prevents screen reader users from completing tasks, while a small color contrast issue (minor) might only affect readability slightly.
+
+We assign each severity level a multiplier:
+
+| Severity | Weight | Why this matters |
+|----------|--------|------------------|
+| Critical | 1.0 | Complete blockers that prevent access |
+| Serious | 0.75 | Major barriers that significantly impair experience |
+| Moderate | 0.50 | Notable issues affecting usability |
+| Minor | 0.25 | Small problems with limited impact |
+
+**Calculate the weighted severity (z):**
+```
+z = (% critical × 1.0) + (% serious × 0.75) + (% moderate × 0.50) + (% minor × 0.25)
+```
+
+This gives us a single number representing the severity distribution across all issues found.
+
+### Step 2: Measure issue density
+
+Raw issue counts don't tell the whole story. Finding 50 issues on a page with 1,000 elements is different from finding 50 issues on a page with 100 elements.
+
+**Calculate the density (y):**
+```
+y = Total issues / Total elements
+```
+
+This ratio shows how widespread accessibility problems are across your page structure.
+
+### Step 3: Calculate the final score
+
+We combine severity weighting and issue density to determine how much they should reduce your score from a perfect 100:
+```
+Accessibility Score = 100 - (y × 100 × z)
+```
+
+The score scales from 0 to 100, where:
+- **90-100**: Excellent accessibility with minimal issues
+- **70-89**: Good, but room for improvement
+- **50-69**: Moderate issues requiring attention
+- **Below 50**: Significant accessibility barriers present
+
+
+**Note:** The Accessibility Score is a proprietary metric developed by LambdaTest. This scoring methodology is unique to our platform and provides a tailored approach to measuring accessibility health.
+
+
+---
+
+## Calculating scores across pages and tests
+
+The same formula applies whether you're looking at a single page or an entire test with multiple pages.
+This approach ensures that particularly problematic pages don't get hidden by well-performing ones, giving you an accurate view of your overall accessibility health.
+
+---
+
+## What impacts your score
+
+- **Severity distribution**: A page with mostly critical issues scores lower than one with mostly minor issues, even if the total count is the same.
+- **Issue density**: More issues relative to page elements means a lower score. A complex page with many elements can absorb more issues before the score drops dramatically.
+- **Total element count**: Pages with more elements have more opportunities for issues, but the density calculation accounts for this fairly.
+
+---
+
+## Improving your score
+
+Focus on high-impact changes:
+
+1. **Fix critical issues first** - They carry the most weight and create real barriers for users
+2. **Reduce issue density** - Systematic problems affecting many elements hurt your score more than isolated issues
+3. **Test iteratively** - Run scans after each fix to track improvements in real-time
+
+
+:::tip Remember
+The goal isn't gaming the score, it's making your product genuinely accessible to everyone.
+:::

sidebars.js

@@ -1960,6 +1960,7 @@ module.exports = {
           "accessibility-passed-test-cases",
           "accessibility-capture-screenshot",
           "accessibility-fragment-identifier",
+          "accessibility-web-score"
         ],
       },
       {