Accessibility for Confluence

WCAG compliance for Accessibility for Confluence

The following is a list, which is not intended to be exhaustive. In brackets, we denote 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 a screen reader activated, menus are generally optimized, so they might be in a different location. 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 the app

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

    • ✅ Order is logical

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

    • ✅ The tabbing order has been corrected