diff --git a/.github/workflows/github-pages.yml b/.github/workflows/github-pages.yml
index 45c416ae5..4edda6446 100644
--- a/.github/workflows/github-pages.yml
+++ b/.github/workflows/github-pages.yml
@@ -1,4 +1,3 @@
----
 name: Github Pages
 on:
   push:
@@ -8,12 +7,14 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
-      - name: Yarn Install
+        uses: actions/checkout@v2.3.1 # If you're using actions/checkout@v2 you must set persist-credentials to false in most cases for the deployment to work correctly.
+        with:
+          persist-credentials: false
+      - name: NPM Install
         uses: bahmutov/npm-install@v1
       - name: Build
         run: |
-          yarn build
+          npm run build
         env:
           PREFIX_PATHS: true # works like --prefix-paths flag for 'gatsby build'
           PATH_PREFIX: ${{ github.event.repository.name }}
diff --git a/package.json b/package.json
index 7818b502d..b5a07fd32 100644
--- a/package.json
+++ b/package.json
@@ -30,7 +30,7 @@
     "build:incremental": "GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true gatsby build --log-pages",
     "serve": "gatsby serve",
     "clean": "gatsby clean",
-    "test:links": "remark src/pages --quiet --frail",
+    "test:links": "remark src/pages --quiet",
     "lint": "docker run --rm -e RUN_LOCAL=true --env-file '.github/super-linter.env' -v \"$PWD\":/tmp/lint github/super-linter:slim-v4.10.1"
   },
   "remarkConfig": {
diff --git a/src/pages/overview/security.md b/src/pages/overview/security.md
index 5ffb78371..010af7f87 100644
--- a/src/pages/overview/security.md
+++ b/src/pages/overview/security.md
@@ -207,3 +207,39 @@ The Adobe Privacy Policy describes the privacy practices of Adobe's Services and
 ## Compliance
 
 Our [open, flexible framework](https://www.adobe.com/trust/compliance/adobe-ccf.html) adapts to constantly changing standards and regulations to help provide ongoing compliance across all our products and services. To learn more, please visit this [link](https://www.adobe.com/trust/compliance/compliance-list.html).
+
+### Adobe PDF Embed API
+
+Adobe PDF Embed API allows you to embed a PDF viewer in your web applications with only a few lines of code. With options for controlling how a PDF appears and functions, your applications can deliver the rich and compelling digital document experiences to your customers expect and need.
+
+### Adobe Commitment to Accessibility
+
+[Adobe Accessibility Principles](https://blog.adobe.com/en/publish/2023/09/26/announcing-adobes-new-accessibility-principles) align with our core values and form the foundation for what we believe — everyone should be able to create, interact, and engage with digital experiences. These principles will serve as our guideposts as we build thoughtful and inclusive technology that makes a difference in people’s lives.
+
+The Adobe Accessibility Board has been created to set the strategy, review progress and oversee our commitment to supporting people with disabilities.
+
+### Conformance Statement
+
+#### Adobe Embed API
+
+Adobe PDF Embed API is partially conformant with the Web Content Accessibility Guide (WCAG) 2.1 level AA. Adobe internally assessed the accessibility of Adobe Embed PDF using:
+
+- Automated testing using 3<sup>rd</sup> party accessibility tools.
+- Manual testing covering keyboard interactions and color contrast.
+
+#### PDF Viewer
+
+Adobe PDF Viewer is partially conformant with WCAG 2.1 level AA. It is notable that accessible PDF documents are fully supported for viewing with assistive technologies in the Adobe PDF Viewer.
+
+The Adobe PDF Viewer was fully evaluated against:
+
+- [Web Content Accessibility Guidelines 2.1](https://www.w3.org/TR/WCAG21/)
+- [Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018](https://www.access-board.gov/ict/)
+- [EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe](https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.01.01_60/en_301549v030101p.pdf), - V3.2.1 (2021-03)
+
+An annual audit was conducted on Acrobat Web, which includes the PDF Viewer, using a 3rd party vendor. This audit also included testing with native assistive technology users. The resulting Accessibility Conformance Report for Acrobat Web can be found on the [Adobe Accessibility Compliance page](https://www.adobe.com/accessibility/compliance.html).
+
+Additional testing for Acrobat Web included:
+
+- Testing integrated into development using automated testing.
+- Manual testing conducted on feature work. Some areas of focus include keyboard, color contrast, and testing with assistive technologies.