Theme Builder includes numerous features to provide a more accessible interface to your wiki...
Meet Legal Requirements
Theme Builder makes it easier for your organisation to meet legal requirements such as Section 508 (USA), the Disability Discrimination Act (UK) and similar laws in other countries.
Skip Navigation
Invisible until needed, it's the first thing a screen reader or Brailler will find on the page and when selected instantly jumps to the main content of the page. Keyboard users can tab "in to" the page to see the link and cycle through a list of other access keys.
Access Keys
The standard theme layout that ships with Theme Builder includes common access keys for selecting page mode, search box, etc.
You can add your own access keys to any link created with the menulink macro or compound-menuitem macro and denote shortcut keys in menu bars and pop-up menus by underlining them.
All defined access keys are automatically added to the access key panel (see Skip Navigation above) and you can cycle through them with successive tab key presses.
Keyboard Input
Our menus, links and other navigation all support keyboard input as standard.
Boilerplate Demotion
Many sites have boilerplate such as disclaimers, copyright notices and other things that would generally annoy anyone using an accessibility device.
Theme Builder allows such content - both in the theme and even on individual pages - to be demoted and appear after the main page content.
Theme Switching
Theme Builder 3.0 and above support end-user theme switching allowing individuals to instantly switch to a more accessible view of your wiki, for example you can provide high-contrast or large-text layouts.
Accessible Forms
We use semantic markup on form elements such as labels and fieldsets in accordance with accessibility requirements.
Our Commitment
We are firmly committed to improving the accessibility of the theme, our macros and other plugins wherever and whenever possible. If you find something that's causing problems, please let us know and we'll add it to our task list for a subsequent release.
Third Party Plugins
While we have complete control over the theme and other Adaptavist plugins, we can't do much about third party plugins. However, we're well connected within the Confluence developer community so we can put you in touch with the developers of any external plugin that causes you problems.
Added by
Hello,
I am interested to know how we can modify the tables on the info tab for a page to allow accessibility? Can builder 3.0 do that?
thanks
The contents of the info tab come from Confluence itself. If you have access to the Confluence source code (commercial or academic license of Confluence required) you can edit the velocity templates used to create those panels.
Thank you.
Do you have an example of a wiki example that was built using theme builder that is 508 accessible?
Thanks
Your question relates specifically to Confluence and not Theme Builder. If you have any specific queries, please let us know via https://tracker.adaptavist.com/browse/BSUP
Actually No. I know that Confluence is not 508 accessible and was very glad to know that Theme builder supports 508 accessibility. I am evaluating theme builder for 508 acessiblity purposes. Thats why I am asking whether there any sites built with theme builder for 508 purposes.
Thanks
Hello again,
where can I find a list of access keys already defined that ship with theme builder.
Thanks
You define your own access keys as part of the theme design. Using the menulink macro and compound-menuitem macro set the acccesskey parameter to any single letter or digit to associate the link with that access key. The link will also then be listed in the panel that appears when you tab in to a page or select an access key.
Hello again.
Please forgive me if I am asking too many questions but 508 accessibility is important and key factor to us as the product will be used in a government agency. Your website doesnt provide much detail here.
I am wondering what you mean when you say keyboard input.
For example I set a space theme to the Adaptavist Theme Builder Default theme and tried to use the keyboard to tab into the links and the Rich text editor. It skipped over the Rich text editor. Does this mean Theme builder really supports acessibility only when menus are designed using theme builder> So the Rich text editor and some existing functions of Confluence are not really part of theme builder?
Thanks
The Rich Text Editor is not part of Theme Builder, it's a plugin that's bundled with Confluence. It should be noted that as of Confluence 2.9 the Office Connector plugin can be used which allows editing content in desktop office applications such as Microsoft Word or Open Office Writer - both of which will likely be better for your needs than the Rich Text Editor.
The macros I previously mentioned can be used both in menus and also to generate text links (which can then be styled with CSS if desired) and associate an access key with them.