Action report: Non-Resident Keralites' Affairs
Grade 2 — Act now: citizens cannot use the site Non-Resident Keralites Affairs (NORKA) Department — Page does not load successfully
Grade 2 — Act now: citizens cannot use the site Page does not load successfully
The server responded, but with an error instead of the page, or a chain of redirects that never arrives anywhere.
Light check 2026-11-19T05:18:05.311Z: http_404
How to fix: Check the server logs for the error status this request returned, and fix or shorten any redirect chain.
Grade 3 — Fix soon Norka Welfare Board (Kerala Non-Resident Keralites Welfare Board) — Page language is missing or wrong
Grade 3 — Fix soon Page language is missing or wrong
A screen reader needs to know what language the page is in to pronounce it correctly -- without this, a Malayalam page read aloud in an English voice is unintelligible.
<html lang="en-gb"> vs. 126% Malayalam content
How to fix: Set <html lang="ml"> (or the correct language) so it matches what the page actually contains.
Grade 3 — Fix soon Not on an official government domain
This site is on a .com/.org/.in/.net address rather than .gov.in/.nic.in/.kerala.gov.in/.ac.in/.edu.in. You cannot tell it apart from a phishing copycat by the address alone, and these domains can lapse and be bought by someone else.
pravasikerala.org
How to fix: Migrate to an official government domain (.gov.in/.nic.in via NIC, or .kerala.gov.in) as soon as practical.
Grade 3 — Fix soon Secure page loads insecure content
The page is served securely but pulls in some scripts, styles or images over an insecure connection, weakening the protection the padlock is supposed to mean.
href="http://keltron.org"
How to fix: Change every http:// resource reference on the page to https://.
Grade 4 — Plan a fix Serious accessibility violations
Automated testing found accessibility problems likely to make parts of this page difficult to use for some visitors.
24 serious violation(s)
How to fix: Fix the serious-impact violations an accessibility scanner reports.
Grade 4 — Plan a fix Text contrast is too low
Some text is hard to read against its background, especially for visitors with low vision or in bright sunlight on a phone.
20 low-contrast element(s)
How to fix: Darken text or lighten backgrounds until the contrast ratio meets WCAG AA (4.5:1 for normal text).
Grade 4 — Plan a fix Footer copyright year is old
The copyright year in the footer is at least two years out of date, a small but visible sign nobody has touched this site recently.
copyright year 2024
How to fix: Update the footer copyright year, ideally to update automatically each year.
Grade 4 — Plan a fix No content-ownership statement
There is no footer statement saying which department owns this content and who built/hosts the site, making it harder to tell an official site from an impersonation.
How to fix: Add a footer statement: "Content owned by <department> — Designed, developed & hosted by <agency>".
Grade 4 — Plan a fix No sitemap page
There is no page listing everything the site contains, making it harder to find something that isn't in the main menu.
How to fix: Add a human-readable sitemap page linking every major section.
Grade 4 — Plan a fix Main content is slow to appear
The largest visible element on the page (usually a heading or image) takes a long time to show up, which feels like the page is stuck.
42401.750499999966ms
How to fix: Optimise the largest above-the-fold image/element: compress it, size it correctly, and load it early.
Grade 4 — Plan a fix Homepage is very large to download
The homepage transfers an unusually large amount of data, which is slow and can be expensive on a limited mobile data plan.
48.1MB
How to fix: Compress images, remove unused scripts/styles, and enable gzip/br compression on the server.
Grade 5 — Minor Minor accessibility issues
Smaller accessibility issues were found; each on its own is unlikely to block anyone, but they add up.
37 moderate/minor violation(s)
How to fix: Work through the moderate/minor findings from an accessibility scanner as time allows.
Grade 5 — Minor Heading structure is missing or broken
Screen-reader users often jump between sections by heading level; a missing top-level heading or skipped levels make the page harder to navigate that way.
no <h1>, heading levels skipped
How to fix: Add one <h1> per page and use heading levels in order without skipping.
Grade 5 — Minor No meta description
Search engines have nothing useful to show as a summary of this page in search results.
How to fix: Add a concise <meta name="description"> summarising each page.
Grade 5 — Minor No Copyright Policy
There is no statement about who owns the content on this site and how it may be reused.
How to fix: Publish a Copyright Policy page.
Grade 5 — Minor No Disclaimer
There is no disclaimer covering the accuracy or official status of the information on this site.
How to fix: Publish a Disclaimer page.
Grade 5 — Minor No feedback mechanism
There is no way to send feedback about the site itself.
How to fix: Add a feedback form or a dedicated feedback email address.
Grade 5 — Minor No Screen Reader Access page
There is no page pointing screen-reader users to compatible software or usage tips for this site.
How to fix: Publish a Screen Reader Access page (GIGW's traditional term for this).
Grade 5 — Minor No Terms & Conditions / Terms of Use
There is no page setting out the terms for using this site.
How to fix: Publish a Terms of Use page.
Grade 5 — Minor No sitemap.xml
This helps search engines find every page on the site; without it, some pages may be harder to discover via search.
sitemap.xml returned 404
How to fix: Generate and serve a sitemap.xml, and reference it from robots.txt.
Grade 5 — Minor www and non-www versions are inconsistent
Depending on whether you type "www." or not, you might get a different result than expected instead of one consistently redirecting to the other.
How to fix: Pick one canonical form and make the other redirect to it.
Grade 5 — Minor Page layout jumps around while loading
Text and buttons shift position as the page finishes loading, which can make you tap the wrong thing.
0.89
How to fix: Reserve space (width/height) for images and ads before they load, instead of letting them push content around.
Grade 5 — Minor Images are uncompressed or oversized
Some images are far larger than they need to be for how they are displayed, slowing the page down for no visible benefit.
How to fix: Resize images to their display dimensions and compress them (WebP/AVIF where possible).
Grade 5 — Minor No Content-Security-Policy header
This is a technical defence-in-depth measure most visitors will never notice missing; it makes some attacks harder for the site to be tricked into if it ever has a bug.
How to fix: Add a Content-Security-Policy header, starting permissive and tightening it once nothing breaks.
Grade 3 — Fix soon Overseas Development and Employment Promotion Consultants Ltd (ODEPC) — Critical accessibility violations
Grade 3 — Fix soon Critical accessibility violations
Automated testing found serious accessibility problems that are very likely to block some visitors, such as screen-reader users, from using this page at all.
2 critical violation(s)
How to fix: Run an accessibility scanner (e.g. axe) and fix every critical-impact violation it reports first.
Grade 3 — Fix soon "Last updated" date is missing or very old
There's no visible sign of when this page was last reviewed, or the date shown is over a year old -- you can't tell whether the information is still current.
no "last updated" date found
How to fix: Show a genuine last-reviewed/updated date on every content page, and actually keep it current.
Grade 3 — Fix soon Uses a non-Unicode Malayalam font
This page uses an old-style Malayalam font (like ML-TTKarthika or ISM/Matweb) that only displays correctly if you happen to have that exact font installed -- for everyone else, the text is unreadable garbled characters.
ml-container
How to fix: Switch to a Unicode Malayalam font (e.g. Manjari, Noto Sans Malayalam) so the text reads correctly for everyone, with no font install required.
Grade 3 — Fix soon Plain http:// does not redirect to https://
If you type the address without "https", you land on the insecure version instead of being sent to the safe one automatically.
How to fix: Add a server-level redirect from http:// to https:// for every page, not just the homepage.
Grade 3 — Fix soon Uses a JavaScript library with a known vulnerability
The page loads a script library with a publicly known security flaw, which could let an attacker interfere with the page in your browser.
jquery 2.1.3, select2 4.0.0, jquery-validation 1.19.0, jquery-validation 1.19.0
How to fix: Update the affected library to a version without the known vulnerability.
Grade 4 — Plan a fix Serious accessibility violations
Automated testing found accessibility problems likely to make parts of this page difficult to use for some visitors.
15 serious violation(s)
How to fix: Fix the serious-impact violations an accessibility scanner reports.
Grade 4 — Plan a fix Text contrast is too low
Some text is hard to read against its background, especially for visitors with low vision or in bright sunlight on a phone.
7 low-contrast element(s)
How to fix: Darken text or lighten backgrounds until the contrast ratio meets WCAG AA (4.5:1 for normal text).
Grade 4 — Plan a fix Footer copyright year is old
The copyright year in the footer is at least two years out of date, a small but visible sign nobody has touched this site recently.
copyright year 2024
How to fix: Update the footer copyright year, ideally to update automatically each year.
Grade 4 — Plan a fix Uses obsolete web technology
This page uses old technology (Flash, Java applets, <marquee>/<blink>, frames) that modern browsers no longer support at all, so part of the page may simply not work.
<marquee
How to fix: Replace Flash/Java-applet content and framesets with modern HTML/CSS/JS equivalents.
Grade 4 — Plan a fix No Accessibility Statement
There is no page explaining the site's accessibility commitments or how to report an accessibility problem.
How to fix: Publish an Accessibility Statement with a way to report barriers.
Grade 4 — Plan a fix No last-updated date shown
There is no visible date telling you when the site (not just one page) was last updated.
How to fix: Show a site-wide last-updated date, typically in the footer.
Grade 4 — Plan a fix No content-ownership statement
There is no footer statement saying which department owns this content and who built/hosts the site, making it harder to tell an official site from an impersonation.
How to fix: Add a footer statement: "Content owned by <department> — Designed, developed & hosted by <agency>".
Grade 4 — Plan a fix No sitemap page
There is no page listing everything the site contains, making it harder to find something that isn't in the main menu.
How to fix: Add a human-readable sitemap page linking every major section.
Grade 4 — Plan a fix Main content is slow to appear
The largest visible element on the page (usually a heading or image) takes a long time to show up, which feels like the page is stuck.
15396.6735ms
How to fix: Optimise the largest above-the-fold image/element: compress it, size it correctly, and load it early.
Grade 4 — Plan a fix No HSTS header
The site does not tell browsers to always use the secure version, so a network attacker can sometimes still trick a browser into the insecure one.
How to fix: Add a Strict-Transport-Security header once HTTPS is confirmed working sitewide.
Grade 5 — Minor Minor accessibility issues
Smaller accessibility issues were found; each on its own is unlikely to block anyone, but they add up.
29 moderate/minor violation(s)
How to fix: Work through the moderate/minor findings from an accessibility scanner as time allows.
Grade 5 — Minor Heading structure is missing or broken
Screen-reader users often jump between sections by heading level; a missing top-level heading or skipped levels make the page harder to navigate that way.
heading levels skipped
How to fix: Add one <h1> per page and use heading levels in order without skipping.
Grade 5 — Minor JavaScript errors on load
The page's own code fails partway through loading, which can silently break some feature on the page without any visible error message.
11 console error(s): Failed to load resource: the server responded with a status of 404 ()
How to fix: Open the browser's developer console on this page and fix the reported script errors.
Grade 5 — Minor No Copyright Policy
There is no statement about who owns the content on this site and how it may be reused.
How to fix: Publish a Copyright Policy page.
Grade 5 — Minor No Disclaimer
There is no disclaimer covering the accuracy or official status of the information on this site.
How to fix: Publish a Disclaimer page.
Grade 5 — Minor No feedback mechanism
There is no way to send feedback about the site itself.
How to fix: Add a feedback form or a dedicated feedback email address.
Grade 5 — Minor No Help page
There is no page explaining how to use the site itself (navigation, search, common tasks).
How to fix: Publish a Help page.
Grade 5 — Minor No Hyperlinking Policy
There is no statement about how this site handles links to and from other websites.
How to fix: Publish a Hyperlinking Policy page.
Grade 5 — Minor No Screen Reader Access page
There is no page pointing screen-reader users to compatible software or usage tips for this site.
How to fix: Publish a Screen Reader Access page (GIGW's traditional term for this).
Grade 5 — Minor No site search
There is no way to search this site directly; you have to browse the menu to find anything.
How to fix: Add a site search facility.
Grade 5 — Minor No sitemap.xml
This helps search engines find every page on the site; without it, some pages may be harder to discover via search.
sitemap.xml returned 404
How to fix: Generate and serve a sitemap.xml, and reference it from robots.txt.
Grade 5 — Minor Images are uncompressed or oversized
Some images are far larger than they need to be for how they are displayed, slowing the page down for no visible benefit.
How to fix: Resize images to their display dimensions and compress them (WebP/AVIF where possible).
Grade 5 — Minor No Content-Security-Policy header
This is a technical defence-in-depth measure most visitors will never notice missing; it makes some attacks harder for the site to be tricked into if it ever has a bug.
How to fix: Add a Content-Security-Policy header, starting permissive and tightening it once nothing breaks.
Grade 5 — Minor No Referrer-Policy header
Without this, the full address of the page you came from (which can include personal details in a URL) may be leaked to other sites you click through to.
How to fix: Add a Referrer-Policy header, e.g. "strict-origin-when-cross-origin".
Grade 5 — Minor No X-Content-Type-Options header
A minor technical hardening header is missing; on its own this rarely affects you directly.
How to fix: Add "X-Content-Type-Options: nosniff".