diff --git a/accessability.md b/accessability.md
new file mode 100644
index 0000000000..30ec84b16b
--- /dev/null
+++ b/accessability.md
@@ -0,0 +1,41 @@
+In open source development, prioritizing accessibility is paramount for fostering inclusivity and ensuring that all individuals, regardless of their abilities, can actively participate in and benefit from the project. By welcoming disabled developers and users, we not only enrich our community with diverse perspectives but also create software that better serves the needs of everyone.  
+   
+
+As part of our commitment to accessibility, CVE Bin Tool proudly pledges its support for the Global Accessibility Awareness Day (GAAD), advocating for awareness, best practices, and active engagement with disabled communities to create a more inclusive digital environment. Join us in building a community where everyone's contributions and experiences are valued and respected.  
+ 
+CVE Bin Tool GAAD Pledge 
+ - Implement an Accessibility issue template.  
+ - Conform to WCAG 2.1 AA standards where appropriate 
+ - Create an Accessibility coding standard for the project 
+ - Create an Accessibility documentation standard for the project  
+ - Implement an accessibility sphinx template 
+ - Test for accessibility using CVE Bin Tool 
+  
+  
+
+Centering accessibility in software development involves placing it at the core of the development process rather than treating it as an afterthought or optional feature. By prioritizing accessibility from the outset, developers ensure that all users, regardless of their abilities, can engage fully with the software. This approach involves integrating accessibility considerations into every stage of development, from design and coding to testing and deployment.   
+
+Accessibility Coding Standards 
+
+ - Use platform-specific accessibility APIs (such as Microsoft Active Accessibility or UI Automation for Windows, and Accessibility APIs for macOS) to expose application functionality to assistive technologies. 
+ - Support screen reader compatibility by providing accessible names, descriptions, and roles for UI components. 
+ - Implement high-contrast themes or provide options for users to adjust color contrast and text size for better readability. 
+ - Use appropriate error handling techniques, including clear error messages and suggestions for resolving issues, to assist users with disabilities. 
+
+Accessible documentation standards 
+
+ - Use semantic HTML elements (e.g., <header>, <nav>, <main>, <footer>) to structure content. 
+ - Provide descriptive and concise alt text for images using the alt attribute. 
+ - Ensure keyboard accessibility by making all functionality available via keyboard navigation. 
+ - Ensure sufficient color contrast between text and background colors to improve readability. 
+ - Provide meaningful headings and use them to structure content hierarchically. 
+ - Ensure that all interactive elements are accessible to screen readers and other assistive technologies. 
+ - Update project documentation for better accessibility and adopt the Intel One Monospace font for code in documentation where possible.  
+  
+ 
+We extend a warm invitation to developers passionate about accessibility to join us in our mission to make CVE Bin Tool more inclusive and user-friendly for individuals of all abilities. Your expertise and insights are invaluable as we strive to implement best practices and ensure that our software is accessible to everyone. Whether you have experience in accessible design, user testing, or simply a desire to contribute to a more inclusive digital landscape, your contributions are highly valued and will help us make a meaningful difference.  
+
+ - Submit a new accessibility Issues using the Accessibility issue tag 
+ - Review known accessibility issues (current number [0])  
+ - Update our documentation for clarity and readability 
+ - Read our Accessibility Coding Standard before creating a pull request