Accessibility

frntdsk builds agents that answer people on whatever channel they reach for, and we want the people who configure those agents, and the people who visit this site, to have the same choice. This statement covers frntdsk.cx and the dashboard. It does not cover the websites of the businesses that run our agents, or the third-party pages we send you to, such as Stripe’s billing portal.

What we aim for

We aim to meet the Web Content Accessibility Guidelines version 2.1 at level AA on this website and in the dashboard, and we design new work against that standard before it ships.

How this site is built

• Pages use semantic HTML: one heading structure, real buttons and links, landmarks for navigation and content, and labels on every form field.
• Everything you can do with a mouse you can do with a keyboard, and the focused element is always visible.
• Text and interface colours come from a fixed palette chosen to meet the contrast ratios the guidelines ask for, and text scales with your browser settings without breaking the layout.
• The painted backgrounds behind the product mock-ups are decorative and hidden from assistive technology. If your browser does not support WebGL you see a plain panel instead.
• If your system asks for reduced motion, the animated demos stop moving: messages appear without transitions, the audio bars hold still and the scrolling effect on the landing page is turned off.
• Nothing plays sound automatically.

The product

We build the dashboard to the same standard: controls reachable by keyboard and labelled for screen readers, status conveyed in text as well as colour, and form errors reported next to the field that needs attention. The agents themselves speak and listen on the phone, type in web chat and SMS, and write email, so a customer can pick the channel that works for them, and a business can route a conversation to a person whenever its procedure calls for one.

Known limitations

• The animated conversation, call and channel demos on the landing page are illustrations. Their content is readable by assistive technology, but the motion itself carries no information you cannot get from the text.
• The voice demo plays a scripted call; the live demo line is a phone call and has no text alternative beyond the examples listed under it.
• Documents you upload to a knowledge base keep whatever accessibility their source had. We do not alter them.
• Some third-party surfaces we embed or link to, such as the Stripe billing portal and Google’s sign-in pages, are governed by their own accessibility statements.

Testing

Before a page ships we walk it with the keyboard alone, with a screen reader and at 200 percent zoom, and we review the landing page and the dashboard against the guidelines each time their design changes.

Tell us

If you find something on this site or in the dashboard that you cannot use, tell us through our contact page and describe the page and what happened. We reply within five business days and we fix accessibility bugs ahead of other work. If you need a document or a page in another format, ask and we will provide it.