Hi Vaishnavi, I did some similar collection of names, you can access the data at: https://github.com/konarkmodi/DigitalIndia - primarily for the purpose of doing analysis about adoption of security practices for government sites. Feel free to use the data if you find it relevant.
It was done in 2017, I can try and run the jobs again to collect a more recent list. -Konark On Mon, Mar 25, 2019 at 10:54 AM Vaishnavi Jayakumar < [email protected]> wrote: > Hi, > > At a PIL compliance hearing > <https://drive.google.com/open?id=1YkPoYZrqnf8rYd2LWfypGHl7_Yn9ASBf>, a > list was requested by Madras High Court judges. We have provided 105 as > lawyer had requested in the hope that through this engagement, we can push > through more sustainable change. > > I remember Sumandro and Srinivas Kodali working on collating the Govt > websites. Could I access that please? What I've attempted primarily from > goidirectory.nic.in is 11000+, with root domains at ~7k. > > Relevant extracts from the correspondence with lawyer are pasted below. > Please note the date for compliance with India's disability act is fast > approaching - 14th June 2019. > > ---------- Forwarded message --------- > From: Vaishnavi Jayakumar <[email protected]> > Date: Mon, 25 Mar 2019 at 15:03 > Subject: Re: Re website accessibility > > Here are 105 websites that would be a good mix to get started. Please note > that root domains have been provided, therefore both 'prefixes and > suffixes' > <https://moz.com/blog/understanding-root-domains-subdomains-vs-subfolders-microsites>would > need to be made accessible as per GIGW 2nd edition of 2018 > <http://dot.gov.in/sites/default/files/2018_06_21%20Endorsement%20GIGW%20Ed2%20to%20DoT%20Units.pdf> > . > > These are 3 entries where a root domain alone has not been provided - that > is because there are key services / apps on the URL linked which would also > need to be accessified : > > 1. digitalindia.gov.in/di-initiatives > 2. meity.gov.in/content/important-links > 3. mohua.gov.in/cms/schemes-or-programmes.php > > Two other entries have been highlighted. > > 1. MyGov.in > 2. PIB.gov.in > > MyGov.in and PIB.gov.in both need to be used as channels by the remaining > 10000+ > websites > <https://docs.google.com/spreadsheets/d/1leK799OxFSWOguYU31Ya_nfQYJ9tgG1TIlOxuA-uykI/edit?usp=sharing> > as it is humanly impossible to keep track of the various notices and public > consultations issued by different departments and ministries. C*onsultation > interfaces are best managed via mygov.in <http://mygov.in> ; and any type > of notice would benefit from media exposure and ensuing free publicity*. > As these 2 websites will be made compliant in the first tranche, it should > ensure that key information is being transmitted accessibly. > > *BACKGROUND TO PROBLEM* > > Currently the inaccessibility of websites and apps is a concern which is > growing day by day. Under the new law, the websites and apps have to be > made accessible by June 14, 2019. And the responsibility of making it sure > is upon the regulator / ministry. > > *VERIFIED IDENTITY & STANDARDISED OFFICIAL NAMING CONVENTIONS * > > There are over 10000 Govt websites in India, whether centre or state - no > list is available with government or any other body. Not all websites are > easily identifiable or verifiable as government websites because they are > not on the .gov.in domain or even on the .nic.in domain. It is therefore > difficult to distinguish between a phishing fake site and a government > site. This is also the case with social media identities of government > bodies where despite availability of official verification by service > providers like Facebook and Twitter, it is difficult to distinguish > between an actual government entity and a fake account whether on social > media or app store. > > Using a Gmail or a personal email id is growing - official email id > <http://mail.gov.in> could always be accessed with NIC's equivalent > <https://eoffice.gov.in/> of a convenient, quick office suite. Earlier > versions of websites cam be made part of the archives > <http://nationalarchives.nic.in/>. Additionally, if 3rd party software > needs to be used, preference should be given to Indian government > equivalents or FOSS - free open source software / formats / fonts. (Bhuvan > <https://bhuvan.nrsc.gov.in/> / OpenStreetMap instead of Google Maps), > EPUB instead of PDFs (which cannot render regional fonts correctly); CDAC's > Sakal Bharathi font /any OpenType Unicode > <http://egovstandards.gov.in/sites/default/files/Fonts-%20Standard%20Ver.1.0.pdfvs> > font vs Vanavil commercial proprietary font > <https://www.elcot.in/tamilfonts_download.php>. > > *ACCESSIBILITY IS DYNAMIC, CERTIFICATION IS STATIC* > > This certification exercise > <http://www.stqc.gov.in/content/website-quality-certification> could go > on endlessly because accessibility is not a one off. A day after receiving > certification a website update could result in a document upload of a > scanned PDF as an image file. To the sighted reader there will be nothing > externally wrong with the document. The blind reader using a screen reader > will not be able to read anything because what appears as text is actually > an image. > > With the Government's thrust on internet transactions, and in some cases, > internet-only transactions, accessibility becomes a non-negotiable issue. > When combined with the fad of having an app for any and every service, a > great deal of money is being spent on what is essentially false prestige! > > To save everybody's time and money, this is what needs to be done : > > *WAY AHEAD* > > 1) *Scrap the mobile apps for RESPONSIVE, LOCALIZED, OPEN web apps* - the > rate at which updates make apps incompatible require almost continuous > development which is financially not sustainable. Also, even the initial > releases of these apps are inaccessible - for eg. something as crucial as > the BHIM app. > > The growing trend of website access via ubiquitous ‘always-on’ economical > mobile devices has led towards increasing appification of the government - > public service interface has taken place resulting in a dated, distributed, > incomplete, unresponsive, monolingual inaccessible website + mobile app > ecosystem. > Instead as the UK government has decided - focus on a *responsive* > website which can be viewed on all devices and can be equally usable > whether a basic phone or a dialup connection. > > 2) NIC to create and offer in collaboration with IGNOU / Skill India - a > *certified > course in website accessibility *(it could be on the lines of DEQUE's > offering for example) > <https://dequeuniversity.com/curriculum/online-classes/> as a > pre-requirement for agencies to get trained, tested and empanelled as > website developers. Only certified agencies to be allowed to bid for > tenders during the procurement process. > > 3) A free online tool to be created by NIC to check *GIGW compliance in > addition to WCAG 2AA accessibility standards, multimedia and document > accessibility*. This will help the average website manager to ensure that > updates do not affect the accessibility. > > 4) Every website to have *1 stop point content* that is now increasingly > being shared over diverse channels like social media with the result that > there is no one place where one is assured of an accessible, usable > experience. Content is outdated with citizen's charters and proactive > information disclosure remaining frozen in time for close to a decade. Date > last updated and content review date need to be provided as a rule. > > 5) An entire revamp would be required with a* single point of contact > *displayed > prominently to escalate issues and track complaint resolution > <http://bit.ly/want2report-form> when a citizen is unable to use a > government web-enabled service due to lack of accessibility. This would > require some *accountability* as an experience with Niti Aayog brought to > light - it could not be escalated as the appellate officer was the primary > offender in unhelpfulness in making a public document usable despite > assurances in the media. > > 6) Future procurement to be standardised for bilingual integrated > responsive website with regional language incorporation (and other > localisation including official ready-to-go- tools > <http://localization.gov.in> as an interim measure) and GIGWv2, 2018 > compliance. Eg CAG.gov.in recent tender > <https://cag.gov.in/sites/default/files/tenders/RFP_CAG_WEB.pdf> can be > referred. All designed-for-publication soft copies must be accompanied with > a plain text, bookmarked alternative. > > 7) All laws and policies to be accompanied by regional, plain language > accessible versions. Process of information retrieval needs to acknowledge > lay person as lowest common denominator and document / policy change > tracking needs to include soft copy technology to hard copy print methods. > >> -- > Datameet is a community of Data Science enthusiasts in India. Know more > about us by visiting http://datameet.org > --- > You received this message because you are subscribed to the Google Groups > "datameet" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Datameet is a community of Data Science enthusiasts in India. Know more about us by visiting http://datameet.org --- You received this message because you are subscribed to the Google Groups "datameet" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
