Endesa Website Testing – Pilot Findings

Accessibility Testing

Browser Compatibility Testing

W3C Standard Mobile Compliance Testing

Pilot Performance Findings

| ©2013, Cognizant 2

Accessibility Testing –

http://www.endesa.com/

| ©2013, Cognizant 3

Accessibility Testing – Pilot Findings

Accessibility Testing ensures that differently abled people can also perceive, understand, navigate and contribute to the Web.

The goal is to evaluate the web application against standard Accessibility guidelines and to verify using assistive technology.

Service Offerings Testing Process Tools & Technologies Process Approach

• Section 508 Compliance Testing

o Includes testing that adheres to U.S. Section 508 Standards

that has been derived from the Rehabilitation Act of 1973

• WCAG 2.0 Compliance Testing

o Includes testing that adheres to WCAG 2.0(Web Content

Accessibility Guidelines) that has been devised from the

Disability Discrimination Act(1995)

• BITV Testing

o Includes testing that adhere to BITV( Barrier-free

Information Technology Ordinance) guidelines which is

based on the German law of equality for physically

challenged(BGG) thereby making internet pages barrier-free

for the disabled

• AccessiWeb Testing

o Includes testing that adheres to French AccessiWeb 1.0

'silver' standards that has been derived from WCAG 2.0

• Web Accessibility Toolbar –

To test the application

against accessibility

guidelines

• Assistive Technologies:

o JAWS Screen Reader

o Supernova Screen

Magnifier

• Manual & tool based

approach

• Test the application

against accessibility

guidelines (DDA

Compliance/

Section508/ WCAG1.0/

WCAG2.0/ AccessiWeb)

• Test the application

against the guidelines

formed explicitly for the

organization

Identify the accessibility guidelines

Test the application against accessibility guidelines

(WCAG/ Section 508/ DDA/ AccessiWeb) manually or

using tools

Validate the application using HTML and CSS validators

Test the application with assistive technologies (JAWS,

Super Nova…) supported

Report the accessibility issues identified

| ©2013, Cognizant 4

Accessibility Testing – Pilot Findings

According to WCAG 2.0 Guidelines 1.4.3(Contrast minimum), “Text and images of text should have a contrast ratio of at least 4.5:1.”

The highlighted foreground text and background colors have a low color contrast ratio of 1.61:1, making it difficult for people with low vision or color blindness to view the contents. Color contrast ratio is recommended to be at least 4:5:1.

| ©2013, Cognizant 5

Accessibility Testing – Pilot Findings

According to WCAG 2.0 Accessibility Guidelines 2.4.1 (Bypass Blocks) , “A link is provided to skip navigation and other page elements that are repeated across web pages.”

No link is provided to skip to the main contents. This creates difficulty for the users with motor disability, as they have to navigate through all the repeated elements highlighted in red across the webpage to reach the main content.

| ©2013, Cognizant 6

Browser Compatibility Testing –

http://www.endesa.com/

| ©2013, Cognizant 7

Browser Compatibility Testing – Overview

It is observed that font type is not the same in IE, Firefox and Chrome browsers for the content highlighted in red. It isrecommended that font type remains consistent across all browsers.

Font - Arial Size - 9

Font – CALIBRI (BODY) Size - 11

The tests have been performed on the browser versions mentioned below Ver. 8.0.7600.16385 Ver. 19.01084.52 Ver. 8.0

| ©2013, Cognizant 8

Browser Compatibility Testing – Overview

The print preview for the webpage across the three browsers (IE, Chrome and Mozilla), does not display all the contents of the webpage, as highlighted in red. The proper print preview should look like the page highlighted in green.

The tests have been performed on the browser versions mentioned below Ver. 8.0.7600.16385 Ver. 19.01084.52 Ver. 8.0

This is how the original webpage looks like

| ©2013, Cognizant 9

Mobile Testing –

http://www.endesa.com/

| ©2013, Cognizant 10

M-Web Checker – Cognizant Proprietary Tool

What it is?

• It is a window based tool which would check the compatibility

of web page for mobile browsers in accordance to W3C

standards.

• The tool evaluates a web page on various parameters and

provides a comprehensive ‘Mobile Compliance Report’

• The tool provides a detailed information on each and every

parameter of a web page to be rendered on a mobile device

• It would render the web page on an iPhone shell simulating a

real experience of browsing on a mobile device

• The tool also contains the HTML source code of the requested

Web Page

Benefits

• Provides the mobile web compatibility percentage with respect

to W3C mobile and cognizant standards

• Helps developers to do quick profiling during web page design

and quick compliance test for Test Engineers

o Points out the errors in a webpage and recommends

changes facilitating faster time to market Simulates how a

page would be rendered on a mobile browser

o Checks for HTTP response headers, encoding, media type,

doctype, page size, external resources, Embedded Scripts,

Caching, valid markup, stylesheet usage and Table usage

M-WebCheckerNormal WebSite

Test for compatibility

Loads the web page

Predict the website’s mobile Compliance %

Evaluates mobile compliant parameter

W3C standards

Mobile Compliance Report

1. Detailed Report on various W3C parameters

2. Provides HTML source code

3. Renders the website in an iPhone shell

How it Works?

| ©2013, Cognizant 11

M – Checker Report

Defect ID

Test Name Defect Description Recommendation

1 Caching This page does not contain Cache headersCaching reduces the need to reload resources, thus

saving download time and charges

2External resources

This page contains more than 20 External Resources

Number of External Resources should be less than 10

faster loading

3Image Dimensions

Quite a few images or objects do not have proper dimension specified

Dimensions of an image should be specified for proper

rendering

1

2

3

| ©2013, Cognizant 12

Performance Testing –

http://www.endesa.com/

| ©2013, Cognizant 13

Gomez - Last Mile Networks

• One or two critical pages of customer’s website (typically home page)

will be chosen for Last Mile POC tests

• Gomez has an intuitive web based interface to pick testing locations, associated

connection speeds to match customers needs and to execute tests

• Testing locations are chosen based on the customer’s base locations

• Requests for the chosen page(s) is submitted 2 to 3 times from the selected

locations with just single user. No concurrent load tests are conducted in

this case

• Response times are captured and plotted in the report

• Optionally, similar exercise can be repeated for customer’s competitor’s websites and performance comparison can be provided

How POC’s are conducted?

About Gomez

• Gomez has On-demand platform that can be

used to optimize the performance, availability,

and quality of the Web and mobile applications

• Cognizant has a strategic partnership with

Gomez in providing services related to

internet-based performance testing

About Last Mile Tests

• Last Mile testing is performed from a globally distributed panel of 12,000+ desktops

• Monitor Website Performance from different connection speeds across the globe

• Analyze Web page or transaction tests across multiple customer profiles

• View object and component-level data to the point-of-failure

• Identify geographic issues and issues across multiple connection speeds

| ©2013, Cognizant 14

Performance Outlook of Endesa Home Page

• This provides the response time for the Endesa home page while it is accessed from different locations• Gomez tool has been used to capture the page response time• Response times were captured for a single user and not multiple users• This will help to understand the end user performance of the application while it is accessed from different locations

(different bandwidth availability, latency)• Better network & lesser latency, better the response time

3.501s, TelefonicaMadrid, Spain

SAO PAULO, BRAZIL

17.781s, Level 3

ARGENTINA29.88, Telefonica

| ©2013, Cognizant 15

Comparison with Competitors Website

Competitors sites – Web Page Response Time & Page size comparison from Madrid, Spain

• The graph provides a performance comparison across other competitor sites and when those sites are accessed from Madrid, Spain

• Lesser the page size, better the response time

• Tunings can also be done to improve the performance such as browser caching, server caching, compress images though the page size cannot be reduced.

Logo URL

Endesa http://www.endesa.com/

The Performance assessment was done comparing Endesawebsite’s URL with three other leading Manufacturing Company’s URL’s

Competitor Site1

Competitor Site2

Competitor Site3

ENDESA

37.847

1.048

29.88

20.048

Response Time (Seconds)

Competitor Site1

Competitor Site2

Competitor Site3

ENDESA

1538.79

0.17

794.48

590.19

Page Size (KBytes)

| ©2013, Cognizant 16

Thank You!