Adobe Behance 2024
Accessibility Conformance Report published by Adobe
Partial extraction. We read 30 of 31 Level A and 20 of 24 Level AA criteria from this document (91% coverage). The remainder are missing from our extraction, not necessarily from Adobe's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.
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 — 30 criteria
- Supports
- 8
- Partially supports
- 12
- Does not support
- 3
- Not applicable
- 7
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 7
- Partially supports
- 8
- Does not support
- 3
- Not applicable
- 2
- 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 (68)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Partially Supports | Web: The product provides sufficient text alternatives for most instances of website. 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: Help Center. An informative 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. This occurs on the following pages: Connect with PayPal or Stripe; Download an Asset; Help Center; Send |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Does Not Support | Web : The product does not provide audio description or transcripts for most video-only media content in the website. Example includes: Some video files have no text transcript or audio description track, so the visual content presented by those videos is not available to people who are blind or have low vision. This occurs on the following pages: Vimeo Video Player; JS Player. |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded synchronized media content that would require captions. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded video content that would require audio description or a media alternative. |
| 1.2.4 | Captions (Live) | AA | Not Applicable | Web: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | Web: The product does not contain prerecorded video content that would require audio description. |
| 1.3.1 | Info and Relationships | A | Does Not Support | Web : Some structure and relationship information are provided through semantics | object information or in text. However, most structure and relationship information are not provided programmatically or in text. Examples include: A set of checkboxes is not programmatically grouped, so the group label for the set of checkboxes will not be conveyed to people who are blind and/or use a screen reader and they will not understand the purpose of the individual checkboxes. This occurs on the following page: Create a Freelance Project. A set of radio buttons is not programmatically grouped, so the gr |
| 1.3.2 | Meaningful sequence | A | Partially Supports | Web: The product presents most content in a meaningful sequence. Exceptions include: Some visually hidden content is announced by a screen reader, so people who are blind and/or use a screen reader may be misled or confused when hearing content that is not intended to be part of the reading order on the page. This occurs on the following page: Create a Project. The screen reader skips and does not announce informative static content (text or images), so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following |
| 1.3.3 | Sensory Characteristics | A | Supports | Web: Instructions do not rely solely on sensory characteristics. |
| 1.3.4 | Orientation (WCAG 2.1) | AA | Supports | Web: Content does not restrict its view and operation to a single display orientation. |
| 1.3.5 | Identify Input Purpose (WCAG 2.1) | AA | Partially Supports | Web: Most input fields in the product do not collect information about the user. However, some input fields collect information about the user and do not programmatically convey their purpose. Example includes: The programmatic purpose provided for an input element (like a text input field) is not accurate, so information automatically suggested by the browser or assistive technology to fill in the input will be incorrect. This occurs on the following page: Download an Asset. |
| 1.4.1 | Use of Color | A | Partially Supports | Web: Most functions of the product do not convey information through color alone. Exceptions include: Color is the only visual method used to identify a link, and a link text's contrast ratio with the color of the surrounding text is less than 3:1, so people who are colorblind or have low vision may not be able to identify the link. This occurs on the following pages: Download an Asset; Help Article/Accessibility Features. 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 colorb |
| 1.4.2 | Audio Control | A | Not Applicable | Web: The product does not contain audio that plays automatically. |
| 1.4.3 | Contrast (Minimum) | AA | Does Not Support | Web : Most text does not meet minimum contrast requirements. Examples include: 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: Your Stats tab; Inbox Page (Employer); Search for a Project; Send & Download Files in Conversation; Work tab; Assets Tab; Connect with PayPal or Stripe; Help Center; Manage Freelance Project & Payments; Receive a Freelance Request - Inbox Employee; Request Payment - connect with Stripe/PayPal; Send Payment to Freelancer |
| 1.4.4 | Resize text | AA | Partially Supports | Web : The product allows browser zoom to resize text up to 200 percent without loss of content or functionality. Exceptions include: 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 may not have access to that content. This occurs on the following pages: Hire Freelancer - Inbox Employer; Receive a Freelance Request - Inbox Employee; Request a Payment; Request Payment - connect with Stripe/PayPal; Search for a Freelancer; View Freelance Project Details; Search for a Service. Functionality is lost when the pa |
| 1.4.5 | Images of Text | AA | Supports | Web: The product uses text instead of images of text, except for branding elements that are considered essential. |
| 1.4.10 | Reflow | AA | Does Not Support | Web: At the required width of 320 CSS pixels, most functions of the product do not meet this criterion. [Loss of information or functionality occurs] and [content which does not require two-dimensional layout for meaning relies on scrolling in two dimensions. Examples include: When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or fun |
| 1.4.11 | Non-text Contrast | AA | Does Not Support | Web: Most meaningful non-text content elements do not have sufficient contrast. Examples 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 perceiving the boundaries of the interactive element. This occurs on the following pages: Account Settings Page; Create a Freelance Project; Inbox Page (Employer); Search for a Freelancer; Search for a Project; Connect with PayPal or Stripe; Hire Freelancer - Inbox Employer; JS Player; Pr |
| 1.4.12 | Text Spacing | AA | Partially Supports | Web: Most functions of the product support the required text style properties without loss of content or functionality. Exception includes: When text spacing is adjusted to help people with vision, reading and cognitive disabilities, some content cannot be seen because it is cut off. This occurs on the following page: Search for an Asset. |
| 1.4.13 | Content on Hover or Focus | AA | Partially Supports | Web: In most cases when additional content is triggered by mouse pointer hover or keyboard focus, that additional content can be dismissed and hovered over, and the content persists until the user dismisses it. Exceptions include: 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: Inbox Page (Employer); Search for a Freelancer; Create a Project; Vimeo Video Player; Hire Freelancer - Inbox Employer; Request a Payment; Receive a |
| 2.1.1 | Keyboard | A | Partially Supports | Web: Most product functionality can be operated through a keyboard interface. Exceptions include: 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 pages: Inbox Page (Employer); Search for a Freelancer; Search for a Project; Search for an Asset; Work tab; Your Stats tab; Create a Project; Download; Free Asset; Help Center; Hire Freelancer - Inbox Employer; Search for a Service; Send & Download Files in Conversation; View Freelance Project Details; View Service & Inq |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts (WCAG 2.1) | A | Not Applicable | Web: The product does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Not Applicable | Web: The product does not include time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Partially Supports | Web: Moving, blinking, scrolling, and auto-updating information can be paused, stopped or hidden by the user. Exception includes: The user cannot pause, stop, or hide content that automatically moves, blinks, or scrolls, 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. This occurs on the following pages: Services tab; Work tab. |
| 2.3.1 | Three Flashes or Below Threshold | A | Not Applicable | Web: The product does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Partially Supports | Web: On most pages, a method is provided to skip navigation and other page elements that are repeated across web pages. Exception includes: The skip link to bypass repeated content is broken or does not function correctly, so people who use the keyboard to navigate content or use a screen reader must navigate through repeated content on every page. This occurs on the following page: Primary Header. |
| 2.4.2 | Page Titled | A | Partially Supports | Web: The titles of pages describe their purpose. Exception includes: The page does not have a programmatic title, so people who use a screen reader will not be able to identify the purpose of the page without reading the page content. This occurs on the following page: Account Settings Page. |
| 2.4.3 | Focus Order | A | Partially Supports | Web: 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: Search for a Project. The focus order is not logical and presents content in an order that misrepresents its meaning or operability, so people who use a keyboard, switch control, or other assistive technology to navigate content may become disoriented or confused. This occurs on the f |
| 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. Exception includes: Multiple links have identical link text but different destinations, and the context provided by the content that immediately surrounds each link does not provide any clarification, so people who are blind and/or use a screen reader will not know or may be confused about where each link goes. This occurs on the following pages: View Freelance Project Details; Primary Header; Work tab. |
| 2.4.5 | Multiple Ways | AA | Supports | Web: Users can locate web pages in the product through Multiple ways. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Web: Most of the headings and labels are descriptive. 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: Your Stats tab; Create a Freelance Project; Inbox Page (Employer); Search for a Freelancer; Search for a Project; Connect with PayPal or Stripe; Help Center; Search for a Service; Settings; View Service & Inquire; Search for an Asset - Responsive Tablet and Mobile Vi |
| 2.4.7 | Focus Visible | AA | Partially Supports | Web: Most focusable elements have a visible keyboard focus indicator. Exception includes: 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 pages: Primary Footer; Secondary Footer; Assets Tab; Inbox Page (Employer). |
| 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: 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 | Web: 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: Inbox Page (Employer); Create a Freelance Project; Search for a Freelancer; Search for a Project; Send & Download Files in Conversation; Work tab; Your Stats tab; Assets Tab; Connect with PayPal or Stripe; Create a P |
| 2.5.4 | Motion Actuation | A | Not Applicable | Web: The product does not have functionality operated by device motion or user motion. |
| 3.1.1 | Language of Page | A | Supports | Web: The language is programmatically determinable within the product. |
| 3.1.2 | Language of Parts | AA | Partially Supports | Web: Changes of language for passages or phrases can be programmatically determined most of the pages. Exception includes: A portion of content on a page that is in a different language from the rest of the content on the page is not programmatically assigned the language for that portion of content, so screen readers may mispronounce that part of the content. This occurs on the following page: Search for a Project. |
| 3.2.1 | On Focus | A | Supports | Web: Components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | Supports | Web: Changes of context do not occur automatically on user input. |
| 3.2.3 | Consistent Navigation | AA | Supports | Web: When navigational mechanisms are repeated in the product, they occur in a consistent relative order. |
| 3.2.4 | Consistent Identification | AA | Supports | Web: Components with the same functionality are identified consistently. |
| 3.3.1 | Error Identification | A | Partially Supports | Web: Most input errors are identified and described to the users in text. Exception includes: A form field with an error is not identified in the text error message or a text alternative for an image, and the error message with the field name is not programmatically associated with the form field (so it is announced when a screen reader user navigates to the field), so people who are blind and/or use a screen reader will not be able to identify in which form field the error occurred. This occurs on the following page: Settings. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Web: 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: Create a Freelance Project; Search for a Project; Download an Asset; Help Center. The label for a form field is missing, so the field's purpose is not clear. This occurs on the following pages: Primary Footer; Secondary Footer. |
| 3.3.3 | Error Suggestion | AA | Supports | Web: Where input errors are automatically detected, suggestions for correction are provided to the user. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Web: The product does not process legal commitments or financial transactions. |
| 4.1.1 | Parsing | A | Supports | Web: Elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique. |
| 4.1.2 | Name, Role, Value | A | Does Not Support | Web: User interface components in most product functions do not provide programmatic [name, role, state, or value] information. Examples include: An element has an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property 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: Send & Download Files in Conversation; Work tab; Your Stats tab; View Fr |
| 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. Exception includes: 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: Create a Freelance Project; Inbox Page (Employer); Request a Payment; Search for a Freelancer; Search for a Project; View Freelance Project Details; Connect with PayPal or S |
| 4.2.7 | Usage with limited manipulation or strength (EU) | - | Does Not Support | Web: Most functions of the product are not usable by people with limited manipulation and/or requires manipulation, simultaneous action, or hand strength. Examples include: 1.3.5 Identify Input Purpose 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.1 Bypass Blocks 2.4.2 Page Titled 2.4.3 Focus Order 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 (EU) | - | Partially Supports | Web: Most functions of the product are usable by people with limited reach. Exceptions include: 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 (EU only) | - | Not Applicable | Web: The product does not contain flashing content. |
| 4.2.11 | Privacy (EU only) | - | Not Applicable | Web: The product does not ask for or display legal, financial, or personal data. |
| 502.2.1 | User Control of Accessibility Features | - | Not Applicable | The product is not platform software |
| 502.2.2 | No Disruption of Accessibility Features | - | Supports | The product does not disrupt most platform accessibility features. |
| 503.4.1 | Caption Controls | - | Not Applicable | The product does not display video with synchronized audio that requires captions. |
| 503.4.2 | Audio Description Controls | - | Does Not Support | The product does not provide user controls for audio descriptions. Example includes: A multimedia player cannot play an audio description track, so people who are blind or have low vision are not able to access the information in the video portion of the multimedia described in the audio track. This occurs on the following pages: Vimeo Video Player; JS Player. |
| 504.2.1 | Preservation of Information Provided for Accessibility in Format Conversion | - | Not Applicable | The product is not an authoring tool. |
| 504.2.2 | PDF Export | - | Not Applicable | The product is not an authoring tool. |
| 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. Exception includes: 4.1.2 Name, Role, Value. |
| 7.1.1 | Captioning playback | - | Not Applicable | The product does not require a caption playback function because no meaningful audio information was observed in the video. |
| 7.1.2 | Captioning Synchronization | - | Not Applicable | The product does not display closed captions. |
| 7.1.3 | Preservation of captioning | - | Not Applicable | The product does not transmit, convert, or record video with synchronized audio. |
| 7.2.1 | Audio description playback | - | Does Not Support | The product does not provide a mechanism to select and play closed audio description. Example includes: A multimedia player cannot play an audio description track, so people who are blind or have low vision are not able to access the information in the video portion of the multimedia described in the audio track. This occurs on the following pages: Vimeo Video Player; JS Player. |
| 7.2.2 | Audio description synchronization | - | Not Applicable | The product does have a mechanism to play closed audio description. |
| 7.2.3 | Preservation of audio description | - | Not Applicable | The product does not transmit, convert, or record video with synchronized audio |
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.