Tutorils is built to be readable and operable by as many people as possible — on a phone, on a desktop, with a keyboard alone, with a screen reader, at 200% zoom, or with motion turned off. This page describes what we target, what we have actually done, where we currently fall short, and how to tell us when something blocks you.
The standard we work to
We aim to meet WCAG 2.2 Level AA across the public site: article pages, category listings, search, navigation, and forms.
We treat that as a working target rather than a finished certification. Parts of the site meet it comfortably, and we describe the known exceptions below rather than claiming a clean bill of health we have not independently audited.
What is in place
Structure and semantics. Pages use a single H1 followed by a logical heading hierarchy, so screen-reader users can navigate by heading instead of reading linearly. Landmarks (header, nav, main, footer) are marked up so assistive technology can jump between regions. Lists, quotes, and tables use real semantic elements rather than styled divs.
Keyboard access. Every interactive control — navigation, the category mega-menu, the search field, carousel controls, FAQ accordions, newsletter and contact forms — is reachable and operable by keyboard. Focus states are visible and not suppressed. A "Skip to content" link is the first focusable element on every page.
Off-screen content is genuinely inert. Inactive carousel slides are marked inert and aria-hidden, so keyboard and screen-reader users are not dropped into content they cannot see.
Images and icons. Article and featured images carry descriptive alternative text. Decorative icons are hidden from assistive technology so they are not announced as meaningless noise.
Colour and contrast. Body text, headings, and interface controls are chosen for contrast against their backgrounds. Colour is never the only way information is conveyed — status and emphasis are also carried by text or shape.
Zoom and reflow. Layouts are responsive and reflow to a single column on narrow viewports, so magnifying to 200% does not require horizontal scrolling to read a sentence.
Motion. The homepage carousel advances on a slow interval and can be controlled manually. We honour the prefers-reduced-motion system setting and suppress non-essential animation when it is enabled.
Forms. Every input has a programmatically associated label. Validation errors are presented as text, not colour alone, and are announced rather than only shown.
Touch targets. Interactive controls, including the mobile navigation bar, are sized to be reliably tappable rather than pixel-precise.
Known limitations
We would rather name these than let you discover them:
- We have not commissioned an independent third-party audit. Our conformance claim is based on our own testing, which means blind spots are likely.
- Third-party content is outside our control. Advertising and consent-management interfaces are rendered by external providers, and their accessibility is determined by those vendors rather than by us.
- Older articles are less consistent. Guides published before our current standards were written may have thinner image descriptions or looser heading structure. We repair these as we revisit them.
- Embedded media from external platforms inherits that platform's player and its limitations.
Telling us about a barrier
If any page, menu, form, image, table, or document stops you doing something, we want to hear about it. Use the Contact page or email contact@tutorils.com and include:
- The URL of the page.
- Your device, browser, and any assistive technology and version.
- What you were trying to do and what happened instead.
Accessibility reports are prioritised alongside factual corrections. Where a fix will take time, we will say so and offer the content in an accessible alternative format in the meantime — a plain-text version of a guide, for example.
Feedback that changes the site
Accessibility problems reported by readers are treated as defects, not suggestions. When a report identifies a barrier we can reproduce, the fix goes into the same queue as any other broken functionality, and we revise our internal standards so the same mistake is not repeated on new pages.
This statement is reviewed as the site changes. The date it was last reviewed appears at the foot of this page.