Skip to content
Quiteful
Log in Start free

Accessibility

Accessibility Statement

Last updated: 13 June 2026

Our commitment

Quiteful is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and aim for the relevant accessibility standards.

Conformance status

We aim to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. These guidelines explain how to make web content more accessible for people with disabilities and more usable for everyone.

Accessibility features

Keyboard navigation

  • All functionality is available via keyboard
  • Logical tab order throughout the interface
  • Visible focus indicators
  • Skip-to-content links on every page

Screen reader support

  • Semantic HTML markup
  • ARIA labels and landmarks where helpful
  • Alternative text for meaningful images
  • Descriptive link text
  • Properly associated form labels and instructions

Visual design

  • Sufficient colour contrast (minimum 4.5:1 ratio)
  • Text resizing up to 200% without loss of functionality
  • No reliance on colour alone for information
  • Clear and consistent layout
  • Readable font sizes and styles

Content

  • Clear and simple language
  • Headings used for structure
  • Lists formatted properly
  • Tables include headers
  • Error messages are clear and helpful

Assistive technologies

Quiteful is designed to work with the following assistive technologies:

  • Screen readers (JAWS, NVDA, VoiceOver)
  • Screen magnification software
  • Speech recognition software
  • Alternative input devices

Browser compatibility

Our platform is designed to work with recent versions of Chrome, Firefox, Safari and Edge.

Mobile accessibility

  • Responsive design for various screen sizes
  • Touch-friendly targets (minimum 44 × 44 pixels)
  • Support for mobile screen readers
  • Gesture alternatives
  • Portrait and landscape orientation support

Known limitations

Despite our efforts, some limitations may exist:

  • Third-party embedded content may not be fully accessible
  • Complex interactive features may require additional navigation
  • Some older browser versions may have reduced functionality

We are actively working to address these limitations.

Ongoing improvements

  • Regular accessibility audits
  • User testing with people with disabilities
  • Training our team on accessibility best practices
  • Monitoring and implementing WCAG updates
  • Incorporating user feedback

Feedback and contact

If you encounter any accessibility barriers, please let us know:

We aim to respond to accessibility feedback within 5 business days.

Formal complaints

If you are not satisfied with our response, you may escalate to the Equality and Human Rights Commission (EHRC).