Accessibility Statement

Last Updated: October 11, 2026

Our commitment

Talking About Testing is committed to making its online learning platform accessible to as many people as possible, including people with disabilities. We believe everyone should be able to learn software testing regardless of how they browse the web. Accessibility is an ongoing effort, and we work to improve the experience continuously.

Conformance status

We aim to follow the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA as our target standard. The platform has not yet been through a formal, independent accessibility audit, so we cannot claim full conformance today. Many parts already align with these guidelines, and we are actively working toward meeting them across the whole platform.

Measures we take

In building and maintaining the platform, we take the following measures to support accessibility:

  • We use semantic HTML landmarks (header, navigation, main, and footer regions) so that assistive technologies can understand the page structure.
  • Each page declares its language, and the whole platform is available in English, Brazilian Portuguese, and Spanish.
  • Interactive components such as menus and expandable sections are built on accessible primitives with keyboard support and appropriate ARIA attributes.
  • Quiz answer options are real radio buttons, so a screen reader announces which option is selected as you move between them, and the arrow keys work as expected.
  • Meaningful images include text alternatives, and purely decorative graphics and icons are hidden from assistive technologies.
  • Signed-in learners can turn off the decorative background circles from the header on larger screens, for a calmer, less visually busy experience.
  • Icon-only buttons include descriptive text for screen reader users.
  • Buttons and links are named by the text you can see on them, so what a screen reader announces matches what is written on the screen. Where the visible text is a short code, such as EN, ES, and PT on the language switcher, the full name is added after it, so the code you can see is still part of what is announced, and each language name is announced in that language.
  • Keyboard focus is visible, so people navigating without a mouse can see where they are.
  • When an interactive component moves to a new step, such as the next quiz question, keyboard focus follows the new content, so people navigating by keyboard or screen reader carry on from where the content changed instead of being sent past it.
  • Each step of the guided tour new students see on a course dashboard is read from the step itself as keyboard focus moves into it, so a screen reader speaks its position, title, and description in the language of the page.
  • The outcome of an action is written out rather than signalled by color alone, and keyboard focus moves onto it so that it is read in the language of the page. The result of a quiz answer, its explanation, and the final score all work this way.
  • Controls whose visible label is shortened on small screens, such as the previous and next lesson buttons, still announce their direction and destination in full to screen readers.
  • Links that lead away from the platform are visually marked so their destination is clear.
  • Light and dark themes are available, and layouts are responsive to different screen sizes and zoom levels.
  • Automated accessibility checks (axe-core) run as part of our test suite against key pages and interactive states, in both the light and the dark theme.

Known limitations

Despite our efforts, some parts of the platform may not yet be fully accessible. Known limitations include:

  • The platform has not yet had a formal, third-party accessibility audit, so some components may not fully meet WCAG 2.2 Level AA.
  • Our automated checks cover the public pages and the core lesson experience. Some signed-in areas, such as the fundamentals section, have not been verified yet.
  • Some decorative motion, such as the celebration animation on the course conclusion page, does not yet respect the operating system's reduced motion setting.
  • On macOS, VoiceOver speaks some status messages and icon-button labels in its own default voice instead of the language of the page, so on the Portuguese and Spanish versions they can be announced with an English accent. We are moving those texts into the page content, which is read in the right language. The quizzes and the guided tour of the course dashboard have already been changed this way.

Ongoing improvements

We treat accessibility as an ongoing part of building the platform, not a one-time task. We are planning further improvements, including addressing the limitations listed above, and will update this statement as those changes ship.

Feedback and contact

We welcome your feedback on the accessibility of this platform. If you encounter any barrier or have a suggestion, please contact us at walmyr@talkingabouttesting.com. We aim to respond within a few business days.