This report is based on VPAT® International Edition Version 2.5Rev
Name of product/version
Quickbase SaaS using the newest features and user interface components
Report date
July 2025
Product description
Quickbase is a cloud-based no-code application platform. Builders create custom solutions that solve a variety of business challenges, without writing code. Quickbase is loosely used by two high-level groups of users. First are the builders who create the software solutions used by their organization. Second are the end users, who use the end solution.
For the purposes of accessibility and this report, we are focused solely on the end-user experience, which covers the vast majority of Quickbase usage. The builder experience is not included in this report.
Contact information
Email: accessibility@quickbase.com
- If you’ve come across a bug or issue related to accessibility, open a tech support case.
- If you’d like to discuss your account, accessibility plans, and how we can help you be successful, please reach out to your account team.
Notes
Quickbase is a mature platform, having been developed and iterated on for 20+ years. The platform currently receives over 3 billion requests per month and has hundreds of thousands of active users. We are committed to ensuring Quickbase is an accessible platform for all users, a value you’ll find reflected in the product areas we modernize. Quickbase aims to meet WCAG 2.2 AA standards in our new and upgraded features that are designed to be consumed by end-users on the web. This report assumes applications are built for end users using the most recent features and user interface components provided by Quickbase. Customers can consult with their account team for review.
With a focus on improving accessibility for the Quickbase end-user experience, this report includes the WCAG 2.2 tables relating to A and AA compliance, as well as Revised Section 508: Chapter 5 – 501 (Web)(Software) and EN 301 549: Clause 9 – Web. It excludes the following, which are out of scope of this report:
Excluded:
- Revised Section 508:
- Chapter 5 — 504.2 - Authoring tools for Content Creation or Editing
- Chapter 6 — 602.3 - Electronic Support Documentation
- EN 301 549:
- Clauses 10.1-10.4 of Clause 10 - Non-Web documents
- Clauses 11.1-11.4 and 11.8.2 of Clause 11 - Software
- Clauses 12.1.2 and 12.2.4 of Clause 12 - Documentation and support services
Though not addressed in this document, improvements are also expected incrementally for builder and app management features and Quickbase mobile. Learn more about our approach to accessibility.
Evaluation methods used
Our accessibility testing process includes automated testing, manual testing with our QA team and various assistive technologies, and third-party testing with an outside vendor that provides access to a diverse community of people with disabilities, who use various assistive technologies. Our evaluation includes the built-in capabilities of the platform, our defaults, and/or the capabilities we offer. Some requirements may be up to the specific application-building patterns created by the builder.
The following operating systems and screen readers are used for evaluation: Mac/VoiceOver, Windows/JAWS, Windows/NVDA, manual accessibility testing, and keyboard testing with visual focus.
In this report
- Applicable standards/guidelines
- Terms
- WCAG 2.2 report
- Revised Section 508 report
-
EN 301 549 report
- Clause 4: Functional performance statements (FPS)
- Clause 5: Generic requirements
- Clause 6: ICT with two-way voice communication
- Clause 7: ICT with video capabilities
- Clause 8: Hardware
- Clause 9: Web (see WCAG 2.2 report section - Tables 1 & 2)
- Clause 10: Non-web documents
- Clause 11: Software
- Clause 12: Documentation and support services
- Clause 13: ICT providing relay or emergency service access
- Legal disclaimer
Applicable standards/guidelines
This report covers the degree of conformance for the following accessibility standards/guidelines:
| Standard/Guideline | Included in report |
| Web Content Accessibility Guidelines 2.0 |
Level A - Yes
Level AA - Yes Level AAA - No |
| Web Content Accessibility Guidelines 2.1 |
Level A - Yes
Level AA - Yes Level AAA - No |
| Web Content Accessibility Guidelines 2.2 |
Level A – Yes Level AA – Yes Level AAA – No |
| Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 | Yes |
|
EN 301 549 Accessibility requirements for ICT products and services - V3.1.1 (2019-11)AND EN 301 549 Accessibility requirements for ICT products and services - V3.2.1 (2021-03) |
Yes |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially supports: Some functionality of the product does not meet the criterion.
- Does not support: The majority of product functionality does not meet the criterion.
- Not applicable: The criterion is not relevant to the product.
- Not evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.
WCAG 2.2 report
The WCAG 2.2 tables 1 and 2 also document conformance with Revised Section 508 and EN 301 549 as follows:
-
Included:
- Revised Section 508:
- Chapter 5 - 501 (Web)(Software)
- EN 301 549:
- Clause 9 – Web
- Revised Section 508:
-
Excluded:
This report addresses the Quickbase platform’s new and upgraded features that are designed to be consumed by end users on the web (refer to the Notes section for details).- Revised Section 508:
- Chapter 5 – 504.2 - Authoring tools for Content Creation or Editing
- Chapter 6 – 602.3 - Electronic Support Documentation
- EN 301 549:
- Clauses 10.1-10.4 of Clause 10 - Non-Web documents
- Clauses 11.1-11.4 and 11.8.2 of Clause 11 - Software
- Clauses 12.1.2 and 12.2.4 of Clause 12 - Documentation and support services
- Revised Section 508:
Note: When reporting on conformance with the WCAG 2.2 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements, WCAG 2.1 Conformance Requirements, and WCAG 2.2 Conformance Requirements.
“WCAG 2.2 uses the same conformance model as WCAG 2.0. It is intended that sites that conform to WCAG 2.2 also conform to WCAG 2.0 and WCAG 2.1, which means they meet the requirements of any policies that reference WCAG 2.0 or WCAG 2.1, while also better meeting the needs of users on the current Web." (Source: WCAG 2.2)
Table 1: Success criteria, Level A
| Criteria | Conformance level | Remarks and explanations |
|
1.1.1 Non-text Content (Level A)
Also applies to:
|
Partially supports | 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:
|
Not applicable | This criteria is not relevant to Quickbase. |
|
1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
|
Not applicable | This criteria is not relevant to Quickbase. |
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
|
Not applicable | This criteria is not relevant to Quickbase. |
|
1.3.1 Info and Relationships (Level A)
Also applies to:
|
Partially supports | 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:
|
Supports |
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:
|
Supports | 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:
|
Supports | 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:
|
Not applicable | This criteria is not relevant to Quickbase. |
|
2.1.1 Keyboard (Level A)
Also applies to:
|
Partially supports |
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:
|
Partially supports | 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)
Also applies to:
|
Supports | 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:
|
Not applicable | This criteria is not relevant to Quickbase. |
|
2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
|
Not applicable | This criteria is not relevant to Quickbase. |
|
2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
|
Not applicable | This criteria is not relevant to Quickbase. |
|
2.4.1 Bypass Blocks (Level A)
Also applies to:
|
Supports | Quickbase includes a “jump to” menu at the beginning of the tab order that provides skip links, enabling users to bypass repeated blocks of content—such as site navigation—and go directly to the main page content. Additionally, the platform uses ARIA landmarks to support efficient navigation with assistive technologies. |
|
2.4.2 Page Titled (Level A)
Also applies to:
|
Supports | Pages have sufficient titles. |
|
2.4.3 Focus Order (Level A)
Also applies to:
|
Supports | The navigation order of focusable Quickbase elements preserves the meaning and operability of the content.
Also, reference remarks on 1.3.2. |
|
2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
|
Supports |
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)
Also applies to:
|
Not applicable | This criteria is not relevant to Quickbase. |
|
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)
Also applies to:
|
Supports |
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. |
|
2.5.3 Label in Name (Level A 2.1 and 2.2)
Also applies to:
|
Supports |
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. |
|
2.5.4 Motion Actuation (Level A 2.1 and 2.2)
Also applies to:
|
Not applicable | This criteria is not relevant to Quickbase. |
|
3.1.1 Language of Page (Level A) <>
Also applies to:
|
Does not support | 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:
|
Partially supports |
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:
|
Supports | In general, entering data into, or changing the setting of, a UI component within Quickbase does not trigger a change of context without warning. Quickbase allows builders to control alerts and notifications if they are adjusting navigation patterns. For example, builders can create and control alerts through form rules. |
|
3.2.6 Consistent Help (Level A 2.2 only)
Also applies to:
|
Supports | Help and support are easily accessible and consistently located in the header of every page. The help mechanism appears in the same position across all pages, ensuring users can reliably find it regardless of where they are within the site or application. The help mechanism is consistently placed in the header, maintaining the same relative order to other content on each page. |
|
3.3.1 Error Identification (Level A)
Also applies to:
|
Supports | 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:
|
Supports |
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. |
|
3.3.7 Redundant Entry (Level A 2.2 only)
Also applies to:
|
Supports | Quickbase allows builders to define, create, and control their applications and forms. Builders have control over ensuring that forms are designed to minimize redundant data entry. Builders have access to methods such as auto-populating fields or providing alternative selection methods like drop-down fields to streamline user input and reduce repetitive tasks. |
|
4.1.1 Parsing (Level A)
WCAG 2.0 and 2.1 – Always answer ‘Supports’ WCAG 2.2 (obsolete and removed) - Does not apply Also applies to:
|
Supports | This criterion has been removed from WCAG 2.2.
“This criterion was originally adopted to address problems that assistive technology had directly parsing HTML. Assistive technology no longer has any need to directly parse HTML. Consequently, these problems either no longer exist or are addressed by other criteria. This criterion no longer has utility and is removed.” (Source WCAG 2.2) |
|
4.1.2 Name, Role, Value (Level A)
Also applies to:
|
Partially supports |
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. |
Table 2: Success criteria, Level AA
| Criteria | Conformance level | Remarks and explanations |
|
1.2.4 Captions (Live) (Level AA)
Also applies to:
|
Not applicable | This criteria is not relevant to Quickbase. |
|
1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
|
Not applicable | This criteria is not relevant to Quickbase. |
|
1.3.4 Orientation (Level AA 2.1 and 2.2)
Also applies to:
|
Supports | The product is not restricted to a single view or orientation. Pages are generally responsive to browser width and special care has been taken for common breakpoint widths. |
|
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)
Also applies to:
|
Partially supports |
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:
|
Supports | 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: Also applies to:
|
Supports | Quickbase supports the zooming features built into modern web browsers. |
|
1.4.5 Images of Text (Level AA)
Also applies to Revised Section 508: Also applies to:
|
Supports | Quickbase uses text to convey information, not images of text. |
|
1.4.10 Reflow (Level AA 2.1 and 2.2)
Also applies to:
|
Partially supports | 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 and 2.2)
Also applies to:
|
Supports | 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 and 2.2)
Also applies to:
|
Does not support | 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 and 2.2)
Also applies to:
|
Partially supports | 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:
|
Supports | 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:
|
Supports | Headings and labels within Quickbase applications are mostly set by the app builders. For example, Quickbase provides an interface for builders to determine appropriate, descriptive, informative, and meaningful form labels such as tab navigation labels, section headings, column headings, field labels, and more. When Quickbase provides headings or labels, they are informative and descriptive. |
|
2.4.7 Focus Visible (Level AA)
Also applies to:
|
Partially supports | 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. |
|
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)
Also applies to:
|
Partially supports | Generally when a user interface component receives keyboard focus, the component is at least partially visible and not entirely hidden due to author-created content.
Exception: On a dashboard in the Expand Widget view, the modal opened with the expanded widgets does not receive focus immediately so focus becomes hidden behind the modal. |
|
2.5.7 Dragging Movements (Level AA 2.2 only)
Also applies to:
|
Partially supports | For functionality that uses a dragging movement for operation such as a rating slider, Quickbase aims to provide an alternative, such as a single click, that can be achieved by using a single pointer without the need for dragging.
Exception: Kanban reports require drag and drop, there is not a single pointer alternative. Keyboard shortcuts do not fulfill this criteria. |
|
2.5.8 Target Size (Minimum) (Level AA 2.2 only)
Also applies to:
|
Partially supports | The size of the target for pointer inputs is generally at least 24 by 24 CSS pixels. If a target is undersized, Quickbase aims to ensure there is sufficient spacing between it and adjacent targets for easy activation.
Exception: On a table report, the edit (pencil) and view (eyeball) icons do not meet the minimum 24x24 standard, there would be an overlap with a 24x24 px bounding box. |
|
3.1.2 Language of Parts (Level AA)
Also applies to:
|
Does not support | 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:
|
Supports | 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:
|
Supports | Quickbase components and UI elements that have the same functionality across multiple pages are consistently identified. |
|
3.3.3 Error Suggestion (Level AA)
Also applies to:
|
Supports | 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:
|
Supports | 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. |
|
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
Also applies to:
|
Supports | Quickbase allows the use of password entry by password manager to reduce memory need and copy and paste of passwords to reduce the cognitive burden of re-typing as ways to assist users in completing a cognitive function test (recalling a password string). Quickbase does not use CAPTCHAs in the authentication process. Quickbase allows realms to control the use of Multi-factor Authentication (MFA) if preferred. |
|
4.1.3 Status Messages (Level AA 2.1 and 2.2)
Also applies to:
|
Partially supports | 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. |
Table 3: Success criteria, Level AAA
Notes:
Quickbase has not been evaluated for compliance with WCAG 2.2 Level AAA.
Revised Section 508 Report
Notes:
The WCAG 2.2 tables 1 and 2 in the previous section also document conformance with Revised Section 508:
-
Included:
- Revised Section 508:
- Chapter 5 - 501 (Web)(Software)
- Revised Section 508:
-
Excluded:
This report addresses the Quickbase platform’s new and upgraded features that are designed to be consumed by end users on the web (refer to the Notes section for details).- Revised Section 508:
- Chapter 5 – 504.2 - Authoring tools for Content Creation or Editing
-
Chapter 6 – 602.3 - Electronic Support Documentation
- Revised Section 508:
Chapter 3: Functional performance criteria (FPC)
Notes:
| Criteria | Conformance level | Remarks and explanations |
| 302.1 Without vision | Partially supports | Quickbase applications are generally navigable using the keyboard and assistive technology; however, there are some exceptions noted in the WCAG Tables 1 and 2 in this document. |
| 302.2 With limited vision | Partially supports | Quickbase generally supports the use of standard browser controls and aims to be compatible with screen reader and other assistive technology for users with low vision; however, there are some exceptions noted in the WCAG Tables 1 and 2 in this document. |
| 302.3 Without perception of color | Partially supports | Quickbase does not rely solely on color to convey information or indicate an action, except for some graphical components such as charts and icons that may use color to differentiate data or categories. Users without perception of color can generally access the same information through alternative means, such as text labels, tooltips, or legends. Reference 1.4.1 and 1.4.3 in Tables 1 and 2. |
| 302.4 Without hearing | Not applicable | Quickbase does not include audio-only features that require the use of hearing. |
| 302.5 With limited hearing | Not applicable | Quickbase does not include audio-only features that require the use of hearing. |
| 302.6 Without speech | Not applicable | Quickbase does not require the use of speech to interact with the platform. |
| 302.7 With limited manipulation | Partially supports | Quickbase generally supports standard input mechanisms, including user-provided keyboards and pointing devices, and the platform typically does not require fine motor skills or simultaneous manual operations. Quickbase aims to maintain accessible target click areas. However, users may encounter some areas that are not fully keyboard accessible or may have focus issues. For more details, refer to Tables 1 and 2. |
| 302.8 With Limited Reach and Strength | Partially supports | Quickbase generally supports standard input mechanisms, including user-provided keyboards and pointing devices, and interaction with the platform does not require reach or strength. For more details, refer to Tables 1 and 2. |
| 302.9 With limited language, cognitive, and learning abilities | Partially supports | Quickbase generally supports users with limited cognitive, language, and learning abilities by providing clear instructions and consistent navigation. However, some areas may still need improvements to fully meet user needs. For more details, refer to Tables 1 and 2. |
Chapter 4: Hardware
Notes:
Not applicable
Quickbase does not produce hardware products. Quickbase is a web application and is not subject to the requirements of this section.
Chapter 5: Software
Notes:
Not applicable
Quickbase is a web application and is not subject to the requirements of this section. Relevant criteria are covered in the earlier WCAG tables 1 and 2.
Chapter 6: Support documentation and services
Notes:
Support documentation and services are excluded from this document. This report addresses the Quickbase platform’s new and upgraded features that are designed to be consumed by end-users on the web (refer to the Notes section at the beginning of this document for details).
Our company support documentation is web-based and can be found in the Quickbase Help Center.
EN 301 549 Report
Notes:
The WCAG 2.2 tables 1 and 2 in the previous section also document conformance with EN 301 549:
-
Included:
- EN 301 549:
- Clause 9 – Web
- EN 301 549:
-
Excluded:
This report addresses the Quickbase platform’s new and upgraded features that are designed to be consumed by end users on the web (refer to the Notes section at the beginning of this document for details).
- EN 301 549:
- Clauses 10.1-10.4 of Clause 10 - Non-Web documents
- Clauses 11.1-11.4 and 11.8.2 of Clause 11 - Software
- Clauses 12.1.2 and 12.2.4 of Clause 12 - Documentation and support services
- EN 301 549:
Clause 4: Functional Performance Statements (FPS)
| Criteria | Conformance level | Remarks and explanations |
| 4.2.1 Usage without vision | Partially supports | Quickbase applications are generally navigable using the keyboard and assistive technology; however, there are some exceptions noted in the WCAG Tables 1 and 2 in this document. |
| 4.2.2 Usage with limited vision | Partially supports | Quickbase generally supports the use of standard browser controls and aims to be compatible with screen reader and other assistive technology for users with low/limited vision; however, there are some exceptions noted in the WCAG Tables 1 and 2 in this document. |
| 4.2.3 Usage without perception of colour | Partially supports | Quickbase does not rely solely on color to convey information or indicate an action, except for some graphical components such as charts and icons that may use color to differentiate data or categories. Users without perception of color can generally access the same information through alternative means, such as text labels, tooltips, or legends. Reference 1.4.1 and 1.4.3 in Tables 1 and 2. |
| 4.2.4 Usage without hearing | Not applicable | Quickbase does not include audio-only features that require the use of hearing. |
| 4.2.5 Usage with limited hearing | Not applicable | Quickbase does not include audio-only features that require the use of hearing. |
| 4.2.6 Usage with no or limited vocal capability | Not applicable | Quickbase does not require the use of speech/vocal capability to interact with the platform. |
| 4.2.7 Usage with limited manipulation or strength | Partially supports | Quickbase generally supports standard input mechanisms, including user-provided keyboards and pointing devices, and the platform typically does not require fine motor skills or simultaneous manual operations. Quickbase aims to maintain accessible target click areas. However, users may encounter some areas that are not fully keyboard accessible or may have focus issues. For more details, refer to Tables 1 and 2. |
| 4.2.8 Usage with limited reach | Supports | Quickbase generally supports standard input mechanisms, including user-provided keyboards and pointing devices, and interaction with the platform does not require reach or strength. For more details, refer to Tables 1 and 2. |
| 4.2.9 Minimize photosensitive seizure triggers | Supports | Quickbase does not include visual flashing features that could trigger photosensitive seizures. |
| 4.2.10 Usage with limited cognition, language or learning | Partially supports | Quickbase generally supports users with limited cognitive, language, and learning abilities by providing clear instructions and consistent navigation. However, some areas may still need improvements to fully meet user needs. For more details, refer to Tables 1 and 2. |
| 4.2.11 Privacy | Supports | Quickbase maintains the same level of privacy for all users. Where applicable, privacy settings and options are accessible and operable by all users, including those with disabilities. |
Clause 5: Generic requirements
Notes:
Not applicable
Quickbase is built using standard web technologies that support the use of assistive technologies, it does not include any closed functionality (such as a kiosk). Quickbase is a web application and is not subject to the requirements of this section.
Clause 6: ICT with two-way voice communication
Notes:
Not applicable
Quickbase does not provide real-time two-way voice communication features or equipment; therefore, Quickbase is not subject to the requirements in this section.
Clause 7: ICT with video capabilities
Notes:
Partially supports (builder-controlled)
Quickbase does not include a built-in media player or provide native video content. However, it allows the use of standard web technologies such as iframes and pop-ups, which may be used to present video content to end users. In these cases, the responsibility for ensuring the accessibility of that content (e.g., captions) rests with the builder. The platform supports embedding accessible video implementations when properly configured.
Clause 8: Hardware
Notes:
Not applicable
Quickbase does not produce hardware products. Quickbase is a web application and is not subject to the requirements of this section.
Clause 9: Web (see WCAG 2.2 Report section - Tables 1 & 2)
Notes:
Quickbase aims to conform to WCAG 2.2 Level AA standards to ensure accessibility. See the WCAG 2.2 Report section earlier in this report, including Tables 1 and 2, for a detailed conformance explanation.
Clause 10: Non-web documents
Notes:
Partially supports (supports with exceptions)
Quickbase allows customers to upload and attach documents that can be viewed and downloaded by end users, such as PDFs, to records within their custom-built applications. In these cases, customers are responsible for ensuring the accessibility of uploaded documents. The platform also includes features where documents can be generated, such as when printing a record or using Document Creation. We aim to ensure these generated documents meet accessibility standards; however, some limitations exist.
| Criteria | Conformance level | Remarks and explanations |
| 10.1.1.1 through 10.4.1.3 | See WCAG 2.2 Report section | See WCAG 2.2 Report section |
| 10.5 Caption positioning | Not applicable. This clause is advisory only and contains no testable requirements under EN 301 549 | Quickbase does not rely solely on color to convey information or indicate an action, except for some graphical components such as charts and icons that may use color to differentiate data or categories. Users without perception of color can generally access the same information through alternative means, such as text labels, tooltips, or legends. Reference 1.4.1 and 1.4.3 in Tables 1 and 2. |
| 10.6 Audio description timing | Not Applicable. This clause is advisory only and contains no testable requirements under EN 301 549 |
Clause 11: Software
Notes:
Not applicable
Quickbase is a web-based application and does not include non-web software components covered by this section (such as a desktop software application). As such, the requirements in Clause 11 do not apply. Accessibility requirements relevant to web applications are addressed in Clause 9: Web and the WCAG Tables 1 and 2 earlier in this report, which reference WCAG 2.2 AA conformance.
Please note that the Quickbase native mobile application is out of scope for this document. Refer to the Notes section at the beginning of the report for details on what is included in this evaluation. Learn more about our approach to accessibility.
Clause 12: Documentation and support services
Notes:
Not evaluated
This report evaluates the accessibility of the Quickbase platform’s new and upgraded features that are designed to be consumed by end users on the web only. Documentation and support services are outside the scope of this assessment. For more information about what is covered, refer to the Notes section at the beginning of this document.
Our company support documentation is web-based and can be found in the Quickbase Help Center.
Clause 13: ICT providing relay or emergency service access
Notes:
Not applicable
The Quickbase platform does not include functionality for providing relay services or access to emergency communication services. Therefore, the requirements in this section do not apply.
Legal disclaimer
Quickbase has made commercially reasonable efforts to confirm the accuracy of this VPAT/Accessibility Conformance Report as of the date of publication and cannot guarantee that any information contained herein will remain accurate after such date. Quickbase will make good faith efforts to monitor the accessibility of its products and may provide periodic updates. The configuration of any particular Quickbase application may render some or all of the VPAT inapplicable. This VPAT is provided for informational purposes only on an “as is” basis.