This week we’re looking at the updated Gallery Element and answering some questions, and yes, I’m sorry this is a bit of a long one, but we had a lot to get through!
In the video we also touch on a few upcoming features, namely “Layouts” and “Custom Elements”. It’s well worth watching the Q&A part to get an early scoop on these two big new features we’ll be demoing soon
We love feedback!
Remember, we’re building Elements in the open so we can get feedback as we go. We want to make sure we’re building the product everybody here wants (including us). Share your ideas and feedback in the comments below.
Your feedback is invaluable; together we can build the best web design app on the Mac!
Oh… and I know some of you were asking about setting html tags on Elements to help with accessibility… you can now set the tag in the Advanced area, choose from a pre-defined list or enter your own. Pretty cool, right?
Great job. About accessibility questions, I think the demand also concern tools to help us too build directly in Elements all what we need. For example subtitles, switch-off buttons, « accept cooky button », « dismiss button », « what the button »… For third party tools, a marketplace sorted by category of tools would be a Nice improvement.
We have been thinking about the best way to do this, however, we haven’t yet landed in what the best approach for this would be.
I think we can definitely offer support for ARIA attributes on the top level DOM element inside the Element, however, I think it’s going to be tricky to give everyone access to add ARIA attributes across all the HTML generated by each Element.
We are baking in ARIA attributes to the HTML code generated by each Element, and we will continue to update and refine this as we go.
I hope to add even more in-depth ARIA and accessibility features in the future.
ARIA should primarily be used at the top level; thus, this approach is sensible. ARIA roles should not be added to the “design structure.” If someone does this, they risk obscuring critical information that most screen readers might not locate, or that a person using a screen reader will be unable to navigate efficiently through the content and “read” the headings (roles).
I continue to be so impressed with what you are all coming up with. Now, every day I work in RW, I think about what you’ve previewed so far and how much better/easier the task I am working on will be in Elements. Can’t wait. Keep a’ going, mates!
One suggestion on the gallery, if possible. I’d prefer to be able to sort the order of the images by moving them around in the grid, rather than selecting the image’s name on the inspector. and moving it around there. The visual and tactile feedback of dragging them around the grid would be more productive…and delightful.
Ref the Gallery Element: With there be an Auto Play option, with associated options, time per photo, transition options? Will we be able to add titles, text, links associated with each photo? What options can we change in single image view? Can we set the Galery to only show one image at a time?
Bonsoir,
Deux aspects négatifs : pas de tutoriel en français et un modèle d’abonnement qui ne me convient pas du tout.
Donc, je renonce à utiliser RW.
Désolé
@MrMacvos Hi thank you for the information. I just checked userway but I didn’t find the free widget to test unless it’s after the robot talk requesting my name, adress and so on (I didn’t go further and quit). I use minicookie and verifystacks from Stacks4stacks on my test site, it’s very easy and works very well too.
In the new Elements Gallery is there any plan for a masonry style grid which will nicely display both landscape and portrait orientation images? It’s rare I would have a shoot or gallery which was solely one direction or the other.
button »… For third party tools, a marketplace sorted by category of tools would be a Nice improvement.