Skip to main content
Labrador keeps all discussion about your audit findings in one place. Team members can leave comments directly on individual issues and criterion results, so conversations stay tied to the specific finding they relate to, no need to track decisions through a separate Slack thread or email chain. When something changes or a new comment appears, Labrador notifies the relevant team members automatically.
Team comments and notifications are available on Plus and Enterprise plans. Free and Core plans are single-user and do not include collaborative commenting or the notifications system.

​
Leaving a Comment

Comments are attached to specific issues within a project, keeping feedback in context and visible to everyone on the team who has access.
1

Navigate to the issue

Open the project, select the relevant page or component, and click through to the issue you want to comment on.
2

Find the Comments section

Scroll to the Comments section within the issue view. This appears below the issue details and any attached media.
3

Write and submit your comment

Type your comment in the input field. Once you’re ready, submit it to post it to the thread. All team members with access to the project will be notified that a new comment has been left.

​
What You Can Comment On

Labrador supports comments at multiple levels of the audit, so discussions stay as close to the source finding as possible.

Individual Issues

Leave comments directly on a logged issue, for example, to ask a clarifying question about a finding, note that a fix is underway, or give developers additional context about the expected remediation approach.

Criterion-Level Results

Add comments to criterion results to discuss how a particular WCAG success criterion was evaluated, flag edge cases, or coordinate with teammates on how to handle a borderline pass or fail. Available on Plus and Enterprise.
Use the Developer role for teammates who only need to update remediation status and leave fix-related comments, they won’t accidentally alter your audit results or criterion assessments.

​
Notifications

Labrador sends notifications to keep team members informed when something relevant happens in a project they’re part of. Notifications are designed to surface the updates that actually require your attention, rather than alerting everyone about every change.
When a teammate leaves a comment on an issue you’ve contributed to, whether you logged it, commented on it previously, or are assigned to it, Labrador notifies you so you can follow up without having to poll the project manually.
When the remediation status of an issue changes, for example, when a developer marks it as Fixed for Retesting or Closed, team members who are involved in that issue receive a notification. This keeps auditors and developers aligned without requiring a manual status check.
When a new team member joins a project or when project-level changes occur that affect your access or workflow, you’ll receive a notification to keep you informed.
To view your notifications, click the notifications icon in the app. Unread notifications are indicated by a badge on the icon.

​
Managing Notification Preferences

You control which notifications Labrador sends you. If you find certain alerts aren’t useful for your role, you can turn them off without affecting what your teammates receive.
1

Open your account settings

Click on your account avatar or name in the app to access your account settings.
2

Navigate to notification preferences

Find the Notifications section within your account settings.
3

Update your preferences

Toggle individual notification types on or off to match how you prefer to stay informed. Changes take effect immediately.
Notification preferences are per-account, not per-project. Any changes you make apply across all projects you’re a member of.