Looks like you're in . Want the local site?
ACCESSIBILITY & RESPONSIVE UX
Most Nepali websites fail the same ten accessibility checks. We audit your site against WCAG 2.1 AA, fix what is broken, and confirm it works on the low-end Android devices your visitors actually use.
We are proudly featured on
Trusted by businesses we have shipped growth for
/ This is for you if
Your international funder, government partner, or procurement body has added WCAG 2.1 AA compliance to their grant or contract requirements. You need a formal audit report, a list of issues with severity ratings, and confirmation that fixes are in place before the submission deadline.
Your traffic is majority mobile, and a significant share of those users are on older Android handsets with smaller screens. Pages overflow horizontally, tap targets are too small to press accurately, and text that looks fine on a laptop is unreadable on a 360px screen. Nobody has fixed it because nobody documented what is actually wrong.
Development organisations funded by USAID, FCDO, the World Bank, or similar bodies increasingly carry accessibility clauses. Your site is the public face of that work. If it does not meet the standard, the clause is a liability. We audit to the clause and produce the report your donor requires.
/ What's broken
Screen readers read alt text aloud to blind users. When alt text is missing, the image does not exist for that user. Product images, infographics, team photos, and decorative images all need to be handled correctly. Missing alt text is the single most common accessibility failure and among the easiest to fix.
Light grey text on white, pale blue on light backgrounds, or muted tones that look clean in a design tool often fail the WCAG AA contrast ratio of 4.5:1 for normal text. This affects users with low vision, colour blindness, and anyone reading outdoors on a bright screen. The fix is a colour value change, not a redesign.
Placeholder text is not a label. When form fields rely on placeholder text alone, screen readers cannot identify what the field is for, and keyboard users navigating by tab order have no reference. Contact forms, application forms, and registration flows are where this appears most often.
A layout that works at 390px can break at 360px or 320px. Older and lower-cost Android handsets sold in Nepal often have narrower viewports. Horizontal scroll, clipped buttons, and overlapping text are symptoms of a layout that was tested on one device and shipped without checking the range.
/ What we engineer
Each workstream is built by the team that audits it, and wired into the rest of your growth system.
We run automated scans with Axe and WAVE, then layer manual testing on top. Automated tools catch around 30 to 40 percent of accessibility issues. The rest require a human to navigate the site with a keyboard, activate a screen reader, and check what the automated tool cannot see.
We test with NVDA on Windows and VoiceOver on macOS and iOS. We navigate key user flows: home, service pages, contact forms, navigation menus, and any interactive components. We document what is read aloud, what is skipped, and what is confusing.
Every interactive element on your site should be reachable and operable using only a keyboard. We tab through the full site, check focus indicators are visible, confirm modals and dropdowns do not trap keyboard focus, and verify that skip navigation links work.
We check every text-background combination against the WCAG AA standard (4.5:1 for normal text, 3:1 for large text). We flag failures, provide the exact contrast ratio, and give you the corrected colour values that pass.
We audit all images for alt text quality, not just presence. We implement ARIA roles, labels, and live regions where they are missing or wrong. We fix landmark regions so screen reader users can navigate by page structure.
We test your site at key breakpoints from 320px to 1440px, on real and emulated devices, including low-end Android handsets. We document every layout failure, including horizontal scroll, clipped content, overlapping elements, and tap targets smaller than 44x44px.
After fixes are implemented, we retest every issue we flagged. The confirmation report documents pass or fail for each item. You receive a final status: compliant, or a list of outstanding items with a clear explanation.
/ What changes
/ How it works
We run automated scans and manual testing across your site. We test with keyboard navigation and screen readers. We check every breakpoint. You receive the full audit report with every issue categorised as critical, major, or minor, plus the WCAG criterion it violates.
We review the audit with you and agree on scope. Some fixes are purely on our side (ARIA, alt text, contrast values). Others may require changes to your CMS templates or component library. We map out what needs to happen and who does what.
We implement fixes in your codebase or CMS. For responsive issues we work at the CSS and template level. For ARIA and focus management we work in the component or JavaScript layer. We document every change we make.
We retest every item from the original audit. Items that pass are marked confirmed. Items that required a content-side change (e.g. alt text on images your team manages) are documented with instructions so your team can maintain compliance going forward. You receive the final confirmation report.
/ Common questions
Straight answers on scope, timelines and cost. Anything else, ask us directly.
Ask us directlyThere is no currently enforced national legislation in Nepal that mandates WCAG compliance for private sector websites, but international funders and development sector contracts regularly include WCAG 2.1 AA as a contractual clause. Government sites under e-governance frameworks reference accessibility standards. If your funding or procurement documentation includes an accessibility clause, it is a binding requirement regardless of domestic legislation.
A full audit of a standard informational website of 10 to 20 pages takes approximately three to five business days. Larger sites with complex components, dynamic content, or multilingual content take longer. We scope the audit before we start and give you a clear timeline.
For some fixes, yes. Alt text, ARIA labels, and certain contrast fixes can be applied through a CMS or via a JavaScript layer. For structural fixes, including keyboard trap issues, focus management, and responsive layout failures, we need access to the codebase or theme files.
We test on a range of real and emulated devices, with specific attention to lower-cost Android handsets common in the Nepali market: devices with 360px and 320px viewport widths, Android 10 and 11, and Chrome Mobile. We also test on iOS (Safari), desktop Chrome, and Firefox.
An automated tool like Axe or WAVE catches approximately 30 to 40 percent of WCAG failures. The rest require a human tester. Automated tools cannot determine whether alt text is descriptive, whether focus order makes logical sense, whether a screen reader user can complete a form, or whether a page is navigable by keyboard alone. A full audit combines automated scanning with manual testing, screen reader use, and keyboard-only navigation.
Start here
We will audit your site against WCAG 2.1 AA, test it with screen readers and keyboard navigation, and give you a prioritised report of what needs to be fixed. No vague recommendations. Every issue is documented with the criterion it violates and the fix required.
Ignited Nepal
Growth engineering · replies within 1 business day
By continuing you agree to our privacy policy.
