At Rightsline, we're committed to ensuring digital accessibility for all users, including people with disabilities. We're continually improving the user experience for everyone and applying relevant accessibility standards to ensure the Rightsline platform is usable and inclusive.
Our Commitment
We strive to follow the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards, which are internationally recognized benchmarks for accessibility. Our goal is to make sure that our website, applications, and content are perceivable, operable, understandable, and robust for all users.
Ongoing Efforts
We are:
- Regularly auditing our platforms for accessibility barriers
- Training our teams on inclusive design and development best practices
- Prioritizing accessibility in our product roadmap and feature updates
- Engaging accessibility tools and experts to identify and address issues
WCAG Conformance Levels
There are three levels of WCAG conformance: A, AA, and AAA. Each level builds on the previous level like a pyramid. So, in order to meet Level AA, you must meet all of Level A, and in order to meet Level AAA, you must meet all of Level AA.
The Rightsline application meets all level A and AA, as well as some AAA (noted below). If an item is marked as not applicable (N/A), that type of feature does not exist in Rightsline.
| Criterion | A | AA | AAA |
| Text alternatives provided for non-text content | |||
| Audio and video content alternatives | N/A | ||
| Content relationships implied by formatting work with assistive technology | |||
| Reading order of content is meaningful, no matter how a user accesses it | |||
| Instructions rely on more than one sense | |||
| Color is not the only way used to distinguish or convey meaning, indicate action, or prompt a response | |||
| All functionality is operable using a keyboard | |||
| The focus does not get trapped on any element in keyboard-only navigation | |||
| No single-key shortcuts are used | |||
| If a page has a time limit, users can adjust it | N/A | ||
| User controls are provided for moving or dynamically changing content | |||
| No content flashes more than three times per second | N/A | ||
| Bypass repeated blocks of content | N/A | ||
| Page titles clearly describe the page topic or purpose | |||
| The tabbing order of the content is meaningful and supports operation | |||
| Every link's purpose is clear from its text (AAA) and/or its context (A) | |||
| Pointer gestures & cancellation | N/A | ||
| Programmatic name contains the text that is presented visually | |||
| Alternative response provided for functions triggered by moving a device or by gesturing | N/A | ||
| Each page has a human language assigned | |||
| Interactive elements receiving focus do not trigger any functionality | |||
| Interactive elements receiving input do not trigger any functionality. | |||
| Help options are consistently available and in the same relative place | |||
| When input error is detected, the user is notified and the error is described | |||
| A persistent visible label and / or instructions are provided for elements that require user input | |||
| Information that the user has already entered during a process is made available to them | |||
| All UI components communicate their accessibility properties and actions to assistive technology | |||
| Screen orientation is not restricted unless the orientation is considered essential | |||
| The purpose of each form field collecting user information is programmatically declared | |||
| The contrast ratio between regular-sized, non-decorative text and its background is at least 4.5:1 | |||
| Text can be resized up to 200% without loss of content or function | |||
| There are no images of text (AAA), with exceptions (AA) | |||
| Content presentation is responsive and doesn't require scrolling in two dimensions | |||
| The contrast ratio between non-text elements and their background is at least 3:1 | |||
| Text spacing can be overridden to improve the reading experience | |||
| When additional content is presented on hover or on focus, the new content is persistent and dismissible | |||
| There is more than one way to reach each page | |||
| Headings and labels are clear and descriptive | |||
| Keyboard focus is clear and visible | |||
| When an actionable element receives focus, at least a portion of it remains visible | |||
| An alternative means of dragging, such as tapping or clicking, is provided | |||
| The size of a target is at least 24 by 24 pixels | |||
| Assistive technology can distinguish and reflect when the human language on a page changes | |||
| Navigational elements are consistently displayed, in the same location and order | |||
| Components with the same functionality are consistently identified | |||
| Users receive helpful / specific suggestions when they make errors | |||
| Financial or legal submissions are reversible, and data is confirmed before submission is finalized | |||
| When a cognitive function test is used to authenticate a user, an alternative way to authenticate is provided | N/A | ||
| Status messages can be presented to the user by assistive technology without receiving focus | |||
| The purpose of elements is programmatically declared by adding semantics or metadata | |||
| Low or no background audio | |||
| With the exception of real-time events, no content requires timed interaction | |||
| Interruptions can be postponed, suppressed, or configured | |||
| User data is saved when re-authenticating | |||
| Users can orient themselves within a set of pages | |||
Feedback
If you encounter any accessibility barriers while using Rightsline, we want to hear from you. Please let us know so we can help and continue to improve.
Email us at: accessibility@rightsline.com
We aim to respond to accessibility-related feedback within 3–5 business days.