guidepup
screenreaders
guidepup | screenreaders | |
---|---|---|
5 | 1 | |
389 | 159 | |
4.1% | -0.6% | |
8.0 | 3.9 | |
2 months ago | 7 months ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
guidepup
- Screen reader driver for test automation (VoiceOver & NVDA)
-
A11y Unlocked: Screen-Reader Automation Tests
// We use a special test instance from the Guidepup package // that gives us access to VoiceOver! import { voTest as test } from "@guidepup/playwright"; import { expect } from "@playwright/test"; // The test setup is exactly the same as normal for // Playwright, expect we now get a `voiceOver` object as well // as the `page` object! test.describe("Playwright VoiceOver", () => { test("I can navigate the Guidepup Github page", async ({ page, voiceOver, }) => { // Let's navigate to Guidepup GitHub page and wait for // page to be ready, nothing special here! await page.goto("https://github.com/guidepup/guidepup", { waitUntil: "domcontentloaded", }); await expect( page.locator('header[role="banner"]') ).toBeVisible(); // This is where things start to get awesome! Let's tell // VoiceOver to interact with the main page content, just // the same as you would when use VoiceOver normally. await voiceOver.interact(); // Let's do something a lil more exciting - move across // the page's headings until we reach the main Guidepup // repo title in the README using VoiceOver! while ((await voiceOver.itemText()) !== "Guidepup heading level 1") { await voiceOver.perform( voiceOver.keyboard.commands.findNextHeading ); } });
-
A11y Testing: Automating ScreenReaders
View on GitHub
-
Automate VoiceOver being controlled by AppleScript
End goal, having successfully found a way to program the ticking of this checkbox, is to build a library so folks can test their websites with screen readers in CI (ref: https://github.com/guidepup/guidepup).
screenreaders
-
A11y Testing: Automating ScreenReaders
Digging further started to yield a little more promise with the discovery of auto-vo, screen-reader-reader, and web-test-runner-voiceover (article - just found this while writing this post!) following the finding of a tweet from Smashing Magazine and then rabbit-holing on twitter... 🕳🐇
What are some alternatives?
cypress-audit - ⚡ Run Lighthouse and Pa11y audits directly in your E2E test suites
audit-a11y - audit websites for accessibility issues
web-test-runner-voiceover - A small plugin for @web/test-runner that uses VoiceOver on Mac for integrated a11y screen reader testing.
setup - Setup your environment for screen reader test automation.
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
pa11y - Pa11y is your automated accessibility testing pal
equal-access - IBM Equal Access Accessibility Checker contains tools to automate accessibility checking from a browser or in a continuous development/build environment
screen-reader-reader - A general purpose screen reader reader
guidepup-playwright - Screen reader driver for Playwright tests.
axe-core - Accessibility engine for automated Web UI testing