Security Contact

Policy Center

Accessibility

This statement describes the accessibility practices used on this website and how to request assistance.

We work to make this website usable with common browsers, devices, and assistive technologies. Third-party content may not provide the same level of accessibility.

Structure

Headings, landmarks, lists, labels, and page titles support navigation and scanning.

Keyboard

Core links and controls are designed to be reachable without a mouse.

Responsive display

Layouts adapt to smaller screens and tables can scroll horizontally when necessary.

Assistance

Users may request information in another reasonable format when a barrier prevents access.

Practical accessibility approach

Design decisions consider contrast, text size, line length, focus visibility, heading order, link meaning, image alternatives, form labels, browser zoom, and compatibility with common assistive technologies. The site uses a skip link, semantic navigation, one primary heading per page, visible keyboard focus, and mobile navigation.

Third-party and embedded content

External widgets, documents, communications platforms, and other provider-controlled components may not offer the same keyboard behavior, labels, contrast, captions, zoom support, or assistive-technology compatibility as company-controlled pages. Where a barrier involves an external service, we may be able to provide a description, link, or reasonable alternative format, but we cannot guarantee changes to a provider’s product.

Limitations

Accessibility may vary with device, browser, operating system, assistive technology, network conditions, and third-party content. We do not claim that every page satisfies every technical standard in every combination of technology and settings. We prioritize reproducible barriers that prevent access to important information or completion of an essential task.

Request assistance or report a barrier

Email Contact email with the subject “Accessibility.” Include the page URL, the task you were trying to complete, device and browser, assistive technology if relevant, and the format or accommodation that would help.

Review process

  1. Confirm the page, task, and barrier.
  2. Attempt to reproduce the issue in a relevant device or browser.
  3. Provide an alternative format or route where reasonably possible.
  4. Repair the company-controlled page or refer the issue to a third-party provider.
  5. Retest the affected interaction after the change.

Content and interaction coverage

Accessibility review applies to navigation, headings, policy tables, images, links, expandable sections, buttons, status messages, and the primary communications action. Content should remain understandable when text is enlarged, when color is unavailable, and when a visitor uses a keyboard instead of a pointer.

Tables may use a contained horizontal scrolling area on smaller screens so the page itself does not overflow. Expandable content must preserve a visible label and a clear open or closed state. Images that convey information should include useful alternative text; decorative images should not repeat nearby text.

  • Page structure should follow a predictable reading order on desktop, tablet, and mobile screens.
  • Focus should move to interactive controls in an order that matches the visual and reading sequence.
  • Links should describe their purpose or destination without relying only on surrounding color or position.

Alternative access and reasonable assistance

When a company-controlled page presents a barrier, a visitor may request the same core information in a practical alternative format. The available response may include plain text, a direct link to the relevant policy section, a description of a chart, or another route to complete the same informational task.

An accessibility request does not require disclosure of a diagnosis or medical history. Provide only the details needed to identify the page, reproduce the barrier, and understand the requested format. We may ask a limited follow-up question when the requested change is unclear or when a third-party component controls the affected interaction.

Feedback

Specific examples are more useful than a general statement that a page is difficult. Screenshots, keyboard steps, screen-reader output, zoom level, and the expected result can help identify the problem. Do not include unnecessary sensitive information.