Accessibility e-MAG

Enforce e-MAG and WCAG accessibility compliance on government web interfaces.

Updated Feb 8, 2026

Search Tags:#accessibility #wcag #government #aria #keyboard-navigation #emag #skip-links

Ready to run

npx skills add https://github.com/joabeoliveira/kit-skills --skill accessibility-e-mag

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Accessibility e-MAG
Source: https://github.com/joabeoliveira/kit-skills/tree/main/.skills/accessibility-emag
Command: npx skills add https://github.com/joabeoliveira/kit-skills --skill accessibility-e-mag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Garante que interfaces governamentais sejam acessíveis, atendendo aos padrões e-MAG e WCAG, reduzindo barreiras para cidadãos com deficiência.

Core Features & Use Cases

Conformidade com padrões e-MAG/WCAG: Assegura que componentes desenvolvidos estejam em conformidade com diretrizes legais de acessibilidade.
ARIA e Semântica: Define uso de ARIA, hierarquia de cabeçalhos e associação de rótulos a inputs.
Navegação e Usabilidade: Inclui navegação por teclado, skip links e mensagens de erro acessíveis para leitores de tela.

Quick Start

Use este Skill durante o desenvolvimento de UI para garantir a conformidade com e-MAG/WCAG.

Frequently Asked Questions about Accessibility e-MAG

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I make government web interfaces comply with e-MAG and WCAG accessibility standards?▼

To make government web interfaces comply with e-MAG and WCAG, enforce keyboard operability, ARIA labeling, semantic heading structure, form labeling, contrast compliance, and skip links across navigation, forms, and content components.

What is the best way to implement keyboard navigation and skip links for screen readers in government portals?▼

Implementing keyboard navigation and skip links for screen readers in government portals requires adding accessible skip links and ensuring full keyboard operability across frontend components to meet e-MAG and WCAG conformance criteria.

How do I add ARIA labels and semantic heading structure to frontend forms for accessibility compliance?▼

Adding ARIA labels and semantic heading structure to frontend forms involves defining ARIA usage, establishing proper heading hierarchy, and associating labels with inputs to ensure forms are accessible and conform to e-MAG standards.

Does this accessibility compliance approach apply to all government web apps and portals?▼

Yes, this accessibility compliance approach applies directly to government web apps and portals, ensuring that frontend components including navigation, forms, and content meet e-MAG and WCAG legal requirements for citizens with disabilities.

Why do I need to follow e-MAG guidelines in addition to WCAG for government digital interfaces?▼

Following e-MAG guidelines in addition to WCAG for government digital interfaces is necessary because e-MAG enforces specific legal accessibility standards tailored to Brazilian government portals, reducing barriers for citizens with disabilities.

How to ensure accessible error messages and form labeling for screen readers in government applications?▼

Ensuring accessible error messages and form labeling for screen readers in government applications requires associating input labels properly and providing screen reader-friendly error notifications to maintain e-MAG and WCAG compliance.