Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreKeep your Zoom app up to date to access the latest features.
Download Center Download the Zoom appDownload hi-res images and animations to elevate your next Zoom meeting.
Browse Backgrounds Zoom Virtual BackgroundsEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI CompanionUser groups are unique spaces where community members can collaborate, network, and exchange knowledge on similar interests and expertise.
Help & Resources is your place to discover helpful Zoom support resources, browse Zoom Community how-to documentation, and stay updated on community announcements.
The Events page is your destination for upcoming webinars, platform training sessions, targeted user events, and more. Stay updated on opportunities to enhance your skills and connect with fellow Zoom users.
The community will still be accessible, however, the creation of any new discussions or replies will be temporarily unavailable. We appreciate your patience during this time.
2025-10-31 04:31 PM
Zoom now allows for accessible semantic links within the chat which I prefer to use for accessibility reasons - this means I type a sensible title and use the link function to convert it to a semantic link.
However, if saving the zoom chat, the export is a text file only and the url is not parsed or included, only the title. This means that if I wanted to include the chat history and any links as a follow up with a recording for participants who missed the meeting, the chat is only saving part of the information.
Now that I have realised this, I can do the manual double handling of including both the semantic link followed by the full url for reference but it would be better if Zoom could do this work in order to be more accessible.
Does anyone know where I can put in a feature request around this improvement or raise a complaint or bug?
Does anyone have any further tips for getting around these sorts of accessibility limitations within the platform/software?