Recursos · 32

Projetar formulários acessíveis e erros recuperáveis

Orientar a entrada, explicar a falha e preservar o progresso do usuário na tarefa.

Atualizado · 8 min

Bancada fictícia de verificação de interfaces sem pessoas, ecrã e tablet com campos abstratos, teclado e amostras de cor Ilustração editorial gerada com IA

O que este guia ajuda a alcançar

  • Limitar campos
  • Nome e guia
  • Explicar erros
  • Testar recuperação

Verificação rápida

  • Cada campo tem um nome compreensível?
  • Os formatos esperados são explicados antes da entrada?
  • Um erro identifica seu campo e a possível correção?
  • Os valores válidos são mantidos?
  • A tarefa pode ser concluída com o teclado e o zoom?

Método passo a passo

  1. 1

    Começar pela tarefa

    Listar apenas os dados necessários para concluir a tarefa e as etapas que uma pessoa deve entender. Remover solicitações que não contribuem para a transação.

    Entregável: formulário mínimo e justificativa dos campos.

  2. 2

    Rótulo e agrupamento

    Conecte cada controle com um rótulo visível, agrupe as opções relacionadas e coloque a ajuda próxima. Verifique a ordem de leitura e tabulação.

    Entregável: estrutura e rótulos testados.

  3. 3

    Prevenir erros

    Ofereça exemplos de formato e especifique as restrições antes do envio. Não use apenas a cor para indicar que um campo é obrigatório.

    Entregável: instruções e estados de entrada.

  4. 4

    Explicar cada falha

    Após a validação, apresente um resumo, conecte cada problema ao seu campo e descreva como resolvê-lo. Mantenha os valores e o contexto corretos.

    Entregável: cenário de erro corrigível.

  5. 5

    Lidar com interrupções

    Distinga erro de entrada, recusa de negócio, tempo limite e incidente do servidor. Indique a próxima etapa sem presumir que a solicitação foi bem-sucedida.

    Entregável: mensagens e recuperação por estado.

  6. 6

    Testar tarefas reais

    Reproduzir sucessos e falhas com teclado, zoom, dispositivos móveis e assistência adequada. Identificar os obstáculos, corrigi-los e testar novamente.

    Entregável: evidência de conclusão da tarefa.

Indicadores de gestão

IndicadorO que medePrimeira ação
CompletudeCampos necessários com rótulos e ajudaCorrigir controles ambíguos
ErrosFalhas com explicação e link para o campoReescrever mensagens
RecuperaçãoValores mantidos após a correçãoCorrigir o gerenciamento de estado
TarefaJornadas concluídas com teclado e zoomRemover barreiras

Erros comuns

  • Usar marcadores de posição em vez de rótulos
  • Exibir apenas "ocorreu um erro"
  • Apagar todo o formulário após um erro
  • Testar apenas o fluxo normal com o mouse

Perguntas frequentes

Um marcador de posição é suficiente?

Não. Um rótulo identificável deve permanecer disponível enquanto uma pessoa insere um valor.

Quando um erro deve aparecer?

Escolha um momento oportuno e explique a causa e a solução sem interrupções desnecessárias.

E se o servidor falhar?

Não declare sucesso; preserve o que pode ser salvo e ofereça uma recuperação compreensível.

Formulários: critérios, erros e contraste

As notas detalhadas desta edição estão disponíveis em inglês.

An accessible form lets people understand the request, reach controls, correct an error and finish the task. For an incident-reporting portal, service request or authentication journey, quality also depends on waiting, failure and backtracking states.

This editorial selection connects 17 WCAG 2.2 Level A or AA criteria to review questions and evidence to retain. Identifiers, English titles and levels were checked against the W3C Recommendation of 12 December 2024, consulted on 23 October 2026. The selection does not cover every criterion applicable to a page or process.

Separate the rule, its explanation and observed evidence

Separate the rule, its explanation and observed evidence
Reading layerWhat it providesHow to use it
WCAG 2.2 RecommendationNormative text: read the criterion, definitions and exceptions together.Connect the finding to the exact criterion and examined scope.
WAI Understanding and tutorialsInformative explanations and guidance for interpretation and implementation.Use them to prepare checks without presenting them as new normative requirements.
Journey observationA check on a page, version, state and configuration.Retain reproduction steps and evidence; a calculation or scanner does not replace complete evaluation.

W3C · Web Content Accessibility Guidelines (WCAG) 2.2 · Recommendation · 12 December 2024

17 criteria for a form review

Questions and checks below are CIE editorial methodology. Each criterion links to the dated normative text; its Understanding link leads to an informative explanation. Levels are neither a score awarded to this site nor an audit result.

17 criteria for a form review · WCAG 2.2 · 2024-12-12
W3C criterion and levelCIE review questionEvidence or check to prepare
1.3.1 · Info and Relationships

Level A

Understanding ↗

Do field labels and groups remain understandable in the semantic structure?Accessibility tree and traversal of named groups.
1.3.5 · Identify Input Purpose

Level AA

Understanding ↗

For personal inputs covered by the taxonomy, can software identify the input purpose?Purpose-appropriate autocomplete tokens; distinguish a label from a purpose token.
1.4.1 · Use of Color

Level A

Understanding ↗

Can an error or selection be understood without relying on colour alone?Error text, field identification and state independent of red or green.
1.4.3 · Contrast (Minimum)

Level AA

Understanding ↗

Does meaningful text stand out from its background in relevant states?Actually adjacent colours, text size and weight; criterion threshold and exceptions.
1.4.11 · Non-text Contrast

Level AA

Understanding ↗

Is visual information needed to identify components and states distinguishable?Necessary border, icon or other cue compared with adjacent colours; examine exceptions.
2.1.1 · Keyboard

Level A

Understanding ↗

Can the journey’s actions be operated by keyboard within the criterion’s scope?Pointer-free scenario: selection, entry, help, correction and submission.
2.4.7 · Focus Visible

Level AA

Understanding ↗

Can visitors see which interactive element has keyboard focus?Tab and Shift+Tab through initial, error and confirmation states.
2.4.11 · Focus Not Obscured (Minimum)

Level AA

Understanding ↗

Does the focused component remain at least partly visible despite author-created content?Test sticky headers, banners and panels; this AA minimum does not mean no obscuration at all.
2.5.3 · Label in Name

Level A

Understanding ↗

Does the accessible name contain visible label text where this criterion applies?Compare visible text and computed name, including for voice control.
2.5.8 · Target Size (Minimum)

Level AA

Understanding ↗

Do pointer targets reach 24 × 24 CSS pixels or satisfy a criterion exception?Measure bounds and examine spacing, equivalent control, inline text, user-agent control or essential presentation.
3.3.1 · Error Identification

Level A

Understanding ↗

When an input error is automatically detected, are its field and nature described in text?Submit a missing value and an incorrect format; retain the message associated with the field.
3.3.2 · Labels or Instructions

Level A

Understanding ↗

Are necessary labels or instructions available before entry?Requirements known in advance: expected field, mandatory entry and useful format.
3.3.3 · Error Suggestion

Level AA

Understanding ↗

Is a known correction suggested where it does not compromise security or content purpose?Compare a generic message with actionable help for the error actually detected.
3.3.7 · Redundant Entry

Level A

Understanding ↗

Within one process, is previously supplied information populated or available to select, subject to exceptions?Return to a step; distinguish still-valid data, essential requirements and security needs.
3.3.8 · Accessible Authentication (Minimum)

Level AA

Understanding ↗

Does an authentication step require a cognitive test without an alternative, assistance or specified exception?Usable password-manager, paste and other mechanisms; read the complete exceptions.
4.1.2 · Name, Role, Value

Level A

Understanding ↗

Are component name, role, value and relevant states exposed to assistive technologies?Inspect native and custom controls, then change their states.
4.1.3 · Status Messages

Level AA

Understanding ↗

Can relevant status messages be presented by assistive technology without receiving focus?Waiting, error or brief result; test announcements and avoid unnecessary interruptions.

Five recovery situations to write and test

Five recovery situations to write and test
Illustrative situationUseful feedbackCheck
Required field left blankIdentify the field and explain the expected information in text.Keep the message associated with the field and the label visible.
Unaccepted formatExplain the actual accepted format and suggest a correction where possible.Do not erase other valid entries; let the person resume correction.
Multiple input errorsProvide an overview and messages close to the fields.Error-summary links reach the correct controls and keyboard order remains coherent.
Service waiting or failureSay whether the request is pending, failed or requires another action.Useful status feedback is perceivable without repeated announcements on every keystroke.
Returning to a step in the same processRetain still-valid information or make it available to select.Examine 3.3.7 exceptions and avoid unjustified forced re-entry.

W3C WAI · Forms Tutorial · Labeling Controls · Practical guidance · consulted 2026-10-23

W3C WAI · Forms Tutorial · User Notifications · Practical guidance · consulted 2026-10-23

Calculadora local de contraste

Calculation uses two opaque, solid sRGB colours. Enter #RGB or #RRGGBB, case-insensitively. The ratio uses relative luminance and (lighter L + 0.05) / (darker L + 0.05). Numeric display is rounded for reading; threshold comparisons use the unrounded result.

This model does not inspect website styles and does not handle transparency, gradients, background images, video, other colour spaces or rendering variations. It compares numbers with thresholds; it does not decide whether a criterion applies or its exceptions are satisfied.

WCAG large-scale text includes at least 18 point, or 14 point bold, or equivalent sizing under the definition’s rules. Text merely looking “large” on screen does not justify choosing a reduced threshold. For non-text, examine necessary identifying information and all relevant adjacent colours.

W3C WAI · Understanding SC 1.4.3 · Contrast (Minimum) · Informative explanation · consulted 2026-10-23

W3C WAI · Understanding SC 1.4.6 · Contrast (Enhanced) · Informative explanation · consulted 2026-10-23

W3C WAI · Understanding SC 1.4.11 · Non-text Contrast · Informative explanation · consulted 2026-10-23

Seven calculated pairs, available without JavaScript

Seven calculated pairs, available without JavaScript
Learning caseForeground / backgroundCalculated ratioNumeric thresholds reached
Illustrative gold and dark background#D4BD7F / #1017199.826201:13:1 · 4.5:1 · 7:1
Black and white#000000 / #FFFFFF21.000000:13:1 · 4.5:1 · 7:1
Grey below the 4.5 threshold#777777 / #FFFFFF4.478089:13:1
Grey just below the 3 threshold#959595 / #FFFFFF2.995346:1Numeric threshold not reached
Grey above the 7 threshold#595959 / #FFFFFF7.004729:13:1 · 4.5:1 · 7:1
Red and white#FF0000 / #FFFFFF3.998477:13:1
Identical colours#777777 / #7777771.000000:1Numeric threshold not reached

#777777 grey on white gives approximately 4.478089:1: the 4.5:1 threshold is not reached. #959595 on white gives approximately 2.995346:1: rounding it to 3.0 does not make it reach the 3:1 threshold. These are calculations, not measurements of a real journey.

A task-oriented verification method

  1. Define the task

    Specify what the person needs to complete and the pages and states involved: entry, waiting, error, correction and confirmation.

  2. Test different uses

    Navigate by keyboard, with zoom and on a small screen; also inspect names and states exposed to assistive technology.

  3. Keep reproducible findings

    Record version, configuration, steps, expected and observed results. Link barriers to criteria and retain the exceptions examined.

  4. Retest after correction

    Recheck the whole task with the actual components and services, retaining any points still requiring confirmation.

Copyright © 2020–2024 World Wide Web Consortium. W3C Recommendation WCAG 2.2, 12 December 2024. Copyright © 2023 W3C®. This document includes material copied from or derived from Web Content Accessibility Guidelines (WCAG) 2.2. Identifiers, titles and levels are attributed to W3C; questions, examples and method are CIE synthesis. This is not an official translation or a modified technical specification.

W3C · Web Content Accessibility Guidelines (WCAG) 2.2 · Recommendation · 12 December 2024

W3C · Document license · 2023 version · Terms and attribution consulted 2026-10-23

Verified documentary edition

WCAG 2.2 · Recommendation · 2024-12-12 · 2026-10-23

Source HTML SHA-256: 6e3c5fe397257cae509a2fb4752b73062cf8cbeb92c2cec618989b17e4cf7057

Referências oficiais

As referências apoiam o método. Adapte as verificações ao seu contexto; elas não são uma certificação. Os títulos das referências originais e os documentos de origem podem estar em outro idioma.

Referências consultadas em .