# Accessibility Grid Studio is designed to be usable by everyone, regardless of vision, working environment, or session length. This section covers the accessibility features built into Grid Studio 2.1, with a particular focus on the UI theme options. UI Themes Grid Studio offers five built-in UI themes. Each theme adjusts the colour palette across the entire interface — including panel backgrounds, text, icons, status indicators, and timeline elements — so that you can choose the option that best suits your environment and your vision. To find out how to switch themes, please refer to [here](/grid/grid-studio-fundamentals/fundamentals/interface/grid-studio-ui/theme.md). *** ## Accessibility themes supported by: ### Dark mode As well as our dark grey SP Grid signature default theme, "Dark mode" uses a low-luminance background with high-contrast foreground elements. This reduces eye strain during long sessions and is well-suited to typical studio and control room environments where ambient light is kept low. ### Light mode A bright, high-luminance theme designed for well-lit environments such as offices, on-location setups, or daytime outdoor work where screen glare can make dark interfaces harder to read. Light mode preserves the same information hierarchy as Dark mode, with adjusted contrast ratios for bright surroundings. ### Red/Green mode A theme designed specifically with colour vision accessibility in mind. Grid Studio uses colour throughout the interface to convey meaning — status indicators, warning severities, tracking states, calibration feedback, and timeline elements all rely in part on colour coding. For users with red-green colour vision differences (including deuteranopia and protanopia, the most common forms of colour blindness), distinguishing between these states in the default themes can be difficult. Red/Green mode addresses this by: * Replacing problematic red/green pairings with colour combinations that remain distinguishable across the most common forms of colour vision. * Reinforcing colour-coded information where appropriate. * Maintaining the same overall layout and information density as the other themes, so no functionality is hidden or simplified. Choosing the right theme There is no single "correct" theme. We recommend trying each one in your typical working environment to see which feels most comfortable. Users may switch themes depending on the situation — for example, Dark mode in a dimly lit studio and Light mode for prep work in a bright office. If you have a colour vision difference, or if you find that status colours are hard to distinguish in either Dark or Light mode, we recommend trying Red/Green mode as your default. *** ## Other accessibility considerations Beyond themes, the following features support a more accessible workflow: * [Resizable panels](/grid/grid-studio-fundamentals/fundamentals/workspace-views.md) — the UI layout is fully resizable, allowing you to scale panels and content to suit your screen and viewing distance. * [UI Scaling](/grid/grid-studio-fundamentals/platform/preferences/interface.md#global-ui-scale) - the overall UI can be scaled up and down to accomodate for different pixel density screens * [Viewport adjustments](/grid/grid-studio-fundamentals/project/project-settings/3d-widget.md) - the viewport allows of the flexiblity to change the color used as the background, label color, label size that best suits your need * [Artboard background color](/grid/grid-studio-fundamentals/system/artboards-and-widgets/artboard.md#additional-settings) - each artboard has its own background color adjustments for better differentiation between each other --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://stage-precision.gitbook.io/grid/grid-studio-fundamentals/fundamentals/interface/grid-studio-ui/accessibility.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.