Accessibility Statement

We treat accessibility as an ongoing responsibility, not a one-time project. We design and build cribb with the goal that people who use screen readers, keyboard-only navigation, screen magnification, speech-recognition software, or other assistive technologies can access the same information and complete the same tasks as anyone else.

We also aim to meet our obligations under the Accessibility for Ontarians with Disabilities Act, 2005 (AODA) and its Integrated Accessibility Standards Regulation (O. Reg. 191/11), including the principles of providing information in accessible formats and welcoming feedback on accessibility.

cribb aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

cribb is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not yet fully meet the standard. We have not yet completed a formal third-party accessibility audit, and we do not claim full conformance. One remaining gap touches Level A, not only Level AA: the auto-rotating headlines described in section 4 stop for anyone using the "reduce motion" setting, but they still offer no on-screen pause control. We are working to close the gaps described below.

• Semantic structure: Pages use meaningful HTML headings, landmarks, and lists so assistive technologies can convey page structure.
• Skip link and focus order: A "Skip to main content" link is available at the top of every page, and interactive elements are generally reachable in a logical order.
• Visible focus: A focus outline is applied globally, so interactive elements show where you are when navigating by keyboard. Buttons that stay transparent until you hover them used to render their focus outline transparent too; every one of them now becomes visible when it receives keyboard focus, including the photo galleries and the remove-photo buttons on the listing, sublet and admin upload forms.
• Reduced motion: cribb honours the operating-system "reduce motion" setting for CSS animations, transitions, and smooth scrolling site-wide, and the rotating headlines on the home page, sign-up, log in, and password-reset screens hold still when it is on. Some other JavaScript-driven motion is not yet covered. See section 4.
• Responsive, resizable layouts: Content reflows on small screens and remains usable when text is zoomed, without horizontal scrolling at standard breakpoints.

We want to be honest about where cribb does not yet fully meet our target. Known limitations include:

• Form labels on the main student flows: The fields on sign-up, log in, and both password-reset screens are now properly labelled, so a screen reader announces what each one is for and clicking the label moves focus into the field. The search boxes on browse, sublets, and the marketplace are still outstanding: they rely on placeholder text, which screen readers may not announce and which disappears as soon as you type.
• Keyboard access to some core interactions: The photo gallery on a listing page can now be enlarged from the keyboard, and both it and the message compose dialog close with Escape. The compose dialog also holds keyboard focus inside itself while it is open and hands focus back to the button that opened it. Our four full-screen image viewers now do the same: the enlarged photo on a listing page, the shared photo viewer used on building, landlord property and marketplace pages, the profile-photo viewer, and the floor-plan viewer. Each one keeps keyboard focus inside the viewer while it covers the screen, closes with Escape, returns focus to whatever opened it, moves between images with the left and right arrow keys where there is more than one, and shows a focus outline on its close and arrow buttons. Browsing, opening a listing, and saving are keyboard-operable.
• Text alternatives on listing images: Listing photos currently fall back to generic alt text such as "Photo 1" rather than a description, and the small building thumbnails inside some cards have empty alt text with no other accessible name, so a screen reader may announce nothing useful for them.
• Motion that does not stop: The headlines on the home page, sign-up, log in, and password-reset screens rotate through several phrases on a timer. They now stop entirely if your operating system is set to reduce motion. There is still no on-screen pause control for anyone who has not set that preference, so we do not yet claim to meet WCAG 2.2.2 (Pause, Stop, Hide) at Level A. Some other JavaScript-driven motion is also not covered by the CSS rule in section 3.
• Interactive maps: Our maps use Google Maps. The map canvas itself may not be fully operable by keyboard or screen reader. Where a map appears, we also provide the property address in text, and nearby points of interest are listed in text below the map so the information is available without using the map.
• User-generated content: Listing photos, marketplace photos, and profile images are uploaded by students and landlords. We cannot guarantee that every uploaded image includes a meaningful description written by the uploader.
• Uploaded documents: Documents provided for landlord verification are supplied by third parties and may not be in an accessible format.
• Some complex components: Certain interactive components (such as date pickers, sliders, and modal dialogs) are being reviewed and refined for full keyboard and screen-reader support.
• Colour contrast: We have not yet completed a full colour-contrast review. Some lighter text and subtle UI elements may not meet the WCAG AA contrast ratio, and we are auditing and correcting these.
• Icon-only controls: Some icon-only buttons are still being given clearer names for screen-reader users. Form fields are covered separately at the top of this list.

Some features rely on third-party services, for example Google Maps for maps and address lookup, and Cloudflare Turnstile for bot protection. We do not control the accessibility of these third-party components, but we choose providers that publish their own accessibility commitments and we provide text alternatives where we can. Content posted by other users (listings, reviews, marketplace items, and messages) is created by those users and is not authored by us.

cribb is designed to work with current versions of major browsers (Chrome, Safari, Firefox, and Edge) and with the assistive technologies built into modern operating systems, including screen readers and browser zoom. It may not work well with browsers or assistive technologies more than a few versions out of date. If you use a specific setup and run into a barrier, please tell us. It helps us prioritise.

If you need information that is on cribb (such as a listing's details, our Terms, or this statement) in an accessible format or with communication support, contact us and we will work with you to provide it in a way that meets your needs, at no additional cost. We will consult with you about your needs and aim to provide the requested format in a timely manner.

We welcome your feedback on the accessibility of cribb. If you encounter a barrier, or if something does not work with your assistive technology, please let us know. Your reports directly shape what we fix next.

• Email: hello@findyourcribb.com (please put "Accessibility" in the subject line).
• What helps us: the page or feature, what you were trying to do, the browser and assistive technology you were using, and what went wrong.

We aim to acknowledge accessibility feedback within five business days and to give a substantive response, including next steps or a timeline, as soon as we reasonably can. Feedback is accepted by email and we will arrange an alternative method on request.

Accessibility is never "done." As we add features and as standards evolve, we review new and existing pages, fix issues we find or that you report, and revisit this statement. We intend to pursue a more formal accessibility review as cribb grows.

We may update this statement as cribb changes and as our accessibility work progresses. The "Last updated" date above reflects the most recent revision.

For anything related to accessibility: hello@findyourcribb.com

You can also reach the people behind cribb directly: Adeoluwa Ojulari (adeoluwaojulari@gmail.com) and David Amaefula (professionaldavid14@gmail.com).