Accessibility Statement

Studio Nope builds HubSpot CMS themes, and the people who buy them go on to publish sites used by the public. Accessibility is therefore part of the product, not an afterthought applied to it.

We aim to make this website and the themes we ship usable by as many people as possible, including people who navigate by keyboard, use a screen reader or magnifier, rely on high contrast, or prefer reduced motion.

We measure our work against the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

This website is partially conformant with WCAG 2.1 Level AA. Partially conformant means that most of the content meets the standard, but some parts do not yet. The known gaps are listed in section 5 below.

We describe the status honestly rather than claiming full conformance, because a demonstration site carrying sample imagery and embedded third-party content will always contain material we do not fully control.

Accessibility features present across this site and the themes it demonstrates include:

• Semantic structure: Landmark regions, a single main heading per page and a logical heading order, so assistive technology can present an accurate outline.
• Keyboard operability: Every interactive control can be reached and operated with a keyboard. Menus, accordions, tabs, modals and carousels follow expected key patterns, and modals trap and restore focus.
• Visible focus: A clear focus indicator is drawn on every focusable element and is never removed by the stylesheet.
• Skip link: A skip to main content link is the first item in the tab order.
• Colour contrast: Body text and interface controls are checked against the 4.5 to 1 ratio, and large text against 3 to 1, in every colour preset a theme ships.
• Colour independence: Meaning is never conveyed by colour alone; status and emphasis carry text or an icon as well.
• Text alternatives: Image fields in every module expose an alt text input, and decorative images are marked so screen readers skip them.
• Form labelling: Inputs carry persistent visible labels, errors are announced and described in text, and required fields are marked in the accessibility tree.
• Reduced motion: Scroll animations, counters and parallax effects are disabled when the operating system requests reduced motion.
• Responsive and zoomable: Layouts reflow to 320 pixels wide and remain usable at 200 percent zoom without horizontal scrolling.

We combine automated and manual testing, because automated tools alone catch only a portion of real barriers:

• Automated audits with axe and Lighthouse on every template before release
• Manual keyboard-only walkthroughs of each page and each interactive module
• Screen reader spot checks with VoiceOver on macOS and NVDA on Windows
• Contrast verification of every colour preset a theme offers
• Zoom and reflow checks at 200 and 400 percent

We are aware of the following gaps and are working on them:

• Embedded third-party content. Video players, maps and chat widgets embedded on demo pages are rendered by their providers, and their accessibility is outside our control.
• Sample imagery. Placeholder graphics on demo pages carry generic alternative text, because they illustrate layout rather than convey information. Real alt text is expected to be written by whoever publishes the site.
• Complex data displays. A small number of charts and comparison tables on demo pages do not yet offer a full text equivalent.
• Documentation code samples. Long syntax-highlighted code blocks in our documentation can be verbose when read aloud.

A theme can only supply the foundation. Whether a finished site is accessible also depends on the choices made by the team publishing it. If you are building on one of our themes, please:

• Write meaningful alternative text for every image that carries information
• Keep headings in order and do not pick a heading level for its size
• Write link text that makes sense on its own, rather than click here
• Check contrast again after applying your own brand colours
• Caption and transcribe video and audio you add
• Keep custom code you add as accessible as the theme you added it to

This site is designed to work with recent versions of Chrome, Edge, Firefox and Safari, used with current versions of VoiceOver, NVDA and JAWS. It should degrade gracefully in older browsers, but some visual refinements will be absent.

If you meet a barrier on this site, or in a theme you have licensed from us, please tell us. Reports from people who use assistive technology are the most useful information we get.

Please include the page address, what you were trying to do, and the browser and assistive technology you were using. We aim to acknowledge reports within two business days and to give you a target date for a fix.

If we cannot make something accessible in a reasonable timeframe, we will offer the information or function in another way.

This statement was prepared through a self-assessment carried out by Studio Nope against WCAG 2.1 Level AA. It is reviewed whenever a theme is released and at least once a year.

To report an accessibility problem or to request content in an alternative format, contact us by email.

Email: hello@studionope.com
Website: www.nopethemes.com