Accessibility Statement

S92.com.pk publishes informational guides about the S92 game platform. We want readers to be able to find and understand those guides on different devices and with different ways of using the web.

A page that opens successfully is not necessarily easy for everyone to use. Text may be hard to read, a menu may be difficult to reach with a keyboard, or an image may contain information that is missing from the article. This statement explains the areas we consider and how you can tell us about a problem.

Reading on a Phone

Many readers visit S92.com.pk on a phone. An article should fit the screen without cutting off sentences or forcing you to move sideways to read each line.

Text should remain readable when you enlarge it. Headings should help you find the subject you came for, and buttons should be spaced so that tapping one does not open another by mistake.

If a menu covers the article, an image hides important text, or a page becomes difficult to read at a larger text size, send us the page URL and tell us what happened. Your phone model and browser can help us understand the issue.

Clear Headings and Simple Language

Headings give readers a quick way to understand how an article is organised. Each heading should describe the information below it rather than repeat a keyword without adding meaning.

We also try to explain unfamiliar terms in ordinary English. Readers should not need specialist knowledge to understand a basic guide about a screen or device setting.

If an instruction is confusing, please tell us which sentence caused the problem. You may understand a topic well but still find that an article skips an important step. That feedback can help us improve the explanation for others.

Using a Keyboard

Some visitors use a keyboard instead of a mouse. They should be able to move between links, menus, and form fields in a sensible order.

The item currently selected by the keyboard should be visible. A menu or pop-up should not trap someone so they cannot return to the article or close it.

If you cannot reach a link or submit a form using a keyboard, tell us which page you were on and what you tried. A description such as “I pressed Tab but could not reach the contact form” gives us a useful place to start checking.

Images and Screenshots

Images can make a guide easier to follow, especially when they show a platform screen. Important information should also appear in the article text so that a reader does not have to rely only on the image.

A meaningful image should have a text description suited to its purpose. For a screenshot, that description should help identify the screen or feature being discussed. A decorative image does not need to repeat the entire article.

If text inside an image is too small to read, we may need a clearer image or a written explanation nearby. You can report the image by sending the article URL and describing where it appears.

Screen Readers

A screen reader speaks page content aloud or presents it in another accessible form. Links and buttons need useful names so a person can understand their purpose without seeing the layout.

For example, a link named only “click here” gives little context when heard on its own. A link that says which policy or guide it opens is more helpful.

A logical heading order also makes it easier to move through a long article. If a screen reader announces an unnamed button or skips information that appears visually, please tell us the page and the action you were trying to take.

Colours and Contrast

Text should stand out clearly from its background. A colour that looks attractive in a banner may still make a small paragraph difficult to read.

Information should not depend only on colour. If a form field has a problem, a written message should explain what needs to be fixed. A warning should remain understandable to someone who cannot distinguish the colours used on the page.

Tell us if a heading, button, or paragraph is hard to see. If possible, include the page URL and whether you use dark mode, a larger text setting, or another display preference.

Contact Forms and Error Messages

A contact form should make clear which fields need to be completed. If a message cannot be sent, the page should explain the problem in words a reader can act on.

After submitting, a visitor should be able to tell whether the message went through. A form that silently fails makes it difficult to report any issue, including an accessibility problem.

If the form on Contact Us is not working for you, tell us through any other contact method displayed on that page. Please do not send passwords, one-time codes, or payment details while reporting a form problem.

Pop-Ups and Moving Elements

A notice or pop-up should not prevent readers from reaching the article. Its controls should be understandable and usable on a small screen and with a keyboard.

Moving elements can make reading difficult when they interrupt a paragraph or repeatedly draw attention away from the page. If a banner covers content, moves unexpectedly, or cannot be closed, let us know where you saw it.

We can review elements on S92.com.pk. A pop-up or page opened on a separate website is controlled by that website’s operator.

Links to Other Websites

An external website may have accessibility features or problems of its own. We cannot change its design, but we can describe where a link goes and avoid relying on that destination for information that should be explained in our article.

If a link on S92.com.pk has unclear wording or opens somewhere unexpected, report it through Contact Us. Our External Links Policy explains how we handle destinations outside this domain.

How to Report a Problem

Please send the page URL, what you tried to do, and what prevented you from doing it. If you can, include your device, browser, or assistive tool. You do not need to share private account information to report a reading or navigation problem.

For example, you might tell us that a button had no name when read aloud, that text disappeared after zooming in, or that the contact form could not be completed with a keyboard. Specific details help us find the problem.

You can reach us through Contact Us. Our About Us page explains the purpose of the website. We want that purpose to be reflected in pages readers can actually use.

Improving the Website

Website accessibility requires attention when articles, images, menus, and forms change. We can use reader reports and practical checks on different devices to find problems that are easy to miss during ordinary editing.

The W3C Web Accessibility Initiative provides guidance on making websites easier to use. Linking to that guidance does not mean this website has passed a formal accessibility audit.

If you find a barrier on S92.com.pk, please tell us. We can review the part of the website under our control and improve the page where a change is needed.