What this page covers
This page describes the accessibility direction for Cricbolo's public pages. It is intended to explain current priorities, likely limitations, and the reporting route for anyone who finds a barrier while using the site.
Accessibility
Accessibility
Accessibility is part of trust. This page explains the practical accessibility goals Cricbolo is working toward, the kinds of barriers that may still appear, how visitors can report an issue, and how the platform should treat accessibility feedback as an operational priority rather than a side note.
Current accessibility focus
- Readable text hierarchy with stronger spacing and contrast
- Consistent navigation across major pages
- Mobile-friendly layouts that reduce horizontal overflow
- Clear support and policy routes for users who need help
Where barriers may still appear
Accessibility is an ongoing process. Some interactions, future widgets, or third-party content may require additional review over time. Cricbolo treats reported barriers as product issues that should be examined and improved.
How to request assistance
If you face difficulty accessing content, reading a page, or using a feature, email knowmore@cricbatball.com with the page name, device details, and a brief description of the issue.
Review approach
Cricbolo may update page structure, labels, color contrast, and input behavior as the site evolves. Accessibility feedback helps prioritize those changes.
Accessibility on Cricbolo should be visible in structure, navigation, and support
Readable structure
Headings, spacing, page flow, and content grouping should help visitors scan pages without unnecessary confusion.
Usable interaction
Where interactive elements exist, they should be labelled clearly and remain usable across desktop and mobile contexts.
Responsive layouts
Pages should adapt to smaller screens without forcing avoidable horizontal scrolling or breaking key content blocks.
Clear support routes
Visitors who need help should not have to guess where to report an accessibility problem or request assistance.
Specific feedback makes accessibility fixes faster and more accurate
If possible, include the page name, device, browser, what you expected to happen, what actually happened, and any screenshot that helps describe the barrier. That gives Cricbolo a clearer starting point for review and improvement.
Support route: send accessibility issues to knowmore@cricbatball.com so the team can review the exact barrier involved.
Accessibility should be reviewed whenever the site or its features change
- New layouts, forms, widgets, or embedded tools should be reviewed for readability and usability
- Reported barriers should be treated as product issues rather than isolated complaints
- Support, policy, and contact routes should stay accessible as the site evolves
- Third-party tools may require separate review because they can introduce their own accessibility limitations
This page explains accessibility goals, not a blanket certification claim
Cricbolo aims to improve against practical accessibility principles, but this page should not be read as a claim of full legal or technical compliance certification unless that is separately stated in writing. The honest approach is to describe what is being improved, where issues may still exist, and how visitors can help identify barriers.