As promised here is the continuation for my previous post Accessibility of IRCTC registration. Before reading this post its worth having a look at the previous part.
Booking a ticket –Home
- No mechanism to jump to the main content of the page including HTML headings. User has to navigate through the entire top navigation links and come to the form.
As per WCAG 2.0 SC “2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
- No form field have a label. The form elements such as From, To Date, Ticket Type and Quota should have a label tag and the label should be associated with the input field with “for†and “id†attributes.
As per WCAG 2.0 SC 3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input.
Example: <label for=”source”>From</label>
<input type=”text” id=”source” size=”22″ /> - Calendar is opened automatically when the user focus on the calendar icon While using tab key to navigate the web page. User should be given the opportunity to open the calendar instead of opening automatically.
As per WCAG 2 .0 SC 3.2.1 On Focus: When any component receives focus, it does not initiate a change of context.
- Once the find trains button is clicked the list of the trains are provided in a tabular format. The table is completely inaccessible. The data table do not have a caption tag or summary attribute, headers are not associated with their corresponding rows and columns. It is a real challenge to check the exact coach against the train.
As per WCAG 2.0 SC 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
- Once the required train and coach is selected by checking the radio button the availability is shown on some other portion of the page. User is not given an option to confirm the selection or no intimation is provided to let the user know that the availability and book button are shown on the page.
As per WCAG 2.0 3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
Ticket Reservation Page
- A level 3 heading is provided for the user to jump directly to the main content. <h3>Ticket Reservation</h3>. As per the accessibility standards the main heading of the page should be level one. Unfortunately the next heading Passenger details is also level 3.
As per WCAG 2.0 SC 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
- For the passenger list a tabular form is provided. No form field is provided with labels and the association of labels with their corresponding inputs are available. This issue is already discussed in the previous page.
- This page contains the inaccessible CAPTCHA. CAPTCHA is discussed clearly in “IRCTC registration page.
Ticket Confirmation Page
The main heading level 3 “Ticket reservation” should be changed to more appropriate heading such as “Confirm Ticket Details”. The headings “passenger details” and “Ticket details” are also in h3 which is not appropriate.
Make payment page
- No headings are available in the page. It will take a while for the user to find the various payment options that are available in the page.
- Once the appropriate option eg: Credit card or Debit card or mobile /internet banking is selected the corresponding banks are provided in the same page. No intimation is provided to the user regarding the same.
- Once the bank is checked the user is redirected to the login page of that particular bank without any intimation.
Another vital accessibility problem in the website is logout from the website after a period of inactivity. No intimation is provided to the user that the session will be expired after a certain period of inactivity or no warning is provided before signing out. No option is provided for the user to extend the time limit.
As per WCAG 2.0 SC 2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true:
- Turn off: The user is allowed to turn off the time limit before encountering it; or
- Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
- Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, “press the space bar”), and the user is allowed to extend the time limit at least ten times; or
- Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible ;or
- Essential Exception: The time limit is essential and extending it would invalidate the activity ;or
- 20 Hour Exception: The time limit is longer than 20 hours.
In the continuation post I will map the WCAG 2.0 level A guidelines that are violated by IRCTC website.