Folks,
I just posted some feedback on IRCTC. would be writing more in due course. 
Meanwhile if you guys know anyone at IRCTC, please share. I did send to their 
care ID. 

Regards,
Srinivasu Chakravarthula | PayPal | @csrinivasu
Sent from my iPhone 5C

Begin forwarded message:

> From: Sai Gagan Accessibility Solutions <donotre...@wordpress.com>
> Date: 5 August 2014 22:58:55 IST
> To: sriniv...@srinivasu.org
> Subject: [New post] Accessibility Review – IRCTC Next Generation e-Ticketing 
> System – Part 1
> 
> 
> New post on Sai Gagan Accessibility Solutions
>                                                                               
>                 
> 
> Accessibility Review – IRCTC Next Generation e-Ticketing System – Part 1
> by SG Accessibility Solutions
> IRCTC has recently launched their next generation ticketing system and we 
> decided to post accessibility review in a two or more parts. Reason for 
> splitting into parts is that we would want IRCTC to fix problems in phased 
> manner and start with the main and popular section of the website - Booking a 
> train ticket!
> 
> Firstly, I congratulate IRCTC for their efforts to provide best possible 
> experience. For a long time we hear comments like "IRCTC is slow", "never 
> able to book tickets on IRCTC" and so on... and this next generation 
> ticketing system is really fast. I have used it for about last a month or so 
> and booked several tickets and never had a problem in terms of speed or 
> booking process.
> 
> So one problem is almost solved as far as booking process is concerned and 
> now I urge IRCTC to consider looking into accessibility aspect of the portal. 
> Below are some findings to start with:
> 
> Login Page
> Very difficult for keyboard users to reach login form: As we know login is 
> one of the popular section that a user would use. For a keyboard only users, 
> as of writing, it requires using tab key for 8 times. One way to resolve this 
> issue is by providing a same page link called Skip to Login at the top of the 
> page. The code would look something like this:
> At the top of the page: <a href="#login">Skip to login </a>
> Just before the login heading: <a name="login">
> Lack of heading structure: Though visually all sections appears to have 
> headings, they are not marked up with <heading> attributes thus assistive 
> technologies such as screen readers and search engines cannot identify these 
> headings.
> Associated labels are missing for form fields: Similar to headings, visually 
> one would see form labels but due to lack of "for" and "id" attributes, 
> association between <label> and <input> fields are missing. For a screen 
> reader user, it would be read something like "edit, edit, select" and so on...
> CAPTCHA: I know security is important and for such a large scale application, 
> definitely "yes"; however, currently there is no way on this site how 
> customers with vision impaired can solve this image based CAPTCHA. There 
> needs to be an alternative such as audio CAPTCHA and to address needs of 
> everyone, it would be recommended to have a text based CAPTCHA such as a math 
> question etc.,
> Search trains & book tickets
> Like mentioned above, it's very difficult for keyboard only users to reach 
> the booking form. It requires them to press tab key for 11 times to reach 
> booking form. Solution would be add "Skip to booking form" link at the top of 
> the page.
> Associated labels are missing for form fields: Similar to headings, visually 
> one would see form labels but due to lack of "for" and "id" attributes, 
> association between <label> and <input> fields are missing. For a screen 
> reader user, it would be read something like "edit, edit, select" and so on...
> Date picker: It's impossible for a keyboard only user as well as screen 
> reader users to use date picker. Firstly while pressing tab key, focus will 
> just skip the date picker field being it a read-only input field; thus it 
> cannot be used via keyboard. Solution would be let user enter the date either 
> manually or using date picker. Providing both options would be great. In 
> addition required date format can be notified.
> Radio buttons to select "general / ladies / tatkal" does not have associated 
> labels
> Appropriate labels are present to fill in passenger details - great! However, 
> a few fields like contact number are missing the associated labels
> Again, there needs to be an alternative for CAPTCHA on booking page
> I think if IRCTC could start fixing these issues, it would be really great! 
> In addition, it would be absolutely valuable to avoid table mark-up for 
> layout purposes; instead use CSS.
> 
> Dear IRCTC, you delivered a really fast and intuitive portal so please 
> consider looking into accessibility and it would be helpful to large number 
> of customers who are with disabilities. Thank you in advance.
> 
> Best,
> Srinivasu
> 
> SG Accessibility Solutions | August 5, 2014 at 10:57 pm | Tags: 
> accessibility, IRCTC | Categories: Web Accessibility | URL: 
> http://wp.me/p30sfG-5u
> Comment          See all comments
> Unsubscribe to no longer receive posts from Sai Gagan Accessibility Solutions.
> Change your email settings at Manage Subscriptions.
> 
> Trouble clicking? Copy and paste this URL into your browser: 
> http://sgaccessibility.com/sites/accessibility-review-irctc-next-generation-e-ticketing-system-part-1/
> 


Register at the dedicated AccessIndia list for discussing accessibility of 
mobile phones / Tabs on:
http://mail.accessindia.org.in/mailman/listinfo/mobile.accessindia_accessindia.org.in


Search for old postings at:
http://www.mail-archive.com/accessindia@accessindia.org.in/

To unsubscribe send a message to
accessindia-requ...@accessindia.org.in
with the subject unsubscribe.

To change your subscription to digest mode or make any other changes, please 
visit the list home page at
http://accessindia.org.in/mailman/listinfo/accessindia_accessindia.org.in


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..

Reply via email to