Car insurance guides
\n\n A quarter of 18-34 year olds believe that tech companies could offer better financial services than banks\n
\n \n{"pages":[{"name":"Framework","page":"index.html","template":"styleguide/templates/simple.tpl","section":"brand","content":"
That’s why we’ve made these guidelines really simple. They inform the way we look, feel, behave and sound as a company. They help ensure we remain consistent, impactful and recognisable across all of our communications.
\nUsing our expansive market knowledge and customer insight, we want to provide a simple, relevant service allowing customers to switch with minimal hassle.
\nTo be the UK’s leading comparison site for all consumers who wish to make their money go further.
\nWe are the comparison service of choice – because we make it relevant, personal and simple to use for consumers and partners.
\nWe help our customers feel like life just keeps on switching for the better, allowing their time and money to be spent on what really matters.
\nWe are connected to the individual needs of our customers. In fact, we work to understand them better than anyone. We use masses of customer data, constantly capturing more and more to continually improve the relevance of our advice. Add that to our commitment to ensure ours is the most simple and comprehensive switching service available, and our customers can find clarity in a confusing marketplace and build confidence in our brand.
\nWe know what we’re talking about because we’re experts in what we do. We can demonstrate an unparalleled in-depth and connected understanding of our customers, the economy, household finances and the industries in which we operate. We’re always frank. We fight for what we believe is fair. And we do what we believe is right to build respect and trust.
\nWe are a human brand that talks to our customers, not preaches. We treat them like knowledgeable peers. Always consistent in our tone, look and customer experience across all touch points. To make things easy to understand, information is visualised and brought to life, enabling our customers to see how they can save money or get better value for money.
\nWe are pro-active, always adapting and pre-empting changes in customer mood and wider markets in which we exist. It lets our customers connect and interact with us with confidence.And we are proud of our BETA mindset. We stay agile, but we never look unpredictably experimental. Rather, we are open, current, honest, committed and consistent with our advice
\n","subNav":[]},{"name":"Imagery","page":"index.html","template":"styleguide/templates/simple.tpl","section":"design","content":"\n\nWe use imagery to relate and engage with our customers, to support our message, and to aid in understanding. These guidelines are here to help you chose images that reflect our brand values and personality. If you’re questioning whether an image is suitable, ask a designer – they’ll be happy to help.
\n\nImages are more interesting when they have a point of focus.
\n\nPeople and objects should be properly contextualised. Avoid cropping an image so severely that it’s setting is lost.
\n\nMake sure clothing, architectural features, light and style have a UK feel.
\n\nRelatable, genuine, optimistic, affirmative.
\n\nOur preference is for natural light where possible. Colours should be warm, vibrant and saturated where possible – avoid images that are “washed out”. Do not use dramatic filters, colourisation effects, or black and white.
\n\nLifestyle shots should be reportage in style, documenting people in their day-to-day lives. Subjects should be unposed, and within their natural environment. People should never be cut out or appear over solid backgrounds. Images should be relatable and feature real, everyday people. Avoid fake or forced emotions as it can seem ingenuine. A range of gender, race, and age should be represented.
\n\nObject focused imagery may be cut out and appear over our brand colours or on white. When cut out, the whole object must be appear – edges must never be cut off.
\n\nWhen objects aren’t cut out, they should be realistic in their setting and not appear staged. Images should be straightforward, not overly metaphor based, and should not appear noticeably manipulated.
\n\nIllustrations may be used to add understanding and delight to an experience.
\n\nOur illustrative style is simple and geometric. Our brand colours should be used predominantly, although variations in shades and saturation may be necessarily. Illustrations should generally appear over solid colour or white backgrounds. Avoid using illustrations that are clichéd or overly metaphor based.
\n\nWe generally try to avoid commissioning photography unless completely necessary as it can prove to be extremely expensive. Before commissioning new photography, carefully consider:
\n\nWhere we do shoot our own (product shots, staff portraits etc being examples of where this may be necessary) we follow these guidelines.
\nImages will often need to be cropped to fit various size requirements. When cropped, images should still follow all guidelines.
\nThe following sites are our preferred resources as images are royalty-free, reasonably priced, and generally good quality. There are shared uSwitch logins for these sites – get in touch with the Service Desk if you don't have access.
\n\nMonthly subscription which allows us to download 750 images per month
\n\nMonthly subscription which allows us to download 10 signature images per month
\n\nImages are purchased individually.
\nStock sites often allow you to purchase images in Small, Medium and Large sizes. Purchasing the largest option is recommended as this will cover most of our online use cases and allow for flexibility when it comes to cropping.
\n\nMost photography that you purchase from stock sites will be either JPG or TIFF format. Either is fine, but if it’s a TIFF, it will need to be converted to a JPG before using online.
\n\nGraphics and illustrations are usually available in EPS, SVG, or PNG format. When available, EPS or SVG files are preferred as they can be scaled to any size. EPS files will need to be converted to an SVG or PNG before using online.
\nRights-managed images often have limitations in regards to the following:
\n\nRoyalty-free images can generally be used on multiple projects for an unlimited amount of time. They should not be confused with “free”. You must still pay a one-off cost to use them.
\n\nWe prefer royalty-free images as there’s fewer restrictions around using them. However even with this type of licence, there may be some usage restrictions, so it’s important to read the licence agreements and act accordingly.
\n\n \n\nCreative Commons means the owner of an image has made it available for use under certain restrictions. Restrictions often include that you must attribute the image to the owner, that you may not use it for commercial purposes, or that you may not alter the image.
\n\nFlickr is a good resource for images that have been made available through Creative Commons, but make sure you understand and comply with any restrictions they’re being offered under.
\n\nPublic Domain refers to images that do not have a copyright and therefore free for anyone to use. It can apply to images that are very old or where the creator has given up their copyright.
\n\nKeep in mind that manipulating an image that isn’t yours (adding a filter, cropping etc) doesn’t give you the right to use it.
\nPurchased images should be added to our shared Google Drive storage within the appropriate category. This should be the original, full-sized, uncropped and uncompressed image only. This allows for cross vertical sharing as well as usage in other mediums such as email.
\n\nWhile the shared library exists so images can be reused, try not to overuse images to the point that they lose their impact.
\n\nImages should be named with a few descriptive words, with words separated by hyphens. Images that are an illustration should have the prefix of "illustation-".
\n\nFor mobile phones, image names should be formatted as follows:
\nyyyy-mm-dd-manufacturer-phonename-phoneversion.png
\nFor example: 2015-04-10-samsung-galaxy-s6.png
\nThe date refers to the date of the phone release.
\n\nFor searchability, it's important to include descriptive tags for each image you add to Google Drive. You can do this under the "Description" field. The first two tags should be the stock site you got the image from, as well as the image number. Include any other tags that might be useful, separating each tag with commas.
\nRetina display refers to monitors and devices that have a very high pixel density, making screen content appear very crisp and sharp.
\n\nTo take advantage of these high-quality displays, we must use Retina images. That simply means that we need to double the intended size of our images.
\nBelow are the minimum required sizes for our images in various materials. If an image does not meet this size, it can’t be used and an alternate image will need to be sourced. An image must not be scaled up in order to meet the minimum required size.
\n\nAlt text is an important aspect of web accessibility. All images on our site should include meaningful alt text. See here for best practices.
\nIf the image is purely decorative, it should have a blank alternative text\n so something unintended (like the image file name) is not read out by a screenreader.
\n\n Do
\n Images feel natural and authentic.\n
\n Don't
\n Images appear staged.\n
\n Do
\n Subject is contextualised.\n
\n Don't
\n Image is too closely cropped.\n
\n Do
\n Houses are a typical UK style.\n
\n Don't
\n Houses feel american style.\n
\n Do
\n Image has warm tones.\n
\n Don't
\n Image is too cool.\n
\n Do
\n Image does not appear altered.\n
\n Don't
\n Image is noticeably manipulated.\n
\n Do
\n Image is realistic and relatable.\n
\n Don't
\n Image is cliché and metaphor based.\n
\n Tip
\n Images where subjects are placed to the left/right and top/bottom are more interesting than those placed centrally.\n
\n Do
\n Illustrations are simple, geometric and consist primarily of brand colours (or shade/tones of brand colours).\n
\n The sum of our efforts towards style guidelines, a pattern library and an automated front-end. Made with ❤ at uSwitch.com\n
\nuStyle includes documentation and guidelines relating to our core design principles. It is where we document everything that happens within our brand, UX and front-end development.
\nuStyle is a gem, a bower package, a npm package and static assets. This allows our team setup to choose how they wish to implement the core front-end of uSwitch. We've tried to be as accessible as possible.
\nAt its core, uStyle is a pattern library. It contains all current components and elements of the uSwitch UI. These are documented in the pattern library section.
\nDelivering designer + developer happiness is very important to us. uStyle provides a base for all our design and development work and allows our designers and developers to focus on the things that matter, whilst making their lives easier when prototyping.
\nThere is no reason for this logo other than it's funny and unicorns are all the rage just now.
\n\nDisclaimer: uSwitch is not a unicorn company.\n
Want to help us build more things like uStyle? We're constantly trying to deliver a better experience for customers and developers, and we're looking for passionate people to join our team.
\nFire us an email at jobs@uswitch.com with your CV and tell us a bit about yourself.
\n\n Our pattern library comes as an easily distributed package, ready to use in multiple programming environments. It contains our basic CSS components and correct usage, as well as JavaScript components that are widely used across the website.\n
\nView on GitHub\nuStyle was initially created as a gem. Some of the Sass functions rely on Ruby to run. You can install it via any Gemfile and it will install the required dependencies.
\ngem 'ustyle', git: "git@github.com:uswitch/ustyle.git"
\n Install it as a bower package. This will pull down the original .scss
files and compiled static CSS + JS.
\n "dependencies": {\n "ustyle": "git@github.com:uswitch/ustyle.git#~0.19.1"\n }\n
\n Every time uStyle gets a new version, the version gets updated across our Cloudfront distributions.\n
\n <!-- get latest -->\n <link href='//assets0.uswitch.com/s3/uswitch-assets-eu/ustyle/ustyle-latest.css' media='all' rel='stylesheet' type='text/css' />\n <!-- get versioned -->\n <link href='//assets0.uswitch.com/s3/uswitch-assets-eu/ustyle/VERSION/ustyle-latest.css' media='all' rel='stylesheet' type='text/css' />\n
\n \n "devDependencies": {\n "ustyle": "git@github.com:uswitch/ustyle.git#~0.19.1"\n }\n
\n We use Autoprefixer + Browserlist to decide what vendor prefixes to apply to our Sass
files. We have a slightly wider browser support than the default (here). Currently we support all the way to IE9.
Below is what we support. Each line is the minimum version or % use based on CanIUse metrics
\nBrowser | \nMinimum version supported | \n
---|---|
Safari, Chrome, Opera | \nLast 5 versions | \n
Firefox | \nESR | \n
Internet Explorer | \n10 | \n
Global usage | \n> 1% | \n
See our GitHub for documentation on installing this across applications.
\n\n We've made our logo available in vertical and horizontal formats to\n allow for flexibility in various layouts. Choose the format that best\n suits the usage.\n
\n\n Vertical orientation\n
\n\n Horizontal orientation\n
\n\n Our logo should only appear in our approved colours. The brand blue logo\n is the preferred version. It can also be displayed on a cyan background.\n
\n\n Brand blue is the preferred version of the logo.\n
\n\n Alternatively it can also be used in white on dark backgrounds.\n
\n\n It can also be used on a cyan background.\n
\n\n The black and white versions of our logo should only be used when colour\n reproduction is not available. Choose the option that will provide the\n most contrast with the background.\n
\n\n The black logo is for use on light backgrounds where colour\n reproduction is not available.\n
\n\n The white logo is for use on dark backgrounds where colour\n reproduction is not available.\n
\n\n Always leave plenty of room around the logo. This will enable it to\n feature prominently without clutter.\n
\n\n The 'S' from our wordmark can be used to measure out the exclusion zone.\n
\n\n An alternative version of our logo must be used when it's being displayed\n at smaller sizes. It ensures that the arrowhead, a key element of our\n brand, remains clear and prominent.\n
\n\n Use the alternative version of the vertical logo when using at a\n height of 98px or less.\n
\n\n Use the alternate version of the horizontal logo when using at a\n height of 64px or less.\n
\nTo ensure legibility of our logo, it must not be used below the\n minimum size.
\n\n The minimum height that the vertical logo may be used at is 50px.\n
\n\n The minimum height that the horizontal logo may be used at is 25px.\n
\n\n Our icon and wordmark must always be used together. The only\n exceptions are our app icon, website favicon and awards logos. Do not\n separate the icon and wordmark in any other instances.\n
\n\n The icon may only be used separately from the wordmark in approved\n situations, such as our app icon.\n
\n\nDo not separate the elements in any other situations.
\nPlease make sure you’re not tempted to do any of the following to the logo:
\n\n Here you can download the standard and smaller versions of the uSwitch\n logo. Each .zip file comes with .eps, .svg and .svg versions of the logo.\n
\n \nEveryone experiences disability at some point in their life, whether permanent\n(blindness, deafness, motor impairment) or temporary (fatigue, migraines, a broken arm).\nThese things may make the things we build difficult to use.
\nBelow, you'll find recommended tools and processes that will help make it easier\nfor folk to use the things we build without frustration.
\nThe web is for everyone, and it is our job to make sure that everyone can access it.
\nThere are a lot of options, both free and paid for, to automatically test the\naccessibility of our products. From the most basic like tota11y and a11y\n, to\nthe more involved like Chrome’s Accessibility Audit tool and aXe. These tools can\nprovide a great overview of where we might be going wrong, and even suggest ways\nto improve.
\nBut with great power, comes great responsibility. We cannot rely on automated tool\nto help us find and fix all the issues.\nGDS discovered\nthat even a tool like Chrome's Accessibility auditor only surface 17% of accessibility issues.
\nJust because a tool says something is broken, we should still manually test to\nprove it is. These automated tools provide solutions, but they are neither the\nonly or the most suitable solution for our users.
\nNothing really beats manual testing. The more you do this, the easier you’ll find\nit to spot potential accessibility errors.
\nUse a screen reader like NVDA,\nJAWS, or\nVoiceOver to go through your\nweb page.
\nNote that you shouldn’t sink time into becoming an expert with a screen reader.\nUnless you use a screen reader every day and have a legitimate need to do so, you\nare unlikely to ever use a screen reader how they should be used.
\nIt's important to note here that you cannot truly say your product is accessible\nuntil you've tested them with folk who benefit from this work.
\nFor more about how we can make uSwitch and the world more accessible, check out\nour blog posts on quick wins\nand how to perform an accessibility audit.
\nCheck out our tips on usability testing, too.
\n","subNav":[]},{"name":"Typography","page":"typography.html","template":"styleguide/templates/simple.tpl","section":"design","content":"Typography is a key element of how we communicate at uSwitch. We've recently revised our type settings and removed Open Sans from our fonts to increase legibility across devices.
\nWe have chosen to use system fonts across the website for multiple reasons:
\nDepending on the operating system you are on, you will get one of the following fonts:
\nFont | \nDevice Targeted | \n
---|---|
-apple-system (San Francisco) | \niOS Safari, macOS Safari, macOS Firefox | \n
BlinkMacSystemFont (San Francisco) | \nmacOS Chrome | \n
Segoe UI | \nWindows | \n
Roboto | \nAndroid, Chrome OS | \n
Oxygen / Oxygen-Sans | \nKDE | \n
Fira Sans | \nFirefox OS | \n
Droid Sans | \nOlder versions of Android | \n
Ubuntu | \nUbuntu | \n
Cantarell | \nGNOME | \n
Helvetica Neue | \nmacOS versions < 10.11 | \n
Arial | \nAny | \n
sans-serif | \nAny | \n
Usability testing can be used to establish problems that need solving, validate a hypothesis or to test a solution. Depending on what's required, there are different types of testing availability.
\n\nHowever, not every change needs to be tested. This page is deisgned to highlight when should and shouldn't use testing, and how we should do it when we do.
\n\n\nPlenty of design changes don’t require upfront hypothesis validation. If the design change is due to any of the following it may not need validation from users:
\n \n\n \nColour, font, shading, button types, and anything in uStyle is a given. We want to achieve site consistency for brand reasons.
\nFunctionality, UI, hierarchy are not 'look and feel' consistency.
\nMoving the first two Broadband designs ('Oldest stlye' and 'Old style') to be more ‘in line’ with the third design ('New style') is an on-going project of consistency.
\nChanging the colours of the first design or moving to a consistent layout would not require testing.
\nSimilarly, changing the row-data presentation in the second example to be more consistent with the third example would not require testing.
\nThere are certain web-design standards, and in our aim for a consistent user experience, maintaining web consistency is an important part of that.
\nThe following is a non-exhaustive list of design conventions:
\nA basic UI convention is the distinction between active elements and inactive elements, with inactive elements being 'greyed out'.
\nThe below car insurance has an overlay that must be interacted with to continue with the page below, but only part of the page is greyed out.
\nFive clickable elements on this page aren’t greyed out, despite not being clickable:
\nThe ten basic usability heurisitcs, like basic design rules, give us a number of usability principles that must be sense-checked against. Designs that do not meet these requirements give us a clear problem to be solved without the requirement of validation.
\n\nKeep users informed about what is going on through appropriate feedback within reasonable time. In the example below the user cannot see what impact selecting a dropdown option has because the overlay covers the results table:
\n\n "Did updating those filters do anything?"\n
\nSpeak the users' language with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
\n\n "Large as in size of people or house? Doesn’t it depend what they’re doing? What’s a Plusnet safeguard?"\n
\nIf a user makes a mistake, let them undo, redo, go back, etc...
\n\n "I wanted more details...and now i've left the site....how do I get back?”\n
\nUsers should not have to wonder whether different words, situations, or actions mean the same thing.
\n\n "Is a plan and a tariff the same thing?”\n
\nEven better than good error messages is a careful design which prevents a problem from occurring in the first place.
\n\n "No deals, why did you present it as an option?"\n
\nMinimise the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part to another.
\n\n "I’ve filtered these results, but by what?"\n
\nllow users to tailor frequent actions. 1-button checkout via Amazon, or Add to my wishlist via Airbnb.
\n\n "I personalised all these details yesterday, why has it just reverted?"\n
\nEvery extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
\n\n "What am I supposed to do on this page?"\n
\nError messages should be expressed in plain language, precisely indicate the problem, and constructively suggest a solution.
\n\n "Ahhhh....the ol' requested format..."\n
\nAny such help information should be easy to find, focused on the user's task, list concrete steps to be carried out, and not be too wordy.
\n\n \nSometimes design is dictated - commercial or regulatory or business.
\nIf there is flexibility around how these are implemented we can enter the design process. Sometimes there isn’t though, and they have to be implemented.
\n\n "The brand red clashes with this provider's red."\n
\nIf our change isn’t down to one of the above then it’s problem solving, so we need to structure our approach to design differently - we need to understand the problem first.
\n \nA problem statement is the design brief, but first we need a good problem.
\nData tells us about results, not causes. It tells us that it looks like there is a problem, but now what the problem is. Data comes from:
\nSimilarly business objectives are things we desire to happen. They tell us what we want to the outcome to be. Objectives sound like:
\nThese tell us there is a problem, but we don’t know what it is.
\nA real problems is something we’ve observed a significant number of occasions.
\n\nTesting designed to steer design, or validate assumptions about what problems users are encountering, is known as ‘formative’ testing. It’s open-ended, and the tasks are simply to run a comparison, or to go through a journey start to finish.
\nAny type of testing, whether it be face-to-face, guerilla, remote, or interviews, can help define the problem. This allows us to frame the problem with a problem statement. A problem statement is:
\nA concise description of the issues that need to be addressed - it is specific, measurable and explains what it impacts. There are no assumptions or solutions.\n\n
Once the problem is clearly defined, start trying to solve it (one problem at a time), but remember to validate the solutions as soon as possible.
\n'Summative' usability testing can help validate. Summative testing gives the user a particular task to complete that tests the solution against the problem. Again, any type of testing can perform this function.
\n\nUser testing is great to validate flows, designs and interactions, but it's not exhaustive. There might be bugs, or solutions that don't work in certain scenarios. This is where in-house testing and the device lab comes in.
\nSo what type of testing should we use, and when?
\n This article by Nielsen Norman Group is a great starting point to understand testing methods and when to apply each. \nThere are over 20 types of validation, including quant methods, but here at uSwitch we predominantly use the following:
\n \n \n \nInterviews are designed to understand behaviours, needs and pain-points around a particular task.
\nThey are open-ended and can help define design personas - archetypes that can be used as a reference point for any design changes for that product.
\nSee the interview checklist
\nInterviews are most commonly used at the earliest stage of product development to determine the needs/problems that the product will address.
\n\n \nFace-to-face testing can be used in a formative or summative sense, and can be combined with an interview and simple exercises, like card sorting.
\nThis is the highest-fidelity form of validation. The feedback you receive will be of the highest quality, but it will also take you the most time.
\n \nFace-to-face testing consists of preparing a particular task, putting it in front of real users, and seeing how they get on.
\nAs it’s face-to-face, you can also interview users in this format, or ask them to complete exercises such as:
\nSee the testing checklist for a step-by-step guide to setting up and running a test. The most crucial components are:
\nAnytime. For an existing product where the objective is to discover problems, an open-ended test asking users to complete the most common journey. This should be done at least once a year.
\nFor a new product or feature face-to-face testing is always a good idea. The objective here is to test the solution against the problem using particular tasks.
\n\n \nA lower-fidelity version of face-to-face testing, guerilla testing sacrifices quality for speed. The feedback you receive will be of lower quality as the participants may not fit user types, and the testing environment is more ‘ad-hoc’ (think coffee shops, sandwich places).
\nJust like face-to-face testing, guerilla testing involves preparing a particular task, putting it in front of real users, and seeing how they get on. You can also do interviews and get quant feedback but again, the feedback will be lower quality.
\nSee the guerilla testing checklist for a step-by-step guide to setting up and running a test.
\nThe number of participants should be at least 5 for guerilla testing, but you can use your discretion.
\nGuerilla testing is perfect at the early stage of a design, when you want to sense check a particular flow, component, or wording.
\nAny fidelity of design can be used. Guerilla testing works best when kept relatively informal, and the participant feels at ease.
\n \n \nAsking your colleagues in the office for feedback. This is the quickest but lowest quality form of validation.
\nLike guerilla testing this is an informal type of testing, but the quality is considerably lower owing to familiarity with the product, bias based on personal relationships and a mismatch between persona types and testers.
\nIn-house testing is perfect for bug testing, seeing if anyone can ‘break’ your design, and last-minute tweaks. It is not for designed to surface flow or interaction changes.
\nSee the bug-testing checklist
\nA few days before release
\n \nThe smallest mistake can undermine the biggest (and most important) of messages. Those writing for uSwitch should ensure they follow these style rules that cover everything from headlines to hyphens, and numbers to names.
\n\nAbbreviations
\nFor names of companies or organisations, if an abbreviation is more familiar than the full form (e.g. BBC, IBM) use that. If not, write the name in full the first time you mention it, followed by the abbreviation in brackets. The next time you refer to it, use only the abbreviation.
\n\nAcronyms
\nWrite out in first use, noting the acronym in brackets; then use just the acronym going forward. Familiar acronyms such as WiFi, HTML, HMRC and BT are exempt from this rule.
\n\n The TaxPayers’ Alliance (TPA) has warned that the campaigns being led by lobbies could lead to higher household bills. Matthew Sinclair, director of the TPA ... \n\n\n
\nAmpersand
\nDo not use the “&” symbol unless it is part of a company or product name.
\n\nApostrophes
\nAvoid common misuse of apostrophes:
\n\nBritish English
\nUse the British ‘s’ in words such as ‘realise’, and ‘specialise’, rather than the American ‘z’.
\n\nBullet points
\nBullet points are a good way to make web copy easier to scan for readers. Bullet points should always be round, and limit bullets to six or fewer. Make sure they are grammatically logical.
\n\nCapital letters
\nNever use all capital letters. Headlines follow usual sentence structure, with only the first word and proper nouns utilising capitals.
\n\nCompany names and references
\nFollow punctuation and capitalisation of company names and products as they are branded.
\n\n E.ON, iPhone, iSaver\n\n\n
When referencing a company in a news or guide, remember to always keep them in the singular.
\n\n BT is launching a new ... (not BT are launching a new ...)\n\n\n
\nContractions
\nOur tone of voice is friendly and familiar, so it’s fine to use contractions like ‘they’ll’, ‘it’ll’, ‘isn’t’.
\n\nDashes and hyphens
\nIf you use a dash within a sentence to create emphasis, then use a long em dash – rather than a hyphen (-).\nCompound adjectives before a noun generally use a hyphen (e.g. ‘the well-organised energy provider’). After a noun, they should be separated (e.g. ‘the energy provider was well organised’).
\n\nDates
\nAlways write out the date, using day, month, year format in news and guides:
\n\n 9 December 2013. When using dates in tables, this may be shortened for space reasons to 9/12/13\n\n\n
In forms when asking for a date we always use the DD/MM/YYYY format.
\n\nExclamation marks
\nUse sparingly, never in headers or intro copy, best suited for marketing/promotional material or news/blogs.
\n\nFull stops
\nDon’t use full stops at the end of headlines.
\n\nGovernment
\nDo not capitalise unless starting a sentence. The abbreviated Gov’t can be used in headlines and desk heads/straplines.
\n\nLegals, disclaimers and caveats
\nSuperscript numbering should be used when there is more than one caveat, however, when there is only one caveat in a communication, an asterisk (*) should be used.
\n\nLess vs. Fewer
\nUse “less” when the subject is something that cannot be counted
\n\nShe wants to have less clutter on her desk.\n\n\n
Use “fewer” when the subject is something that can be counted
\n\nHe sent fewer texts after getting a £100 phone bill.\n\n\n
\nNumbers
\n\nOK
\nNot Ok or okay.
\n\nPercentages
\nAlways use the “%” symbol; only use “per cent” at the start of a sentence. Always use numerals when talking about percentages (54%), unless it starts a sentence. We never use abbreviation “pc” when talking about percentages.
\n\n Fifty-five per cent of the population own an iPhone.\n\n\n
\n Of those surveyed, 55% said they had been denied a credit card. \n\n\n
\nPlans vs tariffs
\nPlans is the preferred term, only switch to use of tariff when trying to avoid repetition within one email or guide.
\n\nQuotation marks
\nAlways use double quotation marks (“) when placing a direct quote in body copy.
\nUse single quote marks (‘) in headlines, standfirsts/dek heads and when quoting within a quote:
\n\n Super-fast broadband uptake ‘reaches 20% in UK’\n\n\n
\n “Super-fast broadband will be the engine for growth for the broadband future of Britain," he said. \n\n\n
\nTitles and Names
\nProfessional titles are not capitalised unless it directly precedes a name:
\n\n Director of Consumer Policy Jane Smith said that the news was a shock.\n\n\n
\n Jane Smith, director of consumer policy at the company, said the news came as a shock.\n\n\n
On first reference, use the person’s first and last name. On subsequent references, last name only is used.
\nMr/Mrs/Miss/Ms is never used.
\n\n Energy Secretary Ed Davey was on-hand to field questions about the news. Davey arrived late, citing a long-running meeting.\n\n\n
\nWi-Fi
\nNot wifi, WIFI, WiFi, etc.
\n","subNav":[{"name":"Abbreviations","link":"#Abbreviations"},{"name":" Acronyms","link":"#Acronyms"},{"name":"Ampersand","link":"#Ampersand"},{"name":"Apostrophes","link":"#Apostrophes"},{"name":"British English","link":"#British English"},{"name":"Bullet points","link":"#Bullet points"},{"name":"Capital letters","link":"#Capital letters"},{"name":"Company names and references","link":"#Company names and references"},{"name":"Contractions","link":"#Contractions"},{"name":"Dashes and hyphens","link":"#Dashes and hyphens"},{"name":"Dates","link":"#Dates"},{"name":"Full stops","link":"#Full stops"},{"name":"Government","link":"#Government"},{"name":"Legals, disclaimers and caveats","link":"#Legals, disclaimers and caveats"},{"name":"Less vs. Fewer","link":"#Less vs. Fewer"},{"name":"Numbers","link":"#Numbers"},{"name":"OK","link":"#OK"},{"name":"Percentages","link":"#Percentages"},{"name":"Plans vs tariffs","link":"#Plans vs tariffs"},{"name":"Quotation marks","link":"#Quotation marks"},{"name":"Titles and Names","link":"#Titles and Names"},{"name":"Wi-Fi","link":"#Wi-Fi"}]},{"name":"Microcopy","page":"microcopy.html","template":"styleguide/templates/simple.tpl","section":"language","content":"Anything shorter than a paragraph is classified as microcopy. Think anything from tooltips to button text.
\n\nHelp text/tool tips
\n\nTooltips are an interruption, use them sparingly (or not at all).
\nKeep the tooltip text concise. Tooltips are perfect for short sentences and sentence fragments; large blocks of text can be overwhelming and should be avoided.
\nTooltip text must be informative. Don't make it obvious or just repeat what is already on the screen. Because tooltip text isn't always visible, it should be supplemental info that users don't have to read.
\n\nBadge/label/USP
\n\nVery short text (1-4 words max) to distinguish products from one another and highlight features of a product that are otherwise not included on the results table. Annotated versions are paired with a descriptive line.
\nShould be written in sentence case, not upper case. The label should be 1-4 words, while descriptive lines should be as concise as possible without wrapping on any device.
\nMust be quantifiable facts about a product, deal or plan be honest and as descriptive as possible. No exclamation points.
\n\nProduct info
\nSummary of product features relevant to users. Must be concise, relevant and quantifiable facts about a product, deal or plan – be honest and as descriptive as possible
\nBe consistent in the way and the order information is presented and the types of information shown. Second person is ok (e.g. “More people in your region switched to this plan than any other”)
\n\nSmall print
\n\nSmall print reassures users and is vital for transparency.
\nAs long as any compliance rules are taken into account, you should treat this copy like any other, and have a responsibility to make this text as comprehensible as possible to a user
\n\nCaveats
\n\nSmall print text to back up any absolute claims (i.e. savings figures), denoted with an asterisk, followed by an anchor and double-anchor for further caveats. The caveat must appear on the same page as the symbol.
\nExamples of when caveats are required...
\nAnd when they're not required...
\n\nButton text
\nVery short (1-3 words) actionable description of what happens when the button clicked, namely, what's on the next page.
\nButton text should “keep its promise” and properly set up expectations of what comes next
\nIt should be concise (1-3 words), should not contain exclamation points, should feel actionable (e.g. “buy” “switch” “get” “apply” “compare”), and can make use of urgency (e.g. “today” “now”)
\nFirst person can be used (e.g. “Tell me more”).
\n\nCTAs
\nAn introduction to button text, usually one to two lines, that provides a reason to click the accompanying button
\nThis is only used on editorial pages. Sentence case should be used, no exclamation points, and the text must relate to the button and its action. A CTA should not end with punctuation (unlike a standard paragraph).
\nShould not be more than two lines, usually made up of a title and copy.
\n\nForm text, form labels
\nDescription of what information is required from the user. Always aim for clarity and be consistent – if using questions ('Where do you live?') or statements ('Address')
\nSecond person is acceptable, and use tool tips to explain any terms that may be unfamiliar
\nForm label naming conventions:
\n\nPlaceholder text for fields
\nPre-populated text in a field that is supposed to serve as an example or a necessary instruction.
\nWe only use placeholder text for instructions, as a last resort, when we have no space for labels, or for email/password.
\nSymbols can be used (e.g. £ ) and we use sentence case. Our standard placeholder text is:
\n\nError text
\n\nText that is triggered by a user trying to move forward without providing requested info.
\nError text should be as specific and as useful/helpful as possible, but should also be short; sentence fragments are acceptable.
\nNever be alarming, technical, or condescending (in life, but especially when it comes to error text)
\n\nH1
\nShort description of the page, at a glance.
\nThis text should be genuinely helpful, in sentence case, and should be kept as short as possible.
\n\nIntroductory text
\nA short (two lines at most) introduction that follows on from the H1. Describes the following content and encourages the user to read on, and provides as much relevant information as possible.
\nThis text should be genuinely helpful, sentence case, and should tell the user whether they are in the right place.
\n","subNav":[{"name":"Help text/tool tips","link":"#Help text/tool tips"},{"name":"Badge/label/USP","link":"#Badge/label/USP"},{"name":"Product info","link":"#Product info"},{"name":"Small print","link":"#Small print"},{"name":"Caveats","link":"#Caveats"},{"name":"Button text","link":"#Button text"},{"name":"CTAs","link":"#CTAs"},{"name":"Form text, form labels","link":"#Form text, form labels"},{"name":"Placeholder text for fields","link":"#Placeholder text for fields"},{"name":"Error text","link":"#Error text"}]},{"name":"uSwitch tone of voice","page":"tone.html","template":"styleguide/templates/simple.tpl","section":"language","content":"Here at uSwitch, we offer everyone ‘Supportive Switching’.
\nThat means we’re not just passively comparing prices, we’re actively enabling and supporting the decision to switch.
\nWhat we write, the way we speak to customers and every conversation we have must give people clear, timely and relevant information. And we should communicate that information in a simple but attractive way.
\nWith the right tone of voice, our words create a decisive moment: we take people from passively knowing they should switch to actively having the confidence to make the right switch
\n\n
- Empathetic
- Expert
- Empowering
To give people the support they need to switch, we need to be able to deliver the right kind of message at the right time. That means our voice needs to be able to flex from simply informative – for example when we’re describing features of a product – to inspirational, when people are at the decisive moment and need extra encouragement to switch.
\nThe trick is to strike the right balance. Our three core principles will help us do this, guiding our communications and making sure that we deliver each message in the most appropriate way.
\nEverything we say should always carry some elements of our core principles in varying degrees. The following framework is designed to make sure we get the balance right.
\n\n
Our three principles work together, and we adjust the emphasis and balance depending on who we’re talking to, why and when.
\nOne voice principle doesn’t exclude another; it’s how we mix them that gives uSwitch a rounded and distinctive voice.
\nAnd, as with people, we’re not one thing all the time, or everything at once — but we have a consistent basis that’s us. For uSwitch, that means we’re always Empathetic. We dial up and down the Expert and Empowering qualities of our voice as needed.
\nThe key thing is to think about the main reason(s) to communicate – and use the principles accordingly.
\n\n\n
Being empathetic means being:
\nOur experience gives us insight and understanding, so being Empathetic means our writing is practical, good humoured and down to earth.
\nBeing empathetic also means we don’t make assumptions about what people know and don’t know. \nWe shouldn’t assume confidence either. We show people that we understand what’s important to them and talk about topics and issues that are directly relevant to them.
\nWhen we write or speak, our language is outgoing and conversational, positive but never over the top.
\nWe want people to know they can rely on us to find the switch that’s right for them - and support them through it.
\nHow we show empathy in our writing
\n\n
Being expert means being:
\nIt’s our responsibility to direct people to the information or product that’s relevant for them. So we make information quick and easy to find, and ensure the pros and cons for switching are obvious and understandable.
\nWe don’t blind with science and we don’t dumb down. We give information succinctly and simply — but never rush the conversation.
\nAt all times we are scrupulously balanced, accurate and honest, and this reassures people by clearly showing that we know what we’re talking about.
\nHow we show expertise in our writing
\n\n
Being empowering means being:
\nWe write and speak to inform and change minds, giving people the straightforward facts and, in turn, the confidence they need to switch.
\nOur explanations and opinions should challenge, involve, entertain, pleasantly surprise and convince – we’re good company.
\nThe facts and figures are important, and we know them inside and out. But we make them more compelling by putting them in context, helping people see what switching could mean for them — whether that’s finally feeling in control of their household bills or that much closer to their dream holiday savings goal.
\nWe know who we are and what we’re about. So we believe wholeheartedly in what we do, knowing that it benefits everyone. So we’re never afraid to show our enthusiasm and commitment in our writing.
\nHow we empower with our writing:
\n\n Our grid is a 12 column grid, with similar sizes to that of Bootstrap. We also adhere to the same naming standards for device breakpoints.\n
\n.us-container
, you must have this to start building the uSwitch layouts..us-grid-row
is then used when you are building rows of columns (gives a negative margin to the container so they align correctly)..us-col-
.Here is an example of a grid which will turn into 100% width columns on mobile.
\n\n<div class="us-grid-row">\n <div class="us-col-md-2">.us-col-md-2</div>\n <div class="us-col-md-2">.us-col-md-2</div>\n <div class="us-col-md-4">.us-col-md-4</div>\n <div class="us-col-md-4">.us-col-md-4</div>\n</div>\n<div class="us-grid-row">\n <div class="us-col-md-8">.us-col-md-8</div>\n <div class="us-col-md-4">.us-col-md-4</div>\n</div>\n<div class="us-grid-row">\n <div class="us-col-md-6">.us-col-md-6</div>\n <div class="us-col-md-6">.us-col-md-6</div>\n</div>\n
\nArticle listings for news are important on the landing pages.
\n","markup":{"example":"\n A quarter of 18-34 year olds believe that tech companies could offer better financial services than banks\n
\n \nOur guide and news articles are used across the site to communicate news/guide snippets. The layout is decided by our grid, by default they have 100% width.
\n","markup":{"example":" ","escaped":" <div class='us-article-group'>\n <div class='us-guide-item us-col-md-4'>\n <a class='us-guide-item-link' href='#'>\n <div class='us-guide-item-image-container'>\n <div class='us-guide-item-image background' style='background-image: url(https://assets0.uswitch.com/s3/uswitch-wp-cms-assets/money/guides/wp-content/uploads/2014/11/DB2011AU01018_SMALL.jpg)'></div>\n </div>\n <div class='us-guide-item-content'>\n <h4 class='us-guide-item-title'>Car insurance guides</h4>\n <p class='us-guide-item-description'>Read our car insurance advice guides for the facts on why you need car insurance, the types of cover available, and tips on how to make a claim.</p>\n </div>\n <div class='us-guide-item-readmore'>\n <span class='us-news-item-readmorelink'>Read more</span>\n </div>\n </a>\n </div>\n </div>"},"path":"vendor/assets/stylesheets/ustyle/articles/_guide.scss","file":"_guide.scss","link":"guide_article"},{"page":"Pattern Library/Articles","name":"More article","description":"If the article listing has more in a category, we use this to let a user navigate to that category.
\n","markup":{"example":" ","escaped":" <div class='us-more-item us-col-md-4'>\n <a class='us-more-item-link' href='#'>\n <span class='us-more-item-title'>See more banking news</span>\n </a>\n </div>"},"path":"vendor/assets/stylesheets/ustyle/articles/_more.scss","file":"_more.scss","link":"more_article"},{"page":"Pattern Library/Articles","name":"News article","description":" The news item article standard. It mirrors the guide article. The news item image is a background image as the problem of not displaying <img>
tags on mobile hasn't been resolved.
Related lists used for content sidebars.
\n","markup":{"example":"The default heading styling across all uSwitch pages.
\n We allow extending the sizes of these headings with %heading-{$i}
so that we don't repeat similar font sizes across the site.
Headings are for structure, not presentation
\nThe first heading on the page should be an H1
\nHeadings should be listed in consecutive order [H1, H2, H3], not [H1, H5, H2]
\nDefault paragraph styling with a margin bottom.
\n","state":[{"name":".us-standfirst","escaped":"us-standfirst","description":"Used for heros and introductory paragraphs.","markup":{"example":"\n Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean vel arcu non magna varius sagittis vel at elit.\n Vivamus et orci pretium, commodo eros vitae, tincidunt purus. Nunc consequat condimentum porttitor.\n Cras at mi sed quam hendrerit bibendum ac a lorem. Mauris a sapien vitae massa lacinia malesuada.\n
"}}],"markup":{"example":"\n Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean vel arcu non magna varius sagittis vel at elit.\n Vivamus et orci pretium, commodo eros vitae, tincidunt purus. Nunc consequat condimentum porttitor.\n Cras at mi sed quam hendrerit bibendum ac a lorem. Mauris a sapien vitae massa lacinia malesuada.\n
","escaped":" <p>\n Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean vel arcu non magna varius sagittis vel at elit.\n Vivamus et orci pretium, commodo eros vitae, tincidunt purus. Nunc consequat condimentum porttitor.\n Cras at mi sed quam hendrerit bibendum ac a lorem. Mauris a sapien vitae massa lacinia malesuada.\n </p>"},"path":"vendor/assets/stylesheets/ustyle/basics/_typography.scss","file":"_typography.scss","link":"paragraphs"},{"page":"Pattern Library/Typography","name":"Lists","description":"Normal list styling.
\n","markup":{"example":"Default blockquote.
\n","markup":{"example":"\n","escaped":" <blockquote>\n <p>\n Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n Aenean vel arcu non magna varius sagittis vel at elit.\n Vivamus et orci pretium, commodo eros vitae, tincidunt purus.\n </p>\n </blockquote>"},"path":"vendor/assets/stylesheets/ustyle/basics/_typography.scss","file":"_typography.scss","link":"blockquote"},{"page":"Pattern Library/Typography","name":"Numbered list","description":"\n Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n Aenean vel arcu non magna varius sagittis vel at elit.\n Vivamus et orci pretium, commodo eros vitae, tincidunt purus.\n
\n
Our default numbered list styling.
\n","state":[{"name":".us-custom-list-alt","escaped":"us-custom-list-alt","description":"Allows us to use the lists on hero/blue backgrounds.","markup":{"example":"Our default ticked list styling.
\n","state":[{"name":".us-custom-list-alt","escaped":"us-custom-list-alt","description":"Allows us to use the lists on hero/blue backgrounds.","markup":{"example":"Our colours (with a "u", we're a UK company) are divided into primary, secondary and tertiary palettes. The primary and secondary are core to all our design work and supported by the tertiary which we use in infographics, graphs and the like. CMYK equivalents are available for print work.
\nDo not rely only on colour to provide information. A green circle means little, a green circle with "success" in the middle gives actual information.
\nMake sure your text is sufficiently contrasted against its background
\nBreadcrumbs are used to provide signposting of a users location and to enable quick navigation around the site. They are only to be used as a secondary means of navigation however. Pages should also be navigable through other means.
\n","markup":{"example":" Our buttons used across the site. The states give different use cases. Both <a>
and <button>
tags are supported. Please use role='button'
when using an <a>
tag.
The calculator tends to sit in the table toolbar component and is used to refine results from comparison tables, and give estimated info about products based on the input.
\n","markup":{"example":" ","escaped":" <form class='us-calculator'>\n <h2 class='us-table-toolbar__heading'>How much would you like to transfer?</h2>\n <div class='us-calculator__input us-input-group'>\n <div class='us-input-group__box'>ÂŁ</div>\n <input type='text' class='us-form-input' pattern='[0-9]*' name='amount' id='amount' value='3000' />\n </div>\n <button class='us-calculator__btn us-btn us-btn--primary'>Update results</button>\n <div class='us-tooltip us-tooltip--right'>\n <div class='us-tooltip__wrapper'>\n <div class='us-tooltip__icon'></div>\n <div class='us-tooltip__note'>\n <div class='us-tooltip__arrow'></div>\n Note that this is illustrative and this figure does not reflect the credit limit you will be offered.\n </div>\n </div>\n </div>\n </form>"},"path":"vendor/assets/stylesheets/ustyle/components/_calculator.scss","file":"_calculator.scss","link":"calculator"},{"page":"Pattern Library/Components","name":"Comp table row","description":" The .us-ct__row
appears in the comparison tables, and contains a single product.
aqua Reward With Cashback
\nAdditional criteria for acceptance from the lender may apply.
\naqua Reward With Cashback
\nAdditional criteria for acceptance from the lender may apply.
\nCompliance banner and disclaimer below the comparison table
\n","markup":{"example":" ","escaped":" <div class=\"us-comp-banner\">\n <div class=\"us-comp-banner__inner\">\n <p class=\"us-comp-banner__text\">uSwitch Limited is a credit broker, not a lender, for consumer credit products.</p>\n <p class=\"us-comp-banner__text\">uSwitch services are provided at no cost to you, but we may receive a commission from the companies we refer you to.</p>\n </div>\n </div>"},"path":"vendor/assets/stylesheets/ustyle/components/_compliance-banner.scss","file":"_compliance-banner.scss","link":"compliance_banner"},{"page":"Pattern Library/Components","name":"Content group","description":" The .us-content-group
is a separator element for content groupings. Ideal to split up landing pages with reasonable padding.
\n Swat at dog intrigued by the shower missing until dinner time and run in circles use lap as chair.\n
\n\n Swat at dog intrigued by the shower missing until dinner time and run in circles use lap as chair.\n
\nUsed within guide and news articles, these CTAs (Calls to Action) are intended to not interupt the content but to integrate in more subtle means.
\n","markup":{"example":" The .us-hero
is used for the upper part of most pages, where the calls to action are usually kept.
It is intended to draw attention with $c-cyan
as it's background color, and should be used across all landing pages.
Swat at dog intrigued by the shower missing until dinner time.
\nSwat at dog intrigued by the shower missing until dinner time.
\nAnchor tag styling, with and without a border.
\n","state":[{"name":".us-link","escaped":"us-link","description":"Adds a border bottom to the link.","markup":{"example":"Link"}},{"name":".us-link--light","escaped":"us-link--light","description":"Changes the link colours to white for when links are placed on dark backgrounds.","markup":{"example":"Link"}}],"markup":{"example":"Link","escaped":"<a href=\"#\">Link</a>"},"path":"vendor/assets/stylesheets/ustyle/components/_links.scss","file":"_links.scss","link":"anchor_links"},{"page":"Pattern Library/Components","name":"Link lists","description":"The default list styling for lists that have anchors to take you to other pages.
\n","markup":{"example":"Loader component to be added to any AJAX/filter loads across uSwitch. We use them specifically in tables when loading new rows.
\n .us-loader--loading
will initiate the animation and .us-loader--centered
will vertically center the loading SVG.
The progress navigation should be used for any funnel journeys on the website. Once a section has been completed the user should be able to get back to that step.
\nThe mobile view of the navigation just has the dotted numbers.
\n","markup":{"example":"Promotional banner
\n","markup":{"example":" ","escaped":" <div class=\"us-promo-banner\">\n <div class=\"us-promo-banner__inner\">\n <h3 class=\"us-promo-banner__title\">Title block here</h3>\n <ul class=\"us-promo-banner__list\">\n <li class=\"us-promo-banner__list-item\">\n <span class=\"us-promo-banner__circle\">1</span>\n <span class=\"us-promo-banner__text\">Text here</span>\n </li>\n <li class=\"us-promo-banner__list-item\">\n <span class=\"us-promo-banner__circle\">2</span>\n <span class=\"us-promo-banner__text\">Text here</span>\n </li>\n <li class=\"us-promo-banner__list-item\">\n <span class=\"us-promo-banner__circle\">3</span>\n <span class=\"us-promo-banner__text\">Text here</span>\n </li>\n </ul>\n <div class=\"us-promo-banner__button\"><a class=\"us-btn us-btn--action us-btn--large\" href=\"#\">Promo CTA text</a></div>\n </div>\n </div>"},"path":"vendor/assets/stylesheets/ustyle/components/_promo-banner.scss","file":"_promo-banner.scss","link":"promo_banner"},{"page":"Pattern Library/Components","name":"Reminder","description":"Placed underneath some tables to enable reminders
\n","markup":{"example":"Create a reminder and we'll let you know when you're nearing the end of your 0% period
\n \n Create a reminder\n \nCreate a reminder and we'll let you know when you're nearing the end of your 0% period
\n \n Create a reminder\n \nCreate a reminder and we'll let you know when you're nearing the end of your 0% period
\n \n Create a reminder\n \nAbove table, tab-style navigation
\n","markup":{"example":"The table toolbar sits above comparison tables and holds search refinement and filtering tools.
\n","markup":{"example":" ","escaped":" <div class=\"us-table-toolbar\">\n <div class=\"us-table-toolbar__wrapper\">\n <form class='us-calculator'>\n <h2 class='us-table-toolbar__heading'>How much would you like to transfer?</h2>\n <div class='us-input-group us-calculator__input'>\n <div class='us-input-group__box'>ÂŁ</div>\n <input type='text' class='us-form-input' pattern='[0-9]*' name='amount' id='amount' value='3000' />\n </div>\n <button class='us-btn us-btn--primary'>Update results</button>\n <div class='us-tooltip us-tooltip--right'>\n <div class='us-tooltip__wrapper'>\n <div class='us-tooltip__icon'></div>\n <div class='us-tooltip__note'>\n <div class='us-tooltip__arrow'></div>\n Note that this is illustrative and this figure does not reflect the credit limit you will be offered.\n </div>\n </div>\n </div>\n </form>\n </div>\n <div class=\"us-table-toolbar__wrapper us-table-toolbar__wrapper--right\">\n <div class=\"us-table-toolbar__sort\">\n <h3 class=\"us-table-toolbar__heading\">Sort by:</h3>\n <select class=\"us-form-select name=\"sort\"\">\n <option value=\"popularity\">Popularity</option>\n <option value=\"apr\">Lowest APR</option>\n <option value=\"min-credit-limit\">Minimum credit limit</option>\n <option value=\"max-credit-limit\">Maximum credit limit</option>\n </select>\n </div>\n </div>\n </div>"},"path":"vendor/assets/stylesheets/ustyle/components/_table-toolbar.scss","file":"_table-toolbar.scss","link":"table_toolbar"},{"page":"Pattern Library/Components","name":"USPs","description":"USPs (Unique Selling Points) are used within tables and on splash pages to highlight offers within a deal, and also to differentiate deals.
\nGeneral guidelines; There should only be one USP per deal. Text within USPs should be written in sentence case (not uppercase).
\n","state":[{"name":".us-usp--blue","escaped":"us-usp--blue","description":"uSwitch related.","markup":{"example":" .us-overlay
slides in from either side of the viewport, or can be shown as a modal window.
These are the basic tabs used for landing pages. You can either reference a data-target for the urls or href for the target tabs. They have a non-js fallback and fold over to accordion when in small tablet view. They are initialised on page load if the tabs classes exist.
\n","javascript":"\n var tabs = new Tabs({\n tabContainer: ".us-tabs",\n tabLinks: ".us-tabs-nav-mainlink",\n tabTitle: "us-tab-title",\n activeClass: "active",\n changeUrls: true,\n collapsible: true,\n autoScroll: false\n });\n ","markup":{"example":"Fatback capicola leberkas pork loin pork jowl. Meatloaf shoulder pancetta, salami prosciutto ribeye andouille chuck landjaeger short loin filet mignon sirloin. Pork chop tri-tip ham pork hamburger frankfurter leberkas short ribs biltong. Prosciutto ham hock rump, andouille tongue flank sirloin tri-tip ball tip frankfurter ham drumstick meatloaf pork loin.
\nKielbasa tenderloin spare ribs, andouille doner brisket chuck drumstick bresaola short loin pork t-bone ground round jowl. Ball tip pork loin doner tongue filet mignon biltong hamburger leberkas. Filet mignon kielbasa kevin short ribs, drumstick chuck shankle spare ribs tri-tip.
\nPig pastrami pork loin kielbasa, filet mignon meatloaf short ribs tenderloin. Pork loin leberkas kevin fatback porchetta bresaola. Cow rump shoulder pastrami. Andouille pork belly t-bone short ribs brisket. Bresaola pork belly tail salami capicola meatball. Pork belly beef ham landjaeger.
\n .us-tooltip
can be applied to any parent, and by hovering over it, it will toggle the visibility of .us-tooltip__note
. Please note that on mobile viewports, the tooltip will appeat underneath the element that is aligned with the tooltip icon.
This is the basic form field, .us-field
wrapper for any single input or select. It sets a few layout options by default (margin) and styles any labels within. You can create a fake label style with .us-faux-label
All form inputs must have a corresponding label, linked to the input
\nThe label should be visible; placeholders should not be relied on as not every browser can see them, nor can all screenreaders. A visible permanent label provides continuous context
\nFor text inputs that are optional, add "(optional)" to the input label
\nAdd aria-required
to any input field that must to be filled in
See our best practices for writing form labels
\nInput groups allow you to add "boxes" to the left or right of an input. These boxes usually contain a visual icon to represent the usage of the input.
\n","state":[{"name":".us-input-group--disabled","escaped":"us-input-group--disabled","description":"Disabled state for input groups.","markup":{"example":"Our standard input styling across the website. This is specifically for text, email, password, search etc. type inputs.
\nSpecifying an appropriate type attribute (e.g. type="tel" for telephone number fields) will not only control what input is displayed, but also helps mobile devices select a keyboard layout suitable for entering that type of data.
\nWhere appropriate use the autocomplete attribute to make it easier for the browser to fill in fields on the users behalf, saving them time on lengthy forms.
\nBrowsers that support screen density media features display our font icon tick or a box shadow circle. Other browsers fallback to default styling.
\nLike select boxes, radio buttons are good for making a selection from a mutually exclusive list of options. The main difference between the two is that with radio buttons, the user must choose exactly one of the options.
\nUse radio buttons when each of the choices matters to the user. Each needs to be considered before they make their choice.
\nCheckboxes in a group should be used for choosing zero or more options from a list of independent options. Toggling one should not change the state of others in the group.
\nA stand-alone checkbox is good for toggling something on/off or opting in/out.
\nProvide a default selection to radio and checkbox groups if it's necessary and wont be changed by 90% of your users.
\nTry to keep the number of radio buttons and checkboxes in the same group to a maximum of 6.
\nSelect boxes allow users to choose an option or options from a list of options.
\nUse select boxes when choosing one or more options from a list of related, but mutually exclusive options e.g. profession, title, month.
\nIt can be tempting to put many things in a select box for users to choose from. Try to keep the list of options to between 4 and 15 so the user doesn't become overwhelmed with choices.
\n