Accessibility review of Board elections

## Context

We want to properly test our DSF Board elections flow to make sure everyone can make use of the available information and actually go through with voting.

Related: [Accessibility review of code.djangoproject.com](https://github.com/django/code.djangoproject.com/issues/250)

## Audit requirements

### Standards

- [WCAG 2.2 AA](https://www.w3.org/TR/WCAG22/)
- Some AAA-level success criteria where relevant
- Some elements of [ATAG 2.0](https://www.w3.org/WAI/standards-guidelines/atag/) – for example reviewing whether it’s possible to create accessible content in Trac comments.

### Scope

- [ ] [Candidates listing](https://www.djangoproject.com/weblog/2024/oct/28/2025-dsf-board-candidates/) (from previous elections)
- [ ] Ranked Vote official demos
- [Ranked Vote voting form](https://app.rankedvote.co/rv/nsxqnxeoyrry1tsgr4/vote)
- [Ranked Vote results page](https://app.rankedvote.co/rv/nsxqnxeoyrry1tsgr4/results)
- [ ] Our own demo setup, with 20 candidates registered (a@example.com, b@example.com, c@example.com, etc)
- [Test for 2026 DSF Board elections](https://app.rankedvote.co/rv/qy0b152qbq2gbmp4dg/vote)

### Reporting

- Format similar to [djangoproject.com accessibility audit](https://github.com/django/djangoproject.com/issues/1381), with a single GitHub comment arranged in sections, here ideally
- Accompanying video or screenshots if relevant

### Testing methodology

Automated tasks:

- Accessibility Insights

Manual tasks:

- Screenshot-taking & visual review for tab order
- Manual keyboard navigation testing
- Manual 400% zoom testing
- Desktop screen readers: VoiceOver macOS
- Speech recognition: Voice Control
- Windows contrast themes

## Audit planning

- [ ] Validate requirements & decide on approach
- [ ] Confirm availability of relevant stakeholders / auditors
- [ ] Audit
- [ ] Report
- [ ] (Backlog curation)