Effective Date: January 1, 2026
shelftunnelsy.bond is committed to ensuring digital accessibility for all users, including people with disabilities. We aim to provide a clear, readable, and accessible experience across common devices and platforms.
We utilize semantic HTML5 elements (such as <header>, <nav>, <main>, and <footer>) to ensure screen readers and other assistive technologies can properly understand the page layout and hierarchy.
We strive to ensure that all interactive elements, such as links, navigation menus, and form fields, can be accessed and operated using a keyboard interface without requiring a mouse.
We employ legible fonts (Georgia for headings, Helvetica Neue/Arial for body text) and use relative sizing. This approach allows users to scale text appropriately through their browser zoom settings without breaking the page layout.
Our colour palette features a high-contrast combination of Deep Navy and Paper backgrounds to ensure that text and interactive elements remain readable for users with visual impairments or colour vision deficiencies.
The website is designed to be fully responsive, adjusting gracefully to different screen sizes, orientations, and magnifications, ensuring content is readable without requiring two-dimensional scrolling.
All input fields in our contact form are associated with clear text labels to assist users navigating with assistive technologies, ensuring they know exactly what information is requested.
We use descriptive text for links and buttons, avoiding ambiguous phrases like "click here." This ensures the destination or action is clear when read out of context by a screen reader.
We aim to provide descriptive alternative text (alt attributes) for all meaningful images to support visually impaired users. Purely decorative icons or layout elements may be provided with empty alt attributes to reduce screen reader clutter.
Where appropriate, ARIA attributes (such as aria-label and aria-expanded on our mobile menu toggle) are implemented to communicate the state and purpose of dynamic elements to screen readers.
While we strive for comprehensive accessibility, some older browsers or specific assistive device configurations may not perfectly render all stylistic choices. We do not claim full formal accessibility certification (such as strict WCAG 2.1 AAA compliance), as this is an independently maintained editorial project.
We view accessibility as an ongoing and iterative effort. We continuously review our codebase and design choices to implement best practices as they evolve.
We welcome your feedback. If you encounter accessibility barriers on our reading guide or have suggestions for improvement, please let us know by utilizing the form on our Contact page.