I'd like to start a mini-crusade to improve Accessibility in Confluence 
I'm not disabled myself (although I do have a problem understanding the concept of "time"), but being based in the UK any online site I work on has to adhere to the regulations defined in the Disabilities Discrimination Act. People in the USA have a similar thing, only it's called Section 508. I'm sure most countries have legislation like this, yet Confluence is lacking in some areas.
1. Ability to define language for the whole site and also allow a space to override the language [Related JIRA Issue]
It should be possible to easily define the default language used for the site, override the language in any spaces that contain a different language and even allow users to specify their preferred languages in their profile.
This is important for a number of reasons:
- Correctly define language for whole site and also for individual spaces
- Helps search engines categorise your site more correctly
- Helps screen readers and other accessibility devices convey information more accurately
If you like this idea, please view the Related JIRA Issue and vote for it.
2. Ability to alter the "Site Title" that gets shown in the browser bar [Related JIRA Issue]
It should be possible to change the default " - Confluence" part of the html title for a site and also individual spaces.
This is important for a number of reasons:
- Allows better customisation of Confluences and spaces within
- Improved search engine results
- Helps screen readers, braillers, etc., convey improved information
One of the most notable reasons for this requirement is that many individuals with disabilities make regular use of features that list all open windows along with access keys to quickly get to them - being able to replace "Confluence" with "Technical Support", etc., would be very helpul.
If you like this idea, pease view the Related JIRA Issue and vote for it.
 | I've had feedback already that the site title can be changed (see Admin, General Config, Site title) and in Confluence 2.0 the space title is added as well! Great news! |
3. Relative Link tags, at least in spaces [Related JIRA Issue]
Adding relative link tags, at least within spaces, would provide the following benefits:
- Improved navigation controls in browsers such as Opera and Linx
- Easier navigation to related places for people using screen readers, braillers, etc
- Automatic access keys are provided my most browsers, etc., that process link tags
If you like this idea, pease view the Related JIRA Issue and vote for it.
4. Content anchor and access keys [Related JIRA Issue]
Individuals using screen readers and braillers can get quite frustrated at having to wade through all the site navigation before getting to the content they are after. This simple feature provides the following benefits:
- Immediately jump to start of main content via bookmark relative link (see JIRA issue regaridng relative link tags earlier)
- Immediately jump to start of main content using a shortcut key (usually Alt+1 - or applicable replacement for Alt key depending on platform)
- Allows links from other pages to take you to the top of an article or news post, etc.
In addition, access keys should be provided to key locations such as the home page, dashboard, printable view, profile, etc.
If you like this idea, pease view the Related JIRA Issue and vote for it.
5. Make Site Map accessible with keyboard shortcuts [Related JIRA Issue]
If you don't have a mouse, the site map is currently off-limits. For any individual that is not able to use a mouse (or cannot accurately use a mouse), the site map is impossible to use.
- Keyboard shortcuts need to be provided for collapsing and expanding branches
- Keyboard shortcuts need to be provided for moving around the site map (arrow keys?) - for example, pressing the right arrow key should move from the parent to it's first child item, expanding the branch if it's not already shown
If you like this idea, pease view the Related JIRA Issue and vote for it.