Search

36 pm Hello, There is an easier way. A keyboard layout for other language than English can be set on Linux to input characters of that language directly in the <oXygen/> editor panel. On Fedora with KDE go to KMenu -> Control Center -> Regional and Accessibility -> Keyboard Layout, select Enable

36 pm Hello, There is an easier way. A keyboard layout for other language than English can be set on Linux to input characters of that language directly in the <oXygen/> editor panel. On Fedora with KDE go to KMenu -> Control Center -> Regional and Accessibility -> Keyboard Layout, select Enable

36 pm Hello, There is an easier way. A keyboard layout for other language than English can be set on Linux to input characters of that language directly in the <oXygen/> editor panel. On Fedora with KDE go to KMenu -> Control Center -> Regional and Accessibility -> Keyboard Layout, select Enable

Center -> Regional and Accessibility -> Keyboard Layout, select Enable Keyboard Layouts, select Greek from the list of available layouts and add it to the list of current layouts. A small icon appears in the taskbar near the clock, click on it to switch from one keyboard layout to another and then you

And I think of it as a fairly standard UI design practice to have functions available in the menus...And I think it can help with accessibility to be able to use alt keys to get to functions. Top Post Reply Print view Display: All posts 1 day 7 days 2 weeks 1 month 3 months 6 months 1 year Sort by

reason. If you implement this feature, it would be nice if the Oxygen WebHelp UI somehow made these keyboard shortcuts known (or "discoverable") to the user, so that authors don't feel the need to describe those shortcuts in a bespoke "Accessibility" documentation topic. Top Costin Posts: 846 Joined

reason. If you implement this feature, it would be nice if the Oxygen WebHelp UI somehow made these keyboard shortcuts known (or "discoverable") to the user, so that authors don't feel the need to describe those shortcuts in a bespoke "Accessibility" documentation topic. Top Costin Posts: 846 Joined

"navheader_label" and "navheader_separator" strings to the topic titles, which we don't want to see. We just want the topic title to appear. I cannot remove those strings, because that would break the aria-label code for accessibility purposes. Is there a way to only show the topic titles next to the arrows

Topics Posts Last post Feature Request Topics: 6 6 Topics 35 Posts Last post Re: XML Usage Decreasing JSON… by teo View the latest post Tue Feb 18, 2020 3:55 pm Common Problems Topics: 22 22 Topics 82 Posts Last post Re: Set "Enable Accessibility… by cristi_talau View the latest post Thu Jul 16, 2020 5

paulkhillier Fri Jan 22, 2021 5:37 pm Trademark in TOC Last post by cosmin_andrei « Fri Jan 22, 2021 1:05 pm Replies: 5 by syed » Wed Aug 05, 2020 10:26 am 5 Replies 2715 Views Last post by cosmin_andrei Fri Jan 22, 2021 1:05 pm Potential Accessibility Issues in Webhelp Responsive Output Last post by alin