Member Application Accessibility Overview

Navigation, text communication, and applicant assistance

1. Purpose and scope

Glide maintains a WCAG 2.1 Level AA checklist and uses it to verify the member-facing application against the standard’s accessibility requirements. This overview describes keyboard navigation, visual orientation, and text-based communication during personal account opening, along with assistance and accessibility feedback channels.

2. Keyboard navigation and visual focus

Skip to main content. A keyboard-accessible “Skip to main content” link moves focus to the primary page content. The link becomes visible when it receives keyboard focus.

Visible focus indicators. Focus outlines identify the active control as an applicant navigates with a keyboard. These indicators help applicants track their position on the page.

Dropdown interaction. Dropdown controls provide visible feedback for the focused control, highlighted option, and selected option. Keyboard navigation improvements support moving through options and making selections.

3. Page structure and text-based interaction

Main content landmark. The application identifies its primary content with a semantic main landmark, providing a navigation target for assistive technologies.

Action labels. Text labels identify application actions, including identity verification. Native button controls provide an interactive target for those actions.

Written verification instructions. The phone-confirmation screen presents instructions in text and uses SMS verification codes. Applicants read the message and enter the code in the application.

Visible error feedback. The phone-confirmation screen displays invalid-code and expired-code messages in text. Applicants receive written feedback to guide their next action.

4. Application services and applicant assistance

Glide’s account-opening journey includes integrated services for identity verification. The application opens Plaid Link for the identity-verification step.

Applicants request help from their financial institution through the contact information provided in the application. Use that contact channel to request assistance with an application or describe an accessibility barrier.

5. Accessibility questions and feedback

Financial institutions submit accessibility questions and feature requests through their established Glide support channel. A useful report identifies the application page or step, the barrier encountered, the action attempted, and the browser or device used. Include the assistive technology and preferred communication method when relevant.

For a vendor review, specify the application journey, the accessibility features being evaluated, and the documentation required. This helps Glide and the financial institution address the request in the context of the applicant’s workflow.