The Commits Page

Link to The Commits Page copied to clipboard

axe Developer Hub shows your project's Git commits

Free Trial

Only shown for projects that use Git.

The commits page shows the scanned commits that are part of the selected branch. This page is shown when you click on the View Commits button on the branches page.

Commits page in axe Developer Studio showing the commits that are part of the content-changes branch

note

This page only contains those commits that were scanned by running your modified test suite. Running your modified test suite saves the current commit in the current branch, so you need to run your modified test suite on every commit and branch to save that information to axe Developer Hub.

🄰: Commit Page Breadcrumb

The breadcrumb panel for the commit page with links to projects, the branches page, and the name of the current commit.

Item A is the breadcrumb and helps navigate around the site. The items are:

  1. Clicking on the first item returns to the Projects page.
  2. The second item is the current project. Clicking on main-website returns to the branches page for the main-website project.
  3. The last item is the Git branch (content-changes).

The button on the right copies a link to the clipboard to share this page with others.

🄱: Accessibility Standard and Commit Count

Currently selected filter and the number of commits in this branch.

This item shows the current standard configuration (the top row) for accessibility rules (best practices and WCAG level), and the second row includes a count of commits in this branch that have been scanned by the @axe-core/watcher package.

note

Best practices and WCAG level are not currently configurable and do not reflect your configuration in other Deque products.

🄲: Commits

A annotated view of a commit. Six items are detailed in the following list.

(Only one of the commits is shown above.)

  1. Git commit message (fix: missing copyright message) and first seven characters of the commit's SHA (d1e0c35)
  2. The user who authored this commit and the relative time of the test run
  3. Number of issues that exceed the accessibility (a11y) threshold (see Change the Accessibility (A11y) Threshold for more information)
  4. Summary of this commit compared to the previous one (identified by its SHA).
  5. The first URL the test suite visited to test for accessibility errors
  6. Versions of axe-core and the @axe-core/watcher package

You can click the View Issues** button to see the issues page to find more information about each accessibility error.

See Also

View Accessibility Issues

The Branches Page

The Test Runs Page

The Issues Page