- Applicants use Argyle Link to connect their payroll or employment accounts and, at their direction, share their income and employment data straight from the source.
- Link is designed and tested to meet modern accessibility standards, including for people who use assistive technology.
Why accessibility matters
- Accessibility supports inclusion — An estimated 1.3 billion people, or about one in six people worldwide, experience a significant disability, including visual, auditory, motor, cognitive, or vestibular disabilities (World Health Organization).
- Accessibility supports compliance and procurement — Accessibility requirements apply across many markets and public-sector procurement programs, including Section 508 for U.S. federal agencies and ADA Title II for state and local government services.
- Accessibility improves the experience for everyone — Clear structure, keyboard support, readable contrast, and predictable interactions benefit people with and without disabilities.
Standards we follow
Argyle Link targets Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, and is aligned with Section 508. Argyle documents its accessibility work through independent third-party audits and an Accessibility Conformance Report (ACR) prepared using the Voluntary Product Accessibility Template (VPAT), available upon request. Argyle’s accessibility work includes:- Keyboard operation — Every step can be completed with a keyboard, with a visible focus indicator.
- Color contrast — Text has a contrast ratio of at least 4.5:1; large text and UI components have a contrast ratio of at least 3:1.
- Text alternatives — Informational images and icons include appropriate text alternatives.
- Semantic structure — Headings, landmarks, and lists support reliable navigation.
- Form labels and errors — Inputs have programmatically associated labels, and error messages are clear and accessible.
- Accessible names — Interactive controls have names that convey their purpose.
- Dynamic content — Status, loading, and error messages are announced to assistive technologies.
- Zoom and reflow — Content supports zoom and reflow up to 400% without loss of content or function.
WCAG 2.2 criteria
We test against the WCAG 2.2 criteria that are especially relevant to a login-and-submit flow:- Focus Not Obscured (2.4.11) — Focused elements remain visible rather than being entirely hidden behind sticky headers, sheets, or other content.
- Target Size (2.5.8) — Touch targets are large enough to activate reliably on mobile devices.
- Accessible Authentication (3.3.8) — Sign-in and verification-code steps do not rely on a cognitive test that a person must memorize or transcribe without assistance.
- Redundant Entry (3.3.7) — People are not asked to re-enter information they already provided in the same flow.
What Link provides automatically
When you embed Link, accessibility support includes:- Keyboard navigation — People can navigate every step in a logical order with visible focus states.
- Screen reader support — Link is tested with common assistive technologies, including NVDA, JAWS, and VoiceOver.
- Semantic markup and ARIA — Structure, roles, and states are conveyed programmatically.
- Accessible modals and dialogs — Focus moves into the dialog, background content becomes inert, and the dialog can be dismissed using its controls, the Escape key, or by selecting outside it when that behavior is supported.
- Accessible forms — Search, login, verification-code, and income-confirmation steps include labeled inputs and inline errors.
- Contrast and typography — Link is designed to meet Level AA contrast requirements and support OS-level text sizing and reduced-motion preferences.
Your integration responsibilities
Because Link runs within your application, end-to-end accessibility is a shared responsibility. Argyle maintains Link’s accessibility support, and your integration should preserve it.- Provide an accessible entry point — The button or link that launches Link needs an accessible name, keyboard focus, and sufficient contrast.
- Avoid accessibility overrides — Do not use CSS or scripts that remove focus indicators, alter ARIA attributes, or trap focus around the embedded experience.
- Embed Link correctly — If you render Link in an iframe, give the iframe a concise, descriptive
title, ensure it can receive focus, and do not block keyboard interaction. - Test the complete flow — Before going live, test your integrated experience with a keyboard and screen reader.
Branding and configuration
Argyle Link’s core interface is not customizable. Argyle designs and maintains its layout, components, and accessibility. The only client-configurable branding option is a brand color, which applies to the landing page and invitation email, not Link itself. When selecting a brand color, choose one that maintains sufficient contrast — at least 4.5:1 for text and 3:1 for large text and UI components — and do not rely on color alone to convey meaning. Because this color does not affect Link itself, it does not affect Link’s WCAG 2.2 AA conformance. You can validate color choices with a contrast-checking tool such as the Contrast plugin for Figma.Testing and conformance
- Independent third-party audit — A third party audits Link against WCAG 2.2, Level AA, and Section 508. Results are delivered as an Accessibility Conformance Report (ACR) using the Voluntary Product Accessibility Template (VPAT).
- Manual and automated testing — Certified testers perform manual and assistive-technology testing alongside automated testing in continuous integration (CI), including axe-core and regression checks.
- Ongoing validation — Argyle retests Link on a regular cadence as the experience evolves.