At Telefónica, we want everyone to enjoy the benefits of good clear communication. We are committed to helping improve accessibility by doing everything we can to make our services easier to use.
As part of our commitment to continuously improve the level of accessibility across all our websites, we have ensured that this site's design, navigation and functionality is available and inclusive, to all user groups, regardless of their location, internet experience, and type of technology used.
The website has been developed in line with the priority levels 1, 2 and two checkpoints in level 3 of the Web Accessibility Initiative (WAI) guidelines, part of the World Wide Web Consortium (W3C).
This section outlines some of the accessibility features that we have provided for users and guidance on how to use them. Please refer to your web browser and operating system 'Help' for their additional accessibility features.
Note: Conformance levels are notated in long-text so they may be understood when rendered to speech by screen readers.
| WCAG Checkpoint | WCAG Priority Level & Checkpoint Reference | |
|---|---|---|
| General statements | ||
| HTML code validates to published standards | Double A 3.2 | |
| XHTML code validates to published standards | Double A 3.2 | |
| CSS code validates to CSS standards | Double A 3.2 | |
| Absolute units are not used in markup language attribute values and style sheet property values | Double A 3.4 | |
| Equivalents for dynamic content are updated when the dynamic content changes | Single A 6.2 | |
| Dynamic content is accessible | Double A 6.5 | |
| The user can control screen flickering | Single A 7.1 | |
| The user can control content blinking | Double A 7.2 | |
| The user can control content movement | Double A 7.3 | |
| The user can control auto refreshing pages | Double A 7.4 | |
| Page redirects are preformed server side | Double A 7.5 | |
| Pop-ups and other windows are not used and do not change the current window without informing the user | Double A 10.1 | |
| The latest versions of World Wide Web Consortium (W3C) technologies have been used wherever appropriate | Double A 11.1 | |
| Depreciated features of W3C technologies have not been used | Double A 11.2 | |
| An accessible alternative has been provided where a page can not be made accessible | Single A 11.4 | |
| Metadata has been provided for each page | Double A 13.2 | |
| The clearest and simplest language appropriate for a site's content has been used | Single A 14.1 | |
| Images | ||
| A text alternative is available for images and multimedia presentations | Single A 1.1 | |
| A text link has been provided for each area of an image map | Single A 1.2 | |
| Text links are provided for each active region of a client-side image map | Triple A 1.5 | |
| Markup has been used, rather than images to convey information | Double A 3.1 | |
| It is possible to resize images | Double A 3.4 | |
| Client side server maps instead of server side image maps have been provided except where regions can not be defined with an available geometric shape | Single A 9.1 | |
| Colour | ||
| Information is available with and without colour | Single A 2.1 | |
| For images, foreground and background colours contrast sufficiently | Double A 2.2 | |
| For text, foreground and background colours contrast sufficiently | Triple A 2.2 | |
| Multimedia | ||
| An audio description is available for multimedia presentations | Single A 1.3 | |
| Synchronized alternatives are provided for time based multimedia presentations | Single A 1.4 | |
| Style sheets | ||
| Website layout and presentation is CSS controlled | Double A 3.3 | |
| Page can be read with CSS disabled | Single A 6.1 | |
| Text | ||
| The text can resize | Double A 3.4 | |
| User is informed if language changes | Single A 4.1 | |
| Document structure | ||
| Header elements are used to convey document structure | Double A 3.5 | |
| All list items are marked up and grouped correctly | Double A 3.6 | |
| Quotation markup is not used for formatting effects such as indentation | Double A 3.7 | |
| Large blocks of information are divided into manageable groups | Double A 12.3 | |
| Tables | ||
| For data tables, rows and column headers are identified | Single A 5.1 | |
| For data tables with 2 or more logical levels of row or column headers, data cells and header rows have been associated | Single A 5.2 | |
| Tables are not used for layout unless the table makes sense when linearised | Double A 5.3 | |
| If a table is used for layout, structural markup is not used for the purpose of visual formatting | Double A 5.4 | |
| Scripts | ||
| Page functionality work with scripts turned off | Single A 6.3 | |
| Event handlers for scripts are device independent | Double A 6.4 | |
| Non-functional programmatic elements are directly accessible/compatible with assistive technologies | Single A 8.1 | |
| Functional programmatic elements are directly accessible/compatible with assistive technologies | Double A 8.1 | |
| For scripts, logical event handlers have been specified rather than device dependant event handlers | Double A 9.3 | |
| Forms | ||
| Labels and form controls are associated and positioned correctly | Double A 10.2 | |
| Labels are asscoiated explicitly with their controls | Double A 12.4 | |
| Frames | ||
| Frames are clearly titled to facilitate identification and navigation | Single A 12.1 | |
| The purpose of frames and how they relate to each other has been described if it is not obvious by frame titles alone | Double A 12.2 | |
| Navigation | ||
| Page can be controlled in a device independent manner | Double A 9.2 | |
| A logical tab order through links, form controls and objects has been provided | Triple A 9.4 | |
| Link destination is clearly identified | Double A 13.1 | |
| A site map is available | Double A 13.3 | |
| Navigation is consistent through all pages | Double A 13.4 | |
![Telefónica : telefonica.com [external link]]](img/logo-telefonica.jpg)

![segala [external link]](img/logo-segala.gif)