Milestones
List view
Things that need to be done and broken down in tickets: * Adjusted backgrounds so they are all white. * Corrected vertical spacing so type is easy to read at all sizes. * Brought P4 & Gutenberg blocks into line so the same type and vertical spacing rules apply to both types. * The colour pallet has been condensed and minor non-accessibility friendly colours refactored. * Modified all greys from red grey to blue grey. * Create an enter Alt tag field in the backend. With a prompt about accessibility. This makes sure the content creator is aware. * Make sure that all HTML mark-up is Semantic. So that TAB navigation, screen reader and ‘Reader Mode’ work perfectly. * Create a section in the onboarding document that refers to the accessibility rules. Does & don'ts, 4.5.1 colour ratio, creating screen reader-friendly links.
No due date•22/22 issues closedWe launched the Handbook a few years ago kind of in a rush to cope with multiple implementations, MVP, capacity building etc.. then reviewed it a little in 2019, but only from a navigation / homepage point of view, trying to deprecate a little implementation-related pages and fix the may 404s we had. For 2020 and beyond, we should iterate its design and UX to make its content more consumable, more accessible and more sexy. Areas of improvements include but are not limited to: - Overall UX / UI redesign - Review of the Taxonomy and Navigation - Continuous inclusion in releases (not sure this is happening regularly) - Plugin review and upgrade (LoCo, IdeaPush..) - Permission review
No due date•18/18 issues closed