Adobe behance android 2025
Accessibility Conformance Report published by Adobe
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.
Level A — 32 criteria
- Supports
- 10
- Partially supports
- 8
- Does not support
- 2
- Not applicable
- 12
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 7
- Partially supports
- 4
- Does not support
- 1
- Not applicable
- 12
- Not evaluated
- 0
Source: View the original report published by Adobe.
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 (100)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Partially Supports | Software: The product provides sufficient text alternatives for most instances of applications. Exceptions include: A decorative image is not hidden from screen readers, so people who are blind and/or use a screen reader will have to navigate through unnecessary and duplicative text. This occurs on the following page: View Thread - Dark Mode. An image does not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image, and if it is an active image, will not understand its function. This occurs on the following p |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | Software: The product does not contain prerecorded audio-only or video-only media. |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | Software: The product does not contain prerecorded synchronized media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | Software: The product does not contain prerecorded video content that would require audio description or a media alternative. |
| 1.3.1 | Info and Relationships | A | Does Not Support | Software: Some structure and relationship information, is provided through element semantics | object information or in text. However, most structure and relationship information are not provided programmatically or in text, such as: Text that visually functions as a heading is not marked up as a heading, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Notifications; User Profile; Report Content; Manage Mood Board; Hire Creatives; My Project; Create new Project Proposal t |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Software: The product presents most content in a meaningful sequence. Exceptions include: Web: The reading and navigation order of most content is logical and intuitive. The following exceptions exist: Screen readers can read content outside the modal dialog, so people who are blind and/or use a screen reader may become disoriented or confused. This occurs on the following page: Incoming Messages. The screen reader skips and does not announce informative static content (text or images), so the intended meaning of that content will be lost or changed for people who are blind and/or use a screen |
| 1.3.3 | Sensory Characteristics | A | Supports | Software: Instructions do not rely solely on sensory characteristics. |
| 1.4.1 | Use of Color | A | Supports | Software: The product does not convey information through color alone. |
| 1.4.2 | Audio Control | A | Not Applicable | Software: The product does not contain audio that plays automatically. |
| 2.1.1 | Keyboard | A | Partially Supports | Software: Most product functionality can be operated through alternative input methods or keyboard interface. Exceptions include: An action cannot be performed when using a screen reader, so people who are blind and others who use a screen reader cannot perform this action. This occurs on the following pages: Save and Publish; Home. An action cannot be performed using only a switch control, so people who use a switch control alone to navigate and operate content cannot perform this action. This occurs on the following pages: Save and Publish; Home. |
| 2.1.2 | No Keyboard Trap | A | Supports | Software: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Not Applicable | Software: The product does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Not Applicable | Software: The product does not include time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Partially Supports | Software: Moving, blinking, scrolling, and auto-updating information can be paused, stopped or hidden by the user. Exceptions include: The user cannot pause, stop, or hide auto-updating content, so people who cannot read text quickly, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content before it updates. This occurs on the following page: Fill out Payment Info. |
| 2.3.1 | Three Flashes or Below Threshold | A | Not Applicable | Software: The tested application does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Not Applicable | Software: This criterion does not apply to non-web software. |
| 2.4.2 | Page Titled | A | Not Applicable | Software: This criterion does not apply to non-web software. |
| 2.4.3 | Focus Order | A | Partially Supports | Software: Most components receive focus in a meaningful order. Exceptions include: Keyboard focus or touch screen swiping goes to an element that is hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs on the following page: Manage Freelancer with Creative. Focus is not confined within a modal when using a switch control, so people who use a switch control to navigate content will be able to navigate outside of the modal, which may cause them to become disoriented. This occurs on the following pages: |
| 2.4.4 | Link Purpose (In Context) | A | Not Applicable | Software: The product does not contain links. |
| 2.5.1 | Pointer Gestures | A | Partially Supports | Software: Most functionality that can be operated with a pointer can be operated with single-point actions. Exceptions include: Functionality (excluding operating system, user agents [like a browser], or assistive technology functions) relies on path-based gestures that require the user to move the finger or pointer in a specific path or sequence, so people with motor disabilities or limited dexterity and people who use certain assistive technology to interact with the page will not be able to operate this functionality. This occurs on the following pages: Lightbox Image. Functionality (exclud |
| 2.5.2 | Pointer Cancellation | A | Supports | Software: Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click. |
| 2.5.3 | Label in Name | A | Partially Supports | Software: In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include: The accessible name of an interactive element (such as a link, button, or form input) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following pages: My Project; Create new Project Proposal to Hire; People. An interactive element (such as a link, button, or form input) does not have an accessible name because its visible label is not programmatically associat |
| 2.5.4 | Motion Actuation | A | Not Applicable | Software: The product does not have functionality operated by device motion or user motion. |
| 3.1.1 | Language of Page | A | Supports | Software: The product relies on the features of the underlying operating system to set and indicate the language of the user interface. |
| 3.2.1 | On Focus | A | Supports | Software: Components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | Supports | Software: Changes of context do not occur automatically on user input. |
| 3.2.6 | Consistent Help | A | Supports | Software: On screens that contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other screen content unless the user changes that order. |
| 3.3.1 | Error Identification | A | Supports | Software: Where input errors are automatically, items in error are identified and error messages are provided as and conveyed to assistive technologies. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Software: Labels are provided for most input fields. Exceptions include: 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: Report Content; My Profile; Create Mood Board. |
| 3.3.7 | Redundant Entry | A | Supports | Software: 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 | Not Applicable | Software: The product is not implemented using markup languages. |
| 4.1.2 | Name, Role, Value | A | Does Not Support | Software: User interface components in most product functions do not provide programmatic name, role, state, or value information. Examples include: A button does not have a programmatic name, so its name (such as "Submit" or "Cancel") 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: Manage Mood Board; My Project; Manage Freelance with Hirer: Thread Info; My Profile. A button does not have a programmatic role, so its role (usually button, but sometimes link or something else) i |
| 1.2.4 | Captions (Live) | AA | Not Applicable | Software: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | Software: The product does not contain prerecorded video content that would require audio description. |
| 1.3.4 | Orientation | AA | Does Not Support | Software: On most screens, the product restricts its view to landscape orientation. When the display orientation is changed (from portrait to landscape or vice versa), the content does not adjust to the new orientation, so people who require a particular display orientation may not be able to access some of that content or functionality. This occurs on the following pages: Landing Page/Sign in; Home; My Profile; Create Project; Save and Publish; Create Mood Board; Manage Mood Board; People; User Profile; My Project; Report Content; Send Message; Notifications; Incoming Messages; View Thread - |
| 1.3.5 | Identify Input Purpose | AA | Not Applicable | Software: The product’s technology does not have support for programmatic identification of input purpose. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Software: Most text meets minimum contrast requirements. Exceptions include: The color contrast ratio between placeholder text in an input and the input's background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the placeholder text. This occurs on the following pages: Create Mood Board; Fill out Payment Info. The color contrast ratio between text and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following pages: View Thread - Dark Mode; Hire Creatives |
| 1.4.4 | Resize text | AA | Not Applicable | Software: This success criterion technically doesn't apply to Native Android application. |
| 1.4.5 | Images of Text | AA | Supports | Software: The product uses text instead of images of text, except for branding elements that are considered essential. |
| 1.4.10 | Reflow | AA | Not Applicable | Software: This success criterion technically doesn't apply to Native Android application. |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Software: Most meaningful non-text content elements have sufficient contrast. Exceptions include: The visual boundary of an interactive element (like a radio 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 in perceiving the boundaries of the interactive element. This occurs on the following pages: Manage Mood Board; Create new Project Proposal to Hire; Send Message; My Profile; Create Mood Board. An icon (or part of the icon required to understand its content) does not have a 3:1 color cont |
| 1.4.12 | Text Spacing | AA | Not Applicable | Software: The product is not implemented using markup languages. |
| 1.4.13 | Content on Hover or Focus | AA | Not Applicable | Software: The product does not contain elements triggered by hover or focus. |
| 2.4.5 | Multiple Ways | AA | Not Applicable | Software: This criterion does not apply to non-web software. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Software: Most headings and labels for form and interactive controls are informative. Exceptions include: A programmatic label for a control or form input field does not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what the control does or what data to enter. This occurs on the following pages: My Project; People. Multiple buttons have identical programmatic labels but different functionality, and there is no programmatic context, so people who are blind and/or use a screen reader will not know or may be confused or misled ab |
| 2.4.7 | Focus Visible | AA | Not Applicable | Software: This criterion does not apply to non-web software. |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Not Applicable | Software: This criterion does not apply to non-web software. |
| 2.5.7 | Dragging Movements | AA | Supports | Software: All 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. |
| 2.5.8 | Target Size (Minimum) | AA | Supports | Software: 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 in line 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 | Software: Changes of language for passages or phrases can be programmatically determined. |
| 3.2.3 | Consistent Navigation | AA | Not Applicable | Software: This criterion does not apply to non-web software. |
| 3.2.4 | Consistent Identification | AA | Not Applicable | Software: This criterion does not apply to non-web software. |
| 3.3.3 | Error Suggestion | AA | Supports | Software: Where input errors are automatically detected suggestions for correction are provided to the user. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Software: The product does not process legal commitments or financial transactions and does not modify user-controllable data. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Supports | Software: 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 website. |
| 4.1.3 | Status Messages | AA | Partially Supports | Software: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. The following exceptions exist: 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 following pages: My Project; Incoming Messages; Create Mood Board; Home; Fill out Payment Info. |
| 502.2.1 | User Control of Accessibility Features | - | Not Applicable | The product is not platform software. |
| 502.2.2 | No Disruption of Accessibility Features | - | Not Applicable | The product is not platform software. |
| 502.3.1 | Object Information | - | Partially Supports | The product exposes the name, role and state or value of most objects to assistive technology. Exceptions include: As noted in 4.1.2 Name, Role, Value |
| 502.3.2 | Modification of Object Information | - | Partially Supports | The product allows assistive technology to modify states and properties of some controls and inputs. Exceptions include: As noted in 4.1.2.a Name, Role, Value |
| 502.3.3 | Row, Column, and Headers | - | Supports | The product exposes the row, column, and headers of table cells to assistive technology. |
| 502.3.4 | Values | - | Partially Supports | For most objects that have a current value or have a set or range of values associated with the object, the value(s) are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include: As noted in 4.1.2 Name, Role, Value |
| 502.3.5 | Modification of Values | - | Partially Supports | For most objects that allow the user to set or modify their value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include: As noted in 4.1.2.a Name, Role, Value |
| 502.3.6 | Label Relationships | - | Partially Supports | The product UI exposes most label relationships to assistive technologies. Exceptions include: As noted in 4.1.2 Name, Role, Value |
| 502.3.7 | Hierarchical Relationships | - | Partially Supports | When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. As noted in 1.3.1 Info and Relationships |
| 502.3.8 | Text | - | Partially Supports | The product exposes most text content and text values to assistive technology. Exceptions include: As noted in 1.3.1 Info and Relationships |
| 502.3.9 | Modification of Text | - | Supports | The product exposes text content and text values to assistive technology. |
| 502.3.10 | List of Actions | - | Partially Supports | Most controls in the product expose programmatic role information and actions which can be taken on objects to assistive technology. Exceptions include: As noted in 4.1.2 Name, Role, Value |
| 502.3.11 | Actions on Objects | - | Partially Supports | The product allows assistive technology to perform all actions on objects. Exceptions include: As noted in 2.1.1 Keyboard |
| 502.3.12 | Focus Cursor | - | Supports | The product allows assistive technology to move focus and modify text selection ranges. |
| 502.3.13 | Modification of Focus Cursor | - | Supports | The product allows assistive technology to move focus and modify text selection ranges. |
| 502.3.14 | Event Notification | - | Partially Supports | The product notifies assistive technology to most user interaction events. Exceptions include: As noted in 4.1.3 Status Messages |
| 503.4.1 | Caption Controls | - | Not Applicable | The product does not display video. |
| 503.4.2 | Audio Description Controls | - | Not Applicable | The product does not display video with synchronized audio that requires captions. |
| 504.2.1 | Preservation of Information Provided for Accessibility in Format Conversion | - | Not Applicable | This product is not an authoring tool. |
| 504.2.2 | PDF Export | - | Not Applicable | This product is not an authoring tool. |
| 4.2.1 | Usage without vision | - | Does Not Support | Software: Most functions of the product are not usable without vision. Examples include: As noted in 1.1.1 Non-Text Content As noted in 1.3.1 Info and Relationships As noted in 1.3.2 Meaningful Sequence As noted in 2.1.1 Keyboard As noted in 2.4.3 Focus Order As noted in 2.4.6 Headings and Labels As noted in 4.1.2 Name, Role, Value As noted in 4.1.3 Status Messages |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Software: Most functionality is usable with limited vision. Exceptions are noted in: As noted in 1.1.1 Non-Text Content As noted in 1.3.1 Info and Relationships As noted in 1.3.2 Meaningful Sequence As noted in 1.3.4 Device Orientation As noted in 1.4.3 Contrast (minimum) As noted in 1.4.11 Non-Text Contrast As noted in 2.1.1 Keyboard As noted in 2.4.3 Focus Order As noted in 2.4.6 Headings and Labels As noted in 3.3.2 Labels or Instructions As noted in 4.1.2 Name, Role, Value |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Software: Most functionality is usable without perception of color. Exceptions are noted in: As noted in 1.4.3 Contrast (minimum) As noted in 1.4.11 Non-Text Contrast |
| 4.2.4 | Usage without hearing | - | Supports | Software: The product is functional for users without hearing. |
| 4.2.5 | Usage with limited hearing | - | Supports | Software: The product is functional for users with limited hearing. |
| 4.2.6 | Usage with no or limited vocal capability | - | Not Applicable | Software: The product does not require the use of speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Software: Users with limited manipulation who use speech recognition or voice control software will not have difficulty navigating to most of the controls. Exceptions include: As noted in 1.3.4 Device Orientation As noted in 2.1.1 Keyboard As noted in 2.4.6 Headings and Labels As noted in 2.4.3 Focus Order As noted in 2.5.1 Pointer Gestures As noted in 2.5.3 Label in Name As noted in 4.1.2 Name, Role, Value |
| 4.2.8 | Usage with limited reach | - | Partially Supports | Software: Users with limited reach and strength will not have difficulty navigating to most of the controls. Exceptions include: As noted in 1.3.4 Device Orientation As noted in 2.5.1 Pointer Gestures As noted in 2.5.3 Label in Name |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Not Applicable | Software: The product does not contain flashing content. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Partially Supports | Software: 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: As noted in 1.1.1 Non-Text Content As noted in 1.3.1 Info and Relationships As noted in 1.3.2 Meaningful Sequence As noted in 1.3.4 Device Orientation As noted in 2.1.1 Keyboard As noted in 2.2.2 Pause, Stop, Hide As noted in 2.4.3 Focus Order As noted in 2.4.6 Headings and Labels As noted in 2.5.1 Pointer Gestures As noted in 2.5 |
| 4.2.11 | Privacy | - | Not Applicable | Software: The product does not ask for or display legal, financial, or personal data. |
| 5.1.4 | Functionality closed to text enlargement | - | Not Applicable | The product does not have closed functionality. |
| 5.1.5 | Visual output for auditory information | - | Not Applicable | The product does not have closed functionality. |
| 5.1.7 | Access without speech | - | Supports | The product does not have closed functionality. |
| 5.5.1 | Means of operation | - | Not Applicable | The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate. |
| 5.5.2 | Operable parts discernibility | - | Partially Supports | The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exceptions include: As noted in 1.3.1 Info and Relationships As noted in 4.1.2 Name, Role, Value. |
| 5.6.1 | Tactile or auditory status | - | Not Applicable | Tactile or auditory status is not included in the product. |
| 5.6.2 | Visual status | - | Not Applicable | Visual status of controls isn’t discernible in the product |
| 11.6.1 | User control of accessibility features | - | Not Applicable | The product is not platform software. |
| 11.6.2 | No disruption of accessibility features | - | Supports | The product does not disrupt platform accessibility features. |
| 11.8.2 | Accessible content creation | - | Not Applicable | The product is not an authoring tool. |
| 11.8.3 | Preservation of accessibility information in transformations | - | Not Applicable | The product is not an authoring tool. |
| 11.8.4 | Repair assistance | - | Not Applicable | The product is not an Authoring Tool. |
| 11.8.5 | Templates | - | Not Applicable | The product is not an Authoring Tool. |
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.
Get told when this changes
This report is dated Not stated. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.