Skip to content

Actions: w3c/wcag2ict

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
743 workflow runs
743 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Use consistent language and fix errors documented in Issue 618
Deploy to gh-pages on push to main, check on pull requests #1414: Pull request #689 synchronize by maryjom
June 13, 2025 19:52 30s mjm-issue-618-editorials
June 13, 2025 19:52 30s
pages build and deployment
pages-build-deployment #285: by github-pages bot
June 12, 2025 20:03 34s gh-pages
June 12, 2025 20:03 34s
Merge pull request #688 from w3c/mjm-proposal1-issue-614
Deploy to gh-pages on push to main, check on pull requests #1413: Commit cb130cc pushed by maryjom
June 12, 2025 19:52 8m 13s main
June 12, 2025 19:52 8m 13s
pages build and deployment
pages-build-deployment #284: by github-pages bot
June 12, 2025 15:24 48s gh-pages
June 12, 2025 15:24 48s
SC 3.2.3: change "on multiple" with "in multiple" and update replacem…
Deploy to gh-pages on push to main, check on pull requests #1412: Commit 188ce9b pushed by maryjom
June 12, 2025 15:23 57s main
June 12, 2025 15:23 57s
Proposal 2: Adjust 1.4.2, 2.1.2, 2.2.2, and 2.3.1 "must" to use "it would be necessary for"
Deploy to gh-pages on push to main, check on pull requests #1411: Pull request #682 synchronize by maryjom
June 12, 2025 15:21 32s mjm-proposal2-remove-must
June 12, 2025 15:21 32s
For Proposal 2: Make note consistent between 1.4.2, 2.1.2, 2.2.2, 2.3.1
Deploy to gh-pages on push to main, check on pull requests #1410: Pull request #683 synchronize by maryjom
June 12, 2025 15:17 44s mjm-editorials-for-consistency
June 12, 2025 15:17 44s
Issue 614: Make "closed functionality" verbiage consistent
Deploy to gh-pages on push to main, check on pull requests #1409: Pull request #688 synchronize by maryjom
June 12, 2025 15:08 37s mjm-proposal1-issue-614
June 12, 2025 15:08 37s
Issue 614: Make "closed functionality" verbiage consistent
Deploy to gh-pages on push to main, check on pull requests #1408: Pull request #688 synchronize by maryjom
June 12, 2025 15:07 32s mjm-proposal1-issue-614
June 12, 2025 15:07 32s
Issue 614: Make "closed functionality" verbiage consistent
Deploy to gh-pages on push to main, check on pull requests #1407: Pull request #688 synchronize by maryjom
June 12, 2025 15:06 39s mjm-proposal1-issue-614
June 12, 2025 15:06 39s
Issue 614: Make "closed functionality" verbiage consistent
Deploy to gh-pages on push to main, check on pull requests #1406: Pull request #688 synchronize by maryjom
June 12, 2025 15:06 50s mjm-proposal1-issue-614
June 12, 2025 15:06 50s
Issue 614: Make "closed functionality" verbiage consistent
Deploy to gh-pages on push to main, check on pull requests #1405: Pull request #688 synchronize by maryjom
June 12, 2025 15:05 52s mjm-proposal1-issue-614
June 12, 2025 15:05 52s
Issue 614: Make "closed functionality" verbiage consistent
Deploy to gh-pages on push to main, check on pull requests #1404: Pull request #688 synchronize by maryjom
June 12, 2025 15:04 38s mjm-proposal1-issue-614
June 12, 2025 15:04 38s
Use consistent language and fix errors documented in Issue 618
Deploy to gh-pages on push to main, check on pull requests #1403: Pull request #689 synchronize by maryjom
June 12, 2025 13:44 29s mjm-issue-618-editorials
June 12, 2025 13:44 29s
Use consistent language and fix errors documented in Issue 618
Deploy to gh-pages on push to main, check on pull requests #1402: Pull request #689 synchronize by maryjom
June 11, 2025 15:47 31s mjm-issue-618-editorials
June 11, 2025 15:47 31s
Use consistent language and fix errors documented in Issue 618
Deploy to gh-pages on push to main, check on pull requests #1401: Pull request #689 synchronize by maryjom
June 11, 2025 15:12 49s mjm-issue-618-editorials
June 11, 2025 15:12 49s
Use consistent language and fix errors documented in Issue 618
Deploy to gh-pages on push to main, check on pull requests #1400: Pull request #689 synchronize by maryjom
June 11, 2025 13:29 41s mjm-issue-618-editorials
June 11, 2025 13:29 41s
Use consistent language and fix errors documented in Issue 618
Deploy to gh-pages on push to main, check on pull requests #1399: Pull request #689 synchronize by maryjom
June 10, 2025 22:15 33s mjm-issue-618-editorials
June 10, 2025 22:15 33s
Use consistent language and fix errors documented in Issue 618
Deploy to gh-pages on push to main, check on pull requests #1398: Pull request #689 opened by maryjom
June 10, 2025 22:13 47s mjm-issue-618-editorials
June 10, 2025 22:13 47s
Issue 614: Make "closed functionality" verbiage consistent
Deploy to gh-pages on push to main, check on pull requests #1397: Pull request #688 synchronize by maryjom
June 10, 2025 21:35 29s mjm-proposal1-issue-614
June 10, 2025 21:35 29s
Issue 614: Make "closed functionality" verbiage consistent
Deploy to gh-pages on push to main, check on pull requests #1396: Pull request #688 synchronize by maryjom
June 10, 2025 21:25 30s mjm-proposal1-issue-614
June 10, 2025 21:25 30s
Issue 614: Make "closed functionality" verbiage consistent
Deploy to gh-pages on push to main, check on pull requests #1395: Pull request #688 synchronize by maryjom
June 10, 2025 21:06 29s mjm-proposal1-issue-614
June 10, 2025 21:06 29s
Issue 614: Make "closed functionality" verbiage consistent
Deploy to gh-pages on push to main, check on pull requests #1394: Pull request #688 synchronize by maryjom
June 10, 2025 21:02 30s mjm-proposal1-issue-614
June 10, 2025 21:02 30s
Issue 614: Make "closed functionality" verbiage consistent
Deploy to gh-pages on push to main, check on pull requests #1393: Pull request #688 opened by maryjom
June 10, 2025 20:56 45s mjm-proposal1-issue-614
June 10, 2025 20:56 45s
SC 3.2.3 change "on multiple" with "in multiple" and update replacement language
Deploy to gh-pages on push to main, check on pull requests #1392: Pull request #687 opened by maryjom
June 6, 2025 22:13 32s