Accessibility of Okta products

Okta is continuously working to improve the accessibility of its products in compliance with Section 508 of the US Government as well as the WCAG standards. This page provides information about our efforts to provide a more accessible experience to your end-users.

Okta Browser Plugin

  • Images provide informative alternative text
  • Form fields have valid labels
  • Dialogs can be closed through the keyboard
  • Popup modals have boundaries
  • Popup modals are accessible through the keyboard
  • Custom controls provide proper textual name, role, and state information
  • Keyboard focus is indicated visually
  • All interactive elements are accessible through the keyboard
  • Content reading order is logical

 

Also see

Keyboard shortcuts for Okta Browser Plugin

End-user dashboard

  • CSS background images that convey meaning have textual and visible equivalents
  • Images provide informative alternative text
  • Form fields have valid labels
  • Dialogs can be closed through the keyboard
  • Dialogs use proper structure
  • When dialogs are activated focus moves appropriately
  • Custom controls are accessible through keyboard
  • Custom controls provide proper textual name, role, and state information
  • Link text is meaningful within context
  • Link text is meaningful when taken out of context
Top