Skip to content
https://Juno-innovations.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
5
REVIEW
9
PASS
10
INFO
0
Checks
24
10 PASS 9 REVIEW 5 FIX
D
Mobile-Readable Font Sizes
Action
54% of visible text renders at >= 12 CSS px (107 below threshold)
FIX
54% of visible text renders at >= 12 CSS px (107 below threshold)
Warning::
107 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("Pod Resource Monitor"); <span> 11.0px ("pods"); <span> 10.0px ("</prod>"); <span> 9.0px ("NAMESPACE"); <span> 9.0px ("NAME").
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN CONTENTINFO footer

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C
Heading Hierarchy
Action
30 headings, 2 skip(s)
REVIEW
30 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Run every workload like it's one machine.
  • H3 Running GPU and CPU workloads has meant choosing between two compromises. skipped
  • H3 Hyperscaler GPU rental
  • H3 DIY Kubernetes + VMware glue
  • H3 Two types of teams come to Juno. Here's what changes for each.
  • H3 You're over-provisioning. Every month.
  • H3 Your end users shouldn't need to know Kubernetes.
  • H2 One compute plane. Every workload type.
  • H3 Compute Resource Slicing
  • H3 Many Users, One GPU
  • H2 This won't take long.
  • H3 See how Orion works for your industry
  • H3 🛡️
  • H3 Defense & Government
  • H3 🧬
  • H3 Life Sciences
  • H3 ⚡
  • H3 HPC
  • H3 🤖
  • H3 AI & ML
  • H3 🎬
  • H3 VFX & Animation
  • H3 🌐
  • H3 Edge & Data Center
  • H2 Built-in management tools that keep your team aligned
  • H3 Donald Strubler
  • H1 "Orion shifted our focus from finding stability to using the stability to iterate." duplicate H1
  • H3 ~40% skipped
  • H3 60 sec
  • H3 Breakthroughs run on Juno.

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="button" id="__framer-cookie-component-button-reject">; <input type="button" id="__framer-cookie-component-button-customize">; <input type="button" id="__framer-cookie-component-button-accept">
3 controls
0 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#__framer-cookie-component-button-rejectbutton(none)none
#__framer-cookie-component-button-customizebutton(none)none
#__framer-cookie-component-button-acceptbutton(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="button" id="__framer-cookie-component-button-reject">; <input type="button" id="__framer-cookie-component-button-customize">; <input type="button" id="__framer-cookie-component-button-accept">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

B
Tap Target Adequacy
3 tap target(s) too small or too close together
REVIEW
3 tap target(s) too small or too close together
Info::
3 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Juno Innovations - Breakthroughs Run on Juno ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

1 pass 19 fail WCAG AA 1 pass AA only
h1 Run every workload like it's one machine…
2.25:1
#000000
on
#773217
needs 3.0:1 (large text)
32px · above the fold · over background image/gradient
h1 "Orion shifted our focus from finding st…
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
32px · bottom of viewport
h2 One compute plane. Every workload type.
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
24px · bottom of viewport
h2 This won't take long.
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Built-in management tools that keep your…
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Hyperscaler GPU rental
1.59:1
#000000
on
#512212
needs 3.0:1 (large text)
19px · mid-page
h3 DIY Kubernetes + VMware glue
1.13:1
#000000
on
#220E06
needs 3.0:1 (large text)
19px · mid-page
h3 Two types of teams come to Juno. Here's …
1.05:1
#000000
on
#0A0809
needs 3.0:1 (large text)
19px · bottom of viewport
h3 You're over-provisioning. Every month.
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Your end users shouldn't need to know Ku…
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Compute Resource Slicing
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Many Users, One GPU
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
19px · bottom of viewport
h3 See how Orion works for your industry
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
19px · bottom of viewport
h3 🛡️
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Defense & Government
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
19px · bottom of viewport
h3 🧬
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Life Sciences
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
19px · bottom of viewport
h3 ⚡
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
19px · bottom of viewport
h3 HPC
1.09:1
#000000
on
#0E0E10
needs 3.0:1 (large text)
19px · bottom of viewport

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Run every workload l…2.25:13.0:1
#000000
#773217
Fail
h1 "Orion shifted our f…1.09:13.0:1
#000000
#0E0E10
Fail
h2 One compute plane. E…1.09:13.0:1
#000000
#0E0E10
Fail
h2 This won't take long…1.09:13.0:1
#000000
#0E0E10
Fail
h2 Built-in management …1.09:13.0:1
#000000
#0E0E10
Fail
h3 Running GPU and CPU …3.54:13.0:1
#000000
#9C4E29
Pass
h3 Hyperscaler GPU rent…1.59:13.0:1
#000000
#512212
Fail
h3 DIY Kubernetes + VMw…1.13:13.0:1
#000000
#220E06
Fail
h3 Two types of teams c…1.05:13.0:1
#000000
#0A0809
Fail
h3 You're over-provisio…1.09:13.0:1
#000000
#0E0E10
Fail
h3 Your end users shoul…1.09:13.0:1
#000000
#0E0E10
Fail
h3 Compute Resource Sli…1.09:13.0:1
#000000
#0E0E10
Fail
h3 Many Users, One GPU1.09:13.0:1
#000000
#0E0E10
Fail
h3 See how Orion works …1.09:13.0:1
#000000
#0E0E10
Fail
h3 🛡️1.09:13.0:1
#000000
#0E0E10
Fail
h3 Defense & Government1.09:13.0:1
#000000
#0E0E10
Fail
h3 🧬1.09:13.0:1
#000000
#0E0E10
Fail
h3 Life Sciences1.09:13.0:1
#000000
#0E0E10
Fail
h3 ⚡1.09:13.0:1
#000000
#0E0E10
Fail
h3 HPC1.09:13.0:1
#000000
#0E0E10
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

B
Lighthouse Accessibility Audits
Score 88/100 — 5 failing, 22 passed
REVIEW
88

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GPU Time-Slice Monitor div.ssr-variant > div > div > span
NODE / GPU div.ssr-variant > div > div > span
USER div.ssr-variant > div > div > span
UTILIZATION div.ssr-variant > div > div > span
JOB div.ssr-variant > div > div > span
GPU 0 div > div > div > span
GPU 1 div > div > div > span
GPU 2 div > div > div > span
GPU 3 div > div > div > span
GPU 0 div > div > div > span
GPU 1 div > div > div > span
GPU 2 div > div > div > span
GPU 3 div > div > div > span
3 users · 7 GPUs active · 0 queued div.ssr-variant > div > div > span
Updated 9s div.ssr-variant > div > div > span
* Visualizations represent live cluster state and are illustrative of Orion's o… main.framer-1k7waej > section#features > div.framer-1pmanse > p.framer-text
Compute cost reduction div.framer-1ae6yq8 > div.framer-9zn3fl > div.framer-8lsx3u > p.framer-text
User request to workload running div.framer-13uk021 > div.framer-ptb8e3 > div.framer-jz9opv > p.framer-text
Juno Innovations provides compute orchestration software. Orion is designed for… footer.framer-OACfa > div.framer-zhixdk > div.framer-w3asg > p.framer-text

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Running GPU and CPU workloads has meant choosing between two compromises. div.framer-n6r9la > div.ssr-variant > div.framer-10l2sa3 > h3.framer-text
~40% div.framer-1ae6yq8 > div.framer-1ui2kfd > div.framer-jbawmc > h3.framer-text

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.framer-z3PI5 > div.framer-xmz3tp > div.framer-cm1to5 > a.framer-1hzb0g2 div.framer-z3PI5 > div.framer-xmz3tp > div.framer-cm1to5 > a.framer-1hzb0g2

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Terra App Store div.framer-1h7xzvl > div.framer-1sqrznn > p.framer-text > a.framer-text
KubeVirt — VM Orchestration div.framer-1h7xzvl > div.framer-1hcb4z0 > p.framer-text > a.framer-text
Documentation div.framer-2y62ma > div.framer-1clg6bi > p.framer-text > a.framer-text

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie Settings div.framer-2pSaX > main.framer-1k7waej > div.framer-bm3mjy-container > button.__framer-cookie-component-button
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Info::
3 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "🛡️" - H3: "🧬" - H3: "⚡"
Got: 3 ≤2-char heading(s)
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Alt Text Quality
All 5 images OK
PASS
All 5 images OK
Info::
5 decorative image(s) correctly marked
5 images 5 decorative
All images have appropriate alt text.
A+
Form Input Types
3 form control(s) checked, no type mismatches
PASS
3 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
4 explicit tabindex attribute(s) checked, no anti-patterns
PASS
4 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/2 iframe(s) missing title; 0 placeholder(s)
PASS
1/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://framer.com/edit?framerSiteId=f05068088bc7d52bf1991b23dbc79ec07906b08068…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback