Visa Accessibility - Visa Global Accessibility Requirements
Visa Global Accessibility Requirements
Meets WCAG 2.2 AA
With the Web Content Accessibility Guidelines (WCAG) being the de facto global standard for digital accessibility, Visa is proud to say that the Visa Global Accessibility Requirements (VGAR) meet the W3C's most recent version, which is WCAG 2.2. We were able do so by adding four new requirements to the VGAR and updating two existing ones.
The following requirements were added to VGAR:
- Redundant Entry (INT-WEB-001-11)
- Multiple Authentication Methods (INT-WEB-001-12)
- Click and Drag Movements (INT-WEB-006-05)
- Target Size (VIS-WEB-001-06)
The following requirements were updated:
Custom Written and User-Centric
While WCAG 2.2 is designed to help users with disabilities, the real users of this valuable standard are designers, developers, and testers. After researching these solution makers and how they work and learn, we decided to translate WCAG 2.2 AA into a set of simple requirements and test cases that would allow Visa staff to more easily and consistently create accessible products. We call them Visa's Global Accessibility Requirements, or the VGAR, for short.
Easy to Follow, Easy to Test
Besides writing our own set of 120+ requirements that work for Visa products, we asked our staff how they could best use such requirements. While WCAG 2.2 is organized by user goals, the VGAR is organized in two different ways:
- For developers and designers, the VGAR Requirements are organized by type of work and then by component. With included code samples, the VGAR Requirements give developers what they need, in context, and on demand.
- For QA testers, the VGAR Test Procedures are organized by testing tool. With links and descriptions for each tool (and how-to videos on the way), these procedures give testers what they need in a more efficient order.
Freely Available
We put a lot of time into creating a set of clear and concise requirements that worked for Visa products and it just made sense to share the requirements with others. Your situation may require different or modified requirements, but we invite you to take a look at what we use and contribute to a more accessible web for everyone!
The Process
Everyone involved in the product development lifecycle has a role to play in making products accessible for people around the globe. Learn about users with disabilities and keep these users in mind as features, designs, interactions, and code decisions are made and evaluated. Accessibility is not a fix; it's a process.
Plan and Lead
Product managers, project managers, and leadership have a critical role to play in ensuring a successful accessibility effort. Accessibility must be a priority from the beginning, with direction and strategy pointing to features that include as many people as possible.
Design
Visual and interaction designers are responsible for creating experiences that work for the widest range of users. By following the VGAR design requirements and understanding how different users interact with digital content, this team can deliver more inclusive designs.
Develop
Developers must be disciplined and thorough to deliver pixel- and interaction-perfect interfaces that maintain the inclusivity of the designs they are given. By following the VGAR Requirements and working with an accessibility expert when needed, development teams can deliver more accessible interfaces.
Test
Automated and manual testing is used to validate that accessibility has been effectively considered in a product. The VGAR Test Procedures are streamlined and organized to allow more efficient testing without deep subject matter expertise.