Feature Request

This behavior is extremely confusing for customers who already see a search bar on the page, then having another search bar pop up when they click on the original search bar.

Problem Several common web accessibility issues have been identified across the platform, which can make content difficult or impossible to use for people relying on assistive technologies. These gaps impact overall usability and prevent full compliance with WCAG 2.1 AA standards. Key Accessibility Issues Observed Missing or incorrect ARIA labels and roles Elements lack proper accessible names or use incorrect roles, preventing screen readers from identifying them correctly. Keyboard navigation and focus issues Some elements are not keyboard-accessible, have incorrect tabindex, lack visible focus indicators, or allow focus to move unpredictably. Color contrast problems Insufficient contrast for text, icons, and UI elements makes content difficult to perceive for low-vision users. Missing landmarks and poor semantic structure Pages lack semantic regions (e.g., main, nav, header) or use disorganized heading structures. Incorrect heading hierarchy Heading levels are skipped or used purely for visual styling, breaking screen reader navigation. Form fields without proper labels Inputs, checkboxes, and radio buttons are missing associated labels. Interactive elements without accessible names Icon-only buttons and controls do not convey their purpose to assistive technologies. Modal and dialog focus issues Focus is not trapped within modals, allowing keyboard users to navigate behind dialogs. Hidden elements exposed to assistive technologies Elements hidden visually still receive focus or are read by screen readers. Links with unclear or missing text Links do not clearly describe their destination or behavior (e.g., opening in a new tab). Hover-only or mouse-only interactions Content and controls visible only on hover are inaccessible to keyboard, touch, or screen reader users. Missing or incorrect image alternative text Images lack meaningful alt text or use inaccurate descriptions. Embedded PDFs and media not accessible Inline PDFs are not readable by screen readers such as NVDA. Misuse or overuse of ARIA ARIA attributes are applied unnecessarily or incorrectly, overriding native accessibility behavior.

Our customer has requested an option to track the daily usage of PDF exports (both article and category downloads) on the Knowledge Base site. This visibility into the number of downloads performed each day would help in monitoring feature usage and understanding user engagement.

We would like the option for users with team accounts to be able to follow articles/categories on private workspaces. We have an internal knowledge base and team members should also be able to follow articles/categories on the site so they can receive notifications when something has been added.

It appears that any image added to an article will be configured so that when the user hovers their mouse over the image, the cursor becomes a magnifying glass and they can click to zoom in on it. This is fine most of the time, but I wish I could disable this for certain images. For example, I have an article with tabs, and I want to include a little icon in the tab label. I edited the HTML for the tab and added an img tag, and it displays it, but when I hover over the icon in the reader interface, I get the zoom option. If a reader were to click on this icon, then instead of selecting the tab, it would just zoom the icon. There could be other cases where I don't want the zoom option for an image: e.g. if I use an image in a button or a link, or whenever the image is a little icon/decoration, and there's just isn't a need for the user to zoom it.

Somebody changed our KB site theme to dark mode only, and I had to change it back to light+dark mode. None of these actions appeared in the Audit log, even 'Knowledge Base Site Settings' is enabled in the audit log config.

Requesting the addition of a sorting feature that allows users to organize categories and articles on the Knowledge Base site. The desired functionality includes the ability to sort items alphabetically -> Provide an option to sort categories (e.g., alphabetically). -> Provide an option to sort articles within categories in a similar manner. -> Sorting behavior should apply on the customer-facing KB site

Currently, for private and mixed projects we are adding a SAS token for the media files. After the SAS token expiry if we try to access the media files we are getting an error message as attached. It would be great if we display the message "Refresh the article page and then access the media file" to provide more clarity for the end users.

It would be great to have an export of the entire knowledgebase list of articles with some added data. Firstly since the workflows section isn't good enough, and to have an organized list anyway to use with other parts of the company

When clicking on a specific category, all opened categories should be collapsed and the clicked category should be expanded with articles.