Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-55725

Accessibility fixes for confluence-expand-macro bundled plugin

XMLWordPrintable

    • 1
    • 1
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      Currently there are a few accessibility issues with the templates for this plugin, for example it is missing some accessibility code:

      • expand-macro-core.js (and expand-macro-core-min.js)
        Add aria-expanded attributes.
      • expand-macro.soy
        Add aria-expanded, role="button" and tabindex="0"

       

            [CONFSERVER-55725] Accessibility fixes for confluence-expand-macro bundled plugin

            dkoschmann added a comment -

            Inaccessibility in Confluence macros is a huge issue for Federal clients. Even if the main application is usable with assistive technology, if the macros are not, then content creators can introduce new accessibility issues without realizing it.

            The expand macro is particularly egregious, as it cannot be expanded using keyboard input and is collapsed by default (this differs from the UI Expand macro, which can be set to display expanded by default). This makes the content contained within the macro inaccessible to anyone who cannot use a mouse.

            Relying on user votes to prioritize accessibility issues is a problematic method of addressing these concerns, as the users who are impacted by these failures may not have access to (or be able to use) the bug reporting system.

            dkoschmann added a comment - Inaccessibility in Confluence macros is a huge issue for Federal clients. Even if the main application is usable with assistive technology, if the macros are not, then content creators can introduce new accessibility issues without realizing it. The expand macro is particularly egregious, as it cannot be expanded using keyboard input and is collapsed by default (this differs from the UI Expand macro, which can be set to display expanded by default). This makes the content contained within the macro inaccessible to anyone who cannot use a mouse. Relying on user votes to prioritize accessibility issues is a problematic method of addressing these concerns, as the users who are impacted by these failures may not have access to (or be able to use) the bug reporting system.

            Aryn Frizell added a comment -

            Any idea when this will be implemented? 

            Aryn Frizell added a comment - Any idea when this will be implemented? 

            Zach Mitchell added a comment -

            Greta, Check out CONFSERVER-14249 which is set to "Future Consideration" in it has my source code for the accessibility fixes for v6.4 of confluence to make it meet WCAG 2.0 AA. They have yet to put this into a sprint/timeline. Sad.

            Zach Mitchell added a comment - Greta, Check out CONFSERVER-14249 which is set to "Future Consideration" in it has my source code for the accessibility fixes for v6.4 of confluence to make it meet WCAG 2.0 AA. They have yet to put this into a sprint/timeline. Sad.

            Greta Harding added a comment -

            This is a pretty easy fix, yet has been sitting untouched for 26 weeks. What are your plans?

            Greta Harding added a comment - This is a pretty easy fix, yet has been sitting untouched for 26 weeks. What are your plans?

              Unassigned Unassigned
              dponzio Daniel Ponzio
              Votes:
              19 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated: