Quickbase accessibility conformance report (VPAT)

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Level A (Yes)

Level AA (Yes)

Level AAA (No)

1.1.1 Non-text Content (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Alternative text is defined for most images.  

Reference field autocomplete suggestions are not accessible to Assistive Technology. Users of Assistive Technology can navigate through the reference field drop-down item list to make a selection. 
 
Some page messaging elements are not accessible to Assistive Technology. Some supplementary buttons are not correctly identified to Assistive Technology. Some pages do not have clear heading text elements. Screen reader users are unable to determine the number of items in a list or in search results. 

Most non-text buttons, such as icon buttons, include appropriate aria labels so they can be interpreted by screen readers, and icons receive the presentation aria role so the button label is clear. 

Quickbase does not use CAPTCHAs. 

Support documentation for newly released features, which can be found at help.quickbase.com, does not rely solely on visuals such as imagery and charts to convey the information. When images are used, they generally include alt text in the support documentation for recent features. 

Some non-text content that is purely for formatting or decoration, such as columns on forms, are sometimes not implemented in a way that can be ignored by screen readers. Screen readers will announce the grid structure of a form before the form fields. 

Non-text content such as reports, charts, and diagrams are generally navigable by screen readers but can be inconsistent. Chart titles and descriptions are not announced by screen readers, and there is not a general data summary. 

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

1.2.2 Captions (Prerecorded) (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

1.3.1 Info and Relationships (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Many elements’ visual structure and relationship information is conveyed through object properties or is available in textual form. 

The main navigation, including the top navigation and sidebar navigation, are labeled appropriately so they are accessible and understood by screen reader users. Buttons are given accessible names and generally correctly tagged as HTML button elements so screen reader users can quickly jump between the main actions on a page. 

Required fields are denoted with asterisks in red and help text can be added by the builder to further define the field’s instructions. Required fields are announced by screen readers. Controls are usually grouped with their elements. Tables and headers are tagged as table elements for screen readers. 

Form input fields are generally grouped with their form label, so screen readers announce them in an understandable manner. 

A form’s structure can be perceived by a screen reader in addition to the visual cues. For example, a sighted user can understand that a form may have columns, and columns also have aria labels so a screen reader can announce the structure for low vision users. Forms have sections that can be expanded and collapsed and are correctly tagged to be accessible to a screen reader. Forms can be understood by the heading structure. 

Form record navigation to move between records when viewing or editing records is accessible. 

Most filtering capability is labeled as a filter across the product, except dashboard filters. 

1.3.2 Meaningful Sequence (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Elements across the product are generally in the correct reading order when applicable and can be programmatically determined. For example, the main navigation presents the global bar and app bar in reading order and the list of items in the sidebar, including app tables, can be navigated easily from top to bottom with the keyboard. Additionally, dashboard widgets are also in reading order.  

When HTML tables are used to create structured layouts, the rows and cells are in reading order. For example, this is true for forms, which enables a screen reader to move through a form in the correct sequence regardless of sections, columns, and field groups.  

1.3.3 Sensory Characteristics  (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

The platform and support documentation do not rely solely on sensory characteristics such as shape, size, visual location, orientation, or sound to convey information. 

1.4.1 Use of Color (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

The platform and support documentation do not rely solely on color to convey information. Additional visual methods, such as iconography, text, tooltips, and descriptions, are used alongside color to communicate information. 

1.4.2 Audio Control (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

2.1.1 Keyboard (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Most of the product features for end users can be accessed and operated using a keyboard. 

The main navigation is accessible by keyboard. 

Forms, dashboards, and reports are generally accessible by keyboard, including buttons, header links, context menus, dialogs, etc.  

Skip to page elements and some search results may not fully be keyboard accessible. Some fields are inconsistent with keyboard controls depending on which assistive tech is used, such as select fields. Some fields may not indicate when a drop-down menu is available.

2.1.2 No Keyboard Trap (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Quickbase allows the use of keyboard controls for moving focus in and out of elements, or for revealing and hiding them. There are a few exceptions, such as the expanded view of dashboard widgets, which can be closed through a page refresh.

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

All keyboard shortcuts require a modifier key, ensuring they are not triggered accidentally by single key presses.

2.2.1 Timing Adjustable (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

This criteria is not relevant to Quickbase.

2.2.2 Pause, Stop, Hide (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

This criteria is not relevant to Quickbase.

2.3.1 Three Flashes or Below Threshold (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

This criteria is not relevant to Quickbase.

2.4.1 Bypass Blocks (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Though skip links are not yet available in the main navigation, users can take advantage of the collapse/expand behavior on the navigation sidebar to more quickly jump to the main content of the page.  

Some pages include heading elements to make navigating between the content on the page easier, such as on forms. 

Groups are sometimes used to indicate relationships between components and make jumping between content easier.  

2.4.2 Page Titled (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Pages have sufficient titles.

2.4.3 Focus Order (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

See remarks on 1.3.2. Additionally: 

In general, the order of elements in the DOM determines the focus order, and Quickbase does not override it. 

Focus is generally in a meaningful logical or reading order; however, sometimes focus lands in navigational elements or outside the main content when loading a page so a screen reader user may have to reorient themselves on a new page.

2.4.4 Link Purpose (In Context) (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

The purpose of links can be determined from the link text alone or from the programmatic context of the link, providing clear and informative navigation throughout the site. 

Quickbase avoids ambiguous wording for links, like “More,” or provides additional text for screen readers in an aria tag.

2.5.1 Pointer Gestures (Level A 2.1 and 2.2)

This criteria is not relevant to Quickbase.

Quickbase is operated within web browsers, not a proprietary client. Interactive elements are activated with the usual pointer up-event, not the down-event meaning the site functions that use a single pointer are completed when the user releases the pointer.

See remarks on 1.3.1. In addition: 
 

Form input fields are generally grouped with their form label and the label is read first so screen readers announce them in an understandable manner. For example, checkbox fields have labels that are associated with the component programmatically. 

This criteria is not relevant to Quickbase.

3.1.1 Language of Page (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Every HTML document does not have a lang attribute. While the Quickbase UI is in English by default, customers can create custom pages in other languages. Quickbase cannot accurately predict what language the majority of all pages are in, so a default is not set to avoid causing issues with other languages.

3.2.1 On Focus (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Visible focus indicators are generally exposed for the currently displayed element. Focus state is accessible to Assistive Technology.  

Components in the product do not usually initiate a change of context when focused. Occasionally, the focus may jump unexpectedly up to the main navigation. For example, this happens on some page loads. 

3.2.2 On Input (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Form alerts and notifications are tagged correctly so the user can be given notice of the change in context.  

Low-vision users may occasionally have to reorient themselves on a page to gain proper context. Changes of context can sometimes be inconsistent. 

3.3.1 Error Identification (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

For platform or user-level errors: Error messages are provided as text and the content is generally helpful for the user to understand the error that occurred. Builders can also create custom notifications and error detection rules to supplement the experience inside a Quickbase app. Note: Certain build-level errors cannot easily be surfaced to an end user.

3.3.2 Labels or Instructions (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Labels are provided for all input fields, such as on forms. Tooltips and instructions are provided, when necessary, throughout the product.  

For example, tooltips are provided on hover for icon buttons that do not have a visual label and the appropriate aria roles are used to make icon buttons accessible to screen readers. 

4.1.1 Parsing (Level A)

WCAG 2.0 and 2.1 – Always answer ‘Supports’

Also applies to Revised Section 508:

• 501 (Web)(Software)

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

4.1.2 Name, Role, Value (Level A)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Reference remarks on 1.1.1, 1.3.1, and 2.4.4. 

In general, most components in the product provide role, state, and value information making them compatible with assistive technology. Some HTML divs may be lacking appropriate aria tagging. 

1.2.4 Captions (Live) (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

1.2.5 Audio Description (Prerecorded) (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

1.3.4 Orientation (Level AA 2.1)

1.3.5 Identify Input Purpose (Level AA 2.1)

Forms, form logic, form fields, field labels, and field placeholder text are defined by the person building the form. Because of the vast amount of form use cases, Quickbase does not programmatically identify input fields that collect user information to use the browser’s autofill option.  

Autocomplete is occasionally used, such as when inputting an address in an address field or entering an option from a list in a select field.  

1.4.3 Contrast (Minimum) (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

The Quickbase platform complies with minimum contrast ratios. Text and buttons in the product meet minimum contrast requirements. User-generated content and settings may not comply; however, on newer features, the platform may warn the user that they have chosen an inaccessible color and recommend they update it.

1.4.4 Resize text (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

1.4.5 Images of Text (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

1.4.10 Reflow (Level AA 2.1)

Reference 1.3.4. Additionally:

Most of the UI is generally responsive and fits within the viewport. Reflow is not fully supported and not all content can be viewed at a 400% zoom-level; however, improvements have been made to the browser view at 320px wide and features are generally responsive at this size, though some horizontal scrolling may be required. 

Exception: Quickbase apps include content that requires a two-dimensional layout (both horizontal and vertical scrolling) for usage and meaning, including: data tables, diagrams, charts, etc.

1.4.11 Non-text Contrast (Level AA 2.1)

Significant non-text content elements on the site have adequate contrast. Quickbase components generally support and are distinguishable by individuals with low vision, adhering to the accepted contrast ratio.

1.4.12 Text Spacing (Level AA 2.1)

Quickbase cannot ensure there is no loss of content or functionality when settings or style properties, such as line height and spacing, are changed.

1.4.13 Content on Hover or Focus (Level AA 2.1)

Where a Quickbase component, such as a tooltip, triggers additional content to become visible and then hidden, the content is generally dismissible, hoverable, and persistent.

2.4.5 Multiple Ways (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Quickbase has robust navigation and search functionality. The user can navigate through apps as desired using the various navigation or search options. Builders also have the option to add navigation links, such as buttons on dashboards, that can be added as they see best fit.

2.4.6 Headings and Labels (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Headings and labels within Quickbase applications are mostly set by the app builders. For example, Quickbase provides an interface for builders to determine appropriate and meaningful form labels such as tab navigation labels, section headings, column headings, field labels, and more.

Headings are appropriately tagged in many areas of the Quickbase UI; however, there are some areas missing HTML headings.

2.4.7 Focus Visible (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Quickbase uses the default browser focus in our UI.

Utilizing search may not always move focus to the search results or convey how many search results are present, such as when searching a table report.

3.1.2 Language of Parts (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Quickbase is primarily focused on English as of this writing. Though builders have control to create their apps in different languages, Quickbase does not yet support the programmatic language determination of passages or phrases in content.

3.2.3 Consistent Navigation (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Quickbase has a consistent and reliable navigation pattern, including a global navigation top bar and a sidebar for app navigation.

3.2.4 Consistent Identification (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Quickbase components and UI elements that have the same functionality are identified consistently.

3.3.3 Error Suggestion (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

When an error is automatically detected in a Quickbase app, an error message is provided and tagged as an aria alert so alternative technology users can detect and understand the error. Error messages provide details about the error and suggestions to move forward.

Builders can also create custom notifications and error detection rules to supplement the experience inside an app as needed.

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

Also applies to Revised Section 508:

• 501 (Web)(Software)

Quickbase provides application builders with the techniques and capabilities needed to create custom validation and error detection rules; however, builders must take the steps to create them as needed.

4.1.3 Status Messages (Level AA 2.1)

Quickbase aims to use accurate semantic markup when possible, such as the aria alert role, so that assistive technology can focus on and announce status messages and notifications. Most alerts, including alerts created by app builders, are recognized by assistive technology. There may be some exceptions.