Skip to content
Phyto Nex AI

Accessibility statement

How we design Phyto Nex AI to meet WCAG 2.2 Level AA, where we still fall short, and how to reach us if something gets in your way.

Effective

Last updated

Phyto Nex LLP

01Our commitment

Phyto Nex LLP wants everyone who touches an expense report to be able to use Phyto Nex AI, whether they are an AP reviewer working through a queue of flagged hotel folios, an administrator configuring policy rules or an employee answering a question about a dinner receipt. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, and we treat accessibility defects with the same priority as other functional bugs.

This statement was first published on January 15, 2026 and was last reviewed on September 1, 2026. It reflects the results of our most recent independent audit, completed in July 2026.

02Scope

This statement covers:

  • Our marketing website at www.phytonexai.com, including the leakage calculator, policy templates and resource pages.
  • The Phyto Nex AI web application at app.phytonexai.com, including the review queue, finding detail, policy rule builder, reports and administration screens.
  • Messages that Phyto Nex AI prepares for delivery through Slack, Microsoft Teams and email, including the interactive buttons employees use to reply or upload a corrected receipt.
  • Exported reports in CSV and PDF formats generated by the application.

It does not cover the interfaces of third-party platforms such as SAP Concur, Expensify, Ramp, Brex, Navan, Slack or Microsoft Teams themselves, which are governed by their providers' own accessibility programs.

03Measures we take

  • Keyboard navigation: every action in the review queue, including approving, editing and discarding a draft message, is reachable without a mouse, with a logical tab order and documented shortcuts that can be turned off.
  • Visible focus: all interactive elements show a high-contrast focus ring of at least 2 pixels, and focus is never hidden behind sticky headers.
  • Color contrast: body text and interface controls meet a contrast ratio of at least 4.5:1, and large text at least 3:1. Finding severity is always conveyed by text labels and icons, never by color alone.
  • Reduced motion: animations are short and limited to opacity and position, and are disabled when the operating system's reduced motion setting is on.
  • Semantic structure: pages use landmarks, ordered headings and labelled form fields, and data tables include header cells and captions.
  • Screen reader testing: each release that changes the interface is tested with NVDA on Windows with Firefox and Chrome, JAWS on Windows with Chrome, and VoiceOver on macOS and iOS with Safari.
  • Zoom and reflow: content reflows without horizontal scrolling at 320 CSS pixels wide and remains usable at 400% zoom.
  • Accessible messages: Slack and Teams messages include plain-text fallbacks, descriptive button labels and alternative text for receipt thumbnails.
  • Target size: interactive controls meet the WCAG 2.2 minimum target size of 24 by 24 CSS pixels, and primary buttons are at least 42 pixels tall.
  • Training: designers and engineers complete accessibility training at onboarding, and accessibility checks are part of our design review and pull request checklist.

04Known limitations

Despite our efforts, some content does not yet fully conform. We are working on the following issues and list the target date for each:

AreaIssueWorkaroundTarget fix
Downloadable policy templatesSome PDF templates published before 2026 lack full tagging and reading orderEach template is also available as an accessible Word document on requestDecember 2026
Receipt image viewerOriginal receipt images cannot be read by screen readers; extracted line items are provided as an accessible table beside the imageUse the extracted line-item table, which contains the same valuesOngoing, by design
Policy rule builderReordering rule conditions by drag and drop has no announced live region feedback in JAWSUse the Move up and Move down buttons, which are fully announcedNovember 2026
Embedded webinar recordingsSome third-party video embeds from before March 2026 have auto-generated captions onlyEdited transcripts are available on each webinar pageOctober 2026
Spend trend chartsChart tooltips are not reachable by keyboardEach chart has an adjacent data table with the same figuresNovember 2026

05Compatibility

Phyto Nex AI is designed to work with the current and previous major versions of Chrome, Edge, Firefox and Safari on desktop, and Safari on iOS and Chrome on Android for employee-facing pages. It relies on HTML, WAI-ARIA, CSS and JavaScript. Older browsers such as Internet Explorer are not supported.

06How we assess accessibility

We combine automated and manual testing. Automated checks run on every pull request and catch common issues such as missing labels and contrast failures. Manual testing by our design team covers keyboard use, screen readers and zoom on all new features.

Once a year we commission an independent audit against WCAG 2.2 Level AA. The most recent audit was carried out by Lumen Inclusive Design LLP in July 2026 and covered the marketing website, the full web application and Slack and Teams message flows. All critical issues identified were resolved before August 15, 2026; the remaining items are listed under known limitations above.

07Feedback and assistance

If you have difficulty using any part of Phyto Nex AI, or you need information in a different format, please tell us. We respond within 2 business days and aim to provide a working solution or alternative format within 10 business days.

  • Email: support@phytonexai.com (include "Accessibility" in the subject line so your message is prioritized)
  • Phone: +91 80 4123 7815, or toll-free in India 1800-419-6620
  • Post: Phyto Nex LLP, Attn: Accessibility, 312, Thiruvalluvar Street, Vellakinar Pirivu, Gnanambika Mills, Coimbatore North, Coimbatore, Tamil Nadu 641029, India

When reporting a problem, it helps to include the page or screen, what you were trying to do, and the browser and assistive technology you use. If you are an employee of one of our customers, you can also ask your finance team to raise the issue with us on your behalf.

08Formal complaints

If you are not satisfied with our response, you may escalate your concern to our Head of Design, who will review it and respond in writing within 15 business days. You may also have the right to contact a regulator or enforcement body in your jurisdiction, such as the U.S. Department of Justice under the Americans with Disabilities Act or, in India, the Chief Commissioner for Persons with Disabilities under the Rights of Persons with Disabilities Act, 2016.

09VPAT and procurement documentation

A Voluntary Product Accessibility Template (VPAT 2.5, WCAG and Section 508 editions) and an Accessibility Conformance Report for the Phyto Nex AI web application are available on request. Customers and prospects can request them from sales@phytonexai.com or from their account manager. We update the report after each annual audit.

Questions about this document

Phyto Nex LLP, a limited liability partnership registered in India under the Limited Liability Partnership Act, 2008
312, Thiruvalluvar Street, Vellakinar Pirivu, Gnanambika Mills, Coimbatore North, Coimbatore, Tamil Nadu 641029, India

privacy@phytonexai.com or +91 80 4123 7815