Hi everybody! It’s been a while, but I wanted to give you an update on what’s happening in and around AUI.
Server’s frontend platform team are working on a new major version of AUI.
The work on alpha and beta versions of this release are being published to 2 sites:
- https://testpreview-aui-docs.netlify.app - AUI’s documentation test preview site.
- https://testpreview-aui-flatapp.netlify.app/ - AUI’s test use cases site.
The AUI 9 agenda
This major version has three key features:
- Accessibility - AUI 9 improves screen reader and keyboard support for some components.
- Compatibility - AUI 9 drops support for IE 11.
- Themeability - AUI 9 includes dark mode theme support.
AUI’s UI components have shortcomings when screen reader or keyboard-only users attempt to interact with them.
In AUI 9.0, we have addressed the major interaction flaws in AUI’s layered components and navigation patterns.
The following AUI components have had markup and behaviour tweaks. They should be Perceivable, Operable, Understandable, and Robust when used via the VoiceOver, JAWS, or NVDA screen readers, or when only using a keyboard:
- Application header
- Close buttons
- Current item
- Disabled items
- Hidden items
- Page layout
- Skip links
- Vertical and horizontal navigation
- Dropdown menus
- Inline Dialog2
For a complete list of changes, see the AUI changelog.
Dropping IE 11 support
Back in September 2019, Atlassian announced their end-of-life policy for IE 11 support in Cloud and Server products.
AUI 9 is expected to be adopted in product versions with no support for IE 11. As such, AUI has also dropped its support for IE 11.
Dark mode theme support
With the removal of IE 11 support, AUI is now able to implement a dark mode theme.
AUI now controls its theme values using CSS variables. The dark theme can be enabled by adding an aui-theme-dark class to the .
See AUI’s documentation for more details on AUI’s theme support.
Note that this capability is currently a beta feature . AUI’s implementation is expected to change as Atlaskit and Atlassian products introduce theming support.
What isn’t in AUI 9
To make the transition to or support for products using AUI 9 easier, we decided NOT remove any code originally marked for removal in AUI 9.
- No legacy components will be removed in AUI 9.
- All deprecation warnings have been bumped to AUI 10.
- Legacy components, such as Inline Dialog 1 and Dropdown 1, are still present in the Atlassian Plugin.
The progress so far
The team’s progress is available on the
master branch of AUI.
The AUI 9.0 release is in beta as of today. A final version is expected around the end of June.
Adoption in Server products
Jira Server will be adopting AUI 9.0 in an upcoming release (in a July-September timeframe).
Server products will announce their adoption in upcoming releases at a later date.
Using AUI 9.0
Where to find it
You can download AUI through one of three distribution channels:
- As an Atlassian Plugin (P2) – https://packages.atlassian.com/maven-public/com/atlassian/aui/auiplugin/9.0.0-alpha-17/auiplugin-9.0.0-alpha-17.jar
- As an NPM package – https://www.npmjs.com/package/@atlassian/aui/v/9.0.0-alpha-17
- As a ZIP file – https://packages.atlassian.com/maven-public/com/atlassian/aui/aui-flat-pack/9.0.0-alpha-17/aui-flat-pack-9.0.0-alpha-17.zip
Markup changes and cross-version compatibility
Some of AUI’s components and patterns required small markup changes to improve their accessibility.
Each change is written in AUI’s upgrade guide.
We appreciate that markup changes are awkward. To reduce the impact, we are aiming for the following:
- Most markup patterns that worked in AUI 8 should also work in AUI 9.
- Markup patterns that work in AUI 9 may work in AUI 8, but:
- Some incorrect aria- attribute usages were changed or removed in AUI 9, but were important to styling and behaviour in AUI 8.
- Use of CSS variables to control theming and styles won’t work in AUI 8.
- The recommended page layout markup pattern in AUI 9 may not style the element correctly in AUI 8.
Please refer to the changelog and upgrade guide for how to handle the component changes.
Support for the release
We want to minimise the effort in supporting products using AUI 8.x and AUI 9.x. Where feasible, we’ll update AUI 9.x to improve cross-version compatibility.
You can file bugs and requests in AUI’s public backlog.
If you have any questions or comments, add them to this thread