Tabs and Accordions in Knowledge Article

wow-on-now
Giga Guru

Hi Everyone,

 

I am curious to see if anyone has tried to successfully have tabs and accordions in a knowledge article which is easy to maintain by authors that are not HTML experts. 

 

22 REPLIES 22

John_Wilkes
Tera Expert

I would avoid tabs and accordions. They can be a nightmare for anyone using accessibility software. My view is if your article needs to be broken down like this it may be too big. Might be better to break it down into different articles use the title field as you would to name the tabs or headings in the accordion to make it clear before a user opens the article. will become much easier for your readers to follow in my experience and much easier for those creating the articles as any type of html code however simple it is will be seen as a whole different language to some of your knowledge authors.

These have a time and place, like if you have the same issue, but need to include directions for multiple browsers, then its nice for drop downs so the article doesn't appear long.   However, I have found them to be almost unworkable in the HTML editor (TinyMCE) because it keeps moving the command tags around unless you get things in whatever particular order they have to be in.    Probably not going to work well or be a major pain for knowledge contributors until that type of function is simply built into the editor as an icon to click on and it does the rest behind the scenes.      Classic case of this is why we can't have nice things.  

The thing I don't understand is that TinyMCE has this functionality in it's base package - but SN won't let us implement it. They call it "accordion". Has anyone from SN ever explained why they won't let us use it?

Thanks John. Accessibility can be solved for pretty easily with tab index and aria information. Looking through the Amaze Article Builder implementation, this is done for any and all elements in a KB article and no code required from authors.