Conversation
WalkthroughThe 🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@buffer-web.md`:
- Around line 459-460: The table links currently point to "#document-top"
instead of the actual WCAG section; update each anchor href that wraps the "WCAG
2.x" text to target the exact heading id of the WCAG 2.x section (replace
href="#document-top" with the real id, e.g., "#wcag-2-x" or whatever id the WCAG
heading generates) for the occurrences around the "WCAG 2.x" link (including the
rows shown and the other occurrences noted: 464-465, 528-529, 725-726, 730-731,
750-751, 789-790, 804-805) so the links navigate directly to the WCAG heading.
- Line 13: Update the product scope sentence that currently reads "This report
covers accessibility conformance for the Buffer web application, which includes
the product suite Publish, Analyze, and Start Page." to include Engage so it
matches the PR objective (Publish, Analyze, Engage, and Start Page); locate and
edit the exact Notes line (the HTML-bold "Notes:" sentence) in buffer-web.md and
make the product list consistent across the document/report.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| <b>Contact Information:</b> <a href="mailto:accessibility@buffer.com">accessibility@buffer.com</a> | ||
|
|
||
| <b>Contact Information:</b> <a href = "mailto: accessibility@buffer.com">accessibility@buffer.com</a> | ||
| <b>Notes:</b> This report covers accessibility conformance for the Buffer web application, which includes the product suite Publish, Analyze, and Start Page. |
There was a problem hiding this comment.
Product scope appears incomplete for this VPAT update.
Line 13 excludes Engage, while the PR objective states this report covers Publish, Analyze, Engage, and Start Page. In a conformance report, this scope mismatch can create compliance ambiguity.
Suggested fix
-<b>Notes:</b> This report covers accessibility conformance for the Buffer web application, which includes the product suite Publish, Analyze, and Start Page.
+<b>Notes:</b> This report covers accessibility conformance for the Buffer web application, which includes the product suite Publish, Analyze, Engage, and Start Page.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| <b>Notes:</b> This report covers accessibility conformance for the Buffer web application, which includes the product suite Publish, Analyze, and Start Page. | |
| <b>Notes:</b> This report covers accessibility conformance for the Buffer web application, which includes the product suite Publish, Analyze, Engage, and Start Page. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@buffer-web.md` at line 13, Update the product scope sentence that currently
reads "This report covers accessibility conformance for the Buffer web
application, which includes the product suite Publish, Analyze, and Start Page."
to include Engage so it matches the PR objective (Publish, Analyze, Engage, and
Start Page); locate and edit the exact Notes line (the HTML-bold "Notes:"
sentence) in buffer-web.md and make the product list consistent across the
document/report.
There was a problem hiding this comment.
🧹 Nitpick comments (1)
buffer-web.md (1)
377-377: Clarify conformance scope wording to match included Level A table.Line 377 says the report is against “Level AA,” but this VPAT also includes Level A criteria (Table 1). Consider clarifying this sentence to avoid audit-reader confusion (e.g., “reports against WCAG 2.2 Levels A and AA”).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@buffer-web.md` at line 377, Update the conformance-scope sentence that currently reads “reports against WCAG 2.2 Level AA” to explicitly include Level A (e.g., change the phrase "WCAG 2.2 Level AA" to "WCAG 2.2 Levels A and AA" or "WCAG 2.2 Level A and AA") so the statement matches the included Table 1; locate the exact sentence containing "Level AA" in buffer-web.md and revise it to mention both Levels A and AA.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@buffer-web.md`:
- Line 377: Update the conformance-scope sentence that currently reads “reports
against WCAG 2.2 Level AA” to explicitly include Level A (e.g., change the
phrase "WCAG 2.2 Level AA" to "WCAG 2.2 Levels A and AA" or "WCAG 2.2 Level A
and AA") so the statement matches the included Table 1; locate the exact
sentence containing "Level AA" in buffer-web.md and revise it to mention both
Levels A and AA.
| ## Table 2: Success Criteria, Level AA | ||
| ### Table 3: Success Criteria, Level AAA | ||
|
|
||
| This report does not include Level AAA criteria. Buffer is reporting against WCAG 2.2 Level AA, including WCAG 2.1 Level AA criteria. |
There was a problem hiding this comment.
Wording says "reports against WCAG 2.2 Level AA" but Table 1 below covers Level A criteria as well. Suggest "WCAG 2.2 Levels A and AA" to avoid customer/auditor confusion.
| <b>Platform:</b> Web | ||
|
|
||
| <b>Date:</b> August 2020 | ||
| <b>Date:</b> April 2026 |
There was a problem hiding this comment.
Consider adding a brief "Last Audited" date distinct from the report date, especially if re-audit cadence is important for compliance procurement. Alternatively, clarify whether the April 2026 date represents audit completion or publication.
This is a good Claude suggestion, could be interesting to keep track of historical audits publicly so it shows is not a dormant document.
There was a problem hiding this comment.
Thanks for raising this @magarcia . This is something on my task list, to define some follow-up/improvements/future flows for VPAT + Accessibility moving forward.
One goal moving forward will be to have a plan in place, where we can automate a lot of this flow to ensure this document is updated + reviewed at a minimum anually.
But also with some automated scans ~quarterly/half-yearly to ensure maintenance is kept up with and the yearly update is a minimal task 🤔
| <b>Contact Information:</b> <a href="mailto:accessibility@buffer.com">accessibility@buffer.com</a> | ||
|
|
||
| <b>Contact Information:</b> <a href = "mailto: accessibility@buffer.com">accessibility@buffer.com</a> | ||
| <b>Notes:</b> This report covers accessibility conformance for the Buffer web application, which includes the product suite Publish, Analyze, and Start Page. |
There was a problem hiding this comment.
Engage is deprecated, so you can safely ignore the comment above, but just wanted to point our Community and whether we want to mention that here.
There was a problem hiding this comment.
Thanks for mentioning that @dace ! I was torn in some areas what wording to use. For this section in particular I opted to word it as the 3 seperate product "Publish, Analyze, and Start Page" as they all have there own domains. Which led me to leave out sub areas of publish – Community, Insight, Create, Feeds etc as the list felt quite long and cumbersome.
Happy to update if you feel strongly they should be mentioned here though!
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
buffer-web.md (1)
377-377: Consider simplifying the Level AAA exclusion statement.The phrase "including WCAG 2.1 Level AA criteria" may cause confusion, as WCAG 2.2 Level AA inherently includes all WCAG 2.1 Level AA criteria (the standard is cumulative). The current wording might suggest they are being evaluated separately.
♻️ Clearer alternative wording
-This report does not include Level AAA criteria. Buffer is reporting against WCAG 2.2 Levels A and AA, including WCAG 2.1 Level AA criteria. +This report does not include Level AAA criteria. Buffer is reporting against WCAG 2.2 Levels A and AA.Alternatively, if you want to emphasize the version coverage:
-This report does not include Level AAA criteria. Buffer is reporting against WCAG 2.2 Levels A and AA, including WCAG 2.1 Level AA criteria. +This report does not include Level AAA criteria. Buffer is reporting against WCAG 2.2 Levels A and AA (which incorporates all WCAG 2.1 criteria).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@buffer-web.md` at line 377, Replace the sentence "This report does not include Level AAA criteria. Buffer is reporting against WCAG 2.2 Levels A and AA, including WCAG 2.1 Level AA criteria." in buffer-web.md by removing the redundant "including WCAG 2.1 Level AA criteria" clause; update it to a simpler clear form such as "This report does not include Level AAA criteria. Buffer is reporting against WCAG 2.2 Levels A and AA." to avoid implying separate evaluation of WCAG 2.1 and WCAG 2.2.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@buffer-web.md`:
- Line 55: Update the list item text for "Not Evaluated" to clarify scope:
change the sentence that currently reads "This can only be used in WCAG Level
AAA criteria" so it instead explains that "Not Evaluated" may be applied to any
criterion the organization chooses not to assess and that the restriction to
WCAG Level AAA is specific to this report's scope; locate the list element
containing the phrase "Not Evaluated" in buffer-web.md and replace the wording
accordingly to make the scope limitation explicit.
---
Nitpick comments:
In `@buffer-web.md`:
- Line 377: Replace the sentence "This report does not include Level AAA
criteria. Buffer is reporting against WCAG 2.2 Levels A and AA, including WCAG
2.1 Level AA criteria." in buffer-web.md by removing the redundant "including
WCAG 2.1 Level AA criteria" clause; update it to a simpler clear form such as
"This report does not include Level AAA criteria. Buffer is reporting against
WCAG 2.2 Levels A and AA." to avoid implying separate evaluation of WCAG 2.1 and
WCAG 2.2.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| <li><b>Partially Supports:</b> Some functionality of the product does not meet the criterion.</li> | ||
| <li><b>Does Not Support:</b> The majority of product functionality does not meet the criterion.</li> | ||
| <li><b>Not Applicable:</b> The criterion is not relevant to the product.</li> | ||
| <li><b>Not Evaluated:</b> The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.</li> |
There was a problem hiding this comment.
Clarify scope limitation for "Not Evaluated" term.
The current wording states "This can only be used in WCAG Level AAA criteria," which reads as a universal VPAT rule. In fact, "Not Evaluated" can apply to any criterion the organization chooses not to assess. The restriction to Level AAA is specific to this report's scope.
📝 Suggested clarification
- <li><b>Not Evaluated:</b> The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.</li>
+ <li><b>Not Evaluated:</b> The product has not been evaluated against the criterion. In this report, this is used only for WCAG Level AAA criteria.</li>📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| <li><b>Not Evaluated:</b> The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.</li> | |
| <li><b>Not Evaluated:</b> The product has not been evaluated against the criterion. In this report, this is used only for WCAG Level AAA criteria.</li> |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@buffer-web.md` at line 55, Update the list item text for "Not Evaluated" to
clarify scope: change the sentence that currently reads "This can only be used
in WCAG Level AAA criteria" so it instead explains that "Not Evaluated" may be
applied to any criterion the organization chooses not to assess and that the
restriction to WCAG Level AAA is specific to this report's scope; locate the
list element containing the phrase "Not Evaluated" in buffer-web.md and replace
the wording accordingly to make the scope limitation explicit.
3 participants
Summary
Replaces the 2020 web VPAT with a fully refreshed April 2026 edition reflecting Buffer's current accessibility posture across Publish, Analyze, and Start Page.
What changed
Why
The previous VPAT was five years old and referenced a superseded WCAG version. This replacement brings Buffer's public accessibility statement up to current reporting standards and reflects improvements shipped since 2020 (e.g., route-aware page titles, accessible name fixes in channel-connection flows) as well as gaps that remain (e.g., legacy areas in Analyze and Start Page).
Summary by CodeRabbit