WCAG compliance for Accessibility for Confluence

The following is a list, which is not intended to be exhaustive. In brackets we denoted if this issue pertains to screen reader (SR) use, keyboard only use, or voice activation.

1. Drop-down menus not accessible to screen readers (SR)

   • with activated Screen Reader, menus are generally optimized, so they might be in a different place. They definitely work.

   • in normal view/high-contrast mode, menus have been optimized for use with a keyboard

     • high-contrast mode does not work in Google Chrome

2. Search drop-down box (SR)

   • works in screen reader mode

3. Individual notifications not accessible (keyboard, SR, voice activation)

   • does not work in Screen Reader mode

   • has been optimized for the keyboard in normal view/high-contrast mode

4. Links without appropriate names (SR)

   • optimized in all modes

5. “Write a comment” field is not keyboard accessible (keyboard)

   • works

6. Color picker colors are unlabelled (SR)

   • with activated Screen Reader mode wiki markup can be used to make text colorful in text areas

7. Pop-up modal inaccessible (SR)

   • in Screen Reader mode optimized for users (not global or space admins)

   • attachments can be added via keyboard also in normal mode - via the page menu

8. Focus removed from edit field after making menu selections (all)

   • works with app

9. Focus order after the comment box moves the user to the top of page (SR, keyboard)

   • order is logical

10. Network – Edit field tab order illogical (SR, keyboard)

    • The tabbing order has been corrected

Related Articles