Update to Accessibility Checks & Fixes

Changed files

Choose a file to see its text changes. Binary or large files show metadata only.

.codex-plugin/plugin.json →

.mcp.json →

README.md →

assets/icons/inkable-docs-composer-icon-256-dark.png →

assets/icons/inkable-docs-composer-icon-256.png →

assets/icons/inkable-docs-directory-icon-512-dark.png →

assets/icons/inkable-docs-directory-icon-512.png →

assets/icons/inkable-pen-white-background.svg →

mcp.json →

plugin.json →

skills/check-document-accessibility/SKILL.md →

skills/check-document-accessibility/agents/openai.yaml →

skills/fix-office-accessibility/SKILL.md →

skills/fix-office-accessibility/agents/openai.yaml →

README.md

− removed · + added

--- before
+++ after
@@ -1,48 +1,38 @@
-# Inkable Docs plugin package
+# Accessibility Checks & Fixes
 
-This package connects an agent to the production Inkable Docs accessibility-check connector.
+By **Inkable Docs LLC** · package version **1.1.0**
 
-The `plugin.json` metadata is a standalone OpenAI plugin package for Inkable Docs. The connector supports accessibility checks for PDF and DOCX files, plus asynchronous DOCX remediation that returns a new file without replacing the original.
+Check PDF, Word (DOCX), and PowerPoint (PPTX) accessibility. Fix supported Word and PowerPoint issues and download separate updated files. Findings support WCAG and PDF/UA review workflows; automated results do not certify conformance. PDF remediation is unsupported.
 
-## Included capability
+## Tools
 
-- `check_document_accessibility`: start or reuse an accessibility check for an attached PDF or DOCX.
-- `get_accessibility_check`: retrieve the tenant-scoped status or completed report.
-- `remediate_docx_accessibility`: start or reuse asynchronous remediation for an attached DOCX.
-- `get_docx_remediation`: retrieve the remediation status and the completed DOCX file resource.
+| Task                     | Start                          | Retrieve                  |
+| ------------------------ | ------------------------------ | ------------------------- |
+| Check PDF, DOCX, or PPTX | `check_document_accessibility` | `get_accessibility_check` |
+| Fix DOCX                 | `remediate_docx_accessibility` | `get_docx_remediation`    |
+| Fix PPTX                 | `remediate_pptx_accessibility` | `get_pptx_remediation`    |
 
-PDF remediation is not supported. DOCX remediation returns a new file; the original attachment is never replaced.
+The original attachment is preserved. Jobs can be queued or running before completion. Reports and remediation results retain warnings and remaining/deferred checks; completion does not mean every issue was fixed.
 
-## Connection details
+## Packaged skills
 
-- MCP endpoint: `https://inkabledocs.com/mcp`
-- Authentication: OAuth 2.0 Authorization Code with PKCE
-- Authorization server: `https://clerk.inkabledocs.com`
-- Scopes: `checks:run`, `reports:read`
+- **Check accessibility** (`check-document-accessibility`): submit supported original attachments, retrieve reports, and explain findings without overstating WCAG or PDF/UA coverage.
+- **Fix Word & PowerPoint** (`fix-office-accessibility`): select the dedicated format-specific tools, track asynchronous remediation, and deliver the returned Office file with remaining issues.
 
-The package contains a public OAuth client ID only. It intentionally contains no client secret, API key, environment file, database credential, or deployment credential.
+## Connection and files
 
-## OAuth pre-submission checklist
+- MCP endpoint: `https://inkabledocs.com/mcp`.
+- OAuth 2.0 Authorization Code with PKCE; authorization server: `https://clerk.inkabledocs.com`.
+- Existing public OAuth client and scopes `checks:run`, `reports:read` are preserved.
+- ChatGPT inputs use the original `openai/fileParams` attachment contract, including `download_url` and `file_id`.
+- Completed DOCX/PPTX retrieval returns an embedded binary MCP resource. This package does not use Claude's staged uploads or signed-link output.
 
-The Clerk OAuth application for the client ID in `mcp.json` must be configured as a public PKCE client:
+## Package layout
 
-- Exact registered redirect URI: `https://chatgpt.com/connector_platform_oauth_redirect`
-- Client authentication at the token endpoint: none
-- Authorization endpoint: `https://clerk.inkabledocs.com/oauth/authorize`
-- Token endpoint: `https://clerk.inkabledocs.com/oauth/token`
-- Authorization server base: `https://clerk.inkabledocs.com`
-- Allowed scopes: `openid`, `profile`, `email`, `offline_access`, `checks:run`, and `reports:read`
+- `plugin.json`: canonical portable manifest with OpenAI listing, review cases, and release notes.
+- `.codex-plugin/plugin.json`: matching compatibility manifest, with the same identity, version, publisher, listing, and review metadata.
+- `mcp.json` and `.mcp.json`: matching production MCP and public OAuth configuration.
+- `skills/`: two workflows, each declaring its MCP dependency.
+- `assets/icons/`: original Inkable pen geometry on an opaque white tile. Both themes use the black pen on white, at 256px for the composer and 512px for the listing. The SVG source is included.
 
-The redirect URI must match exactly, including scheme, hostname, path, and the absence of a trailing slash. Test-user credentials must be entered only in the submission portal's private testing field, if requested; they must never be placed in this ZIP or committed to the repository.
-
-## Package files
-
-- `plugin.json`: portable Agent Plugins manifest with OpenAI metadata under `extensions.com.openai`.
-- `.codex-plugin/plugin.json`: compatibility manifest recognized by the current submission uploader.
-- This is a standalone package and intentionally does not include an `.app.json` app reference; the MCP connection is configured through the OpenAI dashboard.
-- `mcp.json` and `.mcp.json`: the same remote Streamable HTTP MCP server and OpenAI OAuth configuration in portable and compatibility layouts.
-- `assets/icons/`: the existing black-and-white Inkable Docs icon variants for directory and composer use.
-
-## Upload
-
-Upload the ZIP as a plugin package using the current OpenAI plugin packaging flow. Review the displayed metadata, OAuth settings, tool scan, and test cases before submitting.
+No client secret, API key, private test credentials, environment file, or deployment credential is included.