Workback Accessibility Conformance Report

Images in the evaluated user flows have text descriptions that screen readers can read, and decorative icons are hidden from screen readers. For example, the customer logos on the Customers page are announced by name ("Zanichelli," "Multiverse," "Coursera"), and the decorative check and X icons in the "Without Workback" and "With Workback" lists on the home page and the customer stories are not read aloud.

The evaluated user flows contain no prerecorded audio-only or video-only content.

The evaluated user flows contain no prerecorded video with audio.

The evaluated user flows contain no prerecorded video.

Headings, lists and page regions in the evaluated user flows are marked up so that screen readers can convey the page structure. For example, the "About" section titles on the Coursera, Multiverse and Zanichelli customer stories are marked up as headings, and every page has a navigation region, a main content region and a footer.

Screen readers read content in the same order in which it appears on screen. For example, blog posts are read from the title, through the article and its section headings, to the "More from the blog" links at the end.

Instructions do not rely solely on shape, color, size, visual location, orientation or sound. For example, links and buttons are identified by their text, such as "Start Your Free Pilot" and "Read the full story."

Color is not the only way information is shown in the evaluated user flows. For example, links in the text of blog posts and the Privacy Policy are underlined as well as colored.

The evaluated user flows contain no audio.

All functionality in the evaluated user flows can be operated with the keyboard alone, including the header navigation, the phone-width menu, the customer story cards and the footer links.

Keyboard focus can move into and out of every component using standard keys. For example, the phone-width menu closes with Escape or its Close button and returns focus to the "Menu" button.

The evaluated user flows use no single-character keyboard shortcuts.

The evaluated user flows have no time limits.

The evaluated user flows contain no moving, blinking, scrolling or auto-updating content.

No content in the evaluated user flows flashes more than three times in any one-second period.

Every page in the evaluated user flows has a "Skip to main content" link, so keyboard and screen reader users can skip past the header and navigation.

Pages have titles that describe their topic or purpose. For example, each blog post and customer story has its own title, such as "Zanichelli wins the ABC International Excellence Award | Workback.ai" and "Multiverse Customer Story | Workback.ai."

Keyboard focus moves through pages in an order that matches the visual layout: header, main content, then footer. When the phone-width menu is open, focus stays inside it until users close it.

Links make clear where they lead, either from the link text or from the sentence around it. For example, the "Read the full story" link on the home page tells screen reader users that it opens the story about Zanichelli winning the ABC International Excellence Award.

No functionality in the evaluated user flows uses multi-finger gestures or drawing a path; everything works with a single tap or click.

Links and buttons activate on release and can be cancelled by moving the pointer away before releasing.

The names screen readers announce for links and buttons match or begin with their visible labels. For example, the home page link labeled "Read the full story" is announced as "Read the full story about Zanichelli winning the ABC International Excellence Award."

No functionality in the evaluated user flows is operated by device motion or user motion.

Each page identifies its language as English, so screen readers read it with English pronunciation.

Moving focus to links, buttons or menu items does not open a new page or window, or move users elsewhere, unexpectedly.

The evaluated user flows contain no form fields or other controls whose value users can change.

The evaluated user flows contain no forms on Workback.ai. Booking a free pilot takes place on a Google Calendar booking page, which is out of scope for this evaluation.

The evaluated user flows contain no forms on Workback.ai. Booking a free pilot takes place on a Google Calendar booking page, which is out of scope for this evaluation.

For WCAG 2.0 and 2.1, the September 2023 errata update indicates this criterion is always supported.

Links, buttons and other controls have names, roles and states that screen readers announce. For example, the phone-width "Menu" button tells screen readers that it opens a dialog, and the menu that opens is announced as "Menu."

The evaluated user flows contain no live audio or video.

The evaluated user flows contain no prerecorded video.

Content displays and operates in both portrait and landscape orientation. No page is restricted to a single orientation.

The evaluated user flows contain no form fields that ask for information about the user. Booking a free pilot takes place on a Google Calendar booking page, which is out of scope for this evaluation.

Content fits a narrow window (320 px wide, the equivalent of 400% zoom) without sideways scrolling. At that width, the header links move into a "Menu" button.

Buttons, links and other controls in the evaluated user flows have enough contrast against their surroundings (at least 3:1).

No content or functionality is lost when line, paragraph, letter and word spacing are increased to the values set by this criterion. For example, the story card titles on the home page wrap onto a new line instead of being cut off.

Content that appears when users hover over or focus on an element can be dismissed, stays visible while users move the pointer over it, and does not disappear on its own.

Text in the evaluated user flows has enough contrast against its background (at least 4.5:1). For example, links in the text of blog posts, in the Privacy Policy and on the home page use a dark orange with a contrast ratio of 5.4:1, and the titles on blog cards appear as light text on a dark panel.

Text in the evaluated user flows can be zoomed to 200% without losing content or functionality.

Text is presented as text rather than as images, except for logos. For example, the titles on the Blog page cards are real text, not part of the card images.

Pages in the evaluated user flows can be reached in more than one way. For example, each blog post can be reached from the Blog page and from the "More from the blog" links at the end of other posts, and each customer story can be reached from the home page, the Customers page and the About page.

Headings and labels in the evaluated user flows describe their topic or purpose. For example, blog posts use descriptive section headings such as "Why Zanichelli won" and "A shared commitment."

Keyboard focus is visible on links, buttons and menu items in the evaluated user flows.

All text in the evaluated user flows is in English, the language of the page. Names such as "Zanichelli" are proper names and do not need their language identified.

The header navigation and the footer appear in the same order on every page in the evaluated user flows.

Components with the same function are identified consistently across the evaluated user flows. For example, the link for booking a pilot is labeled "Start Your Free Pilot" in the header, in the home page hero and in the closing band at the bottom of pages.

The evaluated user flows contain no forms on Workback.ai. Booking a free pilot takes place on a Google Calendar booking page, which is out of scope for this evaluation.

The evaluated user flows on Workback.ai involve no legal commitments, financial transactions or submission of user data.

No status messages, such as confirmations, result counts or error alerts, appear in the evaluated user flows.