Skip to content

Conversation

jatinwadhwa921
Copy link

Fixed Coverity issues

@ankitm3k
Copy link

ankitm3k commented Feb 4, 2025

lgtm

@sfatimar sfatimar merged commit 48f060b into ovep-develop Feb 4, 2025
7 of 13 checks passed
sfatimar pushed a commit that referenced this pull request Feb 5, 2025
sfatimar pushed a commit that referenced this pull request Feb 5, 2025
sfatimar pushed a commit that referenced this pull request Feb 6, 2025
ankitm3k pushed a commit that referenced this pull request Feb 6, 2025
ankitm3k pushed a commit that referenced this pull request Feb 6, 2025
ankitm3k pushed a commit that referenced this pull request Feb 6, 2025
sfatimar pushed a commit that referenced this pull request Feb 6, 2025
sfatimar pushed a commit that referenced this pull request Feb 6, 2025
sfatimar pushed a commit that referenced this pull request Feb 6, 2025
ankitm3k pushed a commit that referenced this pull request Feb 6, 2025
Jaswanth51 pushed a commit that referenced this pull request Aug 28, 2025
…icrosoft#25832)

This PR addresses accessibility issues with focus indicators on the ONNX
Runtime website documentation where contrast ratios were insufficient
for keyboard navigation users. The accessibility audit revealed that
focus states for key navigation elements like "Learn more about ONNX
Runtime & Generative AI", "Quickstart", "Tutorials", "Install ONNX
Runtime", and "Hardware Acceleration" had contrast ratios as low as
1.152:1, well below the WCAG 2.1 AA requirement of 3:1 for UI
components.

## Changes Made

### 1. Enhanced List Group Item Focus Contrast
- **Before**: `color: #555` on `background-color: #f5f5f5` (6.8:1 ratio)
- **After**: `color: #333` on `background-color: #f5f5f5` (**11.6:1
ratio**)

### 2. Improved Info List Group Item Focus Contrast  
- **Before**: `color: #31708f` on `background-color: #c4e3f3` (4.1:1
ratio)
- **After**: `color: #1e4a5f` on `background-color: #c4e3f3` (**7.1:1
ratio**)

### 3. Added Visible Focus Indicators for Form Inputs
Previously, search and filter inputs only removed the default outline
(`outline: 0`) without providing alternative focus indicators, making
them inaccessible to keyboard users.

- **Added**: `border: 2px solid #0050C5` and `background-color: #f8f9fa`
on focus
- **Contrast ratio**: **6.7:1** (exceeds requirements)

## Accessibility Compliance

All changes now exceed WCAG 2.1 AA standards:
- ✅ **3:1 minimum** for UI components and focus indicators
- ✅ **4.5:1 minimum** for normal text (all exceed 7:1)
- ✅ **Keyboard navigation** fully supported with visible focus
indicators
- ✅ **Screen reader compatibility** improved with clear focus states

## Impact

- Low vision users can now clearly see focused elements during keyboard
navigation
- All mentioned navigation elements meet accessibility standards
- No functionality broken - purely visual accessibility enhancements
- Compliance with MAS 1.4.11 Non-text Contrast requirements

## Files Modified

- `csharp/ApiDocs/_exported_templates/default/styles/docfx.css` -
Enhanced input focus indicators
- `csharp/ApiDocs/_exported_templates/default/styles/docfx.vendor.css` -
Improved text contrast ratios

Fixes microsoft#24995.

<!-- START COPILOT CODING AGENT TIPS -->
---

✨ Let Copilot coding agent [set things up for
you](https://github.com/microsoft/onnxruntime/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot)
— coding agent works faster and does higher quality work when set up for
your repo.

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: MaanavD <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants