This section lays out our style in regards to Skylight’s website. While we wrote these guidelines with the Skylight website in mind, you’re welcome to use them for client websites if you don’t have existing guidelines.
alt attribute (
alt tag) is a way to label images, and it’s especially important for people who can’t see the images on our website. An
alt tag should describe the image in a brief sentence or two. It should be used on all non-decorative images.
For more on how and why we use
alt text, read writing for accessibility.
Buttons should always contain actions. The language should be clear and concise. Use sentence case for buttons. It’s OK to use an ampersand in button copy.
- Log in
- Sign up
- Contact us
To highlight certain features of the text, you’ll want to consider adding a callout. Below are the different types of callouts we use at Skylight.
We have two different styles of example callouts. Both styles highlight an example related to the text. We use the first style when working directly with code blocks to differentiate code from text. It features a light gray border and a transparent background.
Home <a href="../" title="home">Click here</a> Keyboard access <a href="../keyboard/" aria-label="Keyboard access">Click here</a>
We use the second callout style solely to highlight text. It features a light gray border and a light gray background. It may also include a green “yes” or red “no” to indicate accuracy.
There are many types of donuts (glazed, powder, chocolate, etc.).
There are many types of donuts (e.g., glazed, powder, chocolate, etc.).
A pull quote emphasizes a particular quote separate from the main text. It features a blue background.
We had been training on agile for some time, and before, we understood all the ingredients. But this workshop brought all the ingredients together and showed us how to bake a cake.Tamara Srzentic, Deputy Director, Office of Innovation at CHHS
A block quote accentuates a longer quote (four lines or more). It’s indented from the main text, but remains integrated within it.
“One problem with technical debt is that the impact can be slow-growing and somewhat hidden. To the question ‘fix the technical debt, or build new features’ we know how it’s usually answered. As it gets worse, customers complain about slow delivery, increasing the pressure to take more shortcuts, which increases the technical debt, which slows the delivery process, which increases customer dissatisfaction, in a rapidly spiraling vicious cycle.”
A note provides the reader with information on further resources to check out (e.g., reading list, resources list). It features a light blue box with an “i” icon.
This is a “note” callout.
A tip offers the reader an actionable piece of advice (e.g., “do this”) and is more integrated with the substance of the text. It features a yellow box with a “lightbulb” icon.
This is a “tip” callout.
News / case study
A news callout highlights additional content that’s separate from the substance of the main text (e.g., links to news articles, case studies). It features a light gray box with a blue border.
A code block highlights a section of code. It features roboto mono text, a light gray box, and a light gray border.
<title>Page Titles - Skylight Accessibility</title>
Use sentence case for checkboxes.
Use sentence case for menu names and menu items.
Form titles should clearly and quickly explain the purpose of the form.
Use sentence case for form titles and form fields.
Keep forms as short as possible.
Only request information that we need and intend to use. Don’t ask for information that could be considered private or personal, including gender. If you need to ask for gender, provide a field the user can fill in on their own, not a drop-down menu.
Headings and subheadings
Headings and subheadings organize content for readers. They should include the most relevant keywords and cover/highlight the main point(s) of the page.
Headings and subheadings are written in sentence case. Avoid using end punctuation except for question marks or when a heading is two or more sentences.
Organize headings and subheadings hierarchically, with headings first, followed by subheadings in order. (An
H2 will nestle under
H2, and on down.) Avoid skipping heading levels (for example, don’t start with an
H3 — use CSS if you want a small
- Headings (
H1) give people a taste of what they’re about to read. Use them for page and blog titles.
- Subheadings (
H3, etc.) break articles into smaller, more specific sections. They give readers avenues into your content and make it more scannable.
Skylight has a Document Style Guide Locked with our standard sizing and colors to use for headings and subheadings.
When inserting a line break, you’ll want to maintain a balance between appropriate line length and effectively communicating your idea. Generally, you should avoid breaking apart a linguistic “whole” or “unit,” (e.g., splitting apart an adjective and the noun that it refers to), which can interfere with intended meaning.
For example, you should prioritize line length in the sentence: “I adopted a dog, a cat, three mice, and a goldfish.”
I adopted a dog, a cat,
three mice, and a goldfish.
I adopted a dog,
a cat, three mice, and a goldfish
However, you should prioritize meaning in the sentence: “I can speak ten modern Romance languages and read Latin pretty well.”
I can speak ten modern Romance languages
and read Latin pretty well.
I can speak ten modern Romance
languages and read Latin pretty well.
Figuring out the right line length comes down to balancing aesthetics and readability. Somewhere between 45 and 90 characters per line is broadly considered to be a readable line length, with 66 characters being a comfortable target for long texts.
In general, longer line lengths are better suited for cases when the information will likely be scanned, while shorter line lengths are more appropropriate when the information is meant to be read thoroughly and contains a call to action.
Provide a link whenever you’re referring to something on an external website. Use links to point users to relevant content and trusted external resources.
Don’t include preceding articles (a, an, the, our) when you link text. For example:
Read the Content Guide for details.
Read the Content Guide for details.
If a link comes at the end of a sentence or before a comma, don’t link the punctuation mark. Leave off quotes and italics from titles in linked text in body copy.
Don’t say things like “Click here!” or “Click for more information” or “Read this.” Write the sentence as you normally would, and link relevant keywords. Users should clearly understand where they’re going just by looking at the link. Avoid linking the same keyword to different places (for example, two links that say “form” that go to different places).
Links should look different than regular copy, strong text, or emphasis text. They should have a hover state that communicates they’re interactive, and should have a distinct active and visited state. When setting the hover state of links, be sure to include focus state as well, to help readers using assistive technologies and touch devices.
Use lists to present steps, groups, or sets of information. Give context for the list with a brief introduction. Number lists when the order is important, like when you’re describing steps of a process. Don’t use numbers when the list’s order doesn’t matter.
If one of the list items is a complete sentence, use proper punctuation and capitalization on all of the items. If list items are not complete sentences, don’t use punctuation, but do capitalize the first word of each item.
Use sentence case for main navigation and subnavigation.
Navigation links should be clear and concise.
Quotations and apostrophes
Use curly quotation marks (“”) and apostrophes (‘’), as opposed to straight quotation marks ("") and apostrophes (').
Use sentence case for headings and button fields.
Sometimes a long piece of copy lends itself to a list of related links at the end. Don’t go overboard — four is usually plenty.
Related articles should appear in a logical order, following the step down/step up rule: The first article should be a step down in complexity from the current article. The second one should be a step up in complexity to a more advanced article.
If you can, avoid repeating links from the body text in related articles.
Titles organize pages and guide readers. A title appears at the beginning of a page and briefly describes the content that follows. Titles also tell search engines what a page is about, and show up in search results. Titles should be unique for each page of the site.
While titles for our internal documents should be written in title case, titles for our website pages are written in sentence case for readability.
Don’t use end punctuation in a title unless the title is a question.
We write for humans, not machines. We don’t use gross SEO techniques like keyword stuffing to bump search results. But we also want to make it easy for people and search engines to find and share our content. Here are some not-icky ways to do this:
- Organize your page around one topic. Use clear, descriptive terms in titles and headings that relate to the topic at hand.
- Use descriptive headings to structure your page and highlight important information.
- Give every image descriptive
- Make sure we have metadata for all the pages we’re creating.
A meta description is an HTML element that gives a short summary of what a given page is about. Search engines will often use meta descriptions to generate search snippets in results pages, providing search engine users a preview of what they’ll find on your page.
Search engines typically truncate meta descriptions that exceed 160 characters (including spaces). In other words, you have about two sentences worth of space to write your meta description. Keep your descriptions between 100 and 155 characters.
Most major search engines don’t use meta keywords for SEO, so you don’t need to use them as part of our web content.