Accessibility
Content Warnings (CWs)
We use the term "warning" because that is the most recognized term and abbreviation. CWs (at least in our usage of them) are actually "content notices," an accessibility feature for our members with various sensitivities to particular topics or types of content.
CWs do not place a judgement on your content or video and they have no effect on awards.
When Hosting RICE Events
RICE takes place in a few dedicated Discord channels visible only to the participants.
During the event, members are encouraged to create their own voice chats, streams, discussions, mini-events, etc.
You may run any type of event you like during RICE - as long as it has something to do with the videos submitted, follows server rules, and you declare what type of discussion will occur.
Everyone has the ability to create threads and events using the Sesh bot. Scheduling events using Sesh will allow you to title and describe your event (which is required by the discussion rules) and give others the opportunity to receive private reminders before the event occurs through RSVPs.
We require a statement about the type of event you are running for accessibility. Some people want to participate, but do not want to hear particular types of feedback.
While harsh constructive criticism is 100% acceptable in RICE, there are few things worse than hopping in a chat just to have fun and unexpectedly being greeted by people tearing apart your or your friend's videos!
We just want people to know what they are getting into before they join it so they know what to expect. 🤗
Some example statements are:
- Positive comments only
- Light critique
- No commentary at all
- More or less a panel where you're simply giving reviews of videos while people listen
Additionally, we have two voice channels during RICE - one with enforced "push to talk" and another which uses the standard "voice activity" so you may run your event in the channel with your preferred setup.
What is push to talk?
Push to talk is one of two voice input modes in Discord. The Push to talk (PTT) setting will automatically mute your microphone unless you are actively pushing a button known as a PTT key. You set what the PTT key is.
This prevents background noise and ensures nothing can be heard unless a user is purposefully speaking.
PTT can be enabled at any time for your personal use across Discord if you prefer this method.
Some voice channels require the use of PTT by all participants. This is the case for the RICE "Push to Talk" channel.
Users who have not set a PTT key in their settings will be muted and unable to speak in the channel until they update their settings.
On desktop, you do not have to change your voice input settings when in a PTT-required voice channel. You only need to have a PTT button set.
On mobile, you may have to change your voice input settings and rejoin the channel in order for the PTT button to appear.
To change your voice settings, go into Discord settings and select "Voice & Video."
Change your input mode to "Push-to-talk."
To set your PTT key, select the keyboard icon ("Edit Keybind") under "shortcut."
Press the key on your keyboard that you want to be the PTT key (right ctrl
or left alt
are some suggestions).
Click the red "stop recording" button when you're done.
In the future, if you want to speak, you must hold down this key while talking to broadcast your voice in a voice channel. The "push-to-talk release delay" setting allows your voice to be broadcast for a slightly longer period of time after you release the PTT key.
If you still want to use Voice Activity by default, change your input mode back to "Voice Activity" when you're done. Otherwise, simply exit the page or hit esc
and your settings will be saved.
To set a PTT key without changing your voice settings, go into Discord settings and select "Keybinds."
You would also use this page if you want to set more than one PTT key, a PTT (priority) key (if you're a moderator), or if you want more control over your voice input options.
Select the "add a keybind" button.
Under "action" select one of the PTT options.
Select the "record keybind" button and press any key on your keyboard that you want to use as your PTT key.
Select "stop recording" when you're done.
The toggle to the right of the row is green for enabled and grey for disabled, if you wish to temporarily disable a certain keybind.
Note:
If you select "Toggle VAD" in the action menu, this allows you to set a keyboard shortcut for switching between Voice Activity and PTT voice input modes.
Warnings Attached to Videos
You do not need to label your videos - the coordinator applies them after video submission.
RICE video submissions can be about anything as long as they follow the video submission requirements and content restrictions.
CWs are applied to videos as a courtesy to others. They do not place a judgement on your video and they have no effect on awards.
RICE participants are encouraged to fill out an optional "Intent to Participate and CW Request" form before the event begins. This form is typically released before submissions open. Users are asked if they would like to be notified of any content that appears in other videos. These are compiled and listed in the CW (content warning) section of the video infosheet, sometimes with expansion in an Extended VPR & CW document.
Vidding Photosensitivity Relay (VPR)
VPR is similar to a CW, but it is specific to content they may cause physical harm to photosensitive individuals.
BentoVid, and by extension, RICE, specifically accommodates our members with these conditions.
The VPR is a tool that allows them to make better informed decisions about which videos they can watch and in what conditions they can watch them in.
Your video does not need to be safe for photosensitive people to watch.
You do not need to make a VPR for your video, but know that your submitted video can receive them.
The content of the VPR is not a judgement on your editing.
RICE uses a modified version of the VPR system. Any physical triggers mentioned in the Intent to Participate form are separated into a VPR-specific list and tagged with the CWs in a slightly different format. They are included in an extended CW & VPR document, an example of which you can view here.
Why doesn't RICE use actual VPR?
To guarantee uniformity across all relays, the coordinator watches every video and applies the VPR themself.
The coordinator gave full VPR for every single video in RICE from 2021 to 2023.
In 2024, it was decided a more reasonable approach would be to ask participants to reveal their triggers in an anonymous form called "Intent to Participate."
Here, they can request any CWs and VPR they would like.
RICE now only warn for triggers mentioned in this form, although full VPR is still possible if someone requests it.
Critique/Feedback
RICE also functions as a workshop to improve our videos and our feedback. All videos will likely get detailed feedback, many down to specific timestamps. All members are encouraged to participate in doing this.
The feedback given does not preclude any video from winning. Critique that is not constructive is removed and users warned/disqualified based on the content. Look to #vid-critique
for examples of how this feedback may look.
You may also view comments left on the 2023 RICE videos here.
RICE uses a "critique tag" to inform participants which videos would like special attention and an even more critical eye. This tag is most useful for editors who plan on changing their video based on the feedback given during RICE. Participants who mark their interest in extended feedback during video submission will have their video marked with a [c]
to denote this desire.
Stress & Managing Expectations
RICE is a stressful event.
RICE typically gets 50+ videos.
Viewing them all and voting within the timeframe by itself is already stressful.
Trying to give good feedback to one video can be difficult enough, but during RICE we want you to give it to as many videos as possible. Assessing, critiquing, and wording useful comments takes time and dedication.
And that's only half of RICE.
The other half of RICE is receiving the feedback. You may not like what you see, and things which may not have upset you in another environment may hurt you more in this one.
We understand RICE is stressful, and we try to make the contest part of it as laid back as possible. But that, too, may upset people as it may not be run how you expected. Please see the Server & Event Culture page for more insight on what to expect.
Please understand that if you have not participated in an event like this before, you may respond in a way you did not expect. Check in with yourself; protect your mental health. It is okay to step away if you have to.
Please read our server guide on how to give, receive, and ask for critique, and for people have never given critique before, try our Musubi Method.
Despite this, BentoVid does NOT condone harassment. Please #contact-staff
if you see this (Ping @Staff
, DM Vars (@standardquip
), create a ticket, or use the /report
command).