MMLow 2026 follows the ACL Rolling Review (ARR) workflow. Submit your paper through OpenReview for MMLow 2026.
To submit your paper to MMLow 2026, follow these steps:
Create an OpenReview account using your institutional email for automatic activation (for all authors).
Submit your paper to the OpenReview link given for the MMLow 2026.
Select the category: Regular or Short paper
Note: New OpenReview profiles without an institutional email may take up to two weeks for moderation. Register early to avoid delays.
Authors are invited to submit two types of papers:
Regular paper: 8 pages, excluding references (mainly workshop papers)
Short paper: 4 pages, excluding references (mainly shared task papers)
References and appendix are unlimited and do not count toward the page limit.
Submission is electronic, using the OpenReview.net platform. All long, short, and theme papers must follow the ACL Author Guidelines. Here are the paper submission form fields for your reference. Submissions that do not conform to the required styles, including paper size, margin width, and font size restrictions, will be rejected without review.
Multiple Submission
Policy ACL 2026 follows the ARR policy on multiple submissions: we will not consider any paper that is under review in a journal or another conference at the time of submission, and submitted papers must not be submitted elsewhere during the review period.
Publication
Accepted papers presented at MMLow 2026 will be published in the AACL-IJCNLP 2026 Workshop Proceedings via the ACL Anthology.
Presentation & Registration
All accepted papers must be presented at MMLow 2026 to appear in the proceedings. Both in-person and virtual presentation options are available.
ARR has adopted the ACL 2023 Policy on AI Writing Assistance. The policy introduces a new item in the responsible research checklist, where authors disclose use of AI assistance. Common cases that should / should not be disclosed are:
Uses that do not need to be disclosed:
Assistance purely with the language of the paper, e.g., paraphrasing, spell-checking, or polishing the author’s original content, without suggesting new content.
Short-form input assistance, e.g., smart compose in google docs, which generates a short continuation of text.
Literature search, e.g., to identify relevant literature, which authors then read, discuss, and cite appropriately.
Uses that need to be disclosed:
Low-novelty text, e.g., producing a description of a widely known concept. Specify where such text was used, and convince the reviewers that the generation was checked to be accurate and is accompanied by relevant and appropriate citations (e.g., using block quotes for verbatim copying). If the generation copies text verbatim from existing work, the authors need to acknowledge all relevant citations: both the source of the text used and the source of the idea(s).
New ideas. If the model outputs read to the authors as new research ideas, that would deserve co-authorship or acknowledgement from a human colleague, and that the authors then developed themselves (e.g. topics to discuss, framing of the problem) - we suggest acknowledging the use of the model, and checking for known sources for any such ideas to acknowledge them as well. Most likely, they came from other people’s work.
New ideas + new text: a contributor of both ideas and their execution seems like the definition of a co-author, which the models cannot be. While the norms around the use of generative AI in research are being established, we would discourage such use in ARR submissions. If you choose to go down this road, you are welcome to make the case to the reviewers that this should be allowed, and that the new content is in fact correct, coherent, original and does not have missing citations.
Code writing assistants. Acknowledge the use of such systems and the scope thereof, e.g. in the README files accompanying the code attachments or repositories.
In all cases, authors are responsible for the correctness of their methods, results, and writing. Authors should check for potential plagiarism, both of text and code.