This is the content for Writing well for the web.", "
This is the content for Writing well for specialists.
This is the content for Know your audience.
This is the content for How people read.
", "accordion-with-summary-sections-heading-1", "govuk-accordion__section-summary govuk-body", "accordion-with-summary-sections-summary-1", "accordion-with-summary-sections-content-1", "accordion-with-summary-sections-heading-2", "accordion-with-summary-sections-summary-2", "accordion-with-summary-sections-content-2", "accordion-with-summary-sections-heading-3", "accordion-with-summary-sections-summary-3", "accordion-with-summary-sections-content-3", "accordion-with-summary-sections-heading-4", "accordion-with-summary-sections-summary-4", "accordion-with-summary-sections-content-4", Replace variables, functions and mixins from our old frameworks, Extending and modifying components in production, There is a problem with the service pages, WCAG 2.1 success criterion 1.3.1 Info and Relationships, share your research or feedback on GitHub. We’re now starting to explore how we might structure content differently, at scale, so pieces of information can be reused and accessed more easily, both across GOV.UK and beyond GOV.UK. - Explaining which visa you should have would need to have a lot of background context before being able to say "this is the visa you should have." This blog post features just a small fraction of the work we’ve done to make our components more accessible. See live examples of GOV.UK Frontend components, and guidance on when to use them in your service, in the GOV.UK Design System. The Government Digital Service (GDS) has led the digital transformation of government and is a model that is being copied internationally. For example GOV.UK Step by step navigation uses the words ‘Show’ and ‘Hide’ on the left side. Developing the, has provided greater ability to join up content across complex user journeys. The details component is less visually prominent than an accordion, so tends to work better for content which is not as important to users. The UK government’s new website, gov.uk, was many times cheaper than its predecessors and even won design of the year in 2013. We’ve helped government to realise more than £1 billion of benefits through scrutinising technology spending. Check the MOT history of a vehicle uses up and down arrows instead of plus and minus icons. Disabling controls is normally confusing for users. on 20 November 2020. posted on Many of these decisions and questions will need insight, feedback and collaboration from across government and I’m interested to hear from other teams who have been thinking about these areas. And we’re now using artificial intelligence to increase our knowledge of the information on GOV.UK, helping us start to understand those characteristics and relationships across hundreds of thousands of pieces of content. GDS worked with organisations across government to create the Digital Buying Guide. The more ambiguous an idea is the more "connections" it will have to other pieces of content, and the more context it would need. GOV.UK Frontend is maintained by a team at Government Digital Service. Quick start https://gds.blog.gov.uk/2020/11/05/new-approaches-to-gov-uk-content/. Consider if it’s better to: Do not use the accordion component if the amount of content it would need to contain will make the page slow to load. Simple markup not only enables search engines to prioritise said content and display it much more clearly in the search results, but it also forces content creators to think more openly in terms of the true purpose of the content being produced. And how can we continue to support them in their work on GOV.UK content? government portfolio design-systems govuk-design-system govuk-design-system-team HTML MIT 121 178 120 (4 issues need help) 16 Updated Nov 29, 2020 Comment by Some of this work has provided opportunities to apply a more modular approach to content, where information is built up using small content components that are designed to be used (and reused) in different ways based on context. Stacked radios. GOV.UK. HTML attributes (for example data attributes) to add to the accordion. And we’ve discussed some of the ways we are looking to support this, through building a more holistic picture of how users use government information and services, developing our data science capability, and introducing early thinking on the idea of a GOV.UK account. Users might need the sections they have opened to stay open if they leave and then return to the page. To host a website on a platform other than GOV.UK, a government agency must be given an exemption to do so. Comment by Do user research to find out the best order for the sections. Accordions push other sections down the page when they open, but tabs do not move which makes it easier to switch. The ‘Open all’ button reads out as ‘Open all sections’ for screen readers. Whether you’re navigating through a menu structure or searching for a term or phrase, GOV.UK helps you get to a page that is relevant to the thing you are looking for. It could provide better exposure of content to third parties, with benefits of search engine optimisation (SEO) and channel-agnostic publishing. If you’re outside of the UK government and have ideas, I’d love to hear from you too! On GOV.UK we use a gem called slimmer which adds our standard header and footer to every page. This is a new service – your feedback will help us to improve it. For example: You should also take into account the number of sections of content – accordions display vertically, so they can fit more sections than horizontal tabs. Happy to chat if it’s helpful? There are 2 ways to use the accordion component. Great way of using AI for content. The report was published in 2010 and work began that year to set up what would become GOV.UK and to build a team that would develop and support it. , helping us start to understand those characteristics and relationships across hundreds of thousands of pieces of content. You’ll find live examples supported with code so you can see how components and patterns work and paste them straight into your application. But the scale of information on GOV.UK, together with the complexity of users’ needs and their expectations when interacting with government, present new challenges that we are starting to work through. And the UK Transition (formerly Brexit) checker has gone even further in giving users a succinct, personalised view of information that spans multiple sets of user needs. Structuring information in the ways I’ve laid out isn’t a new concept: online shops and other commercial sites have been using and refining models of structured information for reuse, personalisation and more for years if not decades. (Deadline for visa applications for 2020 is Dec 19th.). Hundreds of thousands of pieces of content is, of course, the big challenge here. In other words, we can get you to the relevant page, but often it’s then up to you to find the relevant information to your situation. Accordions work best for simple content and links. Thanks to the work of GDS, the UK is consistently ranked as a world-leading digital government. I’m also particularly interested in what skills and capabilities will be needed to support these new content models and approaches. Comment by It’s also about understanding what characteristics each piece of content has and what similarities, differences and other relationships pieces of content have with each other. If you want to know more about how you can use them in your service please get in touch with the GOV.UK Design System team at GDS.