Artemii
Sign in Open Artemii
Legal

Accessibility statement

Draft pending legal review. This is our current wording, written from how Artemii actually works. A solicitor has not yet reviewed it, and it may change. Mayfair's company details will be added once confirmed.

Last updated 5 November 2026. Artemii is made by Mayfair.

Mayfair wants Artemii to be usable by as many people as possible. This statement covers the Artemii web app (chat.mayfairmail.com), the administrator console, this website (ai.mayfairmail.com) and the Artemii Chrome extension.

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. This is a target, not a claim. We have not yet been audited against WCAG 2.2 AA and we do not claim conformance. This statement is based on our own test suites, not on an audit, and no assistive-technology testing has been done.

What has been tested

These are automated or scripted browser tests run by the development team. They show that specific behaviours worked on the test date. They are not a conformance review.

Web app

  • Keyboard: the message box has focus first; Tab reaches New chat, search, chat actions and the account menu; a visible focus outline appears on controls; Ctrl or Cmd+K opens search; Esc closes menus and panels and returns focus to the control that opened them.
  • Structure: a labelled navigation landmark, a main landmark, and labels on buttons, links and inputs that have no visible text. Dialogs have dialog roles.
  • Status: a polite live region announces when an answer is thinking and when it is complete.
  • Responsive layout: phone, tablet and desktop widths with no horizontal scrolling on the tested phone screens; the sidebar becomes a drawer.
  • Reduced motion: animations are switched off when the system asks for reduced motion.
  • Colour contrast: a scripted check of text contrast (4.5:1 for normal text) in light and dark themes on the newest surfaces: citations, sources panel, tool labels, composer notes and action buttons.
  • Voice calls: dialog semantics, a focus trap, the background made inert while a call is open, Esc ends the call, and focus returns to the voice button.
  • Themes and text: light, dark and system themes, a readable font option and three text sizes in Settings.
  • A strict content-security policy with no inline styles, and no uncaught page errors on the tested paths.

Website

  • Landmarks (header, main, footer, navigation), one level-one heading per page, a "skip to main content" link and the language attribute.
  • Text colours checked at 4.5:1 or better in light and dark themes for the site's colour tokens.
  • A visible focus ring on links and buttons; the mobile menu button reports expanded or collapsed and closes with Esc.

Administrator console

Switches use switch roles with checked state, segmented controls respond to arrow keys, and Esc closes dialogs in tested flows. These were checked as part of functional tests, not accessibility tests.

Chrome extension

Replies are drawn as text only. A visible "Artemii is acting on this page" banner has a Stop button, Esc stops in the panel, and a keyboard shortcut (Alt+Shift+S) stops actions. It has not been tested with assistive technology.

Known gaps and limitations

We list these because we would rather you hear them from us.

  1. No assistive-technology testing. We have not tested with screen readers, speech recognition or screen magnifiers, and no automated rule engine is part of our test suites.
  2. Contrast is only partly tested. Scripted checks cover the website's colour tokens and a list of newer chat surfaces. The rest of the chat app, the administrator console and the extension have not been contrast-tested by script. Non-text contrast (icon buttons and focus rings against all backgrounds) has not been tested.
  3. Administrator console has no dedicated accessibility tests: no checks for labels, headings, tables, focus order or contrast beyond what functional tests happen to cover. Data tables and charts have not been reviewed for text alternatives.
  4. AI-generated content. Pages, designs and documents the AI writes are only as accessible as the model makes them. The design model is told to produce accessible designs, but output is not checked, and the sandboxed preview may not work well with screen readers. Please check what you publish.
  5. Pictures. Generated pictures have no automatic text description.
  6. Voice calls use your browser's speech recognition and speech output. Quality, languages and accuracy depend on your browser and device. Spoken replies are captioned only by the chat text.
  7. Streaming text. Answers appear as they are written. The live region announces status rather than every word, and whether this suits screen reader users has not been tested.
  8. Drag, resize and device-switcher controls in the artifact panel have not been checked against the WCAG 2.2 target-size and dragging-alternative criteria.
  9. Sign-in is handled by Mayfair ID, which has its own accessibility position that we have not tested here.
  10. Time limits. A tool approval waits 5 minutes by default and is then declined. Preview and picture links expire in minutes. We have not assessed these against the timing criterion.
  11. Extension. The panel has no tests for keyboard order or screen readers. The on-page banner is drawn in a closed shadow DOM that may not be exposed to assistive technology. Clicks are synthetic, so some sites ignore them.
  12. Languages. The interface is in English. Replies depend on the model.
  13. Downloads. Exports are data files and the AI's own files; none are tagged for accessibility.
  14. Zoom and reflow to 400 percent, text-spacing overrides and orientation have not been tested by script beyond the three layout widths above.

Feedback and contact

If you find a barrier, or need content in another format, email hello@mayfairmail.com with "Accessibility" in the subject. Tell us the page, what you were trying to do, and the device, browser and any assistive technology you use. We will tell you what we can do.

About this statement

Prepared on 5 November 2026 from the project's test suites, not from an audit. We plan to arrange an independent audit against WCAG 2.2 AA before this statement claims any level of conformance.