Skip to main content

Accessibility

At GitHub, our mission is to accelerate human progress through developer collaboration. We believe people with disabilities should benefit from and be able to contribute to the creation of that progress. As such, we strive to ensure that, like our product, our branding efforts are designed to be as inclusive as possible, including to those with visual impairment.

GitHub's accessibility vision

Legibility

To ensure legibility for those with visual impairment:

  • Use our type pairing primitives, which have been designed for legibility. Do not re-scale text sizes.
  • Always ensure that all text has a minimum contrast ratio of AA.
  • Never use only color to convey meaning.

Dark & light mode

We often create assets with color combinations that can stand out both on light and dark backgrounds. The use of light and dark mode derives from an accessibility standpoint in web experiences, and has come to be an integral part of brand expression in recent years.

Two social posts templates with Lorem Ipsum showing the difference between dark and light mode

For assets that have a light and dark version, please stick to only one style for your campaign, based on the surrounding context. If you do not have control over the context, the default should be to use the dark mode version. Do not mix and match different modes in the same campaign/context.

Do not mix and match different modes in the same campaign/context.

Color and render

Though subtle, there are differences in the way we treat the artwork in terms of color, shading and render. Successful examples of Light and Dark Mode artwork here.

Two octocat illustrations on light and dark backgrounds showing the difference in rendering between color modes

Related content