Skip to content
https://rts.ch

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
44
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Heading Hierarchy
Action
98 headings, 5 skip(s)
FIX
98 headings, 5 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Découvrir plus
  • H4 S'informer
  • H4 S'informer
  • H4 Approfondir
  • H4 Se divertir
  • H4 Enfants et jeunes
  • H3 Découvrir plus
  • H4 S'informer
  • H4 S'informer
  • H4 Approfondir
  • H4 Se divertir
  • H4 Enfants et jeunes
  • H2 TV & Streaming
  • H2 Audio
  • H3 Portail audio
  • H4 RUAG mise sur une intelligence artificielle 100% suisse pour répondre aux besoins de la défense
  • H4 "Je suis tellement fière de l’équipe, du staff et du club", partage Laure Margot
  • H4 Fribourg s'impose en prolongations grâce à Julien Sprunger et mène désormais 2-1!
  • H4 Deuxième sacre consécutif pour Nyon!
  • H4 L'émission 36.9° célèbre deux décennies de santé sur la RTS
  • H4 Le procès de Pascal Jaussi, patron déchu de Swiss Space Systems, va enfin s'ouvrir
  • H4 "C'est déjà demain", festival genevois dédié à la jeune création théâtrale
  • H4 L'Iran dit avoir saisi deux navires dans le détroit d'Ormuz après la prolongation de la trêve
  • H2 L'info décryptée
  • H3 La maltraitance animale dans les sports équestres
  • H3 Un banc rouge contre les violences faites aux femmes
  • H3 L'impact de la pénurie de kérosène sur les vols estivaux
  • H3 Patrouille des Glaciers: l'année des femmes
  • H3 Et si c'était la bonne pour Gottéron?
  • H3 Suisse Tourisme agit pour un tourisme responsable
  • H3 Leila Wandeler, t'as quoi dans ton phone?
  • H3 Conflit chez les chimpanzés: une leçon sur nos guerres
  • H3 Beney - Luyet: pros et potes depuis toujours
  • H3 "Instagram a contribué à tuer ma fille."
  • H3 "Des billets à 6000 dollars, qui peut se permettre ça?"
  • H3 4 voitures de luxe sont volées chaque semaine en Suisse
  • H3 Encore un cas de racisme dans le foot suisse
  • H3 Des baskets inclusives
  • H3 L'Italie va perdre l'organisation de l'Euro 2032?
  • H3 Le premier thermomètre de l'IA est Suisse
  • H3 Un Picasso pour 100 euros
  • H3 Pourquoi les filles arrêtent le sport?
  • H3 Le comeback de Naomi Luyet
  • H3 La seconde vie des auberges de jeunesse
  • H2 Les plus populaires
  • H2 Vidéos
  • H3 L'invitée de La Matinale (vidéo) - Mitra Sohrabi, avocate et présidente de l'association "Femme Vie Liberté Suisse"
  • H3 Swiss Space Systems: le procès de Pascal Jaussi va bientôt s'ouvrir à Fribourg
  • H3 4 candidats pour succéder à Antonio Guterres à la tête de l'ONU
  • H3 Le Conseil fédéral en séance extra-muros à Estavayer-le-Lac
  • H3 Régulation des banques d'importance systémique: analyse de Pierre Nebel
  • H3 Baisser la voix
  • H3 Le remboursement des taxes américaines devrait commencer ce lundi
  • H3 L'invité de La Matinale (vidéo) - Eric Bonvin, directeur général de l'Hôpital du Valais
  • H3 Pont de Chippis classé, l'humain plutôt que la vieille pierre
  • H3 Trump prolonge unilatéralement le cessez-le-feu au Moyen-Orient
  • H2 Audios
  • H3 Ca fait quoi, de devenir mère ?
  • H3 Le Jura prépare sa résistance contre l'autoproclamé "roi de Suisse"
  • H3 Qui est vraiment Vincent Bolloré?
  • H3 La Suisse doit-elle limiter sa population: débat entre Lisa Mazzone, Johanna Gapany, Antoine Spillmann et Nicolas Kolly
  • H3 Hockey sur glace: Davos reçoit Fribourg-Gottéron pour le troisième match de la finale des playoffs
  • H3 Pourquoi Donald Trump se prend-il pour Jésus ?
  • H3 Quelles sont les mesures prises par la Suisse vis-à-vis du cadmium, un métal lourd omniprésent dans notre nourriture?
  • H3 Un pilier du climat mondial pourrait s’effondrer, entraînant des conséquences importantes sur le climat européen, selon une étude
  • H3 Après plusieurs débordements de supporters, la sécurité de la BCF Arena sera sous tension
  • H3 Des notaires accusés d'avoir illégalement consulté des données confidentielles sur Crans-Montana
  • H2 Tendances et mode de vie
  • H4 Protéger son audition, c'est préserver son cerveau skipped
  • H4 Podcast – Ca fait quoi, de devenir mère?
  • H4 L'Unesco alerte sur le rôle vital de ses sites protégés face à l'effondrement de la biodiversité
  • H4 Les anniversaires d'enfants deviennent un marché de plus en plus lucratif
  • H2 Culture
  • H4 "Budapest", le labyrinthe urbanistico-littéraire de Nina Yargekov skipped
  • H4 Sofiane Pamart fait tourner les stars autour de son piano sur "Movie", son nouvel album
  • H4 L'impact des guerres sur la Suisse au coeur d'une exposition au Musée national de Zurich
  • H4 Une pétition demande l'annulation de la tournée de concerts de Patrick Bruel
  • H2 Sport
  • H4 Affaire Fischer: "On était tous sous le choc", confie Romain Loeffel skipped
  • H4 Sydney Schertenleib championne d'Espagne avec le Barça
  • H4 Le phénomène français Paul Seixas l'emporte devant le Zurichois Mauro Schmid
  • H4 Mathias Seger: "J'aimais les défis. Je sautais volontiers sur la glace pour les situations chaudes"
  • H2 (empty)
  • H2 Votre soirée TV
  • H2 À ne pas manquer
  • H4 Les Gardiennes skipped
  • H4 L'océan est notre maison
  • H4 Intouchables
  • H4 Nouvel épisode au pays des géants Elbaph!
  • H4 Et si l’avenir appartenait aux nomades?
  • H4 L'humour est dans le pré
  • H4 Une année difficile
  • H4 L’IA, une révolution qui nous dépasse?
  • H2 La RTS se vit avec vous !
  • H4 Le Perchoir en direct skipped
  • H4 En terrain neutre | Gagnez vos billets de cinéma
  • H4 Être paysan·ne | Gagnez vos places pour les avant-premières
  • H3 La RTS

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

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

F
Alt Text Quality
Action
11 of 74 images have issues
FIX
11 of 74 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
3 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
8 image(s) with filename as alt text
Info::
5 image(s) with alt text over 125 characters
Info::
58 image(s) with good alt text
74 images 58 good alt text 8 generic 3 missing
IssueCount
missing3 image(s)
filename8 image(s)
too long5 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

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
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.
B
Form Accessibility
3 of 6 controls have issues
REVIEW
3 of 6 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">; <input type="text" name="q">; <input type="text" name="q">
Info::
3 control(s) properly labeled
6 controls
3 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsubmitRechercheraria-label
inputsubmitRechercheraria-label
inputsubmitRechercheraria-label
qtext(Cherchez un/des mot(s) clé(s))placeholder only
qtext(Cherchez un/des mot(s) clé(s))placeholder only
qtext(Radio Télévision Suisse)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="q">; <input type="text" name="q">; <input type="text" name="q">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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 Page Introuvable - rts.ch ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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 Missing
✓ Multiple Sizes Present
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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

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

A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 La maltraitance anim…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Un banc rouge contre…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 L'impact de la pénu…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Patrouille des Glaci…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Et si c'était la bo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Suisse Tourisme agit…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Leila Wandeler, t'as…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Conflit chez les chi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Beney - Luyet: pros …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 "Instagram a contrib…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 "Des billets à 6000…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 4 voitures de luxe s…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Encore un cas de rac…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Des baskets inclusiv…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 L'Italie va perdre l…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Le premier thermomè…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Un Picasso pour 100 …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pourquoi les filles …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Le comeback de Naomi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 La seconde vie des a…21.00:13.0: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.

A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 27 passed
PASS
94

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.

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
Protéger son audition, c'est préserver son cerveau a.rts-card > div.card-caption > div.card-body > h4.card-title
"Budapest", le labyrinthe urbanistico-littéraire de Nina Yargekov a.rts-card > div.card-caption > div.card-body > h4.card-title
Affaire Fischer: "On était tous sous le choc", confie Romain Loeffel a.rts-card > div.card-caption > div.card-body > h4.card-title
Les Gardiennes a.rts-card > div.card-caption > div.card-body > h4.card-title
Le Perchoir en direct a.rts-card > div.card-caption > div.card-body > h4.card-title

These are opportunities to improve keyboard navigation in your application.

Names and labels

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
div.card-thumbnail > div.embed-responsive > picture > img.embed-responsive-item div.card-thumbnail > div.embed-responsive > picture > img.embed-responsive-item
div.card-thumbnail > div.embed-responsive > picture > img.embed-responsive-item div.card-thumbnail > div.embed-responsive > picture > img.embed-responsive-item
div.card-thumbnail > div.embed-responsive > picture > img.embed-responsive-item div.card-thumbnail > div.embed-responsive > picture > img.embed-responsive-item

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.

○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
●Input buttons have discernible text.
●Form elements have associated labels
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
●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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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 type="image">` elements have `[alt]` text
○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.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback