aboutsummaryrefslogtreecommitdiff
path: root/files/pt-pt/web/accessibility/aria
diff options
context:
space:
mode:
authorRyan Johnson <rjohnson@mozilla.com>2021-04-29 16:16:42 -0700
committerGitHub <noreply@github.com>2021-04-29 16:16:42 -0700
commit95aca4b4d8fa62815d4bd412fff1a364f842814a (patch)
tree5e57661720fe9058d5c7db637e764800b50f9060 /files/pt-pt/web/accessibility/aria
parentee3b1c87e3c8e72ca130943eed260ad642246581 (diff)
downloadtranslated-content-95aca4b4d8fa62815d4bd412fff1a364f842814a.tar.gz
translated-content-95aca4b4d8fa62815d4bd412fff1a364f842814a.tar.bz2
translated-content-95aca4b4d8fa62815d4bd412fff1a364f842814a.zip
remove retired locales (#699)
Diffstat (limited to 'files/pt-pt/web/accessibility/aria')
-rw-r--r--files/pt-pt/web/accessibility/aria/aria_techniques/index.html215
-rw-r--r--files/pt-pt/web/accessibility/aria/aria_techniques/using_the_status_role/index.html83
-rw-r--r--files/pt-pt/web/accessibility/aria/index.html123
3 files changed, 0 insertions, 421 deletions
diff --git a/files/pt-pt/web/accessibility/aria/aria_techniques/index.html b/files/pt-pt/web/accessibility/aria/aria_techniques/index.html
deleted file mode 100644
index 34fa824f8c..0000000000
--- a/files/pt-pt/web/accessibility/aria/aria_techniques/index.html
+++ /dev/null
@@ -1,215 +0,0 @@
----
-title: 'Using ARIA: Roles, states, and properties'
-slug: Web/Accessibility/ARIA/ARIA_Techniques
-tags:
- - ARIA
- - Accessibility
- - NeedsTranslation
- - Overview
- - Reference
- - TopicStub
-translation_of: Web/Accessibility/ARIA/ARIA_Techniques
----
-<p class="summary">ARIA defines semantics that can be applied to elements, with these divided into <strong>roles</strong> (defining a type of user interface element) and <strong>states</strong> and <strong>properties</strong> that are supported by a role. Authors must assign an ARIA role and the appropriate states and properties to an element during its life-cycle, unless the element already has appropriate ARIA semantics (via use of an appropriate HTML element). Addition of ARIA semantics only exposes extra information to a browser's accessibility API, and does not affect a page's DOM.</p>
-
-<h2 id="Roles">Roles</h2>
-
-<h3 id="Widget_roles">Widget roles</h3>
-
-<div class="index">
-<ul>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/button_role" title="Using the button role">button</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/checkbox_role" title="Using the checkbox role">checkbox</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Gridcell_Role">gridcell</a></li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_link_role" title="Using the Link role">link</a></li>
- <li>menuitem</li>
- <li>menuitemcheckbox </li>
- <li>menuitemradio</li>
- <li>option</li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_progressbar_role" title="en/ARIA/ARIA_Techniques/Using_the_progressbar_role">progressbar</a></li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_radio_role" title="en/ARIA/ARIA_Techniques/Using_the_radio_role">radio</a></li>
- <li>scrollbar</li>
- <li>searchbox</li>
- <li>separator (when focusable)</li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_slider_role" title="en/ARIA/ARIA_Techniques/Using_the_slider_role">slider</a></li>
- <li>spinbutton</li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Switch_role">switch</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Tab_Role">tab</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Tabpanel_Role">tabpanel</a></li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_textbox_role" title="en/ARIA/ARIA_Techniques/Using_the_textbox_role">textbox</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Treeitem_Role">treeitem</a></li>
-</ul>
-</div>
-
-<h3 id="Composite_roles">Composite roles</h3>
-
-<p>The techniques below describe each composite role as well as their required and optional child roles.</p>
-
-<div class="index">
-<ul>
- <li>combobox</li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Grid_Role">grid</a> (including <a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Row_Role">row</a>, <a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Gridcell_Role">gridcell</a>, rowheader, columnheader roles)</li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_listbox_role" title="en/ARIA/ARIA_Techniques/Using_the_listbox_role">listbox</a> (including option role)</li>
- <li>menu</li>
- <li>menubar</li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_radio_role" title="en/ARIA/ARIA_Techniques/Using_the_radio_role">radiogroup (see radio role)</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Tablist_Role">tablist</a> (including <a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Tab_Role">tab</a> and <a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Tabpanel_Role">tabpanel</a> roles)</li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Tree_Role">tree</a></li>
- <li>treegrid</li>
-</ul>
-</div>
-
-<h3 id="Document_structure_roles">Document structure roles</h3>
-
-<div class="index">
-<ul>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Application_Role">application</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Article_Role" title="en/Accessibility/ARIA/ARIA_Techniques/Using_the_article_role">article</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Cell_Role">cell</a></li>
- <li>columnheader</li>
- <li>definition</li>
- <li>directory</li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Document_Role">document</a></li>
- <li>feed</li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Figure_Role">figure</a></li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_group_role" title="en/ARIA/ARIA_Techniques/Using_the_group_role">group</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/heading_role">heading</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Role_Img">img</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/List_role">list</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Listitem_role">listitem</a></li>
- <li>math</li>
- <li>none</li>
- <li>note</li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_presentation_role" title="en/ARIA/ARIA_Techniques/Using_the_presentation_role">presentation</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Row_Role">row</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Rowgroup_Role">rowgroup</a></li>
- <li>rowheader</li>
- <li>separator</li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Table_Role">table</a></li>
- <li>term</li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/textbox_role">textbox</a></li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_toolbar_role" title="en/ARIA/ARIA_Techniques/Using_the_toolbar_role">toolbar</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Tooltip_Role">tooltip</a></li>
-</ul>
-</div>
-
-<h3 id="Landmark_roles">Landmark roles</h3>
-
-<div class="index">
-<ul>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_banner_role" title="en/ARIA/ARIA_Techniques/Using_the_banner_role">banner</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Complementary_role">complementary</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Contentinfo_role">contentinfo</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Form_Role">form</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Main_role">main</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Navigation_Role">navigation</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Region_role">region</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Search_role">search</a></li>
-</ul>
-</div>
-
-<h3 id="Live_Region_Roles">Live Region Roles</h3>
-
-<div class="index">
-<ul>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/Alert_Role">alert</a></li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_log_role" title="Using the Log role">log</a></li>
- <li>marquee</li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_status_role" title="Using the link role">status</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/ARIA_timer_role">timer</a></li>
-</ul>
-</div>
-
-<h3 id="Window_Roles">Window Roles</h3>
-
-<div class="index">
-<ul>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_alertdialog_role">alertdialog</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Roles/dialog_role">dialog</a></li>
-</ul>
-</div>
-
-<h2 id="States_and_properties">States and properties</h2>
-
-<h3 id="Widget_attributes">Widget attributes</h3>
-
-<div class="index">
-<ul>
- <li>aria-autocomplete</li>
- <li>aria-checked</li>
- <li>aria-current</li>
- <li>aria-disabled</li>
- <li>aria-errormessage</li>
- <li>aria-expanded</li>
- <li>aria-haspopup</li>
- <li>aria-hidden</li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-invalid_attribute" title="Using the aria-invalid attribute">aria-invalid</a></li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-label_attribute" title="Using the aria-labelledby attribute">aria-label</a></li>
- <li>aria-level</li>
- <li>aria-modal</li>
- <li>aria-multiline</li>
- <li>aria-multiselectable</li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-orientation_attribute" title="en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-orientation_attribute">aria-orientation</a></li>
- <li>aria-placeholder</li>
- <li>aria-pressed</li>
- <li>aria-readonly</li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-required_attribute" title="Using the aria-required property">aria-required</a></li>
- <li>aria-selected</li>
- <li>aria-sort</li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-valuemax_attribute" title="Using the aria-required attribute">aria-valuemax</a></li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-valuemin_attribute" title="en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-valuemin_attribute">aria-valuemin</a></li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-valuenow_attribute" title="en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-valuenow_attribute">aria-valuenow</a></li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-valuetext_attribute" title="en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-valuetext_attribute">aria-valuetext</a></li>
-</ul>
-</div>
-
-<h3 id="Live_region_attributes">Live region attributes</h3>
-
-<div class="index">
-<ul>
- <li>aria-live</li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-relevant_attribute" title="en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-relevant_attribute">aria-relevant</a></li>
- <li>aria-atomic</li>
- <li>aria-busy</li>
-</ul>
-</div>
-
-<h3 id="Drag_drop_attributes">Drag &amp; drop attributes</h3>
-
-<div class="index">
-<ul>
- <li>aria-dropeffect</li>
- <li>aria-dragged</li>
-</ul>
-</div>
-
-<h3 id="Relationship_attributes">Relationship attributes</h3>
-
-<div class="index">
-<ul>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-activedescendant_attribute" title="Role">aria-activedescendant</a></li>
- <li>aria-colcount</li>
- <li>aria-colindex</li>
- <li>aria-colspan</li>
- <li>aria-controls</li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-describedby_attribute" title="Using the aria-labelledby attribute">aria-describedby</a></li>
- <li><a href="/en-US/docs/Web/Accessibility/ARIA/Annotations#Associating_annotated_elements_with_their_details">aria-details</a></li>
- <li>aria-errormessage</li>
- <li>aria-flowto</li>
- <li><a href="/en/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-labelledby_attribute" title="en/ARIA/ARIA_Techniques/Using_the_aria-labelledby_attribute">aria-labelledby</a></li>
- <li>aria-owns</li>
- <li>aria-posinset</li>
- <li>aria-rowcount</li>
- <li>aria-rowindex</li>
- <li>aria-rowspan</li>
- <li>aria-setsize</li>
-</ul>
-</div>
-
-<h3 id="MicrosoftEdge-specific_properties">MicrosoftEdge-specific properties</h3>
-
-<div class="index">
-<ul>
- <li><a href="/en-US/docs/Web/API/x-ms-aria-flowfrom">x-ms-aria-flowfrom</a> {{Non-standard_Inline}}</li>
-</ul>
-</div>
diff --git a/files/pt-pt/web/accessibility/aria/aria_techniques/using_the_status_role/index.html b/files/pt-pt/web/accessibility/aria/aria_techniques/using_the_status_role/index.html
deleted file mode 100644
index 300b0906fc..0000000000
--- a/files/pt-pt/web/accessibility/aria/aria_techniques/using_the_status_role/index.html
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: Utilizar o role status
-slug: Web/Accessibility/ARIA/ARIA_Techniques/Using_the_status_role
-tags:
- - ARIA
- - Acessibilidade
- - RequerConteúdo
-translation_of: Web/Accessibility/ARIA/ARIA_Techniques/Using_the_status_role
-original_slug: Web/Accessibility/ARIA/ARIA_Techniques/Usando_o_role_status
----
-<h3 id="Descrição">Descrição</h3>
-
-<p class="p1">Esta técnica demonstra como usar o <em>role</em> <em><a class="external" href="https://www.w3.org/TR/wai-aria-1.1/#status">status</a>,</em> e descreve ainda o seu impacto em browsers e tecnologia assistiva.</p>
-
-<p class="p1">O <em>role</em> <em>status </em>é um tipo de <em><a class="external" href="http://www.w3.org/WAI/PF/aria/terms#def_liveregion">live region</a></em> para avisos que não são suficientemente importantes para constarem de um <em><a class="external" href="https://www.w3.org/TR/wai-aria-practices/#alert">alert</a>.</em> Tais avisos são normalmente apresentados como uma barra de estado. Quando o <em>role</em> é adicionado ao elemento, o <em>browser</em> envia um evento de estado para produtos de tecnologia assitiva, que por sua vez podem alertar o utilizador.</p>
-
-<p class="p1">Informação de <em>status</em> tem de ser fornecida num objeto de <em>status</em>, objeto este que não deve poder ser focado. Se outra parte da página controla o que aparece como <em>status</em>, deve-se utilizar o atributo <a class="external" href="http://www.w3.org/TR/wai-aria/states_and_properties#aria-controls">aria-controls</a> para relacionar essa parte da página com o objeto de <em>status</em>.</p>
-
-<p class="p1">Produtos de tecnologias assistiva podem reservar determinadas células de uma tela Braille para exibir o <em>status</em>.</p>
-
-<h3 id="Possível_impacto_em_user_agents_e_tecnologia_assistiva">Possível impacto em <em>user agents</em> e tecnologia assistiva </h3>
-
-<p class="p1">Quando o <em>role status </em>é adicionado a um elemento, ou quando esse elemento fica visível, o <em>user agent</em> deve:</p>
-
-<ul class="ul1">
- <li class="li2">Expôr o elemento como tendo um <em>role</em> de <em>status</em> através da API de acessibilidade do sistema operativo. </li>
- <li class="li2">Emitir um evento <em>status</em> acessível através da API de acessibilidade do sistema operativo, se possível.</li>
-</ul>
-
-<p class="p1">Produtos de tecnologia assistiva devem captar o evento de estado e notificar o utilizador adequadamente:</p>
-
-<ul class="ul1">
- <li class="li2">Leitores de ecrã (<em>screen readers</em>) podem implementar uma tecla especial para anunciar o <em>status</em> atual, apresentando assim o conteúdo de uma <em>live region</em> de <em>status</em>. Estes devem ser anunciados apenas quando o utilizador está inativo, a menos que se tenha definido o atributo <em><span class="s1">aria-live=”assertive”</span></em><span class="s1">,</span> caso em que o utilizador pode ser interrompido. </li>
- <li class="li2">Ampliadores de ecrã (<em>screen magnifiers</em>) poderão aumentar o tamanho do <em>status</em>.</li>
-</ul>
-
-<div class="note"><strong>Nota:</strong> Opiniões sobre como produtos de tecnologia assistiva lidam com esta técnica podem variar. A informação acima é apenas uma dessas opiniões, pelo que não pode ser considerada normativa.</div>
-
-<h3 id="Exemplos">Exemplos</h3>
-
-<h4 id="Exemplo_1_Adicionar_o_role_status_em_HTML">Exemplo 1: Adicionar o <em>role</em> <em>status</em> em HTML</h4>
-
-<p class="p1">O <em>snippet</em> em baixo mostra como se pode adicionar o <em>role </em>de <em>status</em> diretamente em código HTML. </p>
-
-<pre class="brush: html notranslate">&lt;p role="status"&gt;Your changes were automatically saved.&lt;/p&gt; </pre>
-
-<h4 id="Exemplos_a_Correr">Exemplos a Correr:</h4>
-
-<ul>
-</ul>
-
-<h3 id="Notas">Notas </h3>
-
-<h3 id="Atribuos_ARIA_utilizados">Atribuos ARIA utilizados</h3>
-
-<ul>
- <li class="p1"><a class="external" href="https://www.w3.org/TR/wai-aria-1.1/#status">status</a></li>
-</ul>
-
-<h3 id="Técnicas_ARIA_relacionadas">Técnicas ARIA relacionadas </h3>
-
-<ul>
- <li class="p1"><a class="external" href="https://www.w3.org/TR/wai-aria-practices/#alert">o <em>role alert</em></a></li>
- <li class="p1"><a href="https://www.w3.org/TR/wai-aria-1.1/#live_region_roles"><em>Roles </em>de <em>Live Region</em></a></li>
- <li class="p1"><a href="https://www.w3.org/TR/wai-aria-1.1/#attrs_liveregions">Atributos de <em>Live Region</em></a></li>
-</ul>
-
-<h3 id="Compatibilidade">Compatibilidade</h3>
-
-<ul>
- <li class="comment">
- <p>The Paciello Group publicou dados sobre da compatibilidade deste <em>role</em> num artigo de 2014: <em><a href="https://developer.paciellogroup.com/blog/2014/03/screen-reader-support-aria-live-regions/">Screen reader support for ARIA live regions</a></em></p>
- </li>
- <li class="comment">
- <p>A determinar: Adicionar informação atualizada sobre combinações comuns de produtos de tecnologia assistiva com<em>user agents</em></p>
- </li>
-</ul>
-
-<h3 id="Mais_recursos">Mais recursos</h3>
-
-<ul>
- <li class="p1">Recomendações anteriores da <a href="https://www.w3.org/TR/wai-aria-1.1/#status">WAI-ARIA 1.0 (2014)</a> para o <em>role</em> <em>status</em></li>
-</ul>
diff --git a/files/pt-pt/web/accessibility/aria/index.html b/files/pt-pt/web/accessibility/aria/index.html
deleted file mode 100644
index 3544038b4b..0000000000
--- a/files/pt-pt/web/accessibility/aria/index.html
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: ARIA
-slug: Web/Accessibility/ARIA
-tags:
- - ARIA
- - Acessibilidade
- - Web
-translation_of: Web/Accessibility/ARIA
-original_slug: Web/Acessibilidade/ARIA
----
-<p><span class="seoSummary"><em>Accessible Rich Internet Applications</em> <strong>(ARIA)</strong> </span> define as maneiras para tornar o conteúdo da Web e aplicações da Web (especialmente aqueles desenvolvidos com Ajax e JavaScript) mais acessíveis para as pessoas com deficiência. Por exemplo, ARIA permite marcos de navegação acessíveis, widgets de JavaScript, dicas de formulário e mensagens de erro, atualizações de conteúdo <em>live</em> e muito mais.</p>
-
-<p>ARIA é um conjunto de atributos de acessibilidade especiais que podem ser adicionados a qualquer marcação, mas é especialmente adequado para HTML. . O atributo <code>role</code> define que tipo geral de objeto é (tais como um artigo, alerta, ou cursor). Os atributos ARIA adicionais fornecem outras propriedades úteis, tais como uma descrição para um formulário ou o valor atual de uma barra de progresso.</p>
-
-<p>ARIA é implementado na maioria dos navegadores populares e leitores de ecrã. No entanto, as implementações variam e as tecnologias mais antigas não o suportam bem (se for o caso). Utilize ARIA 'seguro' que se degrada graciosamente, ou peça aos utilizadores que atualizem para a nova tecnologia.</p>
-
-<div class="note">
-<p><strong>Nota</strong>: por favor, contribua e melhore ARIA para a próxima pessoa! Não tem tempo? Envie as sugestões para a <a href="https://lists.mozilla.org/listinfo/accessibility">lista de endereços de acessibilidade da </a> Mozilla, ou canal <a href="https://wiki.mozilla.org/IRC">IRC</a> #accessibility.</p>
-</div>
-
-<div class="row topicpage-table">
-<div class="section">
-<h3 id="Iniciação_com_ARIA">Iniciação com ARIA</h3>
-
-<dl>
- <dt><a href="/en-US/docs/Accessibility/An_overview_of_accessible_web_applications_and_widgets">Introduction to ARIA</a></dt>
- <dd>A quick introduction to making dynamic content accessible with ARIA. See also the classic <a class="external" href="http://dev.opera.com/articles/view/introduction-to-wai-aria/">ARIA intro by Gez Lemon</a>, from 2008.</dd>
- <dt><a href="/en-US/docs/Accessibility/ARIA/Web_applications_and_ARIA_FAQ">Web Applications and ARIA FAQ</a></dt>
- <dd>Answers common questions about WAI-ARIA and why it's needed to make web applications accessible.</dd>
- <dt><a class="external" href="http://zomigi.com/blog/videos-of-screen-readers-using-aria-updated/">Videos of Screen Readers Using ARIA</a></dt>
- <dd>See both real and simplified examples from around the web, including "before" and "after" ARIA videos.</dd>
- <dt><a class="external" href="https://w3c.github.io/using-aria/">Using ARIA</a></dt>
- <dd>A practical guide for developers. It suggests what ARIA attributes to use on HTML elements. Suggestions are based on implementation realities.</dd>
-</dl>
-
-<h3 id="Melhoramentos_ARIA_Simples">Melhoramentos ARIA Simples</h3>
-
-<dl>
- <dt><a class="external" href="https://www.paciellogroup.com/blog/2013/02/using-wai-aria-landmarks-2013/">Enhancing Page Navigation with ARIA Landmarks</a></dt>
- <dd>A nice intro to using ARIA landmarks to improve web page navigation for screen reader users. <a class="external" href="http://www.paciellogroup.com/blog/2011/07/html5-accessibility-chops-aria-landmark-support/">See also, ARIA landmark implementation notes</a> and examples on real sites (updated as of July 2011).</dd>
- <dt><a href="/en-US/docs/ARIA/forms">Improving Form Accessibility</a></dt>
- <dd>ARIA is not just for dynamic content! Learn how to improve accessibility of HTML forms using additional ARIA attributes.</dd>
- <dt><a href="/en-US/docs/Accessibility/ARIA/ARIA_Live_Regions" title="Live Regions">Live regions (work-in-progress)</a></dt>
- <dd>Live regions provide suggestions to screen readers about how to handle changes to the contents of a page.</dd>
- <dt><a class="external" href="http://www.freedomscientific.com/Training/Surfs-up/AriaLiveRegions.htm">Using ARIA Live Regions to Announce Content Changes</a></dt>
- <dd>A quick summary of live regions, by the makers of JAWS screen reader software. Live regions are also supported by NVDA with Firefox, and VoiceOver with Safari.</dd>
-</dl>
-
-<h3 id="ARIA_para_Widgets_Scripted">ARIA para <em>Widgets Scripted</em></h3>
-
-<dl>
- <dt><a class="external" href="/en-US/docs/Accessibility/Keyboard-navigable_JavaScript_widgets">Keyboard Navigation and Focus for JavaScript Widgets</a></dt>
- <dd>The first step in developing an accessible JavaScript widget is to make it keyboard navigable. This article steps through the process. The <a class="external" href="http://www.yuiblog.com/blog/2009/02/23/managing-focus/">Yahoo! focus management article</a> is a great resource as well.</dd>
- <dt><a class="external" href="http://access.aol.com/dhtml-style-guide-working-group/">Style Guide for Keyboard Navigation</a></dt>
- <dd>A challenge with ARIA is getting developers to implement consistent behavior — clearly best for users. This style guide describes the keyboard interface for common widgets.</dd>
-</dl>
-
-<h3 id="ARIA_-_Recursos">ARIA - Recursos</h3>
-
-<dl>
- <dd>Need a slider, a menu, or another kind of widget? Find resources here.</dd>
- <dt><a class="external" href="http://www.paciellogroup.com/blog/2009/07/wai-aria-implementation-in-javascript-ui-libraries/" title="http://www.paciellogroup.com/blog/2009/07/wai-aria-implementation-in-javascript-ui-libraries/">ARIA-Enabled JavaScript UI Libraries</a></dt>
- <dd>If you're starting a new project, choose a UI widget library with ARIA support already built-in. Warning: this is from 2009 — content should be moved to an MDN page where it can be updated.</dd>
-</dl>
-</div>
-
-<div class="section">
-<h3 id="Lista_de_Endereços">Lista de Endereços</h3>
-
-<dl>
- <dt><a class="link-https" href="https://groups.google.com/forum/#!forum/free-aria">Free ARIA Google Group</a></dt>
- <dd>A place to ask questions about ARIA, as well as make suggestions for improving the ARIA documentation found on these pages.</dd>
-</dl>
-
-<h3 id="Blogues">Blogues</h3>
-
-<p>ARIA information on blogs tends to get out of date quickly. Still, there is some great info out there from other developers making ARIA work today.</p>
-
-<p><a class="external" href="https://www.paciellogroup.com/blog/">Paciello Group</a></p>
-
-<p><a class="external" href="http://www.accessibleculture.org/tag/wai-aria/">Accessible Culture</a></p>
-
-<h3 id="Comunicar_Erros_(Bugs)">Comunicar Erros (<em>Bugs</em>)</h3>
-
-<p><a href="/en/Accessibility/ARIA/How_to_file_ARIA-related_bugs" title="https://developer.mozilla.org/en/ARIA/How_to_file_ARIA-related_bugs">File ARIA bugs on browsers, screen readers, and JavaScript libraries.</a></p>
-
-<h3 id="Exemplos">Exemplos</h3>
-
-<dl>
- <dt><a class="external" href="/en-US/docs/Accessibility/ARIA/ARIA_Test_Cases">ARIA Examples Library</a></dt>
- <dd>A set of barebones example files which are easy to learn from.</dd>
- <dt>Accessible JS Widget Library Demos</dt>
- <dd><a class="external" href="http://hanshillen.github.com/jqtest/">jQuery</a>, <a class="external" href="http://yuilibrary.com/gallery/">YUI</a></dd>
- <dt><a class="external" href="http://mail.yahoo.com">Yahoo! Mail</a></dt>
- <dd>Yahoo! puts it all together with Yahoo! Mail, a web app that almost looks like a native app. It works very well. As a <a class="external" href="http://www.marcozehe.de/2011/09/21/review-the-all-new-yahoo-mail-web-application/">review of Yahoo! Mail</a> by screen reader Marco Zehe says, "Keep up the good work!".</dd>
- <dt><a class="external" href="http://search.yahoo.com">Yahoo! Search</a></dt>
- <dd>Yahoo! has done an amazing job of advancing ARIA here, by exercising ARIA's full capabilities and <a class="external" href="http://ycorpblog.com/2011/03/23/searchdirect/">sharing their techniques</a>. Yahoo! Search uses a combination of ARIA landmarks, live regions, and widgets.</dd>
-</dl>
-
-<h3 id="Esforços_de_Uniformização">Esforços de  Uniformização</h3>
-
-<dl>
- <dt><a class="external" href="http://www.w3.org/WAI/intro/aria.php">WAI-ARIA Activities Overview at W3C</a></dt>
- <dd>Authoritative Overview of WAI-ARIA Standardization efforts by the Web Accessibility Initiative (WAI)</dd>
- <dt><a class="external" href="https://www.w3.org/TR/wai-aria-1.1/">WAI-ARIA Specification</a></dt>
- <dd>The W3C specification itself, useful as a reference. Note that, at this stage, it is important to test compatibility, as implementations are still inconsistent.</dd>
- <dt><a class="external" href="https://www.w3.org/TR/wai-aria-practices-1.1/">WAI-ARIA Authoring Practices</a></dt>
- <dd>
- <p>Like the W3C WAI-ARIA specification, the official best practices represents a future ideal — a day when authors can rely on consistent ARIA support across browsers and screen readers. The W3C documents provide an in-depth view of ARIA.</p>
-
- <p>For now, web developers implementing ARIA should maximize compatibility. Use best practices docs and examples based on current implementations.</p>
- </dd>
- <dt><a class="external" href="http://www.openajax.org/member/wiki/Accessibility">Open AJAX Accessibility Task Force</a></dt>
- <dd>The Open AJAX effort centers around developing tools, sample files, and automated tests for ARIA.</dd>
- <dt><a href="/en-US/docs/Accessibility/ARIA/ARIA_Techniques" title="ARIA Techniques">Under Construction: WCAG 2.0 ARIA Techniques</a></dt>
- <dd>The community needs a complete set of WCAG techniques for WAI-ARIA + HTML, so that organizations can be comfortable claiming their ARIA-enabled content is WCAG compliant. This is important when regulations or policies are based on WCAG.</dd>
-</dl>
-</div>
-</div>
-
-<h3 id="Related_Topics" name="Related_Topics">Tópicos Relacionados</h3>
-
-<p><a href="/pt-PT/docs/Web/Acessibilidade">Acessibilidade</a>, <a href="/pt-PT/docs/Web/Guide/AJAX">AJAX</a>, <a href="/pt-PT/docs/Web/JavaScript">JavaScript</a></p>