371 results found

1. Integration of alt text for visual elements in prototypes

   Blind and severely visually impaired people are largely dependent on the use of screen readers to receive digital content.

   For user testing, the integration of so-called alternative texts plays an important role.
   Adobe XD offers voice playback as an interaction element, but the input of an alternative text, which is analyzed by the screen reader, is not possible from the current point of view.
   I would like to draw attention to this problem, because
   A) due to the legal situation in Europe, private companies are obliged to design their applications accessible until 2025. Here, feedback from the target group, including blind and visually impaired people, is really important.
   B) the prototypes should be accessible for all user groups.

   Blind and severely visually impaired people are largely dependent on the use of screen readers to receive digital content.

   For user testing, the integration of so-called alternative texts plays an important role.
   Adobe XD offers voice playback as an interaction element, but the input of an alternative text, which is analyzed by the screen reader, is not possible from the current point of view.
   I would like to draw attention to this problem, because
   A) due to the legal situation in Europe, private companies are obliged to design their applications accessible until 2025. Here, feedback from the target group, including… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

2. Scale in/scale out animation without auto-animate

   allow to put scale in/ Scale out animations on Adobe XD without having to use Auto-animate since it can get confused sometimes

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

3. Publish prototype in wireframe mode

   Even if you have a design system running, sometimes you need to work on new features in a prototype. So you need to have mixed some components finished with others unfinished. I would love to work directly on the prototype and, while the "design" of new components are not finished, publish all the prototype on "wireframe or grey mode" to avoid distractions of stakeholders. Probably is easy to render only borders and texts of every objects, keeping all the functionalities.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  02 : Prototype mode  ·  Edit…  ·  Delete…  ·  Admin →

4. Enable audio playback on timed transitions

   Allow for audio playback to be enabled for timed transitions as these can only be inputted for tap interactions

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

5. Change Hover state default parameters

   When I create a new Hover State, by default adobe XD create a new hover interaction with default parameters :
   - Auto Animate
   - Ease-Out
   - 0,3 seconds

   I never use this config. I always need this config for hover:
   - Type : Transition
   - Animation : None

   It's very annoying because I have to reset all my Hover interaction every time. Is there a way of modifying these settings by default ? Every time I create an Hover state, i would like to have a transition without any animation by default.

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

6. Smarter text animation to animate text by letter, word, line or paragraph.

   I'd like to see an option in Prototype mode where i can choose to animate text a little easier. There will be new options where you can choose which text animation you want and also which interval time that should be used

   The text animations i'd like to see in that dropdown menu are:

   • As whole (default)
     This is how it is now.

   • Per paragraph
     Animate the text by paragraph.

   • Per line
     Animate the text by line.

   • Per word
     Animate the text by word.

   • Per letter
     Animate the text by letter.

   For each option could be considered to have an option for ignoring whitespaces.

   Having such option gives tons of new possibilities to animate your content. Like the highly requested text input simulation. With the option to animate by letter you can create that typing animation easily. Or fade in text by line to have a smooth transition for your text blocks.

   I believe this is something that Adobe XD needs to have as it gives you more control over prototyping text effects.

   I'd like to see an option in Prototype mode where i can choose to animate text a little easier. There will be new options where you can choose which text animation you want and also which interval time that should be used

   The text animations i'd like to see in that dropdown menu are:

   • As whole (default)
     This is how it is now.

   • Per paragraph
     Animate the text by paragraph.

   • Per line
     Animate the text by line.

   • Per word
     Animate the text by word.

   • Per letter
     Animate the text by letter.

   For each option could be considered to have an… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

7. Persist underlying art-board after subsequent transitions following 'overlay'

   TL;DR: Art boards with transparent fills should continue to overlay the previous art board's underlaying board.

   I can think of many use cases that have required a significantly higher number of art boards, assets and hours to accomplish than should be required. The feature I am requesting would address all of these issues in a simple and intuitive way.

   Let's say I have art boards A, B, and C.

   'A' displays my application, with 100s of assets, text, components, etc.
   'B' displays a modal over the application in state 1, the default state.
   'C' displays state 2 of the modal, which has been dynamically expanded to show a number of additional fields as the user fills out the modal.

   Behind the modal (out of focus), there are 100s of elements that are on screen but remain exactly the same for all three boards since the modal is the only interactive element.

   I am able to use an overlay transition between A and B no problem. So I design 'A' using a transparent art board to avoid having to duplicate the hundreds of items that remain constant between A and B.

   Now here is the issue. I want to use an auto-animation between B and C to show additional fields in the modal. But I can't! Because doing so would make the underlying art board (A) that B is overlaying disappear. After the animation C will be displayed over a black background.

   The workaround I use is to avoid the overlay transition entirely, and include a carbon copy of the contents of art board A in both B and C. This not only significantly increases the number of elements in the file but also makes any changes to art board A significantly more time consuming.

   But wait! It gets worse. Let's say the modal isn't only accessible via screen A. Let's say there are screens A, D and E where the modal can be opened. Well now in order to have two different states of the modal, you need to recreate both B and C over top of A D and E. And just that quickly we are up to 6 art boards just for a modal that transitions between two states.

   Here is what I am proposing:
   Option 1 (Fewer art boards, fewer assets): Once an overlay transition is used, the underlying art board should persist as the 'background' for subsequent transitions until a transition is made to a non-transparent art board.

   Option 2 (Same number of art boards but at least fewer assets): Allow an art board to be re-used as a 'background' element, so that the contents don't need to be repeated in other art boards.

   TL;DR: Art boards with transparent fills should continue to overlay the previous art board's underlaying board.

   I can think of many use cases that have required a significantly higher number of art boards, assets and hours to accomplish than should be required. The feature I am requesting would address all of these issues in a simple and intuitive way.

   Let's say I have art boards A, B, and C.

   'A' displays my application, with 100s of assets, text, components, etc.
   'B' displays a modal over the application in state 1, the default state.
   'C' displays state 2 of the modal,… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  02 : Prototype mode  ·  Edit…  ·  Delete…  ·  Admin →

8. Allow a Group of Artboards to be used as a Multi-State Component

   Right now, the creation of a carousel or 'choose one item' list requires you to have a different COPY of your artboard for each possible iteration of that carousel/list. If you want to showcase 3 multi-artboard interactions in a mockup (if each carousel has 5 images, you need to copy your artboar 125 times, just to show that, without any other bells and whistles).
   In contrast, if you could have an artboard group that is JUST the possible states for 1 carousel, then group those artboards into a single component. Then you only need 1 main artboard (for your app/webpage) and 15 mini-boards (3 components, each with five possible states).
   This single feature can VASTLY broaden the utility of Adobe XD. Most of the buttons and such required for this are already there, so it wouldn't complicate the UI much. Even the simple option to swap a component with another component from your pasteboard on Tap or Dra, etc, would be a massive relief.

   Right now, the creation of a carousel or 'choose one item' list requires you to have a different COPY of your artboard for each possible iteration of that carousel/list. If you want to showcase 3 multi-artboard interactions in a mockup (if each carousel has 5 images, you need to copy your artboar 125 times, just to show that, without any other bells and whistles).
   In contrast, if you could have an artboard group that is JUST the possible states for 1 carousel, then group those artboards into a single component. Then you only need 1 main artboard (for your app/webpage)… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

9. Tap on hover state should transition to another artboard

   Please remove, or add option to remove, the animation from Hover state back to default when a Tap trigger is attached to a component that is in Hover state.

   This animation is unnecessary when navigating to another artboard and can cause all manner of irritation if the artboard to which one is navigating shows the component intentionally in hover state.

   Example:
   - An image control has a hover state
   - When in that hover state, the user can click to cause an action.
   - The action is simulated by a navigation to another artboard
   - In the destination artboard, we would show that image control in its hover state as an indicator that it is currently active.

   As XD is currently implemented, clicking on that control will cause it to animate from hover state to default state (as it leave one artboard) and back to the hover state as designed in the destination artboard.
   It is currently impossible to animate a smooth transition between artboards leaving the component in hover state.

   Please remove, or add option to remove, the animation from Hover state back to default when a Tap trigger is attached to a component that is in Hover state.

   This animation is unnecessary when navigating to another artboard and can cause all manner of irritation if the artboard to which one is navigating shows the component intentionally in hover state.

   Example:
   - An image control has a hover state
   - When in that hover state, the user can click to cause an action.
   - The action is simulated by a navigation to another artboard
   - In the destination artboard, we… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

10. While navigate to a new artboard allow user to choose component state

    while building a prototype when connecting two artboards allow the option to choose the state for the components on the destination artboard

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

11. Honor layers (z-order) in prototype interaction

    We need to be able to set prototype interactions based on visible content.
    Currently, if a larger object [a] is covered (via z-order) by a smaller object [b], a prototype interaction assigned to [a] will be active when the cursor hovers over [b]. This is not the typical expected behavior with regard to click or mouse over events.

    Example:
    In the attached image, there is a modal dialog [b].
    We would want to assign Tap interactions objects within the dialog.
    We would also want to assign a Tap event to the area outside the dialog. In this case, tapping outside the dialog should close the dialog.

    However, because the Tap interaction assignment on the region beneath the dialog [a] will fire regardless of the fact that the dialog [b] is an object group placed above the background region [a] in z-order, the desired effect cannot be achieved.

    We've even attempted to create an exclusion mask on the region [a] beneath the dialog [b] so that the area covered by the dialog would not be considered viable. This did not work either. The entire exclusion group is considered active for the Tap event.

    If, however, the layers (z-order) of objects was taken into consideration, then only the visible portions of the region beneath the dialog would be eligible to activate the associated Tap interaction.

    We need to be able to set prototype interactions based on visible content.
    Currently, if a larger object [a] is covered (via z-order) by a smaller object [b], a prototype interaction assigned to [a] will be active when the cursor hovers over [b]. This is not the typical expected behavior with regard to click or mouse over events.

    Example:
    In the attached image, there is a modal dialog [b].
    We would want to assign Tap interactions objects within the dialog.
    We would also want to assign a Tap event to the area outside the dialog. In this case, tapping outside… more

    •  

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

12. Ability to update selected artboards rather the updating the entire prototype

    most of my project are huge and heavy, not less than 200 artboard

    I would like the ability to update certain or specific artboards on the link rather than uploading all the link again

    that's time-consuming.

    plus some times I would like to share specific changes done with my manager while other changes are still under going-which I don't want my manager to see yet

    9 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

13. Tap Release Interaction Trigger

    I want the possibility to change the state of a component on tap release. This will allow making animations of buttons that don't change the artboard on tap.

    E.g. for IoT applications, I want to give the users the feeling, that the pressed a button.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

14. Anchors within scroll groups and components

    We can add anchor points to our screen to easily move to certain points. But when we have a very long scroll section, like a drop-down menu with around 200 options, it is very difficult to keep scrolling throughout the options.

    If we can make options inside a scroll group which is already in a component into anchor points then we easily can access the options.

    Now, for example, I was developing a dropdown menu to select your country. But it has around 200 options. I Sorted them in alphabetical order and added a new horizontal line with A - Z alphabets.

    Now if a person wants to go and select India, he/she doesn't have to scroll all the way to "I". Instead, he/she can simply just click on "I" which we added on top to directly scroll to the India or from where "I" starts in the list.

    But for now, we can't be able to select an element from inside the component for scroll destination.

    We can add anchor points to our screen to easily move to certain points. But when we have a very long scroll section, like a drop-down menu with around 200 options, it is very difficult to keep scrolling throughout the options.

    If we can make options inside a scroll group which is already in a component into anchor points then we easily can access the options.

    Now, for example, I was developing a dropdown menu to select your country. But it has around 200 options. I Sorted them in alphabetical order and added a new horizontal line with A -… more

    •  

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

15. Define different actions for subsequent interaction triggers

    Give the possibility to add the same trigger in prototyping. For example, the interraction of a dropdown button; you can make a list appear with the tap trigger and another tap trigger to listen to the sound.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

16. Add multiple time triggers to an artboard.

    For example one time trigger would play a sound after 0.6 seconds, and another time trigger would move to the next artboard after 2 seconds.

    11 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

17. Able to change and design the cursor

    Would be great to be able to change the cursors design to fit to designed website.

    •  

    •  

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

18. Preserve Component States

    Just as you can preserve the scroll position between artboards, I need a the option to preserve component states between artboards if that component exists on both artboards.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  02 : Prototype mode  ·  Edit…  ·  Delete…  ·  Admin →

19. Allow nested components to trigger parent component states

    Currently, a nested components cannot trigger a component state. You would have to ungroup it, so that it is no longer a component in order to be able to target a component state.

    eg. I have a card component which has multiple states. Inside the default state, I have a button (which is a component). When I select to Tap that button component, I do not have the option to target the other states of that component. It only displays artboards as potential targets.

    76 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    10 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →

20. Drag (simulated text selection) within vertical scroll areas

    I want to prototype a PDF or other document viewer allowing the user to scroll through a 2-3 page document (images arranged like pages) and then direct them to select the target text on the document.

    Telling a user to select the text, they naturally want to drag to highlight and select the text as they would in a text editor or viewer.

    I want to simulate that so I tried putting a small box with opacity set to 0% just to the left of the text. Then I copied the object for naming and start position and put it on the second artboard, followed by adjusting the object to cover the intended text and set opacity to 50% and some color. On both artboards, these objects are contained in the scrollable area so the user can still scroll the document freely. But when the drag trigger is selected with auto animate between the artboards, dragging in the PREVIEW results in either no animation or jerky/flashing artboards that don't simulate the text selection. I could be doing something wrong and even put a support ticket in thinking it was a bug.

    I believe that there is a bug or lack of polish on the feature to allow dragging while inside a scrollable area. That and if the artboards are nearly identical, passing the preserve scrolling of the scrollable area from one to the other doesn't seem to be a thing.

    I want to prototype a PDF or other document viewer allowing the user to scroll through a 2-3 page document (images arranged like pages) and then direct them to select the target text on the document.

    Telling a user to select the text, they naturally want to drag to highlight and select the text as they would in a text editor or viewer.

    I want to simulate that so I tried putting a small box with opacity set to 0% just to the left of the text. Then I copied the object for naming and start position and put it… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  02 : Prototype mode  ·  Delete…  ·  Admin →