Accessibility Statement

1. Our approach

Accessibility is not just a technical checklist. It is part of making Narrow & Wide useful.

We are trying to build a site that is:

• calm to look at
• easy to read
• easy to navigate
• predictable in layout
• usable on mobile and desktop
• respectful of people's time and energy
• not cluttered with unnecessary movement, urgency, or distraction

This matters for everyone, but especially for people who are disabled, neurodivergent, visually impaired, physically limited, tired, stressed, caring for others, or trying to make complicated decisions.

2. Standards we aim towards

We aim to work towards Web Content Accessibility Guidelines WCAG 2.2 AA where reasonably possible.

WCAG is a recognised international standard for making websites more accessible to people with a wide range of needs, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

Narrow & Wide is still evolving and has not yet had a full independent accessibility audit, so we are not claiming full compliance at this stage.

Instead, we are building with accessibility in mind and will keep improving as the platform grows.

3. What we currently try to support

We aim to support:

• readable text and generous spacing
• clear headings and page structure
• semantic HTML where possible
• keyboard-friendly navigation
• visible focus states
• sensible colour contrast
• mobile-friendly layouts
• forms with clear labels
• buttons and links that make sense
• meaningful alt text for important images
• reduced visual clutter
• cookie and settings modals that can be used with a keyboard
• content that is written in plain English where possible

Where we add interactive tools, such as Boat Log, cost tools, listings, filters, forms, cookie settings, or account features, they should be checked for keyboard use, focus states, labels, readable errors, and mobile usability.

4. Cognitive load and neurodivergence

Accessibility is not only about screen readers or visual contrast.

Narrow & Wide should also be easier to use for people who may be neurodivergent, anxious, fatigued, overwhelmed, or dealing with brain fog.

We aim to reduce cognitive load by:

• keeping pages calm
• avoiding unnecessary clutter
• using clear headings
• avoiding manipulative urgency
• breaking long information into sections
• using plain language where possible
• making actions predictable
• keeping forms as simple as possible
• explaining what happens next

This is especially important because some users may be researching expensive, emotional, or life-changing decisions.

5. Browser and device settings

Many people already use their own browser, operating system, or assistive technology settings. Narrow & Wide should work as well as possible with those settings.

You may be able to adjust:

• browser zoom
• text size
• display scaling
• contrast settings
• reduced motion settings
• screen reader settings
• keyboard navigation
• voice control
• colour filters or display adjustments
• browser extensions that improve readability

We do not currently provide built-in font-size controls or contrast mode controls on the site itself. If these are added later, this statement should be updated.

If browser or device settings do not work well with Narrow & Wide, please let us know.

6. Images, media, maps, and embedded content

Where images are meaningful, we aim to provide useful alt text.

Decorative images may have empty alt text so they do not create unnecessary noise for screen reader users.

Embedded content, such as YouTube videos or maps, may come from third-party services. Where optional embedded content uses cookies or tracking, it should be blocked until consent is given.

We should aim to provide context or alternatives where embedded content is important, especially if it cannot be accessed by everyone.

7. Forms, errors, and account features

Narrow & Wide may include forms for accounts, listings, enquiries, Boat Log, expense tracking, directory submissions, reviews, public notes, cookie settings, and early access lists.

Forms should aim to:

• have clear labels
• explain required fields
• show errors in a readable way
• not rely on colour alone
• preserve user input where possible
• be usable by keyboard
• work on mobile
• avoid unnecessary complexity

As the platform grows, forms and interactive tools should be reviewed carefully because they are often where accessibility problems appear.

8. Known limitations

Narrow & Wide is still being built, so some areas may not yet be as accessible as they should be.

Known or possible limitations include:

• the site has not yet had a full independent accessibility audit
• built-in contrast controls are not currently available
• built-in font-size controls are not currently available
• some future third-party embeds may have accessibility limitations outside our control
• user-submitted content may not always be perfectly formatted or accessible
• new tools may need further testing as they are introduced
• some pages may need further refinement for keyboard, screen reader, or mobile use

We will try to improve these areas over time.

9. What we will do as the site grows

As Narrow & Wide develops, we should keep checking accessibility when adding or changing features.

This includes:

• new forms
• Boat Log
• expense tracking
• cost tools
• listing flows
• filters and search
• maps and embeds
• account dashboards
• payment flows
• public notes and reviews
• cookie settings
• mobile navigation

Accessibility should be considered before a feature is finished, not only afterwards.

10. Reporting accessibility issues

If you find something difficult to use, confusing, inaccessible, or frustrating, please tell us.

Helpful details might include:

• what page or feature you were using
• what happened
• what you expected to happen
• what device or browser you were using
• whether you were using a screen reader, keyboard navigation, zoom, contrast settings, or other assistive tools
• screenshots or screen recordings, if you are comfortable sharing them

You do not need to write a perfect bug report. A simple message is enough.

11. Contact

For accessibility feedback, questions, or support, please contact us.