Posted by Aditi Paul

Every month or so the OTW will be doing a Q&A with one of its volunteers about their experiences in the organization. The posts express each volunteer’s personal views and do not necessarily reflect the views of the OTW or constitute OTW policy. Today’s post is with Mille K, who volunteers in the Support Committee.

How does what you do as a volunteer fit into what the OTW does?

So, as the blurb said, I’m a volunteer for the OTW’s Support branch, which I’ve been doing since May 2024! I’m sure other Support volunteers have explained this far more eloquently in the past, but we basically help users with a wide variety of things. If you want to ask how to change your password, we’re the people to ask. If you run into some kind of error, shoot us a message. If a work has been tagged with the wrong language, that’s also us! Basically, we help the OTW-machine run smoothly.

What is a typical week like for you as a volunteer?
Personally, that depends from week to week! We don’t send out responses to users until another volunteer has read it over and given it the go-ahead (known as betaing), so some weeks I get a lot of my own tickets done, other weeks I prefer focusing on betaing for others! I like to work while I’m drinking something and listening to music, just to make it a bit more cozy. (My music of choice is Citypop and soundtracks to anime and games!)

What made you decide to volunteer?
To put it very simply, AO3/the OTW has done so much for me, and I wanted to give back. It’s been amazing for my personal growth to have a place to meet like-minded people, to post my works to, to read works that have moved me in some form… and then to get to help it run is an amazing experience!

What has been your biggest challenge doing work for the OTW?
Probably having to learn so many new things, like how to use all of our tools, or all of the internal phrasing. It’s definitely been challenging to pick all of that up, but it’s also been super fun, and everyone else has been incredible so far!

What fannish things do you like to do?
I mainly read and write fanfic! I also enjoy art immensely, although I can’t for the life of me make it myself. I also participate in online events from time to time, such as bangs, fests, exchanges, and online cons!


Now that our volunteer’s said five things about what they do, it’s your turn to ask one more thing! Feel free to ask about their work in the comments. Or if you’d like, you can check out earlier Five Things posts.

Posted by Caitlynne

The Policy & Abuse committee (PAC) is responsible for enforcing the AO3 Terms of Service (TOS). To help users better understand the TOS, we’re posting a weekly spotlight series about the TOS and our policies. We’ll also be reading comments and answering questions on this and our other spotlight posts.


Last week’s post was on ratings and Archive warnings. This week, we’ll discuss the other kinds of tags that we enforce, as well as the ones that we don’t. At the end of this post, we’ll provide details on the info that we need included in an incorrect tag report in order to be able to handle it as quickly and efficiently as possible. Although these are minor policy infractions, investigating them can take us a very long time to investigate if the report doesn’t contain enough information.

Don’t go looking for things to report.

Please do not start searching for incorrectly tagged works to report after reading this post. We know that incorrectly tagged works are a problem on AO3. However, when people deliberately search for works to report, we end up getting a lot of duplicate tickets about works that have already been reported. Every ticket we receive is reviewed by a PAC volunteer, so we only need one report in order to investigate an issue. We know it seems like sites only respond to mass reports, but on AO3, duplicate and mass reports increase the time it takes our volunteers to investigate.

Not all tags are required

Every work on AO3 must have at least one rating, Archive warning, fandom, and language tag. If these tags are used incorrectly, then PAC (or, as we’ll discuss below, the Support committee) may intervene. We discussed ratings and warnings in our last post, and we’ll explain what we mean by “incorrect” fandom and language tags below.

All other types of tags, such as category, character, relationship, and additional tags, are optional. Our rules for those kinds of tags are much looser. You’re not required to use them if you don’t want to, and PAC does not enforce the accuracy of these tags.

Fandom tags

Every work must have at least one fandom tag, and some may even have more than one. You are not required to tag every fandom that appears in your work. However, you should not use fandom tags for fandom content that does not appear in your work.

For example, if you’re planning a one-shot anthology for multiple fandoms, you should only add a particular fandom tag after the relevant chapter for that fandom has been posted. Please don’t include a fandom tag if you haven’t yet added any content from that fandom to your work.

We take a pretty broad view of what counts as “fandom content”, and we generally defer to the creator’s judgement. We don’t intervene in cases where franchise or sub-franchise tags have been used. For example, if Darth Vader shows up in your work, you’re allowed to tag it with Rogue One: A Star Wars Story (2016), even if your work is primarily about the Star Wars Original Trilogy. Similarly, if Cloud Strife appears in your work, you could tag your work with Compilation of Final Fantasy VII and/or Kingdom Hearts (Video Games) as fandom tags because Cloud is a character in both fandoms. If a fandom has both a movie and a comics version, we will defer to creators on whether to use the fandom tags for one or the other (or even both). It’s up to the work’s creator to use their best judgement about which fandom tags are most suitable.

However, we do have a few minimum standards. Generally, we don’t consider the following scenarios sufficient to mean a fandom is represented in a work:

  • A minor or off-hand reference to a well-known/pop-culture element from fandom A, such as an item, location, or the name of a character
  • The characters of fandom B are consuming the canon of fandom A, such as by playing a game or watching a movie
  • The characters of fandom B are roleplaying as the characters from fandom A

If a fandom doesn’t feature in your work beyond minor references such as these, you should not tag that fandom on your work. Instead, you can use an additional tag such as References to The Nightmare Before Christmas (1993) or Inspired by The Great Gatsby.

RPF vs FPF

On AO3, we generally differentiate between RPF (Real-Person Fiction) and FPF (Fictional-Person Fiction). When you’re writing about a canon’s real-life actors (such as Chris Hemsworth or Mark Ruffalo), you should indicate that by using the “RPF” version of a tag (such as Marvel Cinematic Universe RPF). If you’re writing about the fictional characters (such as Thor or Bruce Banner), and not their actors, then you should use the tag for that fictional universe (such as Marvel Cinematic Universe). Even if you’re writing about a real-life actor on set, filming a movie, you should still only use the RPF fandom tag and not the tag for the fictional universe: the fictional character isn’t actually present in the work, it’s simply the actor doing their job.

Sometimes, fandoms have only RPF components, typically when the fandom is for a reality show or other non-fictional canon. For example, fandoms like Boys Planet (Korea TV) and My Favorite Murder (Podcast) do not involve any fictional characters, so the RPF-FPF divide does not apply to them.

A fandom tag that is an actor’s name, such as Pedro Pascal – Fandom, is automatically considered RPF. These fandom tags should not be applied to works that are only about the characters an actor portrays. Instead, you can use an additional tag such as Joel (The Last of Us) Played by Pedro Pascal. If you’re a fan of a specific actor or pairing and enjoy seeing them in the different roles they’ve played, you may also be interested in the Actor X/Actor Y Character Combinations additional tag format.

Generic fandom tags

Because we take a very broad view of how relevant a fandom tag is, it’s always OK to use a generic fandom tag such as Unspecified Fandom, No Fandom, or even Original Work. Just as you can always opt out of applying a specific rating (by instead using “Not Rated”) or a specific warning (by instead using “Creator Chose Not To Use Archive Warnings”), you may opt out of using a specific fandom tag by instead using a generic or non-specific fandom tag.

You’re never required to use any particular fandom tag. If you want to tag all your fanworks with Unspecified Fandom instead of specific fandom tags, you’re free to do so. We may require a creator to remove an inaccurate fandom tag, but we will never require a specific fandom tag to be added.

Synonymous tags

AO3’s tag system relies on Tag Wrangling volunteers, who link synonymous tags to a canonical tag if both tags are the same type and have the same meaning. This is why you can click on Buffy the Vampire Slayer or BtVS – Fandom and the same set of results will pop up; these two fandom tags have both been made synonyms of the canonical fandom tag Buffy the Vampire Slayer (TV). The Buffy the Vampire Slayer (TV) works page will show works tagged with exactly “Buffy the Vampire Slayer (TV)” and works tagged with any synonymous fandom tags. If you want to learn more about how tag wrangling works, refer to the Tag Wrangling Work Description.

PAC does not handle issues relating to what tags are canonical, how tags are formatted, or which tags have been made synonymous with which other tags. We only look at the exact tag on a given work, not where it’s linked to. If you have concerns about a Tag Wrangling decision, please contact Support instead.

Language tags

Every work must be tagged with a language reflecting the language the work is presented in. If the work has multiple primary languages, or no language at all (e.g. artwork), we’ll defer to the creator’s judgement about which language to tag their work with.

In 2021, Support took over responsibility for handling language tags. If you find a fanwork that’s labeled with an incorrect language, please report it to Support, not to PAC. Support will contact the creator and ensure their work is labeled with a language that’s represented in the work.

Non-mandatory (optional) tags

Creators can use the category, relationship, character, and additional tag fields to provide more information about their work, but they’re not required to. Neither PAC nor Support will judge the accuracy or relevance of these kinds of tags.

However, all tags (regardless of type) are still subject to our general content policies. Tags can’t be used to engage in commercial activity or harass other users, because these are both not allowed on AO3. (Later posts in this series will discuss these kinds of violations and how we handle them.)

Harassment generally includes tags which insult or threaten other AO3 users. As mentioned above, inaccurate tagging is not considered harassment. Tags which express negative views of characters or relationships are also not considered harassment. AO3 is open to all kinds of fanworks, including ones that are critical, mocking, or parodies.

If you dislike the way a particular user tags their works, the TOS FAQ has some tips on how to avoid content you don’t want to encounter.

What happens if I’m reported for tagging an incorrect fandom?

First, we’ll review the reported work to confirm whether your fandom tags are actually incorrect. If you need to update them, we’ll send you an email telling you to fix the issue.

If you don’t fix it, we’ll remove any inaccurate fandom tags. If doing this means we end up removing all of the fandom tags on your work, we’ll add the “Unspecified Fandom” tag instead.

We don’t ever delete works for having incorrect tags. While we do require inaccurate fandom tags to be fixed, it is very rare for us to apply any penalties to a user’s account for incorrectly tagging a fandom. We usually only penalize a user if they revert the changes we made or required them to make, or if they are frequently mistagging their works despite repeated attempts from us to contact them.

However, tags are still subject to our Content Policy. If you violate our commercial promotion or harassment policies with your tags, penalties will be applied accordingly. We’ll discuss those policies in later posts.

What should I do if I encounter a work that has an incorrect tag?

You can give the creator a heads up by politely commenting on their work and linking to the TOS FAQ or this post. Alternatively, you can:

How do I report a work with the wrong fandom tags?

Although we ask that you do not deliberately seek out incorrectly tagged works to report, if you come across a work tagged with one or more incorrect fandoms, you can report it using the Policy Questions & Abuse Reports form, which is linked at the bottom of every page on AO3. If a work is tagged with multiple incorrect fandoms, please give us a list of all of the fandom tags you think are incorrect and should be removed.

Regardless of what type of incorrect tag you’re reporting, please don’t report more than one user at a time or submit multiple reports about the same user for the same reason. When reporting multiple works by the same user, please submit only one report with links to each work you’re reporting, so that all information about that user is in the same place.

For example, a report of a work with an incorrect fandom might look like this:

Link to the page you are reporting: https://archiveofourown.org/works/00000000

Brief summary of Terms of Service violation: Incorrect fandom tag

Description of the content you are reporting:
This work by USERNAME is tagged with “Star Wars” but it’s actually only about the Avengers, and the characters just watched Star Wars for movie night.

If you are reporting additional works, please include all relevant links and other information in your report description:

Description of the content you are reporting:
This work by USERNAME is tagged with “Star Wars” but it’s actually only about the Avengers, and the characters just watched Star Wars for movie night.

Some of their other works also have the wrong fandom:

https://archiveofourown.org/works/23456789 is tagged “The Avengers (Marvel Movies)” but it’s about Chris Evans and Robert Downey Jr. which means it’s RPF and should be tagged with the RPF fandom tag. Steve Rogers and Tony Stark don’t appear anywhere in the work.

https://archiveofourown.org/works/34567890 This work tags “The Legend of Zelda: The Ocarina of Time” when the character’s sword only shapeshifts into the Master Sword for two sentences before turning into another sword.

You can add more details if you like, but this example provides the basic information we need:

  • Who posted the incorrectly tagged work(s): Tell us their username or if the work is anonymous or orphaned.
  • Where we can find the work(s): Enter one URL in the “Link to the page you are reporting” field, and (if applicable) include links to any other violating works in the description of your report.
  • What violates the TOS: Explain which fandom tag(s) on each work you’re reporting are incorrect. A brief list or description is fine; you don’t need to be very detailed or quote an entire TOS or FAQ section.

You’ll receive an automatic email confirming that we received your report, and our volunteers will investigate when they get a chance. Please be patient and do not submit another report about the same work. While PAC and Support investigate every report we receive, it can take several months for us to process a report, and not every report will receive a reply.

What if I have more questions about tags?

PAC follows a strict confidentiality policy. Therefore, while you are welcome to ask general questions in the comments of this post, we will not give information on specific cases, publicly rule on a work, or update you on the status of a report you have already submitted. Comments on this post that discuss specific works or users will be removed.

If you think you’ve found a work that is tagged with a fandom that doesn’t appear in the work, please report the work to us as described above. If you think you’ve found a work that is tagged with an incorrect language, please report it to Support instead. For more information, you can read our TOS FAQ on other tags.

If you are still uncertain, you can comment below or submit a question through the Policy Questions & Abuse Reports form.

OTW Signal, May 2025

May. 30th, 2025 03:03 pm[syndicated profile] otw_news_feed

Posted by choux

Every month in OTW Signal, we take a look at stories that connect to the OTW’s mission and projects, including issues related to legal matters, technology, academia, fannish history and preservation issues of fandom, fan culture, and transformative works.

In the News

An article by Publishers Weekly notes how demographic changes in readership have influenced publishing houses to diversify the titles they publish. Female readers are at the forefront of this change.

Most top-selling manga titles, though classified as shonen manga, also boast huge female followings. Some are also the work of women, like the hit series Delicious in Dungeon by Ryoko Kui, translated by Taylor Engel (Yen). But girls’ manga is growing in popularity, especially subgenres exploring LGBTQ+ themes. And as the manga audience ages, following a decade-long boom in young adult readership (according to the Beat’s annual BookScan analysis, graphic novel sales reached an all-time peak in 2022, with tween-to-teen manga titles consistently among the top sellers), publishers report that female readers in particular seek out more mature and diverse subject matter.

This diversity is reflected in titles published under subgenres such as BL and GL. BL, short for Boys’ Love, is notable for having a particularly high readership retention rate, prompting publishers to explore a variety of themes. Some of these themes, such as omegaverse, trace their origins to fanfiction.
GL, short for Girls’ Love, draws a much more varied demographic – the article notes that the genre boasts a mixture of male, female, straight and queer fans and creators. A 2020 essay exploring the genre’s readership demographic attests that “yuri is made for a diverse audience by an equally varied group of creators.” Studies, such as Verena Maser’s 2013 survey of Japanese yuri readership found that the gender and sexuality of GL audiences was vastly varied. A 2017 survey by Zeria, aptly titled Yuri isn’t Made for Men, studied the international audience and found that a majority of GL fans are women, who do not identify as heterosexual.
Themes too are pushing the boundaries of what defines a work as manga or literary graphic novel. Female creators are at the helm of this change, creating mature, personal stories that reflect the desire for manga that feels relatable and represents the diversity of its growing audience.

My Friend Kim Jong Un (Feb. 2026), a graphic memoir manhwa by Keum Suk Gendry-Kim, also translated by Janet Hong, describes life with another level of bad neighbor: Gendry-Kim lives on a small island within sight of North Korea.

With such mature topics, Hurren finds, there’s also more crossover with audiences that don’t usually read manga. The titles “belong with our other literary graphic novels. We’re reaching out to manga-specific press, but it’s not a manga-specific trade campaign.”

This evolving landscape of manga readership is not just a trend but a reflection of deeper cultural changes towards a more diverse and inclusive literary future.


Parallel to the rise of female manga readership is the increasing popularity of Chinese web literature in Japan. A recent article by The Star noted that platforms like WebNovel, under China’s Yuewen Group, have seen significant growth, with a 180% surge in Japanese users in 2024 alone. This expansion is not just in readership but also in cultural exchange. Japanese creators and fans are actively engaging with Chinese web novels, translating works, and even co-developing new intellectual properties.
One such example is the Chinese web novel Apocalyptic Forecast, a fantasy fiction that deals with the supernatural and secret societies. Japanese screenwriter and director Hikaru Takeuchi became an avid fan of the novel, translating over 200 chapters into Japanese and sharing them with friends. Her efforts highlight the deep cultural resonance and potential for cross-cultural collaboration such stories hold in the literary world.

When the novel ended, Takeuchi felt compelled to write a letter to its author, Feng Yue. The cross-border fan mail became a symbolic bridge between cultures. In a recent interview, she expressed her hope of introducing more Japanese readers to the rich and emotional world of Chinese web literature.

The success of Chinese web novels like The King’s Avatar and Dragon Raja further illustrates this trend. The King’s Avatar has been downloaded over 30 million times in Japanese, and its anime adaptation has been screened in multiple countries, including Japan. These works are not just gaining popularity, but are also influencing Japanese creators, leading to a blending of cultural elements and shared narratives that appeal to a global audience.

OTW Tips

Ever thought about dipping your toes into editing on Fanlore but weren’t sure how to jump in? 2025’s Monthly Editing Challenges are the perfect place to start! Each month has a new editing task to encourage users to step out of their editing comfort zones. Completion of a month’s challenge can earn you shiny badges for your User page, and who doesn’t love a little digital flair for their efforts?
Not sure how editing on Fanlore works? Check out Fanlore’s Guide to Editing Pages, and if you’re new, create an account to get started!


We want your suggestions for the next OTW Signal post! If you know of an essay, video, article, podcast, or news story you think we should know about, send us a link. We are looking for content in all languages! Submitting a link doesn’t guarantee that it will be included in an OTW post, and inclusion of a link doesn’t mean that it is endorsed by the OTW.

Posted by xeno

The Policy & Abuse committee (PAC) is responsible for enforcing the AO3 Terms of Service (TOS). To help users better understand the TOS, we’re posting a weekly spotlight series about the TOS and our policies. We’ll also be reading comments and answering questions on this and our other spotlight posts.


AO3 is a home for all fanworks and operates under the principle of maximum inclusiveness of fanwork content. We allow content of any rating, and all kinds of fictional topics, as long as the creator provides basic information about the intensity and type of content that may be present in a work.

PAC handles many different types of TOS violations, including incorrect ratings and Archive warnings. In this post, we’ll discuss the requirements for ratings and warnings as well as provide information on how to report works with incorrect ratings or warnings. We do our best to investigate every report, but incorrect ratings and warnings can take us a very long time to investigate if the report doesn’t contain enough information.

Don’t go looking for things to report.

Please do not start searching for works with incorrect ratings or warnings to report after reading this post. We know that these kinds of TOS violations are a problem on AO3. However, when people deliberately search for works to report, we end up getting a lot of duplicate tickets about works that have already been reported. Every ticket we receive is reviewed by a PAC volunteer, so we only need one report in order to investigate an issue. We know it seems like sites only respond to mass reports, but on AO3, duplicate and mass reports increase the time it takes our volunteers to investigate.

Ratings

All works on AO3 must have a rating. Creators can either select a specific rating (“General Audiences”, “Teen and Up”, “Mature”, or “Explicit”) or opt out of providing a specific rating by applying the non-specific rating “Not Rated”.

Our TOS divides ratings into two tiers: ratings that will trigger the Adult Content notification (“Mature”, “Explicit”, or “Not Rated”), and ratings that won’t (“General” or “Teen”). When you click on a work rated “Mature”, “Explicit”, or “Not Rated”, a banner will warn you that you’re about to access a work that may contain adult content. By selecting the “Yes, Continue” button on the banner, you are agreeing to access a work which may contain adult content. Registered users can disable this notification, which is enabled by default on new accounts.

Works rated “General” or “Teen” are not subject to this notification system. If a work rated “General” or “Teen” contains explicit content that you believe should trigger the Adult Content notification, you can report that work to PAC, and we will investigate whether that work needs to use one of the three higher ratings.

However, PAC doesn’t make any distinctions within these two tiers. This means that we won’t require a work rated “General Audiences” to be changed to “Teen and Up”, and we won’t require a work rated “Mature” or “Not Rated” to be changed to “Explicit”, or vice versa. We defer to the work’s creator(s) for those decisions: the only part we enforce is whether or not the work needs a rating that triggers the Adult Content notification.

Archive warnings

There are four specific Archive warnings: “Underage Sex”, “Rape/Non-Con”, “Graphic Depictions of Violence”, and “Major Character Death”. Any work on AO3 that contains content relating to one of the four specific Archive warnings must be tagged with either that warning or the non-specific “Creator Chose Not To Use Archive Warnings” label.

Creators can always Choose Not To Warn.

The “Creator Chose Not To Use Archive Warnings” (CNTW) label is a blanket warning. It means “Read at your own risk!” or “This work may contain any of the four specific Archive warnings.” If you don’t want to encounter content depicting underage sexual activity, rape/non-consensual sex, graphic violence, or major character death, then you should not click on works tagged with “Creator Chose Not To Use Archive Warnings”.

When you post a work, you can use the CNTW label if you don’t want to apply a specific Archive warning. For example, if you don’t want to spoil a plot twist by adding a “Major Character Death” warning, you can instead apply “Creator Chose Not To Use Archive Warnings” to your work. You can also apply a combination of CNTW and other Archive warnings. If your work contains rape and a major character death, and you want to warn for the former without spoiling the latter, you can label the work with both “Rape/Non-Con” and “Creator Chose Not To Use Archive Warnings”.

If you don’t Choose Not To Warn, then you may need to add a specific warning.

As mentioned above, you can always opt out of applying Archive warnings by instead selecting “Creator Chose Not To Use Archive Warnings”. If you do not select this label, then in the following circumstances, you must use one or more of the four specific Archive warnings:

The “Underage Sex” warning is required on works that depict or describe sexual activity involving characters under the age of eighteen (18). We don’t consider dating activities, like kissing, to be sexual content. Offscreen sexual content also doesn’t need a warning.

For characters that are underage in canon, we do not automatically assume (without evidence) that they are also underage in the fanwork. If there are no indications that a particular character is under 18, we will assume they are 18 or older. When evaluating works, we consider explicit statements of a character’s age as well as contextual clues (such as the work being clearly set in a time period where the character is underage). If you’re worried that a character in your fanwork may be misinterpreted as being younger than 18, you can always specify the character’s age in the tags, notes, or body of your work.

The “Rape/Non-Con” warning is required on works that depict onscreen rape or non-consensual sex. If the work only contains a reference to non-consensual sex, then we don’t require this warning to be applied. Additionally, there are circumstances that are not considered consensual in real life, but don’t necessarily require the “Rape/Non-Con” warning on AO3. For example, we don’t inherently require a “Rape/Non-Con” warning for adult/minor relationships (though we might require “Underage Sex” or CNTW). We also do not require a “Rape/Non-Con” warning for situations that are dubiously consensual, such as the Sex Pollen or Fuck or Die tropes. When in doubt, we defer to the creator’s judgement.

Similarly, the “Graphic Depictions of Violence” warning is only required if the work contains graphic violence that is explicitly shown “onscreen” in the work.

We require “Major Character Death” when the character is both a major presence in the fanwork and they’re dead by the end of the fanwork. We don’t take canon into consideration here – what we’re interested in is whether the character is a major presence in your fanwork. If you create a fanwork centered on a character that dies and stays dead in your work, that work should be warned for “Major Character Death” even if they only appear for one line in canon. If that same character dies before the start of your work, and dealing with the grief of their loss is a major part of the fanwork, “Major Character Death” is also required in this situation.

If your work features a character death and that character returns in a later chapter that is currently posted, then this warning is not required. However, if the character does not return to life until a sequel fanwork, the warning is still needed on the work in which they died. Archive Warnings apply to individual fanworks, not to series of works.

“No Archive Warnings Apply” may coexist with other warnings.

There is also a sixth label in this category: “No Archive Warnings Apply”. The best way to think of this Archive warning is as a placeholder. If “No Archive Warnings Apply” is the only Archive warning on a work, then it means that the work should not feature underage sex, rape/non-consensual sex, graphic violence, or major character death – or if it does contain such content, it is only a brief reference.

However, the “No Archive Warnings Apply” label can be present on a work that is also labeled with any or all of the other five Archive warnings. In that case, the other warning label always takes precedence. PAC never removes any Archive warnings already on a work. We only add the “Creator Chose Not To Use Archive Warnings” label to the work if it’s missing a required warning.

For example, some users may apply a “Major Character Death” warning and a “No Archive Warnings Apply” warning in order to emphasize that while the work may contain Major Character Death, it doesn’t contain any of the other warnings. The presence of “No Archive Warnings Apply” does not negate the “Major Character Death” label on the work – a major character death may still occur in this work.

If both “No Archive Warnings Apply” and “Creator Chose Not To Use Archive Warnings (CNTW)” are applied to the same work, then the CNTW warning is what takes precedence, and the work may contain content relating to any of the four specific Archive warnings. Some users may apply both the CNTW label and the “No Archive Warnings Apply” label for ambiguous situations, or to emphasize that while they don’t think the work contains something that needs a warning, it is open to interpretation. However, you should not assume anything about a creator’s intentions or the severity of content in the work – consider works warned with both CNTW and “No Archive Warnings Apply” the same way you’d consider works tagged with only CNTW or any/all of the specific Archive warnings.

We generally defer to the creator’s judgement.

For borderline cases, PAC will defer to the creator’s judgement. However, if we feel that a work depicts content clearly requiring one of the four specific Archive warnings, we’ll require the creator to either add the warning or opt out by applying the “Creator Chose Not To Use Archive Warnings” label.

Can I use Additional tags instead of Archive warnings?

Sometimes users include warnings in the Additional tags of their work. If the content is merely a reference or offscreen, this is fine. However, for any content requiring an Archive warning, the label must also be added in the Archive warnings category. For example, while you are welcome to include an additional tag of “rape” on your work featuring a rape scene, you still need to apply the “Rape/Non-Con” Archive warning (or CNTW).

Why does AO3 have only four required Archive warnings?

AO3’s warning system is deliberately minimal. When AO3 was created, these four warnings were chosen as a balance between the most common types of content that users wanted a warning for, and what would be feasible for PAC (a small team comprised entirely of volunteers) to enforce in a consistent and fair manner. We know that there are many other kinds of content that you might not want to see, so we encourage you to check out the additional tags, summary, notes, and bookmarks of a work before opening it. However, PAC will not enforce the use of tags or warnings beyond what is required by the TOS.

It’s what’s in the work that counts.

When it comes to ratings and warnings, we evaluate what is in the body of the work. If an author says in their notes that they plan to include explicit sex eventually, but the only chapter posted is a fluffy introduction with no explicit content, then we will not require that the work be given one of the higher ratings. Similarly, if a work carries an additional tag of “X dies at the end” but nobody actually dies in the work, then we will not require a “Major Character Death” warning.

Because of this, please do not report works based on what is in their additional tags or summary. Many creators may have begun works and added additional tags or notes based on their plans for future updates, but plans change, and not all works in progress are completed. Please only report works to us when there is actual content in the work itself that necessitates a rating or warning change.

Ratings and warnings are not promises.

AO3’s warnings and ratings both mean “may contain”, not “must contain”. If you want to rate your fluffy, non-sexy slice-of-life as “Explicit”, you’re allowed to do that. A higher rating means that a work may contain explicit content, not that it must contain such content. Similarly, if you want to warn for “Major Character Death” even though nobody has died, you’re allowed; we don’t ever make someone remove a warning.

What will happen if I get reported for having an incorrect rating or missing warning on my work?

First, we’ll review your work to confirm whether or not your work’s rating and/or warnings are insufficient. If we determine that the rating or warnings need to be changed, we’ll send you an email notifying you to update your tags.

We’ll only ever contact you by email, and only after we’ve already reviewed your work and confirmed that the current rating and/or warnings are insufficient. We will never comment directly on your work or contact you through social media. Please make sure to keep your account’s email address up to date and check it regularly (including your spam folder), or else you may miss our email.

If you don’t update your tags, we’ll change them. For an incorrect rating, we’ll set the work to “Not Rated”. For a missing warning, we’ll add the “Creator Chose Not To Use Archive Warnings” label to the work. We won’t remove any of the warnings that are already on the work.

We don’t ever delete works for having insufficient warnings or ratings. While we do require all works to have appropriate ratings and warnings (as specified in the TOS), it is very rare for us to apply any penalties to a user’s account for insufficient ratings or warnings. We would usually only penalize a user if they undo changes we made or required them to make. A user may also receive a penalty if they repeatedly mislabel their works even after being contacted about similar violations, or for the purposes of harassment.

What should I do if I encounter a work that has the wrong rating or a missing warning?

You can give the creator a heads up by politely commenting on their work and linking to the TOS FAQ or this post. Alternatively, you can report the work to us.

How do I report a work with the wrong rating or missing warnings?

Although we ask that you do not deliberately seek out incorrectly tagged works to report, if you come across a work with the wrong rating or missing warnings while browsing, you can report it using the Policy Questions & Abuse Reports form, which is linked at the bottom of every page on AO3.

Please don’t report more than one user at a time or submit multiple reports about the same user. When reporting multiple works by the same user, please submit only one report with links to each work you’re reporting, so that all information about that user is in the same place.

Please tell us exactly where in the work the content requiring the higher rating or warning is. The best way to do this is to give us a short quote from the relevant scene that we can search for in order to immediately find the content. If you are reporting multiple works by the same creator, please group all the works into one report and provide this information for each work.

If the rating or warning issue pertains to a specific character, please tell us the name of that character as used in the work. If it’s Bert who died, please tell us it’s Bert, so that we don’t spend time trying to figure out if it was Ernie (who was only badly wounded). If you are reporting a missing “Underage Sex” warning, please tell us exactly where the underage sexual content occurs and where the indication of the character’s age is. As a reminder, if there are no indications that a particular character is under 18, we will assume they are 18 or older.

Rating and warning issues can take a lot of time for us to investigate if we’re not given clear information about where the violation has happened. PAC will not act unless we’ve confirmed a policy violation ourselves. If we’re sent a report about a work that is 80,000 words long and the report only says “contains rape”, we have to confirm that there is a rape scene somewhere in those 80,000 words before requiring a “Rape/Non-Con” (or CNTW) warning. If we can’t find it easily, the most likely result is that we’ll reply to you asking you to give us more info – and if you don’t, we’ll close your report with no further action. So please make sure to include as much information as possible when submitting a report.

For example, a report of a work with an incorrect rating might look like this:

Link to the page you are reporting: https://archiveofourown.org/works/00000000

Brief summary of Terms of Service violation: Incorrect rating

Description of the content you are reporting:
This work by USERNAME is rated G but it’s entirely smut from the very first sentence.

If you are reporting additional works, please include all relevant links and other information in your report description:

Brief summary of Terms of Service violation: Incorrect ratings and warnings

Description of the content you are reporting:
This work by USERNAME is rated G but it’s entirely smut from the very first sentence.

Some of their other works also have the wrong rating or warning:

https://archiveofourown.org/works/23456789 is rated T with No Archive Warnings Apply, but it has underage sex onscreen. CHARACTERNAME is 17 (in chapter 2 it says “after his seventeenth birthday party three weeks ago”) and has sex in chapter 4 (starting at “He stepped closer, leaning in…”)

https://archiveofourown.org/works/34567890 has the main character CHARACTERNAME die at the end (search for “She gasped in horror”), but the work isn’t tagged with Major Character Death or Creator Chose Not To Warn.

You can add more details if you like, but this example provides the basic information we need:

  • Who posted the incorrectly tagged work(s): Tell us their username or if the work is anonymous or orphaned.
  • Where we can find the work(s): Enter one URL in the “Link to the page you are reporting” field, and (if applicable) include links to any other violating works in the description of your report.
  • What violates the TOS: Explain why you think the rating and/or warning(s) on each work you’re reporting are incorrect, for example by including a quote from the relevant scene(s). A brief description of the work is fine; you don’t need to be very detailed or quote an entire TOS or FAQ section.

You’ll receive an automatic email confirming that we received your report, and our volunteers will investigate when they get a chance. Please be patient and do not submit another report about the same work. While PAC investigates every report we receive, it can take several months for us to process a report, and not every report will receive a reply.

What if I have more questions about ratings and warnings?

PAC follows a strict confidentiality policy. Therefore, while you are welcome to ask general questions in the comments of this post, we will not give information on specific cases, publicly rule on a work, or update you on the status of a report you have already submitted. Comments on this post that discuss specific works or users will be removed.

If you think you’ve found a work that’s incorrectly rated or missing a warning, or if you want to know whether a particular scene requires a specific rating or Archive warning, please report the work to us as described above. For more information, you can read our TOS FAQ on ratings and Archive warnings.

If you are still uncertain, you can comment below or submit a question through the Policy Questions & Abuse Reports form.

Profile

slashwriter: (Default)
slashwriter

January 2018

S M T W T F S
 123456
78910111213
14151617181920
2122232425 2627
28 293031   

Style Credit

Expand Cut Tags

No cut tags
Page generated Jun. 4th, 2025 07:18 pm
Powered by Dreamwidth Studios