Accessibility statement

What this statement covers

This statement applies to novascriptsolutions.com and all of its pages. It describes what has been done so the site works with assistive technology, the standard it is measured against, what is known not to meet that standard, and how to report a barrier.

It describes the site as built rather than as an aspiration. Where something is a limitation it is named as one.

Standard targeted

The site targets WCAG 2.2 at level AA — the level most public-sector accessibility regulations reference, and the level this build aims at throughout rather than on selected pages.

Conformance is asserted on the basis of automated testing across every route, together with manual keyboard and zoom checks. An automated tool reliably catches a subset of failures — missing alternative text, insufficient contrast, unlabelled controls, invalid landmark structure — and cannot judge whether a heading describes its section usefully. The site has not been audited by an independent party.

What has been done

Specific measures in this build, each verifiable by inspecting a page:

• Every page uses one level-one heading and a heading order that does not skip levels
• Landmarks — banner, navigation, main, contentinfo — are present on every page, so a screen-reader user can move between regions
• Text and background colours are checked against the surface each component actually renders on, to 4.5:1 for body text and 3:1 for large display text
• Every interactive element has a visible focus indicator, and the whole site is operable with a keyboard alone
• Form fields have real labels tied to their inputs, and errors are announced rather than indicated by colour alone
• Decorative graphics carry an empty alternative text so assistive technology skips them rather than announcing a filename
• Link text describes its destination, so a list of links read out of context stays usable
• The site is readable and operable at 200% zoom and on a narrow screen, with no horizontal scrolling of the page itself
• Wide content scrolls inside its own container rather than forcing the page sideways
• No content flashes, auto-plays, moves on its own or imposes a time limit
• Typefaces are served from this site's own files, so text renders without waiting on a third-party service
• No third-party JavaScript runs on any page, so no external widget can introduce a barrier

Known limitations

The following are known and stated rather than left to be discovered:

• No independent accessibility audit has been carried out
• No testing with assistive-technology users has taken place
• Screen-reader testing has not covered the full range of screen reader and browser combinations
• The quality of heading wording is a judgement automated testing cannot verify
• No alternative format of the site's content is offered

Reporting a barrier

If part of this site is unusable with your assistive technology, that is a defect worth reporting. A report is most actionable when it names the page, what you were trying to do, the assistive technology and browser you were using, and what happened instead.

The route is the enquiry form on the contact page. That is an imperfect answer — a barrier in the form itself would prevent the report — and it is stated here rather than glossed over.

How this site is built, and why that matters here

The pages are static HTML with no client-side framework rendering the content. Text is present in the page as delivered rather than assembled by JavaScript in the browser, so it is available to assistive technology without waiting for scripts and stays available if a script fails.

There is no analytics, tag manager, chat widget, embedded video or consent banner. Those are a frequent source of accessibility failures a site's own author cannot fix, and this site avoids the category rather than managing it.

Preparation and review of this statement

This statement was prepared on the basis of automated accessibility testing of the built output together with manual keyboard and zoom checks, and has not been reviewed by a third party.

It is updated when an independent audit is carried out, or when a change to the site alters anything described above. A statement not revised alongside the site stops being true, which is why the limitations above are kept specific enough to check.

What to expect with specific assistive technology

A general conformance claim is less useful than a description of what the site actually does, so here is what the build provides for the most common ways of using it.

With a screen reader, each page opens with a skip link to the main content, then a banner containing the navigation, a main region holding the page's content, and a contentinfo region for the footer. Headings form a single outline per page, so navigating by heading gives a reliable map of the content. Links are worded to make sense out of context, which matters because reading a page's links as a list is a common way to navigate.

With a keyboard alone, every interactive element is reachable in the order it appears, and the focused element is always visibly indicated. There are no custom controls that trap focus, no modal dialogues, and no component that requires a hover to reveal something needed to use the page.

With magnification or a large text size, the layout reflows to a single column rather than requiring horizontal scrolling. At 200% zoom no content is lost or cut off. Where a block of content is genuinely too wide to reflow, it scrolls within its own container so the page itself never scrolls sideways.