-
Suggestion
-
Resolution: Fixed
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
It would help individuals with disabilities if there was an anchor at the top of the main content area on pages and blog posts.
<a name="startcontent" id="startcontent" title="Start of Content">Start of Content</a>
With related CSS to ensure it does not appear on-screen:
.skiplink
{display:none; accesskey="1"}That css also provides the Alt+1 (for example) access key to quickly jump to the start of content. "1" is not a defined standard, but is widely used on many sites.
Note: Some sites use "S" but that conflicts with the browsers built-in Alt+S link to the on-screen search box.
Such a feature is useful for people using screen readers and braillers as it allows them to skip all the navigation, etc., and jump straight to the content they are interested in.
- is incorporated by
-
- Closed
- relates to
-
- Closed
-
- Closed
[CONFSERVER-4094] Content Anchor and Access Key
Guy Fraser [Adaptavist.com]
added a comment - FYI, our Theme Builder plugin now implements such a link. It's easy to add to other themes too - just add a anchor at the start of the content area and then create a link at the top of the page that goes to that anchor. The link at the top of the page should be given a class="nonvisual" and anything with that class should be hidden by default, then made visible when the media type is that used by any of the standard accessibility devices.
Based on feedback from clients, the only other bits of Confluence that are a particular problem are the rich text editor (although lots of it's functionality has keyboard shortcuts such as Ctrl+B for bold text, etc) and the hierarchical page tree which can't be expanded or collapsed with the keyboard (last time I checked anyway).
As for access keys themselves, I've been chatting with lots of people and found that they need to be used sparingly otherwise they can get in the way of other standard browser or OS functionality that are more widely used by all users (eg. Ctrl+F for displaying the "Find" prompt in browsers, etc).
Guy Fraser [Adaptavist.com]
added a comment - FYI, our Theme Builder plugin now implements such a link. It's easy to add to other themes too - just add a anchor at the start of the content area and then create a link at the top of the page that goes to that anchor. The link at the top of the page should be given a class="nonvisual" and anything with that class should be hidden by default, then made visible when the media type is that used by any of the standard accessibility devices.
Based on feedback from clients, the only other bits of Confluence that are a particular problem are the rich text editor (although lots of it's functionality has keyboard shortcuts such as Ctrl+B for bold text, etc) and the hierarchical page tree which can't be expanded or collapsed with the keyboard (last time I checked anyway).
As for access keys themselves, I've been chatting with lots of people and found that they need to be used sparingly otherwise they can get in the way of other standard browser or OS functionality that are more widely used by all users (eg. Ctrl+F for displaying the "Find" prompt in browsers, etc). 
Jeanne Spellman
added a comment - We are a US customer that complies with Section 508 (the federal US Accessibility requirements). This is a requirement of section 508:
"(o) A method shall be provided that permits users to skip repetitive navigation links. "
When can this, and other accessibility requirements be included in the product?
Jeanne Spellman
added a comment - We are a US customer that complies with Section 508 (the federal US Accessibility requirements). This is a requirement of section 508:
"(o) A method shall be provided that permits users to skip repetitive navigation links. "
When can this, and other accessibility requirements be included in the product? Guy Fraser [Adaptavist.com]
added a comment - It seems I can't edit this issue, so I'll have to comment.
Here are some useful related URL's:
http://www.cs.tut.fi/~jkorpela/forms/accesskey.html
http://www.webaim.org/discussion/mail_message.php?id=800
It would be worth providing access keys to the following places:
Home page
Alphabetical Index
Dashboard
Printable View
Normal View
Profile
etc.
It seems that there is a growing trend to use numerical access keys (as stated in the first link above) as they don't conflict with other access keys on menus, etc.
Guy Fraser [Adaptavist.com]
added a comment - It seems I can't edit this issue, so I'll have to comment.
Here are some useful related URL's:
http://www.cs.tut.fi/~jkorpela/forms/accesskey.html
http://www.webaim.org/discussion/mail_message.php?id=800
It would be worth providing access keys to the following places:
Home page
Alphabetical Index
Dashboard
Printable View
Normal View
Profile
etc.
It seems that there is a growing trend to use numerical access keys (as stated in the first link above) as they don't conflict with other access keys on menus, etc. 
Confluence 3.3 is going to include skip links at the top of pages that allow users using screen readers to skip to content. However, we have decided not to implement access keys for these links as they are the first thing in the document anyway. Other accessibility improvements have also been made to the menus, icons, forms and certain images.