Dear Access India Members, Thank you for highlighting the accessibility concerns with the new IRCTC beta website.
I fully support bringing this issue to the attention of CRIS and IRCTC. While introducing a modern interface is understandable, accessibility must remain a fundamental requirement throughout the design, development, testing, and deployment process. Unfortunately, based on the observations shared, the beta version appears to be a step backward compared to the existing website. >From a technical accessibility perspective, the following areas require immediate attention: · *Keyboard Accessibility:* Every interactive element, including buttons, links, form controls, and menus, must be fully operable using only the keyboard. Controls should respond correctly to the *Tab*, *Shift+Tab*, *Enter*, and *Spacebar* keys without requiring a mouse. · *Accessible Names and Labels:* All form fields, buttons, icons, and custom controls must have meaningful programmatic labels so that screen readers such as NVDA and JAWS can accurately announce their purpose. Unlabeled controls create significant barriers for blind users. · *Date Picker Accessibility:* The current calendar widget should either be fully keyboard and screen reader accessible or provide a simple editable date field that allows users to type the date directly in a supported format. This is a common accessibility practice adopted by many accessible web applications. · *Station Search Fields:* The "From" and "To" station fields should expose proper semantic information to assistive technologies. Auto-complete suggestions should be keyboard accessible, announced correctly by screen readers, and allow users to select options without relying on a mouse. · *Payment Workflow:* The payment gateway selection process should use standard HTML controls or accessible ARIA patterns. Focus order should remain logical, keyboard focus should always be visible and predictable, and dynamic content updates must be announced appropriately to screen readers. · *Compliance with Accessibility Standards:* The new website should conform to the *Web Content Accessibility Guidelines (WCAG) 2.2 Level AA*. In addition, it should follow *WAI-ARIA Authoring Practices* wherever custom widgets are implemented. Compliance should not only be verified through automated testing but also through comprehensive manual testing with assistive technologies. · *Compatibility with Assistive Technologies:* The website should be tested with commonly used screen readers, including NVDA, JAWS, Narrator, VoiceOver, and TalkBack, across major browsers such as Chrome, Firefox, and Microsoft Edge. As a Certified Web Accessibility Tester, I believe accessibility validation should include real users with disabilities throughout the development lifecycle. Automated tools can identify only a subset of accessibility issues. Practical usability testing by screen reader users is essential to ensure that critical tasks—such as logging in, searching for trains, selecting dates, entering passenger details, completing payments, and downloading tickets—can be performed independently. The existing IRCTC website has enabled many blind users to book railway tickets independently. Therefore, the new platform should preserve and enhance that level of accessibility rather than introducing new barriers. I sincerely hope CRIS treats this as a high-priority issue and engages with the disability community before making the beta website the default platform. Accessibility is not merely a compliance requirement; it is essential for ensuring equal access, independence, and digital inclusion for all users. Thank you for initiating this important discussion. Kind regards, Swagat Waghmare, On Tue, Aug 4, 2026 at 6:36 PM BHAWANI SHANKAR VERMA <[email protected]> wrote: > Hello accessindia! > > > At present, IRCTC has removed the CAPTCHA requirement at both the login > and booking stages of its website. I am not using the mobile > application, but it is important to note that the current website will > soon be phased out, as IRCTC is migrating to a new interface. A beta > version of this new website has already been launched. > The beta interface, however, fails to meet basic accessibility standards > for screen reader users: > Unlabeled or nonfunctional controls: Several buttons lack proper text > labels, and even those with labels are not operable via standard > keyboard inputs such as Enter or Spacebar. > Date input field: The date field is calendarbased, but the calendar > widget is not screen reader accessible. Users should be able to directly > type the date instead. > Station search fields: The “From” and “To” station search fields are > not accessible with screen readers, preventing independent use. > Payment page: The payment gateway selection process is not fully > accessible with JAWS or NVDA. Navigation and selection are cumbersome, > and only advanced users can manage it with difficulty. > These shortcomings represent a regression in accessibility compared to > the current website, where I, as a frequent traveler, am able to book > tickets independently. Due to the inaccessibility of the beta version, I > have refrained from using it further. > It is imperative that this matter be taken up strongly with CRIS, as > they are responsible for the development and maintenance of both the > current and beta versions of the IRCTC website. > > Bhawani > > -- > Disclaimer: > 1. Contents of the mails, factual, or otherwise, reflect the thinking of > the person sending the mail and AI in no way relates itself to its veracity; > > 2. AI cannot be held liable for any commission/omission based on the mails > sent through this mailing list.. > > > Search for old postings at: > http://www.mail-archive.com/[email protected]/ > --- > You received this message because you are subscribed to the Google Groups > "AccessIndia" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/c298c91d-6d5b-414f-adae-f022b5cd66f9%40gmail.com > . > -- Disclaimer: 1. Contents of the mails, factual, or otherwise, reflect the thinking of the person sending the mail and AI in no way relates itself to its veracity; 2. AI cannot be held liable for any commission/omission based on the mails sent through this mailing list.. Search for old postings at: http://www.mail-archive.com/[email protected]/ --- You received this message because you are subscribed to the Google Groups "AccessIndia" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/CAMufbjvMPfkqFRHorGQoBwiauPgM84%3DG382sqR-MygdP5uvpOA%40mail.gmail.com.
