Skip to main content

General

Find general requirements for testing web experiences.

Page title (GEN-1)

Accurate title (GEN-1-1)

An accurate and descriptive page title must be included on every page or view.

How to test

Tool: ANDI

  1. Inspect the HTML DOM and confirm that a element is present.
  2. Verify that the page title provided is accurate and descriptive of the purpose of the page and content.

Test outcomes

  • Pass: Page title is accurate and descriptive of the page content.

  • Fail: Page title is not included or page title is inaccurate and/or not descriptive of the page content.

Related WCAG criteria

WCAG 2.2 A - 2.4.2 Page Titled

Unique title (GEN-1-2)

The page title must be unique and conform to a consistent structure among the other pages.

How to test

Tool: Browser Dev Tools (F12)

  1. Inspect the target page.
  2. Review the html tag.
  3. Verify that the page title is unique and conforms to a consistent structure among the other pages.

Test outcomes

  • Pass: Page title is unique and conforms to a consistent structure among the other pages.

  • Fail: Page title is not unique and/or it does not conform to a consistent structure among the other pages.

Related WCAG criteria

WCAG 2.2 A - 2.4.2 Page Titled

Language (GEN-2)

Lang attribute (GEN-2-1)

The applicable language must be defined on every page, inside the html tag.

How to test

Tool: Browser Dev Tools (F12)

  1. Use the Inspect feature in the browser (for example: Chrome F12 dev tools) to open a view of the page HTML code.
  2. Locate the element at the beginning of the HTML DOM.
  3. Confirm that the attribute is correct for the language of the page content.

Test outcomes

  • Pass: Correct page language is defined.

  • Fail: Page language is not defined or the incorrect page language is defined.

Related WCAG criteria

WCAG 2.2 A - 3.1.1 Language of Page

Lang of parts of page (GEN-2-2)

A lang attribute must be set on every word or phrase that is in a different language than the page’s main language.

How to test

Tool: Browser Dev Tools (F12)

  1. Locate any words or phrases in the page content that are in a language that is different from the language of the other content in the page.
  2. Use the Inspect feature in the browser (for example: Chrome F12 dev tools) to open a view of the page HTML code and inspect each of these words or phrases.
  3. Confirm that each of these words or phrases is wrapped in a element with a attribute that is correct for the language of the word or phrase.

Test outcomes

  • Pass: All words or pages which are in a different language than the global lang are marked up with the appropriate language.

  • Fail: Words or pages which are in a different language than the global lang are not marked up with the appropriate language.

  • NA: No words or phrases are in a different language from the global language.

Related WCAG criteria

WCAG 2.2 AA - 3.1.2 Language of Parts

AT compatible (GEN-3)

Support screen readers (GEN-3-1)

All features and functionality made available to users within the web application must be functionally supported with at least one screen reader per supported platform (for example: JAWS for Windows desktop, VoiceOver for MAC iOS, etc.).

How to test

Tool: Screen reader

Run through all use cases with each supported screen reader, confirming that all features and functionality are fully available to non-sighted users.

Test outcomes

  • Pass: All features and functionality are fully available to non-sighted users.

  • Fail: One or more features or functionality are not fully available to non-sighted users.

Related WCAG criteria

WCAG 2.2 A - 4.1 Compatible

Alerts read (GEN-3-2)

When alerts are shown on screen (for example: success, error, or status/informative) they must also be read aloud by each supported screen reader without receiving focus.

Note: Error messages that appear in-line upon leaving a form field are common examples.

How to test

Tool: Screen reader

Confirm that when alerts are shown on screen (for example: success, error, or status/informative) they are also read aloud by each supported screen reader.

Test outcomes

  • Pass: Alerts shown on screen are read aloud by each supported screen reader.

  • Fail: Alerts shown on screen are not read aloud by each supported screen reader.

  • NA: No alerts are shown on screen.

Related WCAG criteria

WCAG 2.1 AA - 4.1.3 Status Messages

A11y validator (GEN-4)

Use an Automated Testing Tool (GEN-4-1)

When run against the page, the automated validation tool must not report any errors.

How to test

Tool: Accessibility Insights

  1. Run one automated validation tool of your choice against the page and confirm that it reports no errors.
  2. If errors are found, record a FAIL with a FAIL ID for each issue reported by the tool.

Test outcomes

  • Pass: Automated tool returns zero errors.

  • Fail: Automated tool returns one or more errors.

Related WCAG criteria

WCAG 2.2 A & AA

These materials are intended for illustrative purposes only. They are provided AS-IS and should not be relied upon for marketing, legal, tax, financial, regulatory or other advice. Any links to third party sites are for your information only and do not constitute endorsement by or affiliation with Visa. Visa has no insight into and/or control over third party content and code and disclaims all liability for any such components.

Copyright © 2026 Visa. All rights reserved.