Accessibility

Our approach

Accessibility is built into the site’s HTML, CSS and deliberately limited JavaScript. JandaSec does not use a third-party accessibility overlay or toolbar.

The preferred approach is native browser behaviour, semantic HTML, progressive enhancement and straightforward interaction patterns that work without requiring an additional accessibility layer.

Structure and navigation

Pages use English (UK) document language, semantic landmarks and a logical heading hierarchy. A “Skip to content” link is provided so keyboard users can bypass repeated navigation.

Primary navigation, local navigation and mobile navigation use semantic controls and accessible names. Important interactions use native links, buttons, disclosure controls and dialogs rather than clickable non-semantic containers.

Keyboard and focus

The public site is intended to be usable without a mouse. Interactive elements receive visible keyboard focus, and important functionality is not deliberately restricted to hover interaction.

Where a page identifies the visitor’s current location within local navigation, that state is also exposed programmatically rather than relying on colour alone.

Content, images and alternatives

Meaningful images are given text alternatives where they communicate information. Decorative or redundant imagery is hidden from assistive technology where appropriate so that it does not create unnecessary repetition.

Where important text is presented visually, JandaSec aims to expose an equivalent text alternative. This includes the privacy quotation carousel, where each quotation image provides the quotation and author attribution as alternative text.

Information is not intended to depend on colour alone.

Motion and animation

The site respects the browser’s reduced-motion preference. Non-essential animation and smooth scrolling are reduced or disabled when a visitor requests reduced motion.

The privacy quotation carousel also stops automatic progression when reduced motion is requested and can be controlled manually.

Responsive layout and zoom

Layouts use responsive techniques, fluid typography and scalable images so that content can adapt across desktop, tablet and mobile displays.

Browser zoom, reflow, text scaling and target-size behaviour are included in accessibility review as the site develops.

Media and third-party content

The site limits third-party interactive content. The homepage includes one embedded YouTube privacy-enhanced podcast player (youtube-nocookie.com), playable within the JandaSec page using the normal YouTube controls.

The player has a meaningful iframe title, is accompanied by the episode heading and descriptive HTML content, and includes a “Watch on YouTube” link. Caption quality for the source video is managed through YouTube and is subject to separate review.

Decorative video elsewhere on the site is not relied upon to communicate essential page content; equivalent messaging remains available as HTML text.

JavaScript and progressive usability

Most public content is delivered as server-generated HTML and does not depend on client-side JavaScript to be read.

JavaScript is used selectively for limited interactive behaviour such as the privacy quotation carousel and evidence viewer. Native browser controls are preferred where practical.

Accessibility testing

JandaSec combines automated accessibility testing with manual review. Automated tools are useful for identifying technical issues, while manual testing helps assess keyboard use, page structure, zoom and reflow, media, interaction behaviour and the overall user experience.

On 18 October 2026, the public website was reviewed using WAVE, the Web Accessibility Evaluation Tool from WebAIM.

The review reported:

• 0 accessibility errors
• 0 contrast errors
• WAVE AIM score: 10/10
• 3 media-related alerts requiring manual review

The three alerts relate to the site’s single embedded YouTube podcast feature and associated media/link handling. They were reviewed separately and did not identify an accessibility error in the JandaSec implementation.

View the WAVE accessibility report

Automated testing is complemented by manual review because accessibility also depends on interaction, content and behaviour that automated tools cannot fully assess.

Ongoing review

Accessibility is included in normal website engineering and content review. Material changes to navigation, layouts, interactive components, media or page structure should be checked as part of the development process.

JandaSec uses automated testing alongside manual keyboard, zoom, reflow and interaction checks, with additional review where third-party content or more complex interface behaviour is involved.

Accessibility and security

Accessibility improvements should not require visitors to install or trust an additional third-party overlay. JandaSec prefers to fix accessibility in the website itself, reducing unnecessary runtime dependencies while keeping behaviour transparent and testable.