Agree a manual accessibility testing routine for all SciTools repos

Open
#213 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
accessibility

Research direction

Start with the issue description and consult accessibility experts at the UK Met Office about suitable manual checks, including keyboard navigation of headings and screen-reading pages. Agree which checks apply across all SciTools repositories and define a recurring schedule; the work is done when the team has an agreed routine.

Written by the indexing model from the issue text.

Description

Automated testing and continuous integration - #214 - can do much heavy lifting in the accessibility space, but not all elements of accessibility testing should be automated. E.g. the correct alt-text will depend on context. The SciTools team should agree on appropriate manual testing e.g. keyboard navigation of headings or screen-reading a page, with help from experts at UK Met Office, and agree on a schedule for performing this.

Dominant language
Python
Stars
3
Forks
7
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SciTools/.github

All issues in SciTools/.github

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.