updated a/v page

[LolaValente]

Summary by CodeRabbit

• Documentation
  • Reorganized and improved Audio/Video Chat page with a new Overview and clarified A/V capabilities
  • Updated Call button description and image caption/alignment
  • Replaced prior permissions content with a browser-specific setup matrix (Chrome, Firefox, Safari) and step-by-step enabling instructions
  • Added "Disabling A/V Calls" section explaining organization-owner control over A/V availability

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated the Audio/Video Chat documentation: title adjusted, an Overview added, permissions guidance replaced with a browser-specific setup matrix and step-by-step instructions, image caption and alignment updated, and a new section describing how organization owners can disable A/V calls.

Changes

Cohort / File(s)

Summary

Documentation reorganization source/common/develop/ide/editing/av-chat.rst

Title changed to "Audio/Video Chat"; added an Overview with A/V capability bullets; replaced old permissions text with a "Setting Up Permissions" section and a browser-specific permission matrix (Chrome, Firefox, Safari) with step-by-step enablement; updated image caption to "Audio/Video call button" and centered it; added "Disabling A/V Calls (Organization Owners)" section and noted only owners can change the setting.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Review focus:
  • Verify accuracy and completeness of browser-specific permission steps (Chrome, Firefox, Safari)
  • Confirm the Overview accurately reflects supported A/V capabilities
  • Check the new owner-only disabling instructions for clarity and correctness
  • Validate image caption/alignment change and overall formatting
  • Ensure consistent terminology, tone, grammar, and punctuation throughout

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'updated a/v page' is vague and uses generic phrasing that lacks specificity about the actual content changes.	Provide a more descriptive title that highlights the main changes, such as 'Add audio/video call permission setup guide with browser-specific instructions' or 'Restructure A/V documentation with permission matrix and organization controls'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e877a96 and 50529f3.

📒 Files selected for processing (1)

• source/common/develop/ide/editing/av-chat.rst (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.rst

⚙️ CodeRabbit configuration file

**/*.rst: Review files for:

• Consistent formatting (e.g., headings, lists, links).
• Anywhere there are tables, they should use list-table.
• Clear and concise language.
• Correct grammar and spelling.
• Proper use of rst syntax (e.g., avoid broken links or invalid code blocks).
• Adherence to style guides (e.g., consistent tone, terminology).
  Suggest improvements to enhance readability and accessibility.
• Make sure to find all improvements on the first pass.
  Go through the material multiple times before submitting comments.

Files:

• source/common/develop/ide/editing/av-chat.rst

🔇 Additional comments (5)

source/common/develop/ide/editing/av-chat.rst (5)

1-21: Title, structure, and image updates are well-executed.

The title change to "Audio/Video Chat" and the new Overview section provide clear context upfront. The image alt text has been improved to "Audio/Video call button," and the centered alignment enhances readability. Proper RST heading underlines and metadata are in place.

---

10-32: Overview and permission setup sections are clear and well-organized.

The Overview section effectively communicates purpose and capabilities with a clean bullet list. The "Setting Up Permissions" introduction properly sets context by explaining when the feature will be needed. Grammar and clarity are strong throughout this section.

---

70-76: New "Disabling A/V Calls" section appropriately documents admin capability.

The section clearly explains that organization owners can disable A/V calling, with a helpful note reinforcing permission constraints. The reference to detailed configuration instructions is appropriate. Wording and formatting are consistent with the rest of the documentation.

---

73-76: The cross-reference is valid and requires no changes.

The target reference .. _hideav: exists at source/instructors/admin/organization/hide-av.rst:5, making the :ref:Hide A/V Calls `` reference in the file correctly resolvable. No documentation updates are needed.

---

37-66: I'll verify the accessibility of both URLs now.

Let me search more broadly for the current documentation on these browsers' permission settings:<!-- [scratchpad_start]
[task verification_review_links 2/2]
[observations]
FIREFOX URL:

• Original review: https://support.mozilla.org/en-US/kb/site-permissions-panel
• Web search results show ACTUAL current page: https://support.mozilla.org/en-US/kb/how-manage-your-camera-and-microphone-permissions (or alternative language version at /si/kb/)
• Result 7 from latest search shows Apple URL format at https://support.apple.com/en-al/guide/safari/ibrw7f78f7fe/mac
• Apple page path format: /guide/PRODUCT/ARTICLE-ID/OS with language locale (en-al, en-mt, etc.)

SAFARI URL:

• Original review: https://support.apple.com/en-nz/guide/safari/ibrwe2159f50/mac
• Result 7 shows valid Apple Safari Settings guide at https://support.apple.com/en-al/guide/safari/ibrw7f78f7fe/mac
• Apple uses variable locale codes (en-al, en-mt, not en-nz in search results)
• Result 7 confirms proper Safari Settings > Websites > Camera/Microphone configuration path
• The original Apple URL has correct format but may use outdated/unavailable locale or outdated article ID

[analysis]

• Firefox URL in review (site-permissions-panel) appears to be INCORRECT or OUTDATED
• Correct Firefox support documentation exists but uses different article slug: "how-manage-your-camera-and-microphone-permissions"
• Safari URL format is correct style but the specific locale (en-nz) and/or article ID may be incorrect or outdated
• Both links in the review need verification/updating - URLs are not easily findable with direct searches
• The content being documented (Steps 1-3 for Safari Settings > Websites > Camera/Microphone) aligns with actual Apple documentation path shown in result 7
  [pending]
• Confirmed: Firefox URL is incorrect (wrong article slug)
• Confirmed: Safari URL format appears correct but specific locale/article ID may need checking
• Both external links should be updated or verified
  [done]
• Verification complete: Both URLs require correction or verification
• Firefox link definitely needs update to use correct article name
• Safari link needs verification for locale and article ID validity
  [scratchpad_start]
  -->

Update external documentation links with verified current URLs.

The external support links referenced in the table require verification and correction:

• Mozilla Firefox link: The URL references site-permissions-panel, but current Firefox documentation for managing camera and microphone permissions is available through different support pages. Update to a current, working link such as https://support.mozilla.org/en-US/kb/how-manage-your-camera-and-microphone-permissions.

• Apple Safari link: The URL uses locale code en-nz, which does not appear in Apple's current support documentation pattern. Apple's Safari settings guide for customizing website permissions can be accessed by going to the Safari app, choosing Safari > Settings, then clicking Websites, and selecting the setting to customize like Camera. Verify the locale code and article ID in the Apple URL are current, or replace with a more universally accessible locale variant (e.g., en-us).

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3a37f15 and e877a96.

⛔ Files ignored due to path filters (1)

• source/img/monitor_students/call.png is excluded by !**/*.png, !**/*.png

📒 Files selected for processing (1)

• source/common/develop/ide/editing/av-chat.rst (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.rst

⚙️ CodeRabbit configuration file

**/*.rst: Review files for:

• Consistent formatting (e.g., headings, lists, links).
• Anywhere there are tables, they should use list-table.
• Clear and concise language.
• Correct grammar and spelling.
• Proper use of rst syntax (e.g., avoid broken links or invalid code blocks).
• Adherence to style guides (e.g., consistent tone, terminology).
  Suggest improvements to enhance readability and accessibility.
• Make sure to find all improvements on the first pass.
  Go through the material multiple times before submitting comments.

Files:

• source/common/develop/ide/editing/av-chat.rst

🔇 Additional comments (1)

source/common/develop/ide/editing/av-chat.rst (1)

1-76: Documentation structure and formatting look solid.

The reorganization is clear and well-structured:

• Improved heading hierarchy with appropriate RST formatting
• Overview section effectively introduces the feature and Call button trigger
• Centralized image with descriptive alt text enhances accessibility
• Browser-specific instructions are well-organized in a list-table, making quick reference easy
• External support links for Firefox and Safari provide users with official documentation

The tone is professional and language is generally concise. RST syntax (links, reference labels, bold formatting) appears correct throughout.

Minor suggestions for further review:

• Verify that external links to Mozilla and Apple documentation remain current and accessible
• Consider whether the vertical space marker (| on line 23) is necessary, or if RST's natural spacing between sections is sufficient
• Ensure Firefox and Safari instructions align with current UI in these browsers

[jairovelasquez]

Much better!