Usable by everyone.

Our commitment

Noorani Browser and nooranibrowser.com aim to meet WCAG 2.1 Level AA. This is a baseline, not a ceiling — we want Noorani to be usable by people with visual, motor, cognitive, and situational disabilities.

The current state

This site (the marketing site):

• Uses semantic HTML — landmarks, headings in order, proper list markup
• Passes colour-contrast checks at AA for body text and interactive elements
• Is keyboard-navigable — tab order follows visual order, focus is visible
• Declares language (lang="en") and is readable at 200% zoom without horizontal scrolling
• Respects prefers-reduced-motion by disabling scroll animations when requested

The browser itself (shipping v1.0):

• Inherits Chromium's accessibility tree — screen readers and assistive technologies that work with Chrome work with Noorani
• Keyboard shortcuts match Chromium conventions
• Font size respects OS-level scaling
• Our added UI (prayer-time panel, Qibla compass, Quran reader) is screen-reader-labelled

Known limitations

We're being honest: we're pre-launch, and accessibility needs hands-on testing with real users and real assistive technologies. Known gaps as of v1.0:

• The rotating mark on the homepage uses CSS animation; we disable it when prefers-reduced-motion is set, but we haven't tested with every screen reader
• The Qibla compass is visual-first; a text-only alternative (bearing in degrees only) is available but could be more discoverable
• Arabic and Urdu RTL accessibility has had limited testing — this is a priority for the v1.1 release
• We don't yet have a high-contrast theme; one is planned for v1.2

If you rely on assistive technology and try Noorani, we'd like to hear from you. Your experience is load-bearing data.

Reporting issues

If something doesn't work for you accessibility-wise — at any level, with any technology — please tell us:

nooranibrowser@gmail.com  with  [A11Y] in the subject.

We aim to respond within 48 hours. Critical accessibility bugs (anything that locks someone out of a feature) are treated as release-blocking.

Standards we reference

• WCAG 2.1 Level AA — Web Content Accessibility Guidelines
• ARIA 1.2 — Accessible Rich Internet Applications
• Section 508 (US federal) — where it applies to our users
• EN 301 549 (EU) — European accessibility standard

None of these are checklists we satisfy mechanically. We use them as a baseline and aim higher where the work demands it.