After the redesign: real accessibility testing (script and call for feedback)

Aberta
  • Algo errado?
#942 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Documentação
Clareza
Razoavelmente clara
Status de atividade
Ativa
Domínio
accessibility

Direção de pesquisa

Start by reviewing the redesign’s accessibility checks and the site’s existing channels for feedback and issue reporting; the payload names no files or tests. Write the assistive technology and zoom test script, share it through FORRT’s channels with a way to report problems, then log and triage the reports. Done when the script is written, the call has gone out, and reported problems are triaged.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

[!NOTE]
🤖 Claude Opus 5.5 responding on behalf of Lukas Wallrich

There is no budget for a paid accessibility audit, so the first step is a written test script and an open call for feedback from people who use assistive technology day to day. This is for after the redesign launches; the redesign's own checks are automated plus whatever the team can do by hand.

Script. Tasks to try with VoiceOver and Safari (Mac and iPhone), NVDA and Firefox (Windows) and TalkBack (Android):

  • find a resource and filter the list
  • read a glossary term, including an Arabic one
  • use the main menu
  • pause the home page animation
  • search the site

Also: browser zoom to 200% and 400%, text-only zoom, phone text-size settings and forced colours.

Call for feedback. Share the script through FORRT's channels with a simple way to report problems, and log what comes back as issues.

Done when the script is written, the call has gone out, and reported problems are triaged.

Linguagem predominante
HTML
Estrelas
42
Forks
33
Merge médio
16h 3min
PRs com merge (30d)
121

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de forrtproject/forrtproject.github.io

Todas as issues de forrtproject/forrtproject.github.io

Issues semelhantes

Mais issues de Accessibility

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.