Trust Center

MacroMint

Last updated: .

MacroMint, branded page components for Confluence Cloud, runs entirely on Atlassian Forge. It adds six components (Callout, Steps, Cards, Button, KPI and Status) to Confluence pages, an admin page for the site brand and presets, an AI helper and a Rovo agent.

What it stores

MacroMint keeps the site’s brand and presets, a change history and short-lived counters. It does not keep page text: what an author types into a component is saved by Confluence in the page, like any macro’s settings.

MacroMint stores data only in Atlassian Forge hosted storage, which Atlassian provisions per site installation, and in Confluence itself. MacroMint has no external database, file store or backup of its own. What it keeps in Forge storage is configuration and short-lived counters: the site brand, preset styles and names, a change history of brand and preset edits, AI usage counters and Rovo preview records.

People are kept by their Atlassian account ID only, never by name or email. Admin names in the change history are looked up from Confluence, as the admin viewing, each time they are shown, and are never stored.

Retention and deletion

Data kept by MacroMint, where it lives and for how long
DataWhereRetention
A component’s settings, including the text the author typed, and a copy of the site brand at the time it was savedConfluence, in the pageLike any macro’s settings: until the component or the page is removed in Confluence
Site brand (colour, corner style, spacing) and the two switches (custom colours, presets only)Atlassian Forge hosted storage (the customer’s installation)Until an admin changes it, or the app is uninstalled
Approved presets: name (up to 40 characters) and style, up to 15 per component typeAtlassian Forge hosted storage (the customer’s installation)Until an admin deletes it, or the app is uninstalled
Change history: the account ID of the admin who changed the brand or a preset, the time, the action, the old and new style values and the preset nameAtlassian Forge hosted storage (the customer’s installation)The last 200 changes. Older entries are removed as new ones are added
AI usage counters: a count per person per day (the account ID is part of the counter’s key) and a count per site per monthAtlassian Forge hosted storage (the customer’s installation)The per-person counter is removed after about 2 days
Rovo preview records: a one-way hash of the account ID, the page ID and version, and a hash of the inputs, so a save matches what was previewedAtlassian Forge hosted storage (the customer’s installation)10 minutes
A copy of the site brand and preset styles, so pages follow a brand changeEach person’s browserRefreshed about once a day. No personal data

Atlassian documents that deleting expired Forge storage entries can take up to 48 hours. MacroMint keeps no backup or archive of Confluence content outside Atlassian.

Deleting data

  • Remove a component. Removing a MacroMint component from a page removes its settings with it, in Confluence. MacroMint never deletes or changes page content on its own.
  • Brand and presets. A Confluence admin can reset the brand to the defaults and delete presets. Components that used a deleted preset keep their last style.
  • Uninstall the app. Atlassian removes the app’s Forge storage under its platform lifecycle, on Atlassian’s schedule; Atlassian documents that hosted storage is retained for 28 days after uninstallation before it is deleted. After uninstall MacroMint cannot read it. MacroMint does not itself purge storage at uninstall; the platform does. Component settings stay in pages, as Confluence content.
  • Data deletion requests. Contact us through the contact page. We will act on a verified request within 30 days. Data held by Atlassian follows Atlassian’s policy.
  • Site deletion. When a Confluence site is deleted, Atlassian’s site retention applies to the site and the app’s data; app data is deleted when the site is permanently removed.

Data residency

According to Atlassian’s Forge documentation, Forge hosted storage is data-residency enabled: it is held in the location of the host Atlassian product and moves with it when an administrator migrates the product. MacroMint sends no data to another location.

Architecture

MacroMint runs entirely on the Atlassian Forge platform. MacroMint does not operate any server, database or storage of its own: no customer data is processed or stored outside Atlassian infrastructure by MacroMint.

MacroMint architecture: the browser, Atlassian Forge and ConfluenceThe person’s browser shows MacroMint components inside Confluence pages and keeps a copy of the site brand and preset styles, refreshed about once a day. Inside Atlassian infrastructure, MacroMint Forge functions read and write the site brand, presets and change history in Forge hosted storage, and call Confluence’s REST API as the signed-in person: to check whether they are an admin, to search for pages that use components, and, for the Rovo agent, to read and save the page they have open. Component text is saved in the Confluence page. When someone asks the AI helper, the functions call Forge LLM, a model hosted by Atlassian, with that request only. There is no server, database or storage operated by Limbus Lab, and no address outside Atlassian.Person’s browserMacroMint components in pagescopy of the site brand, dailyAtlassian infrastructureAtlassian ForgeMacroMint Forge functionsForge storagebrand, presetsForge LLM(AI helper)Confluence Cloudpages, search, usersForge bridge,HTTPSREST API, as thesigned-in personread, writethe requestonlyNo Limbus Lab server, database or storage, and no address outside AtlassianMacroMint architecture: the browser, Atlassian Forge and ConfluenceThe person’s browser shows MacroMint components inside Confluence pages and keeps a copy of the site brand and preset styles, refreshed about once a day. Inside Atlassian infrastructure, MacroMint Forge functions read and write the site brand, presets and change history in Forge hosted storage, and call Confluence’s REST API as the signed-in person: to check whether they are an admin, to search for pages that use components, and, for the Rovo agent, to read and save the page they have open. Component text is saved in the Confluence page. When someone asks the AI helper, the functions call Forge LLM, a model hosted by Atlassian, with that request only. There is no server, database or storage operated by Limbus Lab, and no address outside Atlassian.Person’s browserMacroMint components in pagescopy of the site brand, dailyAtlassian infrastructureAtlassian ForgeMacroMint Forge functionsForge hosted storagebrand, presets, historyForge LLMAI helper, hosted by AtlassianConfluence Cloudpages, search, usersForge bridge, HTTPSread, writethe requestonlyREST API, as the signed-in personNo Limbus Lab server, database or storage,and no address outside Atlassian
Figure 1. MacroMint between the person’s browser, Atlassian Forge and Confluence. A text description of the diagram follows below.

Data flow

  1. A person opens a Confluence page with MacroMint components. Forge draws each component inside the page, in that person’s browser, from the settings saved with the component in the page.
  2. About once a day, the browser asks MacroMint’s Forge functions for the current site brand and preset styles, and keeps a copy so that pages follow a brand change without being edited. The copy holds no personal data.
  3. When an author inserts or edits a component, the editor reads the site brand and presets from Forge hosted storage through MacroMint’s functions. Saving puts the component’s settings into the page, through Confluence’s own editor.
  4. On the admin page, the functions ask Confluence as the signed-in person whether they are a Confluence admin, then read or write the brand, presets and change history in Forge hosted storage. The usage report searches Confluence as that admin, so it shows only pages they can view.
  5. When someone asks the AI helper, the functions send their request to Forge LLM, a model hosted by Atlassian. See AI.
  6. When someone uses the MacroMint agent in Rovo, the functions read the page they have open, as that person. A change is shown as a preview first and saved to the page, as that person, only after they agree and confirm.

MacroMint never reads Confluence with its own access. Every call to Confluence is made as the signed-in person, so Confluence’s own permissions decide what comes back.

Network diagram

Network connections used by MacroMint
FromToProtocolAuthenticationNotes
Person’s browserConfluence (Atlassian) and the MacroMint components, editors and admin page inside itHTTPSAtlassian user sessionMacroMint screens are rendered by Forge inside Confluence
MacroMint component, editor or admin pageMacroMint Forge functionsForge bridge, HTTPSForge, with the signed-in person’s identityAtlassian-managed
MacroMint Forge functionConfluence Cloud REST API of the same siteHTTPS, via Forge’s managed clientForge-managed, as the signed-in personNo credentials held by MacroMint
MacroMint Forge functionForge hosted storageAtlassian internal, Forge-managedForgePer-installation scope
MacroMint Forge functionForge LLMAtlassian internal, Forge-managedForgeOnly when someone asks the AI helper

MacroMint makes no connection to any non-Atlassian host. Its app manifest declares no outside address (no egress), and there is no MacroMint-operated server, load balancer, database, queue, analytics service or third-party API in the architecture.

Encryption and the browser

The text that applies to every app is in Encryption at Rest. What follows applies to this app only.

So that pages follow a brand change, each person’s browser keeps a copy of the site brand and preset styles, refreshed about once a day. It holds no personal data and no page text. This copy is held by the browser on the person’s own device; it is not Forge storage and the platform encryption does not describe it.

MacroMint stores no API key or other secret. The AI helper is hosted by Atlassian and needs no key of its own.

Logging

The text that applies to every app is in Data Logging and Retention. What follows applies to this app only.

MacroMint keeps Forge platform logs only; its Forge functions write short lines. What a log line may contain: counts and codes only: for example the component type, a result or error code, the name of a Rovo action and the class of an error, and the number of AI tokens used.

MacroMint does not log page text, component text, the words a person types for the AI helper, links, account IDs or names, and it holds no access tokens, API keys or secrets that could be logged. Lines hold counts and codes, never content or personal data.

Subprocessors

The text that applies to every app is in Subprocessors. What follows applies to this app only.

MacroMint sends Confluence data only to the Confluence Cloud APIs of the site it is installed on, and to the browser of the person using it. Its only subprocessor is Atlassian (Forge hosting, storage and logs, and Forge LLM for the AI helper).

Parties that receive data at runtime
PartyRoleWhat it receivesLocation
Atlassian (Forge platform and Confluence Cloud)Infrastructure and product provider: runs MacroMint’s functions, storage and logging; hosts ConfluenceEverything MacroMint processesPer Atlassian’s Forge documentation, Forge hosted storage is kept in the location of the host Atlassian product
Atlassian (Forge LLM)Hosts the AI model used by the AI helperOnly when someone asks: their request, the component’s own settings without links or colours, and its body text if they share it (see AI)Within Atlassian, under Atlassian’s terms for Forge

MacroMint’s Rovo agent answers Rovo, Atlassian’s own AI, as the person asking, with what that person can already see; what Rovo does with that answer is covered by Atlassian’s terms.

Declared outbound (egress) domains: none. MacroMint’s app manifest declares no outside address, so Forge does not let it call any host outside Atlassian. All its calls use Forge’s managed Confluence client, Forge storage and Forge LLM, which need no declared domain. MacroMint is eligible for Runs on Atlassian.

Software dependencies: Atlassian Forge packages and libraries bundled into the app. None is a hosted service and none receives data from MacroMint over a network.

Security and safeguards

The text that applies to every app is in Security and Incident Response. What follows applies to this app only.

Besides the responsibilities every app has, MacroMint is responsible for the permission checks in its functions. MacroMint requests only the Confluence permissions (scopes) listed in its Marketplace listing and at installation, declares no outside address, and makes no call to a non-Atlassian host. Fix targets are in Vulnerability Reporting.

Built-in safeguards

  • Acts as the signed-in person. Every call MacroMint makes to Confluence is made as the person using it, so Confluence’s own permissions apply. MacroMint never reads or writes Confluence with its own access.
  • Admin actions checked on the server. Brand and preset changes, the change history and the usage report each ask Confluence whether the person is a Confluence admin, and refuse if the answer is no or cannot be read. The two admin questions in Rovo are checked the same way.
  • Account IDs only. MacroMint stores people by their Atlassian account ID, never by name or email. Admin names in the change history are looked up as the viewing admin each time they are shown.
  • No raw markup, no code. Components are drawn from checked settings. Text people type is shown as text and never run as code, and nothing is inserted into a page as raw HTML.
  • Checked links. Links in components are checked before they are saved. Through Rovo, a Button may link only to a page on the same Confluence site; outside links, email links and other kinds of address are refused.
  • AI that cannot act on its own. The AI helper’s answer is read as data, checked against the same rules as the manual editor, and stripped of links and colours. It becomes a draft the author uses or discards. See AI.
  • Rovo changes need a click. The Rovo agent shows a preview that changes nothing. A save needs the preview it was shown, made for the same person, page, page version and inputs within 10 minutes, and Rovo asks the person to confirm. Each save adds a note to the page history.
  • Guarded settings. Brand and preset changes are saved together with their change history entry in one step, and a stale or simultaneous save is refused with a clear message.
  • Rate limits. The AI helper is limited to 20 requests per person per day and 500 per site per month.

Incidents

MacroMint follows the incident response plan. For MacroMint, an incident is any event that degrades or interrupts MacroMint’s service (components fail to show on pages, editors or the admin page fail to open, a brand change does not reach pages, the AI helper or Rovo agent unavailable), or that puts customer data at risk (suspected unauthorized access, a person shown content Confluence would not let them see, a page changed without the person’s agreement, cross-tenant exposure, data corruption).

MacroMint severity examples
SeverityExamples
SEV1 CriticalA person shown page content Confluence does not let them see; cross-tenant data exposure; components fail to show everywhere
SEV2 MajorOne component type fails to show; a brand change does not reach pages
SEV3 MinorOne style option not applied; wrong label in the UI

A fix is verified on a real Confluence page and the MacroMint admin page before the incident is closed.

Accessibility

The company statement is in Accessibility Statement. This is MacroMint’s full review of how accessible its screens are, against WCAG 2.2 Level A and AA, made on 15 November 2026 on development version 2.3.0. It is a self-assessment by the MacroMint team, not an independent audit and not a certification. Of the 55 criteria, 36 are rated Supports, 2 Partially Supports and 17 Not Applicable; none is rated Does Not Support and none is left Not Evaluated. No screen reader has been used yet.

The fixes below are in development version 2.3.0 only. The production version does not have them yet; they will be released after the app’s Atlassian Marketplace review. This page will say when a release with them is out.

The same contrast rule protects pages after release: a custom colour or brand colour that would be hard to read on light or dark pages is refused, with the reason, before it can be saved.

Problems found during this review and fixed

  • Tabbing down an editor no longer puts the focused field under the sticky Save and Cancel row (2.4.11).
  • Buttons keep keyboard focus while they are busy (Save, Save brand, Show usage, the AI and preset buttons, Previous and Next), and the page position is announced (2.4.3, 4.1.3).
  • Focus goes to the editor heading after a component is chosen or an AI draft is used or discarded, to a new AI draft when it arrives, and follows a card when it is moved or removed (2.4.3).
  • Deleting an approved preset asks first, with focus on “Keep it” (3.3.4).
  • Every state of the admin page has a main region and a level-one heading (1.3.1, 2.4.6).
  • The focus ring of the Button macro and of linked cards is no longer cut off by the edge of the macro’s frame (2.4.7).
  • The AI request field has a visible label, and its border meets 3:1 on the AI panel (2.5.3, 3.3.2, 1.4.11).

Earlier fixes, from the first check on 12 November 2026: two lists announced as alerts are plain lists; links in an editor’s preview are no longer Tab stops; a callout’s tone is spoken; Steps and Cards have list roles; a disabled Button has the right role.

Known gaps

  • In view mode, titles inside components (Callout, Cards and Steps titles) look like headings but are not marked as headings. A macro is drawn in its own frame and cannot know the heading levels of the page around it (1.3.1).
  • Saved and error messages are marked as status or alert messages, but they appear together with their text, which not every screen reader announces (4.1.3).
  • MacroMint’s editors are closed by Confluence’s own dialog; Escape inside MacroMint’s frame does not close them. Confluence’s dialog keeps Tab inside it, Cancel is reached by Tab, and focus returns to the page editor when it closes.

Questions or feedback about accessibility: the contact page, with the subject “MacroMint accessibility”. Say which component or screen, what you use (for example a screen reader, keyboard only or zoom) and what happened. We reply within 3 business days.

Accessibility Conformance Report (VPAT 2.5, WCAG edition)

Product information
ItemValue
Name of productMacroMint for Confluence, by Limbus Lab
Product version evaluatedMacroMint development version 2.3.0; full review. The production version does not have the fixes yet.
Report date15 November 2026
Product descriptionAn Atlassian Forge app for Confluence Cloud. MacroMint adds six branded page components (Callout, Steps, Cards, Button, KPI, Status), an AI helper that drafts them, and an admin page for the brand kit and presets.
Contact informationLimbus Lab, through the contact page (limbuslab.com/contact/)
EvaluatorMacroMint team, self-assessment (automated scans, keyboard walks, measurements, contrast computation, tests, code review, checks inside Confluence; no screen reader)
Applicable standardWCAG 2.2 Level A and Level AA. WCAG 2.1 Level A and AA criteria are a subset of these tables. 4.1.1 Parsing is obsolete in WCAG 2.2 and is not listed. Level AAA, Revised Section 508 and EN 301 549 tables are not included.
VPAT templateVPAT 2.5 (WCAG edition), ITI terminology

Evaluation methods used

This report is a self-assessment that combines the following. It is not an independent audit.

  1. An automated scan with axe-core 4.14.0 (WCAG 2.0, 2.1 and 2.2 Level A and AA rules, colour contrast on) in Chrome, on the real view, editor and admin screens served from the source with Confluence’s light and dark theme colours: 82 screen states (every component, every editor, the AI screens and every admin page state), in light and dark, at 1280 px and 320 px. 328 runs.
  2. A keyboard walk of every screen, forwards and back, at 1280 and 320 px: 164 walks and 921 focus stops, each checked for a visible, uncut focus ring and for anything covering it.
  3. Measurements: target size, reflow at 320 px, a 640 px view for 200 % zoom, and the WCAG text spacing values.
  4. Contrast computed for every colour pair against Confluence’s light and dark themes.
  5. 1,393 automated tests, including tests for each fix.
  6. Checks inside Confluence by keyboard, on the development installation after the fixes: the Button focus ring, the sticky Save row, the AI field label and border, focus after the AI start screen, the preset delete confirmation, and the Confluence editor dialog around MacroMint’s editors.
  7. A review of the code, criterion by criterion.

Not tested

  • No screen reader has been used on any part of MacroMint.
  • The focus ring on linked cards and the path with the AI switched off were checked in the preview and by tests only, not inside Confluence.
  • Only Chrome was used; other browsers, phones, real browser zoom, speech input and switch access were not tested.
  • The Rovo chat window is drawn by Atlassian; only the words MacroMint gives it were reviewed.

Scope: everything MacroMint draws. Confluence’s page chrome, editor, navigation, sign-in and the frames that host MacroMint are provided by Atlassian and are outside MacroMint’s control.

Terms

  • Supports: the functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supports: some functionality of the product does not meet the criterion.
  • Does Not Support: the majority of product functionality does not meet the criterion.
  • Not Applicable: the criterion is not relevant to the product.
  • Not Evaluated: the product has not been evaluated against the criterion.

Table 1: Success criteria, Level A

Success criteria, Level A
CriterionConformance levelRemarks and explanations
1.1.1 Non-text ContentSupportsEvery picture in MacroMint is decorative and hidden from assistive technology, with the meaning also given in words: component icons in the chooser and admin page, the callout icon (the tone is also given as a hidden word such as "Warning:"), the KPI trend arrow (the trend is written out, for example "Up, improving"), the status glyph (the state name is always there), the step numbers in their badges (the list is an ordered list) and the small style pictures in the preset chips (the chip name says what it is). The colour pickers have names ("Pick a custom colour", "Pick the primary colour"). An automated scan (axe-core 4.14 in Chrome, light and dark, 1280 and 320 px) found no problem on any of the 82 screen states. Not confirmed with a screen reader.
1.2.1 Audio-only and Video-only (Prerecorded)Not ApplicableMacroMint contains no audio or video content.
1.2.2 Captions (Prerecorded)Not ApplicableNo audio or video content.
1.2.3 Audio Description or Media Alternative (Prerecorded)Not ApplicableNo audio or video content.
1.3.1 Info and RelationshipsPartially SupportsEditors and the admin page: every field has a bound label, groups of fields and choices are fieldsets with a legend, list items to edit are named groups ("Card 2"), section titles are headings, the usage report is a table with column headers, steps and cards are real lists. Fixed on the branch, not in production yet (commit 3aedc24): the admin page's not-admin, load-error and licence states now have a main region and a level-one heading, like the full page. Remaining gap: in view mode the titles inside components (Callout title, Cards and card titles, Steps title and step titles) look like headings but are not marked as headings; steps built from the author's headings become titles in an ordered list. A macro frame cannot know the heading levels of the page around it, so this was not changed. The scan found no structure problem otherwise.
1.3.2 Meaningful SequenceSupportsContent is drawn in source order. In the editors the form comes first and the preview after it; at narrow widths the preview moves below the form. The keyboard walk confirmed the same order (AI box, content fields, style fields, Save, Cancel) on every editor.
1.3.3 Sensory CharacteristicsSupportsInstructions name the control or the place by its name ("choose Save as site preset", "Use Next to keep looking", "type your steps on the page"). The presets-only note says "Choose a style above" and sits directly under the ready-made styles it refers to, which are also named in the sentence.
1.4.1 Use of ColorSupportsColour is never the only signal: the KPI trend is written out, the status shows its state name and a different glyph per state, callouts say their tone in words, the chosen style chip has a check mark and bold text as well as its colour, and colour problems are listed in words. Links in page text keep their underline; links in cards and the usage table are whole cards or table cells, not links inside running text.
1.4.2 Audio ControlNot ApplicableNo audio plays.
2.1.1 KeyboardSupportsEvery control is a native button, link, text field, select, check box, date field or colour field. A scripted keyboard walk reached every control on all 82 screen states (164 walks, 921 focus stops), and the actions after a press were checked (save, page, AI draft, use and discard, choose a component, move and remove a card, rename and delete a preset). Ordering cards uses Move up and Move down buttons, not dragging. The colour field opens the browser's own picker; the hex text field next to it does the same job by keyboard. Inside Confluence the Button macro on a page was reached and opened with the keyboard (view mode, production code).
2.1.2 No Keyboard TrapSupportsOn every screen state the keyboard walk tabbed from the top to the end and then back with Shift+Tab in reverse order; no control held focus. The date field moves through its own parts (month, day, year, calendar button) and then on. Checked inside Confluence on the development install: Tab and Shift+Tab stay inside the editor dialog and wrap, Cancel closes it and focus returns to the page editor. Escape does nothing while focus is inside MacroMint's frame; this is not a trap because Cancel is reached by Tab.
2.1.4 Character Key ShortcutsNot ApplicableMacroMint defines no keyboard shortcuts.
2.2.1 Timing AdjustableSupportsNo screen has a time limit and no message disappears on its own. The Rovo agent's preview of a page change is valid for 10 minutes; after that the agent makes a new preview and asks again, so nothing typed is lost and the person can simply confirm again.
2.2.2 Pause, Stop, HideNot ApplicableNothing moves, blinks or scrolls on its own. The only motion is short hover and press effects (under 0.2 s), which are turned off when the system asks for reduced motion. The site brand check runs at most once a day in the background and does not move content.
2.3.1 Three Flashes or Below ThresholdSupportsNothing flashes.
2.4.1 Bypass BlocksNot ApplicableMacroMint is drawn in frames inside Confluence pages, dialogs and the admin area; Confluence supplies page navigation and skip links. MacroMint's own screens repeat no blocks of navigation. The admin page has a main region and headings for each section.
2.4.2 Page TitledSupportsThe page title is Confluence's (the page, the dialog or the admin page). MacroMint's frame documents are titled "MacroMint", and the platform frame used for rich page content inside a component is titled. Not changed in this evaluation.
2.4.3 Focus OrderSupportsPreviously focus could drop to the top of the frame. Fixed on the branch, not in production yet: busy buttons keep focus instead of being disabled (213472c); Previous and Next hand focus to each other when one becomes unavailable (213472c); focus goes to the editor heading after the AI start screen or an AI draft is used or discarded, to a new AI draft when it arrives, and follows a card when it is moved or removed (f3c88a3); after a preset rename or delete focus stays in the list (9a2d45f). Checked by a browser script and by unit tests; tab order on every screen follows the visual order. Inside Confluence on the development install: focus stayed on Show usage after the search, choosing a component on the AI start screen moved focus to the new editor heading, and after deleting a preset focus moved to the section heading. Confluence's editor dialog keeps Tab inside it and returns focus to the page editor when it closes with Cancel.
2.4.4 Link Purpose (In Context)SupportsA card link is named by the card's title and text, a Button by its label, a usage report link by the page title in the Page column. Links that open a new tab say so to assistive technology ("opens in a new tab"). Links in the editor preview and the admin sample do nothing and are left out of the tab order.
2.5.1 Pointer GesturesNot ApplicableNo multipoint or path-based gestures are used.
2.5.2 Pointer CancellationSupportsAll actions run on click (pointer up), from native buttons and links. No action runs on pointer down.
2.5.3 Label in NameSupportsControls with visible text use that text as their name. Fixed on the branch, not in production yet (7190d82): the AI request field had only a placeholder on screen and a hidden name; it now has a visible label with the same words ("Tell the AI what you want", "Ask for a change"), confirmed inside Confluence on the development install. List fields show a caption ("Title") that is part of their name ("Card 2 Title"). Controls named without visible text are the colour swatches ("Use #1868DB") and the preset name boxes, whose visible content is the value.
2.5.4 Motion ActuationNot ApplicableNo motion- or device-sensor input.
3.1.1 Language of PageSupportsEvery MacroMint frame document declares English (lang="en"); all interface text is English.
3.2.1 On FocusSupportsNothing happens when a control gets focus. MacroMint moves focus itself only after the person's own action (see 2.4.3).
3.2.2 On InputSupportsChanging a field updates the live preview only. Choosing Custom colour shows the colour field below it; nothing is saved or sent until Save, Save brand or another named button is pressed.
3.2.6 Consistent HelpNot ApplicableMacroMint's screens offer no help mechanism such as contact details, a chat or a help link; help is given as text next to each field.
3.3.1 Error IdentificationSupportsErrors are shown in text and announced as alerts: save errors name the field (for example "Title must be plain text (no HTML)."), colour problems are listed in words, and failed server calls say what happened and that nothing was changed.
3.3.2 Labels or InstructionsSupportsEvery field has a visible label and, where needed, a help line (for example the date field explains what it is for). Fixed on the branch, not in production yet (7190d82): the AI request field now has a visible label instead of a placeholder only.
3.3.7 Redundant EntrySupportsNo process asks for the same information twice. The editor keeps what was typed when a save fails, an AI draft keeps the author's colour choice, and reopening an editor shows the saved settings.
4.1.2 Name, Role, ValueSupportsNative controls with bound labels; style chips and colour swatches are toggle buttons with a pressed state; a busy button is marked unavailable (aria-disabled) while it works (213472c, not in production yet); a Button macro without a link is a disabled button. The scan found no name, role or value problem on any screen state. Not confirmed with a screen reader.

Table 2: Success criteria, Level AA

Success criteria, Level AA
CriterionConformance levelRemarks and explanations
1.2.4 Captions (Live)Not ApplicableNo audio or video content.
1.2.5 Audio Description (Prerecorded)Not ApplicableNo audio or video content.
1.3.4 OrientationSupportsNo orientation lock. All screens were scanned at 320 px (portrait phone width) and 1280 px wide and work at both.
1.3.5 Identify Input PurposeNot ApplicableNo field collects information about the person using it. Fields hold component text, colours, preset names and a space key.
1.4.3 Contrast (Minimum)Supportsaxe-core in Chrome, with colour contrast on, found no contrast problem on any of the 82 screen states in light and dark at 1280 and 320 px (328 runs). The items axe could not decide were decorative glyphs hidden from assistive technology, and usage table cells scrolled out of view at 320 px, which use the same colours that passed at 1280 px. Unit tests compute every colour pair in the style sheets and every component token pair against the real Atlassian light and dark themes. A custom colour is accepted only if text on it reaches 4.5:1 and it reaches 3:1 on light and dark pages, and coloured text is only used for large text.
1.4.4 Resize TextSupportsA 640 px viewport, which is what a 1280 px window shows at 200% zoom, was used on all 82 screen states: nothing ran off the side and no text was cut off. Real browser zoom and text-only zoom were not used.
1.4.5 Images of TextSupportsNo images of text. All text, including component labels and numbers, is real text.
1.4.10 ReflowSupportsAt a 320 px viewport no element on any of the 82 screen states ran past the right edge. The editor puts the preview below the form, the admin brand form and sample stack, card grids drop to one column. The usage report is a data table and scrolls sideways inside its own box, which this criterion allows. Measured in the local preview; inside Confluence the frame width is set by Confluence.
1.4.11 Non-text ContrastSupportsComputed against the real Atlassian themes: field borders 3.2:1 on white (4.2:1 dark), chip and tile borders 3.9:1, focus ring 3.5:1 on white and 6.9:1 or more in dark, custom colours checked for 3:1 on light and dark pages. Fixed on the branch, not in production yet (7190d82): the AI request field's border was 2.9:1 against the purple AI panel in light mode and is now 3.5:1. The callout tone is shown by its border, icon and a word, so the tinted background is not the only cue.
1.4.12 Text SpacingSupportsThe WCAG values (line height 1.5, paragraph spacing 2 times, letter spacing 0.12 times and word spacing 0.16 times the font size) were applied to all 82 screen states at 1280 and 320 px: no text was clipped or ran out of its box, and nothing ran off the side. No MacroMint box has a fixed text height.
1.4.13 Content on Hover or FocusNot ApplicableMacroMint shows no extra content on hover or focus: no tooltips, pop-ups or menus of its own. Hover and focus only change colours and outlines. Native select lists and the date and colour pickers are the browser's.
2.4.5 Multiple WaysNot ApplicableMacroMint adds components to Confluence pages and one admin page; finding pages is Confluence's job.
2.4.6 Headings and LabelsSupportsEditor headings name the component, section headings say what they hold (Content, Style, Approve this style), admin card headings name the task (Approved presets, Where components are used, Change history), and field labels say what goes in them. The admin page states without access now also have a level-one heading (3aedc24, not in production yet).
2.4.7 Focus VisibleSupportsThe keyboard walk found a drawn focus indicator on every MacroMint control on every screen state (a 2 px ring in the Atlassian focus colour). Found inside Confluence and fixed on the branch, not in production yet (d3cf61b): the ring around the Button macro, and around linked cards, was cut off by the edge of the macro frame so only a sliver showed; both now keep room for the whole ring, confirmed inside Confluence on the development install for the Button (full ring on all four sides); linked cards were confirmed in the local preview only. The date field's calendar button inside the KPI editor uses Chrome's own focus mark.
2.4.11 Focus Not Obscured (Minimum)SupportsPreviously failed in every editor: tabbing down the form put the next field fully under the sticky Save and Cancel row (found on 19 of the editor and AI screen states). Fixed on the branch, not in production yet (9bbfbf4): scroll padding keeps a focused field above the row. Confirmed inside the Confluence editor dialog on the development install: tabbing the Callout editor from Title to Save, no focused field was hidden. After Save as site preset the name box gets focus and can be partly, not fully, under the row. After the fix the keyboard walk found no focused control fully hidden on any screen state; a tall text box can be partly under the row while its top is visible. Confluence's own headers around the frames were not part of the test.
2.5.7 Dragging MovementsNot ApplicableNothing in MacroMint is done by dragging; cards are reordered with Move up and Move down buttons. The browser's colour picker can be dragged, and the hex text field next to it does the same without dragging.
2.5.8 Target Size (Minimum)SupportsMeasured on all 82 screen states at 1280 and 320 px. Buttons are at least 32 px high (44 px on touch screens), tiles 48 px, colour swatches 32 px, fields 36 px. The only controls under 24 px are the 16 px check boxes, which sit inside their full-width label, and usage report links (16 px high) in table rows about 40 px apart; all 78 such cases meet the spacing exception. axe noted one style chip in the Status editor at 320 px as partly covered: it sits just under the sticky Save row when the editor opens, and is 88 by 32 px once scrolled into view.
3.1.2 Language of PartsSupportsAll MacroMint text is English. Text that authors type is shown as typed.
3.2.3 Consistent NavigationSupportsEvery editor has the same order (heading, AI box, Content, Style, Approve this style for admins, Save and Cancel, then the preview), and the two lists on the admin page use the same Previous and Next pager in the same place.
3.2.4 Consistent IdentificationSupportsThe same functions have the same names and look everywhere: Save, Cancel, Previous, Next, Save as site preset, the AI buttons with their sparkle, the danger style for Delete and Remove.
3.3.3 Error SuggestionSupportsErrors say how to fix them: "Use a six-digit hex colour such as #1868DB", "Give the preset a name of 1 to 40 characters", "Describe what you want in a sentence (3 to 500 characters)", and each colour problem says which check failed and that the site brand colour can be used instead.
3.3.4 Error Prevention (Legal, Financial, Data)SupportsPreviously an approved preset was deleted at once, with no way back. Fixed on the branch, not in production yet (9a2d45f): Delete now asks "Delete <name>? This cannot be undone." with Yes, delete and Keep it, and focus starts on Keep it (confirmed inside Confluence on the development install: a test preset was saved, the confirmation appeared with focus on Keep it, and after Yes, delete focus moved to the section heading; the test preset was removed). Other changes can be checked or undone: the brand form shows a live sample before Save brand and Use the defaults restores the defaults; brand and preset changes are listed with their old and new values in the change history; component edits are saved as a new page version in Confluence.
3.3.8 Accessible Authentication (Minimum)Not ApplicableMacroMint has no sign-in of its own; Atlassian handles authentication.
4.1.3 Status MessagesPartially SupportsResults and errors use status and alert roles: "Brand saved.", "Preset renamed.", "Preset deleted.", the preset saved message, the colour check, the AI draft notice and save, AI and load errors. Fixed on the branch, not in production yet (213472c): the pager position ("1 to 10", "Page 2: 25 shown") is now a status message. Remaining gap: most messages are added to the page together with their text; alerts added this way are announced reliably, but status messages added this way are not announced by every screen reader and browser pair. No screen reader was used to check which, so this is rated Partially Supports.

Table 3: Success criteria, Level AAA

Not evaluated.

Summary of ratings

Number of criteria per conformance level
Conformance levelLevel A (31 criteria)Level AA (24 criteria)
Supports2016
Partially Supports11
Does Not Support00
Not Applicable107
Not Evaluated00

Legal disclaimer: this report describes the version named above as reviewed on the report date. It is a self-assessment; no third-party audit and no screen-reader testing has been performed.

AI

The company rules are in the AI Usage Policy. MacroMint uses AI in two places: the AI helper (the MacroMint AI component and the “Describe it (AI)” box in every component editor), and the MacroMint agent in Rovo, Atlassian’s own AI. Components on pages, the brand kit, presets and the usage report use no AI.

The model and where it runs

The AI helper uses a Claude model hosted by Atlassian, called through Forge LLM, Atlassian’s AI service for Forge apps. It runs within Atlassian, under Atlassian’s terms for Forge. MacroMint sends nothing to any other AI provider, holds no AI key, and declares no outside address.

When it is used

Only when a person asks for it:

  • to build a component from a sentence they type,
  • to change the component they are editing (“Change this one”), or
  • to replace what is in the form with a new draft (“Make a new one”).

Nothing is sent to the model in the background.

What it is sent

What the AI model is sent, and what it is never sent
SentNever sent
The sentence the person typed; the settings of the component being edited, without its links or colours; and the text in that component’s body, only if the person ticks “Let the AI read the text in this component’s body” (off by default)The rest of the page, other components, other pages, links and colours, names or account IDs, secrets

What it can and cannot do

  • It only fills in a component’s settings. Its answer is read as data, checked against the same rules as the manual editor, and stripped of links and colours. It is never shown as raw markup or run as code.
  • It makes a draft, not a change. The person sees the draft with “Use this draft” and “Discard”. Nothing changes on the page until they use the draft and save.
  • It never removes the author’s words. A change that would drop any of the author’s text is refused, and nothing changes.
  • It cannot read Confluence. It has no access to pages, spaces or people.

Limits and control

The AI helper is limited to 20 requests per person per day and 500 per site per month. When a limit is reached, the person sees a message and can still build and style components by hand.

The AI helper can be switched off. When it is off, the start screen and every AI box say “The AI builder is switched off on this site.” before anything is typed, no request is sent to the model, and every component can still be built and styled by hand. In this version the switch is an app setting held by Limbus Lab, not a control on the admin page. To ask about it for your site, use the contact page.

Rovo

MacroMint adds an agent to Rovo, Atlassian’s own AI. It can preview and add a component to the page the person has open, preview and convert that page’s info panels to callouts, check whether the page is on brand, and, for Confluence admins, show where components and custom colours are used. It works as the person asking, with their own permissions.

  • A change is always shown as a preview first, which changes nothing. It is saved only after the person agrees, and Rovo asks them to confirm.
  • A preview lasts 10 minutes and works once. Each save adds a note to the page history that starts with “MacroMint agent:”.
  • Through Rovo, a Button may link only to a page on the same Confluence site.