Release 1.11.0 - 2017-01-16 · AusDTO/gov-au-ui-kit

UI-Kit has grown up a bit more -- we now have an official URL! Check it out at http://guides.service.gov.au/design-guide/

Most of the guidance previously sitting in the SASS partials have gracefully uprooted and migrated themselves into the new Design Guide repository, stored now in Markdown. They like their new home.
The images loaded as content in the guide have also joined their friends in the new Design Guide repository.
The English text in some of the markup examples have received some further tlc.
Our browser support document was out of date. It’s been simplified a bit more, and updated to reflect testing conducted end-2016.

New goodies

3 new callout variations: .callout--success, .callout--error, .callout--info have joined the gang.
The tag [definition] lists from the more complex lists are in high demand, so are now available universally anywhere via the .tags class. See the example markup from the complex lists.

The columns of footer menus that have had some organisational issues… the lists themselves contained their heading (thanks to @DJMyles for picking this up). They had crisis meeting: the resolution is each heading and list set gets its own special class (.footer-menu), and this way they get to remain friends. This fixes the semantics and makes it less difficult for CMS template engines to output the right headings and menus. See the footer navigation entry to see what the new markup looks like.

Fixed an obscure issue in Chrome when using a screen reader where labels in forms were rudely not being read out. As a consequence those labels are now being positioned using floats (oh you Chrome, you so random). While at it, the radio buttons and checkboxes decided to improve their distribution of whitespace a bit too. Thanks to @simonschwartz.
It appears Apple’s VoiceOver has a hard time reading out the legend in a form, so after testing we updated some of the form markup snippets to explicitly demo linking a fieldset’s legend with an input (don’t worry: we also feel a bit disgusted that this might mean having to add extra ids). As ever, this is a good reminder that we need to make proper use of aria-describedby in either this approach or the use of hint text.
Our $mobile breakpoint function had a minimum width set on the upper limit, which denied grid support to anything smaller than $mobile-minwidth (420px). Thanks @elisechant.