Linux and MacOS C api packaging #555
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…o dev/shahasad/linux-and-mac-c-api-packaging
…o dev/shahasad/linux-and-mac-c-api-packaging
snnn
reviewed
Mar 6, 2019
| return Status(common::ONNXRUNTIME, common::FAIL, "initialize preallocated buffer failed"); | ||
| } | ||
| deleter.f = DeleteHeapBuffer; | ||
| deleter.f = reinterpret_cast<std::function<void()>>(DeleteHeapBuffer); |
snnn
reviewed
Mar 6, 2019
…o dev/shahasad/linux-and-mac-c-api-packaging
snnn
approved these changes
Mar 6, 2019
snnn
pushed a commit
that referenced
this pull request
Aug 26, 2025
…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 #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] <198982749+Copilot@users.noreply.github.com> Co-authored-by: MaanavD <24942306+MaanavD@users.noreply.github.com>
gedoensmax
pushed a commit
to gedoensmax/onnxruntime
that referenced
this pull request
Sep 2, 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: microsoft#555` on `background-color: #f5f5f5` (6.8:1 ratio) - **After**: `color: microsoft#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] <198982749+Copilot@users.noreply.github.com> Co-authored-by: MaanavD <24942306+MaanavD@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.