Web Declaration of Conformity for the Double-A Accessibility Guidelines

With the aim of making the visitvalencia.com website as accessible as possible to users with disabilities, we are continually working to comply with the Dobel-A accessibility guidelines in accordance with WCAG2.1. 

To ensure that as many people as possible can use this website, we have programmed it so that users can make the following adjustments to the settings: 

 
•   Change colours, contrast levels, and fonts. 
•   Enlarge pages by up to 300% without the text spilling off the screen. 
•   Browse most of the website using only a keyboard. 
•   Browse most of the website using voice recognition software. 
•  Listen to most of the website using a screen reader. 

 

Declaration of Accessibility

The checks carried out have been done according to the Dobel-A accessibility guidelines in accordance with WCAG2.1. Significant pages of the website have been analysed following the Dobel-A accessibility guidelines according to WCAG2.1 and complying with priority 1 and priority 2 checkpoints. 

The results obtained have been unified, indicating non-compliance with the standard in the non-accessible content of this document. 

 

Compliance status

This website is partially compliant with R.D. 1112/2018 due to the exceptions and non-compliance of the aspects indicated below. 

Non-accessible content: 

The content below is not accessible due to the following: 

  • There is no alternative to the captchas used. 

Last updated: 13/11/20223

 

Comments and contact details

You can send notifications concerning accessibility requirements (article 10.2.a) of R.D. 1112/2018, such as, for example: 
• Report any possible non-compliance on the part of this website. 
• Report any other difficulties in accessing the content. 
• Make any other query or suggestion for improvement relating to the accessibility of the website. 

By any of the following means: 

• Sending an e-mail to accesibilidad @visitvalencia.com. 

Notifications will be received and processed by the person in charge of accessibility at the Visit Valencia website. 

Control points we are working on: 

Keyboard

The website is accessible via the keyboard, with no time limit for keystrokes. Keyboard shortcuts and similar elements do not conflict with the functionalities of the browser and/or screen reader. 

Focus

The user can move the focus through all navigable elements in a logical and orderly manner, using only the keyboard. The user can access and exit any component using only the tab key or the arrow keys.  

Focus reception 

There is no context switching when the focus is received by any component.  

Skipping blocks 

We allow skipping blocks of content that are repeated on multiple pages and navigation by headings. 

Varying text size 

We allow the user to vary the text size by up to 200% without losing content and functionality. Content text is readable and functional when enlarged up to 200% without the use of assisted technology. 

Contrast 

Text has a contrast ratio of 4.5:1. For large text (over 18 points or 14 points in bold) the contrast ratio is 3:1. 

Contrast in text images 

We use a contrast ratio in text images of at least 4.5:1. 

Analysis 

The page structure is adapted to XHTML syntax. Pages are developed with complete opening and closing tags, nested correctly, with no duplicate attributes and unique identifiers. Nested elements have correct opening/closing order, attribute values are always enclosed in quotes (single or double), element and attribute names are written in lower case, and we do not use the attribute name as a value. 

Custom components  

We follow XHTML specifications in developed or custom components by determining their name and role to be identified by users. 

Adaptability 

The contents are created to be presented in different ways without losing the information or its structure, ensuring that all the information is available so that it can be understood by all users and presented to users in different ways (visual, audible... keeping a logical browsing and reading order. 

To do this, we have used semantic markup to distinguish headings (h1,..., h6), lists (ul, ol) and text (strong, code, blockquote, etc.). We have also used tables to mark up tabular data, using "td" for data cells and "th" for headings. 

We have also associated "label" tags with their corresponding form fields and grouped them using "fieldset". 

Sensory features 

We do not use content only with sensory features such as shape, size, location, orientation, or sound, ensuring that all users can access instructions for use of the content, even when they cannot perceive shape, size, use over location or spatial orientation information. 

Use of colour 

We do not use colour as the sole means of conveying information.  

Adjustable time limit 

We do not offer time-limited content to perform a task. 

We set a title for all pages 

All pages have a title that describes their subject or purpose. 

We specify the page language 

The language of the page is specified within the html tag. 

Example: <html lang="es"> 

Pause, stop, hide 

We do not provide animated content that moves, flickers, scrolls, or auto-refreshes. 

Purpose of a link 

We write link texts in a way that makes sense with the link. 

Bug identification 

We inform the user through text and by identifying the specific item, of any errors automatically detected in the data entry. 

Tags or instructions 

We provide labels for data entry by the user. The different fields of a form contain descriptive labels for the elements they refer to, using the tag "label" and its "for" attribute. The grouping of fields and their labelling is done using the "fieldset" and "legend" tags respectively. 

Textual alternative  

We provide appropriate textual alternatives to all non-textual content. All images and non-textual content have an appropriate alternative text, which describes the information that can be seen in it. Images use the "alt" attribute. 

CAPTCHA 

We are currently working on providing two options for understanding this that address different senses and accommodate different disabilities. The CAPTCHA image has alternative text, and we are working on making it aim at its target. 

Flash 

We do not create Flash-based content. OR: We do not create flashing content.  

Subtitles 

Videos are embedded on YouTube and those with audio are subtitled in their original language. We provide a textual description of the video. 

Audio control 

We do not allow audios to play automatically on the web. The audios have a mechanism that allows you to start, pause or stop the recording and control the volume independently of the rest of the system. 

Access to content 

We offer direct ways to locate content through a list of related content, table of contents, site map, site search and listing of all content. 

Consistent browsing and identification 

We maintain the relative order of repeated browsing mechanisms on multiple pages. Browsing links that are repeated on multiple pages do not change their order when moving around the site. 

We maintain consistent identification on elements that have the same functionality across a set of pages. 

Error suggestions 

We provide the user with suggestions to automatically correct detected errors. When errors are detected when validating a form, we propose suggestions to help correct them.