Skip to content
https://chinadaily.com.cn

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
36
GRADE
F
FIX
9
REVIEW
4
PASS
0
INFO
0
Checks
13
4 REVIEW 9 FIX
F
Alt Text Quality
Action
95 of 138 images have issues
FIX
95 of 138 images have issues
Critical::
95 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
87 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 decorative image(s) correctly marked
Info::
42 image(s) with good alt text
138 images 42 good alt text 1 decorative 95 missing
IssueCount
missing95 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-6ojpu3
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Present
PNG Icons Missing
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://chinadaily.com.cn/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://chinadaily.com.cn/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set Dark theme-color Not set CSS indicators Not detected

Detection limited to meta tags and inline styles.

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.
D
Lighthouse Accessibility Audits
Action
Score 53/100 — 7 failing, 10 passed
FIX
53

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > nav.navbartop1 > div.nav-fluid > button.navbutton1 body > nav.navbartop1 > div.nav-fluid > button.navbutton1

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.navbartop1 > div.fl-right > a > img nav.navbartop1 > div.fl-right > a > img
body > div.r-tou > a.rtou-lf > img body > div.r-tou > a.rtou-lf > img
body > div.r-tou > span.rtou-rig > img body > div.r-tou > span.rtou-rig > img
div.carousel-inner > div.item > a > img div.carousel-inner > div.item > a > img
div.twBox > div.Pic > a > img#TopNews div.twBox > div.Pic > a > img#TopNews
div.tmR > div.hot-r > a > img div.tmR > div.hot-r > a > img
div.tmR > div.hot-r > a > img div.tmR > div.hot-r > a > img
div.twBox > span > a > img div.twBox > span > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
div.cmLBoxL > div > a > img div.cmLBoxL > div > a > img
div.twBox > span > a > img div.twBox > span > a > img
div.mar-bott > span > a > img div.mar-bott > span > a > img
div.cmLBoxL > div > a > img div.cmLBoxL > div > a > img
div.twBox > span > a > img div.twBox > span > a > img
div.twBox > span > a > img div.twBox > span > a > img
div.cmLBoxL > div > a > img div.cmLBoxL > div > a > img
div.twBox > span > a > img div.twBox > span > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
div.mar-bott > span > a > img div.mar-bott > span > a > img
div.twBox > span > a > img div.twBox > span > a > img
div.cmLBoxR > div.hot-r > a > img div.cmLBoxR > div.hot-r > a > img
div.cmLBoxR > div.hot-r > a > img div.cmLBoxR > div.hot-r > a > img
div.twBox > span > a > img div.twBox > span > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
div.cmLBoxL > div > a > img div.cmLBoxL > div > a > img
div.twBox > span > a > img div.twBox > span > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
div.twBox > span > a > img div.twBox > span > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
ul.twBox > li > a > img ul.twBox > li > a > img
div.twBox > span > a > img div.twBox > span > a > img
div.twBox > span > a > img div.twBox > span > a > img
div.cmLBoxR > div.cmLBoxR_l > a.txt1 > img div.cmLBoxR > div.cmLBoxR_l > a.txt1 > img
div.cmLBoxR > div.cmLBoxR_r > a > img div.cmLBoxR > div.cmLBoxR_r > a > img
div.cmLBoxR > div.cmLBoxR_l > a.txt1 > img div.cmLBoxR > div.cmLBoxR_l > a.txt1 > img
div.cmLBoxR > div.cmLBoxR_r > a > img div.cmLBoxR > div.cmLBoxR_r > a > img
div.mobile-miscs > div.showDesktop > span.showDesktop-English > img div.mobile-miscs > div.showDesktop > span.showDesktop-English > img
div.showDesktop > span.showDesktop-Chinese > a > img div.showDesktop > span.showDesktop-Chinese > a > img
div.mobile-miscs > div.showDesktop > span.showDesktop-Desktop > img div.mobile-miscs > div.showDesktop > span.showDesktop-Desktop > img

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
body > nav.navbartop1 > div.fl-right > a body > nav.navbartop1 > div.fl-right > a
body > div.r-tou > a.rtou-lf body > div.r-tou > a.rtou-lf
div#myCarousel > div.carousel-inner > div.item > a div#myCarousel > div.carousel-inner > div.item > a
div.tMain > div.tmL > div#myCarousel > a#carleft div.tMain > div.tmL > div#myCarousel > a#carleft
div.tMain > div.tmL > div#myCarousel > a#carright div.tMain > div.tmL > div#myCarousel > a#carright
div.tmR > div.twBox > div.Pic > a div.tmR > div.twBox > div.Pic > a
div.cmLBoxL > div.twBox > span > a div.cmLBoxL > div.twBox > span > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBox > div.cmLBoxL > div > a div.cmLBox > div.cmLBoxL > div > a
div.cmLBoxL > div.twBox > span > a div.cmLBoxL > div.twBox > span > a
div.cmLBoxR > div.mar-bott > span > a div.cmLBoxR > div.mar-bott > span > a
div.cmLBox > div.cmLBoxL > div > a div.cmLBox > div.cmLBoxL > div > a
div.cmLBoxL > div.twBox > span > a div.cmLBoxL > div.twBox > span > a
div.cmLBoxR > div.twBox > span > a div.cmLBoxR > div.twBox > span > a
div.cmLBox > div.cmLBoxL > div > a div.cmLBox > div.cmLBoxL > div > a
div#cul-bott > div.twBox > span > a div#cul-bott > div.twBox > span > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBoxR > div.mar-bott > span > a div.cmLBoxR > div.mar-bott > span > a
div.cmLBoxL > div.twBox > span > a div.cmLBoxL > div.twBox > span > a
div.cmLBoxL > div.twBox > span > a div.cmLBoxL > div.twBox > span > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBox > div.cmLBoxL > div > a div.cmLBox > div.cmLBoxL > div > a
div.cmLBoxL > div.twBox > span > a div.cmLBoxL > div.twBox > span > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBoxL > div.twBox > span > a div.cmLBoxL > div.twBox > span > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBoxR > ul.twBox > li > a div.cmLBoxR > ul.twBox > li > a
div.cmLBoxL > div.twBox > span > a div.cmLBoxL > div.twBox > span > a
div.cmLBoxR > div.twBox > span > a div.cmLBoxR > div.twBox > span > a
div.cmLBox > div.cmLBoxR > div.cmLBoxR_l > a.txt1 div.cmLBox > div.cmLBoxR > div.cmLBoxR_l > a.txt1
div.cmLBox > div.cmLBoxR > div.cmLBoxR_r > a div.cmLBox > div.cmLBoxR > div.cmLBoxR_r > a
div.cmLBox > div.cmLBoxR > div.cmLBoxR_l > a.txt1 div.cmLBox > div.cmLBoxR > div.cmLBoxR_l > a.txt1
div.cmLBox > div.cmLBoxR > div.cmLBoxR_r > a div.cmLBox > div.cmLBoxR > div.cmLBoxR_r > a
div.mobile-miscs > div.showDesktop > span.showDesktop-Chinese > a div.mobile-miscs > div.showDesktop > span.showDesktop-Chinese > a

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.

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
Copyright 1995 - 2026 . All rights reserved. The content (including but not lim… body > footer.mobile-foot > div.mobile-miscs > p.footer-p

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

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-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
Document has a `<title>` element
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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
`<frame>` or `<iframe>` elements have a title
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<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.
No element has a `[tabindex]` value greater than 0
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.
Elements with visible text labels have matching accessible names.
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.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

B
Heading Hierarchy
26 headings
REVIEW
26 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Xi: Enhance Sino-Russian strategic coordination
  • H3 Global partners eye prospects at Hainan expo
  • H3 In the age of AI, no one should be left behind
  • H3 Shear whimsy: Sheep-themed drink causes stir online
  • H3 Kiln it — porcelain hub pulls foreign artists
  • H3 Xi: Enhance Sino-Russian strategic coordination
  • H3 Global partners eye prospects at Hainan expo
  • H3 In the age of AI, no one should be left behind
  • H3 Shear whimsy: Sheep-themed drink causes stir online
  • H2 Beijing, Hanoi vow to boost ties
  • H2 VIDEO +
  • H2 China +
  • H2 Business +
  • H2 Culture +
  • H2 World +
  • H2 Travel / Food +
  • H2 Regional +
  • H2 Sports +
  • H2 Opinion +
  • H2 VIDEO +
  • H2 Spotlight
  • H2 Media Partner
  • H2 Special
  • H2 Editor's Pick
  • H2 Columnists
  • H2 ChinaCulture

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
Form Accessibility
Action
6 of 6 controls have issues
REVIEW
6 of 6 controls have issues
Critical::
6 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" id="searchtxt">; <input type="radio" name="pub1InlineRadioOptions">; <input type="radio" name="pub1InlineRadioOptions">; <input type="radio" name="pub1InlineRadioOptions">; <input type="button" name="btnSubmitPub1VoteSub" id="btnSubmitPub1VoteSub">; <input type="button" name="btnSubmitPub1VoteVR" id="btnSubmitPub1VoteVR">
6 controls
0 labeled
0 placeholder only
6 unlabeled
ControlTypeLabelMethod
#searchtxttext(none)none
pub1InlineRadioOptionsradio(none)none
pub1InlineRadioOptionsradio(none)none
pub1InlineRadioOptionsradio(none)none
#btnSubmitPub1VoteSubbutton(none)none
#btnSubmitPub1VoteVRbutton(none)none

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

<input type="text" id="searchtxt">; <input type="radio" name="pub1InlineRadioOptions">; <input type="radio" name="pub1InlineRadioOptions">; <input type="radio" name="pub1InlineRadioOptions">; <input type="button" name="btnSubmitPub1VoteSub" id="btnSubmitPub1VoteSub">; <input type="button" name="btnSubmitPub1VoteVR" id="btnSubmitPub1VoteVR">

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
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title China Daily Website …21.00:14.5:1
#000000
#FFFFFF
Pass
span Search18.81:14.5:1
#000000
#E6F5FA
Pass
a HOME10.37:14.5:1
#000000
#89BDDB
Pass
a CHINA16.60:14.5:1
#000000
#F4E2CC
Pass
a WORLD16.52:14.5:1
#000000
#F5E1CC
Pass
a BUSINESS16.52:14.5:1
#000000
#F4E1CF
Pass
a CULTURE16.08:14.5:1
#000000
#F5DDCA
Pass
a TRAVEL11.05:14.5:1
#000000
#CCB9A5
Pass
a VIDEO5.53:14.5:1
#000000
#918072
Pass
a SPORTS21.00:14.5:1
#000000
#FFFFFF
Pass
a OPINION21.00:14.5:1
#000000
#FFFFFF
Pass
a REGIONAL21.00:14.5:1
#000000
#FFFFFF
Pass
a SERVICE21.00:14.5:1
#000000
#FFFFFF
Pass
a NEWSPAPER21.00:14.5:1
#000000
#FFFFFF
Pass
a MOBILE19.60:14.5:1
#000000
#F7F7F7
Pass
div Site Search21.00:14.5:1
#000000
#FFFFFF
Pass
li Site Search21.00:14.5:1
#000000
#FFFFFF
Pass
li Sogou Search21.00:14.5:1
#000000
#FFFFFF
Pass
a Global Edition21.00:14.5:1
#000000
#FFFFFF
Pass
a ASIA21.00:14.5:1
#000000
#FFFFFF
Pass

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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback