Skip to content
https://astm.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
F
Heading Hierarchy
Action
43 headings, 8 skip(s)
FIX
43 headings, 8 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H6 (empty)
  • H6 (empty)
  • H4 New & Noteworthy
  • H6 Change With Accuris Agreement skipped
  • H6 Enterprise Risk Management
  • H6 ASTM Website in Additional Languages
  • H6 Standardization News March/April 2026
  • H6 About ASTM
  • H6 Membership & Participation
  • H4 Standards & Solutions
  • H5 ASTM Compass®
  • H6 Annual Book of ASTM Standards
  • H6 ASTM Digital Library
  • H6 ASTM SpecBuilder
  • H6 Additional Standards Publishers
  • H4 Market Insights & Innovation
  • H6 Standardization Impact Report skipped
  • H6 ASTM Xcellerate
  • H6 Centers of Excellence
  • H6 Market Intelligence & Wohlers Reports
  • H4 Laboratory Services
  • H6 Comprehensive Solutions for All Your QA/QC Needs skipped
  • H4 Training and Certification
  • H6 Industry Leading Live and OnDemand Training skipped
  • H2 13,000+
  • H6 Global ASTM Standards skipped
  • H2 125
  • H6 MoU Partner Countries skipped
  • H2 35,000+
  • H6 Volunteer Members skipped
  • H4 Latest News
  • H6 New Suite of Supply Chain Standards skipped
  • H6 3 Standards for PFAS Measurement
  • H6 Podcast: Standards on Tap
  • H6 New Sample Procedure for Air Quality
  • H6 Shower Chair Standard Proposed
  • H6 Proposed Urban Heat Standard
  • H6 About ASTM
  • H6 Membership & Participation
  • H6 Standards & Solutions
  • H6 News
  • H6 Help
  • H6 Policies

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

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

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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::
2 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 2 <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
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: ASTM International
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ASTM International ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name ASTM International Display Mode standalone Theme Color #021740 Background Color #021740 Icons 2 icon(s)
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, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA 5 pass AA only
button About ASTM
3.81:1
#000000
on
#4D6C87
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
button Membership & Participation
1.39:1
#000000
on
#01264E
needs 4.5:1 (normal text)
16px · above the fold
button Standards & Solutions
1.39:1
#000000
on
#01264E
needs 4.5:1 (normal text)
16px · above the fold
button News
2.28:1
#000000
on
#1E4C65
needs 4.5:1 (normal text)
16px · above the fold
button Help
2.51:1
#000000
on
#2A526A
needs 4.5:1 (normal text)
16px · above the fold
a FAQ
2.64:1
#000000
on
#31556B
needs 4.5:1 (normal text)
16px · above the fold
span Cart
2.00:1
#000000
on
#13445A
needs 4.5:1 (normal text)
16px · above the fold
span Loading...
1.84:1
#000000
on
#0B3E57
needs 4.5:1 (normal text)
16px · above the fold
span Loading...
1.73:1
#000000
on
#093A50
needs 4.5:1 (normal text)
16px · above the fold
button Menu
1.92:1
#000000
on
#2F3E4E
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Home
2.76:1
#000000
on
#505364
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

3 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
h2 13,000+8.95:13.0:1
#0033CC
#FFFFFF
Pass
h2 1258.95:13.0:1
#0033CC
#FFFFFF
Pass
h2 35,000+8.95:13.0:1
#0033CC
#FFFFFF
Pass
title ASTM International |…5.88:14.5:1
#000000
#708B9E
Pass
span Using Artificial Int…5.72:14.5:1
#000000
#6E899C
Pass
button Menu5.72:14.5:1
#000000
#6E899C
Pass
a Home5.72:14.5:1
#000000
#6E899C
Pass
button About ASTM3.81:14.5:1
#000000
#4D6C87
Fail
button Membership & Partici…1.39:14.5:1
#000000
#01264E
Fail
button Standards & Solution…1.39:14.5:1
#000000
#01264E
Fail
button News2.28:14.5:1
#000000
#1E4C65
Fail
button Help2.51:14.5:1
#000000
#2A526A
Fail
a FAQ2.64:14.5:1
#000000
#31556B
Fail
span Cart2.00:14.5:1
#000000
#13445A
Fail
span Loading...1.84:14.5:1
#000000
#0B3E57
Fail
span Loading...1.73:14.5:1
#000000
#093A50
Fail
button Menu1.92:14.5:1
#000000
#2F3E4E
Fail
a Home2.76:14.5:1
#000000
#505364
Fail
button About ASTM7.13:14.5:1
#000000
#7F9AAD
Pass
button Membership & Partici…6.97:14.5:1
#000000
#7E98AB
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 6 failing, 21 passed
REVIEW
81

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Welcome to astm.org You're about to be directed to the ASTM in the America Lat… body.modal-open > div > div > div.modal

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
header.position-relative > div.container-xl > div.ms-auto > button.d-md-none header.position-relative > div.container-xl > div.ms-auto > button.d-md-none
div.container-xl > div.ms-auto > div.headersignin_headerSignInContainer__JP_Ja > button.astm-btn div.container-xl > div.ms-auto > div.headersignin_headerSignInContainer__JP_Ja > button.astm-btn

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
Apr 16, 2026 div.g-col-12 > a.p-3 > span.d-flex > p.mb-0
Apr 14, 2026 div.g-col-12 > a.p-3 > span.d-flex > p.mb-0
Apr 14, 2026 div.g-col-12 > a.p-3 > span.d-flex > p.mb-0
Apr 13, 2026 div.g-col-12 > a.p-3 > span.d-flex > p.mb-0
Mar 30, 2026 div.g-col-12 > a.p-3 > span.d-flex > p.mb-0
Mar 27, 2026 div.g-col-12 > a.p-3 > span.d-flex > p.mb-0

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Spanish div.d-flex > div.d-flex > p > a
Portuguese div.d-flex > div.d-flex > p > a
Japanese div.d-flex > div.d-flex > p > a
Chinese div.d-flex > div.d-flex > p > a
Korean div.d-flex > div.d-flex > p > a

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
Change With Accuris Agreement div.h-100 > div.d-flex > div.d-flex > h6
Standardization Impact Report div.childfeaturecard_cardMain__AvKXo > div.childfeaturecard_cardBodyPadding__Qh97I > div.flex-grow-1 > h6.text-left
Comprehensive Solutions for All Your QA/QC Needs div.d-flex > div.w-50 > div.styles_contentText__bPJ6F > h6
Industry Leading Live and OnDemand Training div.d-flex > div.w-50 > div.styles_contentText__bPJ6F > h6
Global ASTM Standards div.childstatcard_cardMain__W1zs4 > div.childstatcard_cardBodyPadding__SwNXF > div.text-muted > h6.text-left
MoU Partner Countries div.childstatcard_cardMain__W1zs4 > div.childstatcard_cardBodyPadding__SwNXF > div.text-muted > h6.text-left
Volunteer Members div.childstatcard_cardMain__W1zs4 > div.childstatcard_cardBodyPadding__SwNXF > div.text-muted > h6.text-left
New Suite of Supply Chain Standards div.grid > div.g-col-12 > a.p-3 > h6.styles_contentHeading__Maf1F

These are opportunities to improve keyboard navigation in your application.

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
New Suite of Supply Chain Standards The new standards support goods movement pr… div.d-flex > div.grid > div.g-col-12 > a.p-3
3 Standards for PFAS Measurement PFAS remediation and measurement promises to b… div.d-flex > div.grid > div.g-col-12 > a.p-3
Podcast: Standards on Tap Members of the committee on sensory evaluation have a… div.d-flex > div.grid > div.g-col-12 > a.p-3
New Sample Procedure for Air Quality The new standard will help protect workers… div.d-flex > div.grid > div.g-col-12 > a.p-3
Shower Chair Standard Proposed Participation is sought on the proposed standard… div.d-flex > div.grid > div.g-col-12 > a.p-3
Proposed Urban Heat Standard Participation is sought for the proposed standard,… div.d-flex > div.grid > div.g-col-12 > a.p-3
○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
●Image elements have `[alt]` attributes
●`[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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○`<frame>` or `<iframe>` elements have a title
○`<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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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
○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.
○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+
Alt Text Quality
All 19 images OK
PASS
All 19 images OK
Info::
19 image(s) with good alt text
19 images 19 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsearchSearcharia-label
inputsearchSearcharia-label
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback