At Usabilla we try to make our software accessible for every type of user. This article outlines how Usabilla strives to conform to the WCAG 2.0 guidelines and by doing so aims to provide a website feedback tool for all types of users. All accessibility efforts that are mentioned in this article are limited to Usabilla Buttons and Form. Some of the accessibility efforts include:
Help us improve
- Which browser and version are you using?
- Which screen readers are you using? (e.g. NVDA, Voiceover, Jaws, etc)
- Which automated tooling are you using? (e.g. Axe)
- Which WCAG standard and guidelines does it concern?
If you have any questions regarding this article, please don’t hesitate to contact us. You can reach us by using the contact form on https://usabilla.com/contact.
Introduction to accessibility
We strive to have our Usabilla for Websites tool conform to level AA of the Web Content Accessibility Guidelines 2.0. These guidelines are the internationally recognized benchmark for building accessible websites.
The Web Content Accessibility Guidelines explain how to make content on the web more accessible for all types of users, including those with disabilities. By conforming to these accessibility guidelines we can make the web more user-friendly for all people.
At Usabilla we’re working hard to make Usabilla for Websites conform with the W3C Web Content Accessibility Guidelines 2.0 (WGAC 2.0). The level of Conformance to the WCAG 2.0 guidelines is dependent on the level of satisfaction that is achieved for the success criteria specified in the guidelines. The WCAG 2.0 guidelines state 4 principles that serve as a foundation for the thirteen (13) guidelines. Usabilla is striving to conform to a level AA conformance of WCAG 2.0 which is achieved by meeting the level 2 success criteria. The success criteria for each guideline are organized into three (3) levels. The specific success criteria for each guideline is outlined on the W3C website.
Principles & Guidelines
Principle 1: Content must be perceivable.
Guideline 1.1 Perceivable - Information and user interface components must be presentable to users in ways they can perceive.
- We’ve made sure that all non-text elements have text-alternatives and is read by screen readers.
Guideline 1.2 Time-based Media: Provide alternatives for time-based media.
- Not applicable.
Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
- We’ve made sure that all form controls are being read by screen readers.
- Usabilla for Websites follows a clear informative structure in HTML and CSS.
Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background.
- The default Usabilla for Websites theme has a clear distinguishable presentation to easily separate the foreground information from the background information.
Principle 2: Operable - User interface components and navigation must be operable.
Guideline 2.1 Keyboard Accessible: Make all functionality available from a keyboard.
- The feedback form for Usabilla for Websites is fully usable via a keyboard interface.
Guideline 2.2 Enough Time: Provide users enough time to read and use the content.
- Usabilla for Websites does not maintain a time limit for reading and interacting. The user has full control over these functions
- Usabilla for Websites allows the user to pause anytime
Guideline 2.3 Seizures: Do not design content in a way that is known to cause seizures.
- Usabilla does not use any content that could cause seizures due to photosensitivity. There are no components that flash more than three times in a one second time period.
Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.
- We’ve made sure that users by default have all content needed information to orient and navigate as needed.
Principle 3: Understandable - Information and the operation of user interface must be understandable.
Guideline 3.1 Readable: Make text content readable and understandable.
- By default, Usabilla ensures that the language in Usabilla for Websites forms is set within the HTML of the feedback form.
- In addition, Usabilla for Websites allows content to be enhanced and set using HTML or separate forms specifically for users with assistive technologies.
Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways.
- We made sure that the focus in any Usabilla for Website form goes to the question when a required field is not filled in and submitted.
- Components with the same function are used consistently across the Usabilla for Websites tool.
Guideline 3.3 Input Assistance: Help users avoid and correct mistakes.
- When an input error is made the users are notified by this. This is done using both the Usabilla for Websites input notifications as well as the default user agent input form control notifications.
Principle 4: Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Guideline 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies.
- Usabilla for Websites supports most browsers. The following browsers have been tested and are fully supported: Internet Explorer (version 8 and up), Mozilla Firefox (all versions), Google Chrome (all versions), Safari (all versions) and Opera (version 12 and up).
- Usabilla for Websites has been tested to support the following user agents with assistive technologies Firefox 47 (NVDA), IE 8+(JAWS) and Safari (Voiceover).
- The role and name for all elements within Usabilla for Websites can be programmatically determined.
- Values can be set programmatically and changes within the user interface components are notified to all types of user agents.
Guideline 4.2 Ensure that content is accessible or provide an accessible alternative
- All content in Usabilla for Websites is accessible by using a regular user agent or a user agent with assistive technologies.