Contribution Guide
Learn how to responsibly propose additions, edits, or documentation to maintain quality, accessibility, and alignment with community standards.
Begin by verifying your symbol fits Commonsymbols' scope: it should be widely used, culturally neutral, and not tied to proprietary systems. For new submissions, provide the SVG file, Unicode reference if applicable, and a concise description linking to authoritative sources like ISO, Unicode, or recognized standards bodies. Avoid submitting unverified or branded assets unless clearly labeled as optional extras under permissive terms.
Accessibility edits require verifying semantic context: update aria-label, title, and focus behavior to match intended use without over-describing. For symbols like icons or glyphs, ensure assistive technologies read them appropriately—e.g., an empty label for decorative icons or explicit text alternatives for functional ones. Submit edits alongside usage notes, screen reader test results, and examples of correct DOM placement.
Documentation contributions should follow a consistent format: include use case, common pitfalls, internationalization notes, and integration patterns (e.g., inline SVG vs sprite). Reference existing examples from the repository to match style. All content is reviewed against technical accuracy and inclusivity, so contributions include source links and a statement of compliance with accessibility guidelines like WCAG 2.1.
