ACR Index Accessibility Conformance Reports for software

Okta Platform

Accessibility Conformance Report published by Okta

Conformance by level

Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.

Source: View the original report published by Okta.

These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.

All reported criteria (102)

Conformance as stated by Okta in its published report.
CriterionNameLevel ConformanceRemarks from vendor
1.1.1 Non-text Content A Supports Web: Non-text content has text alternatives or a text alternate that serves an equivalent purpose.
1.2.1 Audio-only and Video-only (Prerecorded) A Not Applicable Web: Prerecorded audio-only files are not present.
1.2.2 Captions (Prerecorded) A Not Applicable Web: Prerecorded videos are not present.
1.2.3 Audio Description or Media Alternative (Prerecorded) A Not Applicable Web: Prerecorded videos are not present, so audio description is not required.
1.3.1 Info and Relationships A Partially Supports Web: Most information, structure, and relationships conveyed through presentation can be
1.3.2 Meaningful Sequence A Supports Web: The reading and navigation order is logical and intuitive.
1.3.3 Sensory Characteristics A Supports Web: Instructions to operate and/or understand content do not rely on sensory characteristics of components such as shape, color, size, and visual location.
1.4.1 Use of Color A Partially Supports Web: For most content, color is not used as the only method to convey information, indicate an action, prompt a response, or distinguish visual elements. The following exception exists: ● Color is used as the only method to convey the state (such as "checked," "pressed," or "selected") of a control, so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following page: Request List- Left side navigation component found on several pages.
1.4.2 Audio Control A Supports Web: A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays for more than 3 seconds.
2.1.1 Keyboard A Partially Supports Web: On most pages, all functionality is available using only the keyboard (unless that functionality cannot be accomplished in any known way using a keyboard). If shortcut keys and accesskeys present, some may conflict with existing browser and screen reader shortcuts, and some functionality based on custom gestures may not be available when a screen reader is turned on. The following exception exists: ● A function cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use this function. This occurs on the following page: End User Dashboard Landing Page.
2.1.2 No Keyboard Trap A Supports Web: Keyboard focus is never locked or trapped in a particular area, and the user is able to navigate to and from all navigable elements using only a keyboard.
2.1.4 Character Key Shortcuts A Supports Web: If a single character key shortcut exists, then the single character key shortcut can be turned off or remapped, or it is only active when the relevant user interface component is in focus.
2.2.1 Timing Adjustable A Supports Web: If a time limit exists, the user is given options to turn off, adjust, or extend that time limit.
2.2.2 Pause, Stop, Hide A Supports Web: Moving, blinking, scrolling, or auto-updating information can be paused, stopped, hidden, or otherwise controlled by the user.
2.3.1 Three Flashes or Below Threshold A Not Applicable Web: The website does not contain flashing content.
2.4.1 Bypass Blocks A Supports Web: A method is provided to skip navigation and other page elements that are repeated across web pages.
2.4.2 Page Titled A Supports Web: Pages have descriptive and informative titles.
2.4.3 Focus Order A Supports Web: The navigation order of interactive elements (such as links, buttons, or form elements) is logical and preserves meaning and operability.
2.4.4 Link Purpose (In Context) A Partially Supports Web: The purpose of most links can be determined from the link text alone or from the link text and its programmatic context. The following exception exists: ● The purpose of the link is not made clear by its text or the context provided by the content that immediately surrounds it, so people who are blind and/or use a screen reader will not know where the link goes. This occurs on the following page: My Review page - Open Tab.
2.5.1 Pointer Gestures A Supports Web: All functionality that can be operated with a pointer can be operated with single-point actions.
2.5.2 Pointer Cancellation A Supports Web: For functionality that can be operated using a single pointer, at least one of the following is true: ● The action is not triggered on the down event. ● The action triggers on the up event, and a mechanism is available to abort the function before completion or to undo the function after completion. ● The up-event reverses any outcome of the preceding down-event. ● Completing the function on the down-event is essential.
2.5.3 Label in Name A Partially Supports Web: For most user interface components that include visible text labels, the accessible name matches (or includes) the visible text in the label. The following exception exists: ● The accessible name of an interactive element (such as a link, button, or form input) contains its visible label, but the words are in a different order, so the accessible name does not contain the visible label, and people who use speech input to navigate and operate content will not be able to access the
2.5.4 Motion Actuation A Not Applicable Web: The website does not contain functionality that can be triggered by device motion.
3.1.1 Language of Page A Supports Web: The language of each page is correct and can be determined programmatically.
3.2.1 On Focus A Supports Web: When an element receives focus, a change in context (such as a substantial change to the page, the spawning of a pop-up window, or a change in focus) that may disorient the user does not occur.
3.2.2 On Input A Supports Web: When a user inputs information or interacts with a control, it does not result in a substantial change to the page that could disorient the user unless the user is informed about the change ahead of time.
3.2.6 Consistent Help A Supports Web: On web pages that contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other page content unless the user changes that order.
3.3.1 Error Identification A Supports Web: For form controls where an input error is automatically detected, a text message or alert is provided that identifies the field/control where the error was detected and describes the error.
3.3.2 Labels or Instructions A Partially Supports Web: For most form controls/input fields requiring user input, labels, instructions, and/or error messages are provided to identify the controls/input fields in the form so that users know what input data is expected. The following exceptions exist: ● The label of an element is not persistent (always visible on the page), so the element's purpose may be difficult to discover. This occurs on the following pages: Pending Reviews tab and Filter; Request list -Header components found on several pages. ● The label for a form field is missing, so the field's purpose is not clear. This occurs on the following page: Pending Reviews tab.
3.3.7 Redundant Entry A Supports Web: If information previously entered by, or provided to, the user is required to be entered again in the same process, that information is either automatically populated or available for the user to select unless the previously entered information is no longer valid or re-entering the information is essential or required to ensure security.
4.1.1 Parsing A Supports Web: For the WCAG 2.0, 2.1, EN 301 549, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata. This criterion was removed from WCAG 2.2.
4.1.2 Name, Role, Value A Partially Supports Web: The name, role, state, and value of most user interface components can be programmatically determined. The following exceptions exist: ● A button does not have a programmatic role, so its role (usually button, but sometimes link or something else) is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Pending Reviews tab; Individual ticket. ● A link does not have a programmatic role, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose and function of the link or how to interact with it. This occurs on the following page: Pending Reviews tab. ● An element that appears and functions like a combobox does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following pages: Request Apps Screen and Header component found on multiple pages.
1.2.4 Captions (Live) AA Not Applicable Web: Live multimedia files with audio are not present, so synchronized captions are not required.
1.2.5 Audio Description (Prerecorded) AA Not Applicable Web: Prerecorded multimedia files are not present, so audio descriptions are not required.
1.3.4 Orientation AA Supports Web: Orientation of the content is not locked to either landscape or portrait unless a specific orientation is essential for the functionality.
1.3.5 Identify Input Purpose AA Partially Supports Web: The purpose of most input fields that collect an individual's personal data are programmatically defined based on the WCAG list of Input Purposes for User Interface Components. The following exception exists: ● No programmatic purpose is provided for an input element (like a text input field), so browsers or assistive technology are not able to automatically suggest information to fill in the input. This occurs on the following page: Personal Information (Editing & Not Editing).
1.4.3 Contrast (Minimum) AA Supports Web: Text and images of regular text have the required color contrast ratio with their backgrounds.
1.4.4 Resize text AA Partially Supports Web: Most content is readable and functional when browser zoom is set to 200% of its initial size. The following exception exists: ● Content is lost, clipped, or obscured when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it
1.4.5 Images of Text AA Supports Web: When content can be presented visually using only text, an image of text is not used to present that text.
1.4.10 Reflow AA Partially Supports Web: The content of most pages is viewable without scrolling horizontally when the viewport is set to 320 CSS pixels wide. The following exceptions exist: ● When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content does not fit horizontally, so it cannot be viewed without scrolling. People with low vision who increase the size of text and other content using the browser zoom may have difficulty accessing the content that can only be seen by horizontal scrolling. This occurs on the following page: Pending Reviews tab. ● When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or
1.4.11 Non-text Contrast AA Partially Supports Web: Most of the boundaries and indicators of the visual state(s) of each active user component and any graphics required to understand content have a 3:1 color contrast ratio with adjacent color(s) or their background. The following exception exists: ● The focus indicator of an interactive element (like a button or input field) does not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving when the interactive element is receiving focus. This occurs on the following page: Review user access or change department review and Header component found on multiple pages.
1.4.12 Text Spacing AA Supports Web: The spacing between letters, words, lines of text and paragraphs can be adjusted with no loss of content or functionality.
1.4.13 Content on Hover or Focus AA Partially Supports Web: In most cases when additional content is triggered by pointer hover or keyboard focus, that additional content can be dismissed and hovered over, and the content persists until the user dismisses it. The following exception exists: ● Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) is not dismissible, so it obscures all or part of the original content on the page. This occurs on the following pages: Request list; Individual ticket.
2.4.5 Multiple Ways AA Supports Multiple ways are available to find other pages on the site.
2.4.6 Headings and Labels AA Partially Supports Web: Most headings and labels for form and interactive controls are informative. The following exception exists:
2.4.7 Focus Visible AA Partially Supports Web: In most cases, it is visually apparent which page element is currently receiving keyboard focus. The following exception exists: ● An interactive element (such as a link, button, or form input) does not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when that element is receiving focus. This occurs on the following page: Pending Reviews tab.
2.4.11 Focus Not Obscured (Minimum) AA Partially Supports Web: When most user interface components receive keyboard focus, each component is not entirely hidden due to author-created content. The following exceptions exist: ● A focused element is completely covered by other author-created content, which may cause people who use the keyboard to navigate content to become disoriented. This occurs on the following page: Request Apps Screen.
2.5.7 Dragging Movements AA Partially Supports Web: Most functionality that uses a dragging movement can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. The following exception exists: ● Some functionality relies on a dragging movement with no single-pointer, single touch alternative, making it difficult or impossible for persons with motor difficulties and users of assistive technology to perform the gesture on the following page: End User Dashboard Landing Page and left side navigation component found on several pages.
2.5.8 Target Size (Minimum) AA Supports Web: The size of the target for each clickable control is at least 24 by 24 CSS pixels, except where the target size is determined by the user agent; there is a different control with equivalent functionality; the target is inline with text; the presentation of the target is essential to the function or otherwise exempted under the rule; or each control is spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control.
3.1.2 Language of Parts AA Supports Web: The language of each section of content that is different from the default language of the page is correctly identified and can be determined programmatically.
3.2.3 Consistent Navigation AA Supports Web: Navigation patterns that are repeated on web pages are presented in the same relative order each time they appear and do not change order when navigating through the site.
3.2.4 Consistent Identification AA Supports Web: Labels, names, and text alternatives for content that have the same functionality across multiple web pages are consistently identified.
3.3.3 Error Suggestion AA Supports Web: If input errors are automatically detected, suggestions are provided in text for correcting the input in a timely and accessible manner before the data is submitted to the server.
3.3.4 Error Prevention (Legal, Financial, Data) AA Supports Web: If the user can change or delete legal transactions, financial transactions, student exam responses, or data transactions that are unrecoverable or unintentionally modify or delete data, the changes and/or deletions are reversible, verified, or confirmed.
3.3.8 Accessible Authentication (Minimum) AA Supports Web: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless either another method is available that does not rely on a cognitive function test; help is available to assist the user in completing the test; or the test is to recognize objects or identify non-text content the user provided to the Web site.
4.1.3 Status Messages AA Partially Supports Web: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. The following exception exists: ● A status message is not automatically announced by the screen reader, so people who are blind and/or use a screen reader or other assistive technology may completely miss the status message or they may not hear it in a timely fashion. This occurs on the
502.2.1 User Control of Accessibility Features - Not Applicable The website does not have any accessibility features.
502.2.2 No Disruption of Accessibility Features - Not Applicable The website does not have any accessibility features.
502.3.1 Object Information - Partially Supports Web: The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exceptions are noted in: ● 4.1.2 Name, Role, Value
502.3.2 Modification of Object Information - Partially Supports Web: For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions are noted in: ● 4.1.2 Name, Role, Value
502.3.3 Row, Column, and Headers - Supports Web: When a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology.
502.3.4 Values - Partially Supports Web: For most objects that have a current value or have a set or range of values associated with the object, the value(s) is available programmatically, so it can be perceived and conveyed by assistive technology. Exceptions include: ● 4.1.2 Name, Role, Value
502.3.5 Modification of Values - Partially Supports Web: For most objects that allow the user to set or modify its value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include: ● 4.1.2 Name, Role, Value
502.3.6 Label Relationships - Partially Supports Web: For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions are noted in: ● 1.3.1 Info and Relationship ● 4.1.2 Name, Role, Value
502.3.7 Hierarchical Relationships - Partially Supports Web: When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. ● 1.3.1 Info and Relationship
502.3.11 Actions on Objects - Partially Supports Web: For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exceptions include: ● 2.1.1 Keyboard
502.3.14 Event Notification - Partially Supports Web: In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions are noted in: ● 4.1.3 Status Messages
503.4.1 Caption Controls - Not Applicable Web: The website or application does not contain media with an audio component that has closed captions.
503.4.2 Audio Description Controls - Not Applicable Web: The website or application does not contain media with an video component that offers audio descriptions.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion - Not Applicable Web: The website or application is not an authoring tool.
504.2.2 PDF Export - Not Applicable Web: The website or application is not an authoring tool.
4.2.1 Usage without vision - Partially Supports Web: Most functionality is usable without vision. Exceptions are noted in: ● 1.3.1 Info and Relationships ● 1.4.1 Use of Color ● 2.1.1 Keyboard ● 2.4.4 Link Purpose (in context) ● 2.4.6 Headings and Labels ● 4.1.2 Name, Role, Value ● 4.1.3 Status Messages
4.2.2 Usage with limited vision - Partially Supports Web: Most functionality is usable with limited vision. Exceptions are noted in: ● 1.3.1 Info and Relationships ● 1.4.1 Use of Color ● 1.4.4 Resize Text ● 1.4.10 Reflow ● 1.4.11 Non-Text Contrast ● 1.4.13 Content on Hover or Focus ● 2.1.1 Keyboard ● 2.4.4 Link Purpose (in context) ● 2.4.6 Headings and Labels ● 2.4.7 Focus Visible ● 3.3.2 Labels or Instructions ● 4.1.2 Name, Role, Value
4.2.3 Usage without perception of colour - Partially Supports Web: Most functionality is usable without perception of color. Exceptions are noted in: ● 1.4.1 Use of Color ● 1.4.11 Non-Text Contrast
4.2.4 Usage without hearing - Supports Web: All functionality is usable without hearing.
4.2.5 Usage with limited hearing - Supports Web: All functionality is usable with limited hearing.
4.2.6 Usage with no or limited vocal capability - Not Applicable Web: The product does not require the use of speech or other vocal output.
4.2.7 Usage with limited manipulation or strength - Partially Supports Web: Most functionality is usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions are noted in: ● 1.3.5 Identify Input Purpose ● 1.4.13 Content on Hover or Focus ● 2.1.1 Keyboard ● 2.4.4 Link Purpose (in context) ● 2.4.6 Headings and Labels ● 2.4.7 Focus Visible ● 2.5.3 Label in Name ● 4.1.2 Name, Role, Value
4.2.8 Usage with limited reach - Partially Supports Web: Most functionality is usable by people with limited reach. Exceptions are noted in: ● 1.3.5 Identify Input Purpose ● 1.4.13 Content on Hover or Focus ● 2.5.3 Label in Name
4.2.9 Minimize photosensitive seizure triggers - Supports Web: All functionality may be operated in a mode that minimizes the potential for triggering photosensitive seizures.
4.2.10 Usage with limited cognition, language or learning - Partially Supports Web: Most functionality is usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Exceptions are noted in: ● 1.3.1 Info and Relationships ● 1.3.5 Identify Input Purpose ● 1.4.1 Use of Color ● 1.4.10 Non-Text Contrast
4.2.11 Privacy - Not Applicable
5.1.4 Functionality closed to text enlargement - Not Applicable The website does not have closed functionality.
5.1.5 Visual output for auditory information - Not Applicable The website does not have closed functionality.
5.1.7 Access without speech - Not Applicable The website does not have closed functionality.
5.5.1 Means of operation - Not Applicable The product is a web application and has no physical parts.
5.5.2 Operable parts discernibility - Not Applicable The product is a web application and has no physical parts.
5.6.1 Tactile or auditory status - Not Applicable The product is a web application and has no physical locking or toggle controls.
5.6.2 Visual status - Not Applicable The product is a web application and has no physical locking or toggle controls.
7.1.1 Captioning playback - Not Applicable The website does not contain video that has synchronized audio.
7.1.2 Captioning synchronization - Not Applicable The website does not contain video that has synchronized audio.
7.1.3 Preservation of captioning - Not Applicable The website does not contain video that has synchronized audio.
7.1.4 Captions characteristics - Not Applicable The website does not contain video that has synchronized audio.
7.1.5 Spoken subtitles - Not Applicable The website does not contain video that has synchronized audio.
7.2.1 Audio description playback - Not Applicable The website does not contain video that has synchronized audio.
7.2.2 Audio description synchronization - Not Applicable The website does not contain video that has synchronized audio.
7.2.3 Preservation of audio description - Not Applicable The website does not transmit, convert, or record video that has synchronized audio.
12.1.1 Accessibility and compatibility features - Not Evaluated Support Documentation and Services is not included as part of the current scope
12.1.2 Accessible documentation - Not Evaluated Support Documentation and Services is not included as part of the current scope
12.2.2 Information on accessibility and compatibility features - Not Evaluated Support Documentation and Services is not included as part of the current scope
12.2.3 Effective communication - Not Evaluated Support Documentation and Services is not included as part of the current scope
12.2.4 Accessible documentation - Not Evaluated Support Documentation and Services is not included as part of the current scope

Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.