Skip to main content

Accessibility FAQs

In this article

Standards and compliance

Where is the most recent Quickbase VPAT?

Find our most recent Accessibility conformance report (or VPAT) in the help center.

How does Quickbase comply with U.S. Section 508?

Refer to our most recent Accessibility conformance report (VPAT), which we have updated to include details about our compliance with Section 508 standards.

What accessibility standards does Quickbase follow?

Quickbase aims to meet WCAG 2.2 AA standards in all our new and upgraded features designed for end-users on web.

To what extent is Quickbase accessible to people with disabilities—including people who are blind or have low vision, are Deaf or hard of hearing, have mobility or dexterity limitations, and have speech impairments?

As a company, we take critical accessibility gaps and regularly weigh them with our ongoing efforts for improvement. For specific details on how Quickbase complies with WCAG 2.2 AA standards, refer to our latest Accessibility conformance report (VPAT).

We understand the importance of accessibility and aim to make our platform usable for everyone. If there is an issue, please contact your account team so we can resolve it.

Product development

What experience coding for accessibility do Quickbase developers have?

We have a dedicated team of developers, Quality Assurance (QA) specialists, and designers who are trained in the WCAG 2.2 AA standards. Not only do they work on developing new features and components for Quickbase, but they each are also designated mentors across all our engineering teams.

Does Quickbase have a roadmap for accessibility?

Yes, we include accessibility improvements in the roadmap for all features we are working on according to the WCAG 2.2 AA standards.

As a company, we also regularly take critical accessibility gaps and weigh them with our ongoing efforts for improvement. Please reach out to your account team to discuss this in detail.

Why does Quickbase focus on new features and UI for accessibility improvements?

Quickbase has been developed and iterated on for over 20 years. As we continue to grow, we are focused on bringing new and enhanced features to modernize the platform. Prioritizing accessibility in these new efforts helps us provide the most usable and inclusive experience possible in our evolving platform.

Is there a process for enabling an accessibility mode or alternate interface? Is this process accessible for a person using assistive technology?

There is no enabling or use of an alternate interface required because Quickbase automatically uses the builder-defined schema of the application (like field names and report names) to inform elements (like ARIA labels). The accessibility of an application will ultimately depend on how a builder incorporates accessible features into the overall design of an application.

Testing and evaluation

What is the Quickbase accessibility conformance testing process?

Our accessibility testing process includes:

  • Automated testing
  • Manual testing with our QA team
  • Third-party testing with an outside vendor that provides access to a diverse community of people with disabilities, who use various assistive technologies

Does Quickbase do testing with users with disabilities? If so, explain the process and the range of disabilities and access technologies used.

Our team currently partners with an outside vendor that provides access to a diverse community of people with disabilities, who use various assistive technologies. The community uses the following assistive technologies:

  • Screenreaders: JAWS, NVDA, VoiceOver, TalkBack, Narrator
  • Magnification: ZoomText, iOS Zoom, Android Zoom, Browser Zoom
  • Alternative navigation: Dragon NaturallySpeaking, Switch systems, Headmouse, On-screen keyboard

What methods does Quickbase use to determine the accessibility of the product?

We use our Quality Assurance (QA) and System Quality (SQ) teams, as well as our team of trained designers and developers.

Customer feedback

Does Quickbase have clients who require accessibility (federal government, international, or local company policies)? If so, how are they ensuring Quickbase meets their requirements?

We have thousands of customers that use Quickbase in many different ways. They each have varying needs related to accessibility. We engage with customers on accessibility questions by sharing our roadmap and working with their account teams to understand and prioritize their requests.

We are committed to promoting and improving accessibility for our users with disabilities. To do this, we:

  • Aim to make all new features comply with the Web Content Accessibility Guidelines (WCAG) 2.2 AA.
  • Provide customers with the most recent Voluntary Product Accessibility Template (VPAT) for our service(s).
  • Are open to discussing areas of particular importance to our customers and helping to identify solutions to meet their needs.

If customers discover changes need to be made to web or mobile interfaces/apps, what guarantee can they have that these will be implemented to their satisfaction before implementation?

Quickbase has strict quality standards that we adhere to, and accessibility issues are assessed by their severity against WCAG 2.2 AA standards. We take feedback from customers seriously and weigh feedback against all customers and all priorities.

If there are specific concerns blocking implementation, we encourage you to work directly with your account team.

Contact for accessibility feedback

We always appreciate any feedback related to accessibility and usability so that we may continue to improve.

Related articles

Top