Lista de verificação em branco, formulário para impressão

Lista de verificação WCAG 2.2

Lista de verificação em branco para preenchimento offline.

Marque uma caixa por linha. Adicione comentários e referências de prova na coluna Notas conforme necessário.

Percetível

CS	Nível	Nome	Estado
1.1.1	A	Conteúdo Não TextualEvery image, icon, chart, or other non-text element must have a text alternative that serves the same purpose as the original.	☐ Aprovado ☐ Reprovado ☐ N/A
1.2.1	A	Apenas Áudio e Apenas Vídeo (Pré-gravado)Prerecorded audio (e.g., a podcast clip) needs a transcript. Prerecorded video with no audio (e.g., a silent product demo) needs either a transcript or an audio track.	☐ Aprovado ☐ Reprovado ☐ N/A
1.2.2	A	Legendas (Pré-gravadas)All prerecorded video that contains audio must have captions. Captions must be synchronised with the audio and include all speech and important non-speech sounds.	☐ Aprovado ☐ Reprovado ☐ N/A
1.2.3	A	Audiodescrição ou Alternativa em Mídia (Pré-gravado)Prerecorded video with audio track must have either an audio description (narration of visual information) or a full text alternative describing what is shown.	☐ Aprovado ☐ Reprovado ☐ N/A
1.2.4	AA	Legendas (Em Direto)Live video streams (webinars, live events, broadcasts) must have live captions provided in real time.	☐ Aprovado ☐ Reprovado ☐ N/A
1.2.5	AA	Audiodescrição (Pré-gravada)At Level AA, audio description (not just a text alternative) is required for all prerecorded video. The full audio description track must be provided.	☐ Aprovado ☐ Reprovado ☐ N/A
1.3.1	A	Informação e RelaçõesVisual structure (headings, lists, tables, form groupings) must be conveyed in the code, not just through styling.	☐ Aprovado ☐ Reprovado ☐ N/A
1.3.2	A	Sequência SignificativaWhen the order of content matters for understanding, the DOM order must reflect the correct reading sequence — not just the visual layout.	☐ Aprovado ☐ Reprovado ☐ N/A
1.3.3	A	Características SensoriaisInstructions must not rely exclusively on visual cues like shape, color, or position. Include text-based references alongside sensory ones.	☐ Aprovado ☐ Reprovado ☐ N/A
1.3.4	AA	OrientaçãoWebsites and apps must not lock to portrait or landscape. Users with mounted devices (e.g., wheelchair-mounted tablets) may be unable to rotate.	☐ Aprovado ☐ Reprovado ☐ N/A
1.3.5	AA	Identificar a Finalidade do CampoForm fields collecting personal data must have autocomplete attributes so browsers and assistive technologies can autofill them.	☐ Aprovado ☐ Reprovado ☐ N/A
1.4.1	A	Utilização da CorNever use color as the only way to communicate something. Always provide a secondary non-color cue.	☐ Aprovado ☐ Reprovado ☐ N/A
1.4.2	A	Controlo de ÁudioAudio that auto-plays for more than 3 seconds must be pausable or have independent volume control.	☐ Aprovado ☐ Reprovado ☐ N/A
1.4.3	AA	Contraste (Mínimo)Normal text needs 4.5:1 contrast ratio against its background. Large text (18pt/24px or 14pt/~19px bold) needs 3:1.	☐ Aprovado ☐ Reprovado ☐ N/A
1.4.4	AA	Redimensionar TextoUsers must be able to zoom to 200% without losing content or functionality.	☐ Aprovado ☐ Reprovado ☐ N/A
1.4.5	AA	Imagens de TextoUse real HTML text instead of images of text wherever technically possible. Images of text cannot be resized, reflowed, or read by screen readers without alt text.	☐ Aprovado ☐ Reprovado ☐ N/A
1.4.10	AA	RefluxoAt 320px viewport width (equivalent to 400% zoom on a 1280px screen), all content must be accessible without horizontal scrolling.	☐ Aprovado ☐ Reprovado ☐ N/A
1.4.11	AA	Contraste Não TextualThe visual boundaries of form fields, buttons, checkboxes, and graphical elements used to understand content must have 3:1 contrast against adjacent colors.	☐ Aprovado ☐ Reprovado ☐ N/A
1.4.12	AA	Espaçamento de TextoWhen users override text spacing (line height 1.5×, paragraph spacing 2×, letter spacing 0.12em, word spacing 0.16em), no content should be lost or obscured.	☐ Aprovado ☐ Reprovado ☐ N/A
1.4.13	AA	Conteúdo em Hover ou FocusTooltips and hover popups must be: hoverable (mouse can move over them), dismissible (Escape closes them), and persistent (they stay until explicitly closed).	☐ Aprovado ☐ Reprovado ☐ N/A

Operável

CS	Nível	Nome	Estado
2.1.1	A	TecladoEverything a mouse user can do, a keyboard user must also be able to do. No functionality should require a mouse.	☐ Aprovado ☐ Reprovado ☐ N/A
2.1.2	A	Sem Bloqueio do TecladoKeyboard users must never get stuck. Focus must always be escapable. Intentional focus traps in modals are acceptable only if Escape closes the modal.	☐ Aprovado ☐ Reprovado ☐ N/A
2.1.4	A	Atalhos com Teclas de CaracteresSingle-character keyboard shortcuts (like 'G' to go, 'F' for find) must be disableable or remappable. They conflict with speech input users who dictate text.	☐ Aprovado ☐ Reprovado ☐ N/A
2.2.1	A	Tempo AjustávelSession timeouts, time-limited forms, and timed quizzes must give users a way to turn off, adjust, or extend the time limit.	☐ Aprovado ☐ Reprovado ☐ N/A
2.2.2	A	Pausar, Parar, OcultarMoving, blinking, or auto-updating content must have a pause/stop/hide control. This includes carousels, tickers, animated banners, and live feeds.	☐ Aprovado ☐ Reprovado ☐ N/A
2.3.1	A	Três Flashes ou Abaixo do LimiarContent must not flash more than 3 times per second. Flashing content can cause seizures in people with photosensitive epilepsy.	☐ Aprovado ☐ Reprovado ☐ N/A
2.4.1	A	Saltar BlocosKeyboard users must be able to skip past repeated navigation blocks to reach the main content quickly.	☐ Aprovado ☐ Reprovado ☐ N/A
2.4.2	A	Página com TítuloEvery page must have a descriptive <title> element that helps users understand what the page is about.	☐ Aprovado ☐ Reprovado ☐ N/A
2.4.3	A	Ordem do FocusThe keyboard Tab order must follow a logical sequence — typically top-to-bottom, left-to-right in Western languages — that preserves meaning.	☐ Aprovado ☐ Reprovado ☐ N/A
2.4.4	A	Finalidade da Ligação (Em Contexto)Link text must be descriptive enough to understand its destination — either from the text alone or from its surrounding context.	☐ Aprovado ☐ Reprovado ☐ N/A
2.4.5	AA	Várias FormasUsers must have more than one way to find any page on the site (e.g., navigation + site search, or navigation + sitemap).	☐ Aprovado ☐ Reprovado ☐ N/A
2.4.6	AA	Cabeçalhos e EtiquetasWhen headings and form labels are used, they must be descriptive — they need not be comprehensive, but they must accurately describe their associated content.	☐ Aprovado ☐ Reprovado ☐ N/A
2.4.7	AA	Focus VisívelKeyboard users must always be able to see which element has focus. Never suppress the focus outline completely.	☐ Aprovado ☐ Reprovado ☐ N/A
2.4.11	AA	Focus Não Obscurecido (Mínimo)New in WCAG 2.2: sticky headers, cookie banners, and chat bubbles must not completely cover the focused element.	☐ Aprovado ☐ Reprovado ☐ N/A
2.4.12	AAA	Focus Não Obscurecido (Avançado)At AAA level: the focused element must be completely visible — not even partially obscured by sticky content.	☐ Aprovado ☐ Reprovado ☐ N/A
2.4.13	AA	Aparência do FocusLevel AA (WCAG 2.2): the focus indicator must cover at least a 2 CSS pixel perimeter of the unfocused component and have 3:1 contrast between focused and unfocused states.	☐ Aprovado ☐ Reprovado ☐ N/A
2.5.1	A	Gestos de ApontadorAny feature requiring a swipe, pinch, or multi-finger gesture must have an equivalent single-tap or click alternative.	☐ Aprovado ☐ Reprovado ☐ N/A
2.5.2	A	Cancelamento de ApontadorDon't trigger actions on mousedown/touchstart if the user might accidentally tap. Use mouseup/click (which fires on up-event) so users can cancel by moving away.	☐ Aprovado ☐ Reprovado ☐ N/A
2.5.3	A	Etiqueta no NomeThe accessible name of a button or link must contain the visible text label — this is essential for voice control users who say what they see.	☐ Aprovado ☐ Reprovado ☐ N/A
2.5.4	A	Acionamento por MovimentoFeatures that use device shake, tilt, or motion must also be operable via standard UI controls, and motion must be disableable.	☐ Aprovado ☐ Reprovado ☐ N/A
2.5.7	AA	Movimentos de ArrastarNew in WCAG 2.2: drag-and-drop must have a click/tap alternative. Sliders must be adjustable without dragging.	☐ Aprovado ☐ Reprovado ☐ N/A
2.5.8	AA	Tamanho do Alvo (Mínimo)New in WCAG 2.2: interactive targets must be at least 24×24 CSS pixels, OR have sufficient spacing between targets.	☐ Aprovado ☐ Reprovado ☐ N/A

Compreensível

CS	Nível	Nome	Estado
3.1.1	A	Idioma da PáginaThe <html> element must have a lang attribute set to the page's primary language.	☐ Aprovado ☐ Reprovado ☐ N/A
3.1.2	AA	Idioma de PartesWhen content switches language (e.g., a French quote in an English article), the language change must be marked with a lang attribute.	☐ Aprovado ☐ Reprovado ☐ N/A
3.2.1	A	Ao Receber FocusReceiving focus must never automatically navigate, submit a form, or launch a popup. Focus changes must be predictable.	☐ Aprovado ☐ Reprovado ☐ N/A
3.2.2	A	Ao Introduzir DadosChanging a form control (selecting a dropdown option, checking a box) must not automatically navigate or submit without warning.	☐ Aprovado ☐ Reprovado ☐ N/A
3.2.3	AA	Navegação ConsistenteNavigation menus must appear in the same order on every page. Users with cognitive disabilities rely on consistent placement.	☐ Aprovado ☐ Reprovado ☐ N/A
3.2.4	AA	Identificação ConsistenteThe same function must have the same label everywhere on the site. A search button should not be labelled 'Search' on one page and 'Find' on another.	☐ Aprovado ☐ Reprovado ☐ N/A
3.2.6	A	Ajuda ConsistenteNew in WCAG 2.2: help mechanisms (phone number, live chat, FAQ link) must appear in the same relative position on every page where they appear.	☐ Aprovado ☐ Reprovado ☐ N/A
3.3.1	A	Identificação de ErrosWhen a form error is detected automatically, the specific field in error must be identified and described in text.	☐ Aprovado ☐ Reprovado ☐ N/A
3.3.2	A	Etiquetas ou InstruçõesEvery form input must have a visible label. Instructions about required format (date format, password rules) must be provided before the input.	☐ Aprovado ☐ Reprovado ☐ N/A
3.3.3	AA	Sugestão de ErrosError messages must tell users how to fix the error — not just that an error occurred. Exceptions apply for security-sensitive validations.	☐ Aprovado ☐ Reprovado ☐ N/A
3.3.4	AA	Prevenção de Erros (Jurídicos, Financeiros, de Dados)High-stakes forms (purchases, legal agreements, exam submissions, data deletion) must let users review, correct, or reverse the action.	☐ Aprovado ☐ Reprovado ☐ N/A
3.3.7	A	Introdução RedundanteNew in WCAG 2.2: if users must re-enter data they already provided in the same session, auto-populate it or let them select it from a list.	☐ Aprovado ☐ Reprovado ☐ N/A
3.3.8	AA	Autenticação Acessível (Mínimo)New in WCAG 2.2: authentication must not require a cognitive-only challenge unless an alternative exists. Password managers and magic links must be supported.	☐ Aprovado ☐ Reprovado ☐ N/A
3.3.9	AAA	Autenticação Acessível (Avançado)New in WCAG 2.2 (AAA): No authentication step may require a cognitive function test of any kind. Unlike SC 3.3.8, there are no exceptions for object recognition or personal content — all authentication must be cognitive-test-free.	☐ Aprovado ☐ Reprovado ☐ N/A

Robusto

CS	Nível	Nome	Estado
4.1.1	A	Análise SintáticaSC 4.1.1 is obsolete in WCAG 2.2 and always passes with modern browsers. It was removed because modern browsers handle malformed HTML gracefully and assistive technologies do not rely on valid HTML parsing.	☐ Aprovado ☐ Reprovado ☐ N/A
4.1.2	A	Nome, Função, ValorEvery interactive element must expose its name (what it is called), role (what type of control it is), and current state/value to assistive technologies.	☐ Aprovado ☐ Reprovado ☐ N/A
4.1.3	AA	Mensagens de EstadoSuccess messages, loading states, result counts, and errors must be announced by screen readers without moving focus to them.	☐ Aprovado ☐ Reprovado ☐ N/A