From 4c9408f79ed6ccf2b81c4cfaf73cb34cf4d25eb4 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Tue, 27 Jul 2021 11:33:49 -0400 Subject: Remove link title attributes thats just the href es (#1737) * remove link 'title' attributes that's just the 'href' (es) * a couple more --- .../how_to_build_custom_form_controls/index.html | 24 +++++++++++----------- .../forms/how_to_structure_a_web_form/index.html | 4 ++-- files/es/learn/forms/index.html | 2 +- .../sending_and_retrieving_form_data/index.html | 22 ++++++++++---------- files/es/learn/forms/styling_web_forms/index.html | 6 +++--- files/es/learn/forms/your_first_form/index.html | 4 ++-- 6 files changed, 31 insertions(+), 31 deletions(-) (limited to 'files/es/learn/forms') diff --git a/files/es/learn/forms/how_to_build_custom_form_controls/index.html b/files/es/learn/forms/how_to_build_custom_form_controls/index.html index 1f83cf0ad0..13687a21c5 100644 --- a/files/es/learn/forms/how_to_build_custom_form_controls/index.html +++ b/files/es/learn/forms/how_to_build_custom_form_controls/index.html @@ -36,7 +36,7 @@ original_slug: Learn/HTML/Forms/como_crear_widgets_de_formularios_personalizados
-

Nota: Mover el foco al rededor de la página generalmente se hace presionando la tecla de tabulación, pero este no es el estándar en todas partes. Por ejemplo, el ciclo a través de enlaces en una página se realiza en Safari de forma predeterminada usando la combinación combinación Opction+Tab.

+

Nota: Mover el foco al rededor de la página generalmente se hace presionando la tecla de tabulación, pero este no es el estándar en todas partes. Por ejemplo, el ciclo a través de enlaces en una página se realiza en Safari de forma predeterminada usando la combinación combinación Opction+Tab.

El widget está en su estado activo cuando:
@@ -81,9 +81,9 @@ original_slug: Learn/HTML/Forms/como_crear_widgets_de_formularios_personalizados

En nuestro ejemplo, las especificaciones faltantes son obvias, así que las manejaremos, pero puede ser un problema real en widgets nuevos y exóticos, para los cuales nadie tiene la menor idea de cuál es el comportamiento correcto. Por lo tanto, siempre es bueno pasar tiempo en esta etapa de diseño, porque si defines un comportamiento deficiente u olvidas definir uno, será muy difícil redefinirlo una vez que los usuarios se hayan acostumbrado. Si tiene dudas, solicite las opiniones de los demás y, si tiene el presupuesto para ello, no dude en realizar las pruebas de usuario. Este proceso se llama Diseño UX. Si desea obtener más información sobre este tema, debe consultar los siguientes recursos útiles:

@@ -311,7 +311,7 @@ original_slug: Learn/HTML/Forms/como_crear_widgets_de_formularios_personalizados
-

Note: Creating reusable widgets is something that can be a bit tricky. The W3C Web Component draft is one of the answers to this specific issue. The X-Tag project is a test implementation of this specification; we encourage you to take a look at it.

+

Note: Creating reusable widgets is something that can be a bit tricky. The W3C Web Component draft is one of the answers to this specific issue. The X-Tag project is a test implementation of this specification; we encourage you to take a look at it.

Why isn't it working?

@@ -323,7 +323,7 @@ original_slug: Learn/HTML/Forms/como_crear_widgets_de_formularios_personalizados
  • The script is not loading. This is one of the most common cases, especially in the mobile world where the network is not very reliable.
  • The script is buggy. You should always consider this possibility.
  • The script is in conflict with a third party script. This can happen with tracking scripts or any bookmarklets the user uses.
    • -
  • The script is in conflict with, or is affected by, a browser extension (such as Firefox's NoScript extension or Chrome's NotScripts extension).
    • +
  • The script is in conflict with, or is affected by, a browser extension (such as Firefox's NoScript extension or Chrome's NotScripts extension).
  • The user is using a legacy browser, and one of the features you require is not supported. This will happen frequently when you make use of cutting-edge APIs.
    • @@ -404,7 +404,7 @@ original_slug: Learn/HTML/Forms/como_crear_widgets_de_formularios_personalizados

    In the code we are about to build, we will use the standard DOM API to do all the work we need. However, although DOM API support has gotten much better in browsers, there are always issues with legacy browsers (especially with good old Internet Explorer).

    -

    If you want to avoid trouble with legacy browsers, there are two ways to do so: using a dedicated framework such as jQuery, $dom, prototype, Dojo, YUI, or the like, or by polyfilling the missing feature you want to use (which can easily be done through conditional loading, with the yepnope library for example).

    +

    If you want to avoid trouble with legacy browsers, there are two ways to do so: using a dedicated framework such as jQuery, $dom, prototype, Dojo, YUI, or the like, or by polyfilling the missing feature you want to use (which can easily be done through conditional loading, with the yepnope library for example).

    The features we plan to use are the following (ordered from the riskiest to the safest):

    @@ -679,7 +679,7 @@ window.addEventListener('load', function () {

    We have built something that works and though we're far from a fully-featured select box, it works nicely. But what we've done is nothing more than fiddle with the DOM. It has no real semantics, and even though it looks like a select box, from the browser's point of view it isn't one, so assistive technologies won't be able to understand it's a select box. In short, this pretty new select box isn't accessible!

    -

    Fortunately, there is a solution and it's called ARIA. ARIA stands for "Accessible Rich Internet Application", and it's a W3C specification specifically designed for what we are doing here: making web applications and custom widgets accessible. It's basically a set of attributes that extend HTML so that we can better describe roles, states and properties as though the element we've just devised was the native element it tries to pass for. Using these attributes is dead simple, so let's do it.

    +

    Fortunately, there is a solution and it's called ARIA. ARIA stands for "Accessible Rich Internet Application", and it's a W3C specification specifically designed for what we are doing here: making web applications and custom widgets accessible. It's basically a set of attributes that extend HTML so that we can better describe roles, states and properties as though the element we've just devised was the native element it tries to pass for. Using these attributes is dead simple, so let's do it.

    The role attribute

    @@ -731,7 +731,7 @@ window.addEventListener('load', function () { highlightOption(select, optionList[index]); }; -

    Here is the final result of all these changes (you'll get a better feel for this by trying it with an assistive technology such as NVDA or VoiceOver):

    +

    Here is the final result of all these changes (you'll get a better feel for this by trying it with an assistive technology such as NVDA or VoiceOver):

    @@ -756,9 +756,9 @@ window.addEventListener('load', function () {

    Here are a few libraries you should consider before coding your own:

    diff --git a/files/es/learn/forms/how_to_structure_a_web_form/index.html b/files/es/learn/forms/how_to_structure_a_web_form/index.html index e2a1a8efa9..1bde629579 100644 --- a/files/es/learn/forms/how_to_structure_a_web_form/index.html +++ b/files/es/learn/forms/how_to_structure_a_web_form/index.html @@ -41,7 +41,7 @@ original_slug: Learn/HTML/Forms/How_to_structure_an_HTML_form

    El elemento {{HTMLElement ("fieldset")}} es una forma cómoda de crear grupos de controles de formulario (también denominados widgets) que comparten el mismo propósito, con fines semánticos y de aplicación de estilo. Puedes etiquetar un elemento {{HTMLElement ("fieldset")}} incluyendo un elemento {{HTMLElement ("legend")}} justo debajo de la etiqueta de apertura {{HTMLElement ("fieldset")}}. El contenido textual del elemento {{HTMLElement ("legend")}} describe formalmente el propósito del elemento {{HTMLElement ("fieldset")}} que está incluido dentro.

    -

    Muchas tecnologías de asistencia utilizarán el elemento {{HTMLElement ("legend")}} como si fuera una parte de la etiqueta de cada control dentro del elemento {{HTMLElement ("fieldset")}} correspondiente. Por ejemplo, algunos lectores de pantalla como Jaws y NVDA leerán el contenido de la leyenda antes de decir la etiqueta de cada control.

    +

    Muchas tecnologías de asistencia utilizarán el elemento {{HTMLElement ("legend")}} como si fuera una parte de la etiqueta de cada control dentro del elemento {{HTMLElement ("fieldset")}} correspondiente. Por ejemplo, algunos lectores de pantalla como Jaws y NVDA leerán el contenido de la leyenda antes de decir la etiqueta de cada control.

    Un pequeño ejemplo:

    @@ -291,7 +291,7 @@ original_slug: Learn/HTML/Forms/How_to_structure_an_HTML_form

    Ver también

    {{PreviousMenuNext("Learn/Forms/Your_first_form", "Learn/Forms/Basic_native_form_controls", "Learn/Forms")}}

    diff --git a/files/es/learn/forms/index.html b/files/es/learn/forms/index.html index 6413d9490a..6343bb09b1 100644 --- a/files/es/learn/forms/index.html +++ b/files/es/learn/forms/index.html @@ -20,7 +20,7 @@ original_slug: HTML/HTML5/Forms_in_HTML5