English

العربية

English

العربية

Appearance

Accessibility statement ​

AppyThings wants every person in your organisation to be able to use API-dex, whatever assistive technology they rely on. This statement describes the standard the portal meets, what that covers and how to tell us when something falls short.

Standard ​

As of release 3.1.0, API-dex's core user interface components meet WCAG 2.2 Level A: the Web Content Accessibility Guidelines published by the World Wide Web Consortium. Level AA is not claimed at this release.

What is covered ​

The 3.1.0 release reworked the components every screen is built from so that they meet the standard:

  • Buttons, form fields, checkboxes, radio buttons and selects are fully operable by keyboard, carry labels that screen readers announce, and show a visible focus state.
  • Dialogs trap focus while open, return focus on close and are announced to assistive technology.
  • Tabs and tables are navigable by keyboard and expose their structure to screen readers.
  • Light and dark display modes are both maintained for contrast.
  • Right-to-left languages are supported with a fully mirrored layout.

Assistive technology ​

API-dex is built to work with current versions of the major browsers and with screen readers that follow the platform's accessibility APIs. Keyboard-only use is supported throughout the portal.

Known limitations ​

Content that an organisation publishes inside API-dex, such as its own documentation pages and API descriptions, is authored by that organisation and is not covered by this statement. Third-party content rendered inside the portal, such as an API specification, follows its source.

Reporting an accessibility problem ​

If any part of API-dex is difficult to use with your assistive technology, tell us. Use Talk to us in the top bar, or contact your AppyThings account representative, and describe the page, the technology you were using and what happened. Accessibility reports are handled as defects.