I think accessibility was never a primary consideration during the design phase of this website. While there are serious accessibility issues across the entire website, I believe we should first highlight the ones that critically impact core functionality like the booking flow and payment experience, as well as widely used features such as PNR enquiry, train schedule, booking history, and ticket cancellation. If we plan to send a representation to CRIS and the Ministry of Railways, we should categorize the issues based on user impact, severity, and fixing priority so that the most critical problems are addressed first. For example, I really do not understand why they removed the functionality of manually typing the desired travel date, and I find serious accessibility issues with the calendar component they are using for this purpose. I think they are using a much older version, likely version 10 or earlier, of the PrimeNG p-calendar component with some custom styling overrides and Angular Reactive Forms integration. This calendar component has quite a lot of known accessibility issues. For example, missing accessible names for individual dates and the next and previous month buttons, no programmatic indication of disabled dates, no live region implementation to announce month and year changes, missing aria-selected state to indicate the current selection, missing essential ARIA attributes like aria-controls and aria-owns, and issues with basic keyboard interaction and focus management. They need to upgrade the PrimeNG p-calendar component to version 16 or later with the desired modifications for better accessibility. Alternatively, they can use any other accessible components, like NgxDatePickerComponent, Duet Date Picker or similar such components based on technical feasibility. Apart from the date picker, there are some other notable issues as well, like no information for screen reader users to indicate the specific days on which the train runs, missing heading tags for the trains to easily jump across the available options, no information about the selected travel date when navigating back to the trigger control, no prefix before the departure time, trip duration, and arrival time, a significant number of unlabelled controls on the Passenger Details screen, and missing tab focus and roles for the Edit and Delete passenger buttons, to name a few.
On Sat, Jul 18, 2026 at 7:55 AM Devender Singh <[email protected]> wrote: > Sir, > Post this review on irctc and railway ministry twitter page > > On Thu, 16 Jul, 2026, 7:20 pm Vaibhav Bhandari, < > [email protected]> wrote: > >> Hi everyone, >> >> I would like to add a few more accessibility related observations: >> 1. On the IRCTC eQuery interface (https://equery.irctc.co.in/), the >> combo-boxes for selecting categories and sub-categories are not labeled. >> Additionally, there is no option to report accessibility-specific issues >> under the website or mobile app categories. >> 2. The "Contact Us" dialogue box appears in the middle of the page >> directly after the navigation links, which is unusual compared to most >> websites where it typically appears at the top or bottom. >> Regarding where to send our representation, the email address for CRIS >> was not working when I last checked. We might want to try reaching out via >> their 24/7 helpline as a starting point. >> On a different note, I did not experience issues with the station >> selection combo-boxes. Typing a few letters of the station and navigating >> the filtered results with the Tab key worked well for me. While it differs >> from the traditional,simpler method of selecting combo-box options, I found >> it to be an interesting approach and a breath of fresh air to be fair 😀. >> >> >> On Thu, Jul 16, 2026 at 1:04 PM Zoher Kheriwala <[email protected]> wrote: >> >>> Hello, friends Asyou all are aware that IRCTC has launched its new >>> website for ticket booking, which is in beta form right now. I tried to use >>> this website and found following observation regarding accessibility. >>> >>> I found following issues regarding accessibility of the new website of >>> IRCTC. >>> 1. Identical page title for home page, log in page and post log in >>> booking page. This makes blind and cognitivedisabled to identify the >>> exact page they are on. >>> 2. Missing link for skip to main content. The skip to main content link >>> must be provided in header region for key board only user to bypass >>> repeated blocks. >>> 3. Missing h1. Heading level 1 which should be provided to main content >>> so screen reader users can jump to the main content directly. >>> 4. Inappropriate heading structure. The hierarchy of heading number is >>> not followed which may confuse screen reader user to navigate entire page. >>> 5. Missing list markup. List markup is missing for list of options >>> provided under navigation region >>> 6. Missing key board support for buttons under navigation region. The >>> buttons are not activated upon pressing enter on it. >>> 7. Missing instruction for mandatory fields. No instruction in text >>> format is provided saying that which fields are compulsory and which >>> are not. It makes specially cognitive user to fill form difficult. >>> 8. Incorrect selection of input field. The input field for from and to >>> station has given as combo box. After activating the combo box a screen >>> reader user doesn’t find directly the edit box to enter the station >>> name.to type the station name, he has to press enter again to expand >>> the text input and find matching results by pressing tabs. Instead of >>> using combo box a search box would be better option. >>> 9. Inaccessible date menu. The form field for date is in menu format >>> and screen reader don’t announce any thing after expanding that menu. >>> >>> These are some accessibility challenges I observed. As I could not >>> cross train search page, I could not find issues on other pages. >>> >>> I used Crome with jaws 23. >>> >>> -- >>> 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/CF1F4586-ECC5-460F-8D9D-D56F92F91332%40gmail.com >>> <https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/CF1F4586-ECC5-460F-8D9D-D56F92F91332%40gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> >> >> -- >> Thanks/regards: Vaibhav Bhandari >> >> -- >> 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/CADDLUp1FM9b6t87d_26t4q2VG40gqO5e5KzqvQb8yS8qs7kwVQ%40mail.gmail.com >> <https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/CADDLUp1FM9b6t87d_26t4q2VG40gqO5e5KzqvQb8yS8qs7kwVQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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/CACjo7_dSWtyyHaza9ErBVRpe1vPPXpwoCkA4EBec1RcK%3D_1HiA%40mail.gmail.com > <https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/CACjo7_dSWtyyHaza9ErBVRpe1vPPXpwoCkA4EBec1RcK%3D_1HiA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAPXdUpfEGhO4cYhhGGV52gGOk-gRcVY43uFdkXZmsv0g0U4KGw%40mail.gmail.com.
