diff --git a/_community_members/alejandrasevilla.md b/_community_members/alejandrasevilla.md
new file mode 100644
index 0000000000..21b67edd17
--- /dev/null
+++ b/_community_members/alejandrasevilla.md
@@ -0,0 +1,72 @@
+---
+#
+# Sample data for community members.
+#
+
+# The short name is used to identify related pieces of content in the site. For example it is used in the "authors" array of blog posts, and it is used in the "presenters" array for OpenSearch Conference sessions to identify who is speaking.
+# The format for existing values is not normalized. In some cases it is "first-initial-of-first-name" + "last-name", or matching a GitHub username, or something all together random. What is important is that it is unique within the system.
+short_name: "alejandrasevilla"
+
+# The member's full name, or otherwise meaningful preferred name. It is used in the templates for presenting content authors as well as the name of conference speakers.
+name: "Alejandra Sevilla"
+
+# The path to the community member's photo.
+photo: "/assets/media/community/members/alejandrasevilla.jpg"
+
+# Used as the level 1 page header text.
+primary_title: 'Alejandra Sevilla'
+
+# Used as the document title displayed in the browser title bar.
+title: 'OpenSearch Project Community Member: Alejandra Sevilla'
+
+
+# Community member job title and company where they work.
+job_title_and_company: 'UI/UX Product Manager at Protegrity'
+
+# Array of conference IDs for which the community member is a keynote speaker, if any, or boolean false otherwise.
+# This value is only relevant for member's with the "conference_speaker" user persona.
+#keynote_speaker:
+# - '2023-north-america'
+# keynote_speaker: false
+
+# The conference topic track for the conference sessions that the user is a speaker. These are shaped as an array of value pairs mapping conference ID and name.
+# For example for the North American conference for the year 2023, and the "Community" track:
+#session_track:
+# - conference_id: "2023-north-america"
+# name: "Community"
+
+# URL for the community member profile.
+permalink: '/community/members/alejandra-sevilla.html'
+
+# Array of community member user personas.
+# At this time, only conference_speaker, and author are defined.
+personas:
+# - conference_speaker
+ - author
+
+# Array of conference IDs that the member is a speaker.
+#conference_id:
+# - "2023-north-america"
+
+
+# Optional GitHub username
+#github: githubusername
+
+# Optional LinkedIn username
+linkedin: alejandra-sevilla-2514a841
+
+# Optional Twitter username
+#twitter: twitterusername
+
+# Optional Mastodon server url, and username / handle.
+#mastodon:
+# url: https://mastodon.social/@mastodonusername
+# name: mastodonusername
+---
+Alejandra Sevilla is a UI/UX Product Manager at Protegrity, where she applies
+her product management experience to deliver accessible and user-friendly
+digital solutions. Passionate about inclusive design, Alejandra prioritizes
+accessibility in every project she works on. Near the completion of her
+Master’s in Data Analytics at Georgia Tech, Alejandra enjoys using data and
+advocating for using data for good. In her spare time, she enjoys traveling,
+crocheting, and dancing.
\ No newline at end of file
diff --git a/_community_members/kfallis.md b/_community_members/kfallis.md
index 462507f1ec..1636070f59 100644
--- a/_community_members/kfallis.md
+++ b/_community_members/kfallis.md
@@ -4,7 +4,7 @@ name: Kevin Fallis
title: "OpenSearch Project Community Member: Kevin Fallis "
primary_title: Kevin Fallis
permalink: /community/members/kevin-fallis.html
-photo: /assets/media/community/members/kevin-fallis.jpg
+photo: /assets/media/community/members/kevin-fallis.png
job_title_and_company: "Principal Search Specialist at Amazon Web Services"
@@ -23,3 +23,4 @@ linkedin: kevinmichaelfallis
twitter: AWSCodeWarrior
---
+Kevin Fallis is a Principal Search Specialist SA (AWS). He has been with AWS for almost 11 years and has been working with search technologies since 2010 when he used search to power mobile advertising technology. He is passionate about building the future of search on OpenSearch and enjoys building new ideas to further innovation. In his spare time he plays drums, spends time with his family, and is considered Mr. Fixit on the family farm
\ No newline at end of file
diff --git a/_community_members/natalienew.md b/_community_members/natalienew.md
new file mode 100644
index 0000000000..a672d84ef4
--- /dev/null
+++ b/_community_members/natalienew.md
@@ -0,0 +1,64 @@
+---
+#
+# Sample data for community members.
+#
+
+# The short name is used to identify related pieces of content in the site. For example it is used in the "authors" array of blog posts, and it is used in the "presenters" array for OpenSearch Conference sessions to identify who is speaking.
+# The format for existing values is not normalized. In some cases it is "first-initial-of-first-name" + "last-name", or matching a GitHub username, or something all together random. What is important is that it is unique within the system.
+short_name: "natalienew"
+
+# The member's full name, or otherwise meaningful preferred name. It is used in the templates for presenting content authors as well as the name of conference speakers.
+name: "Natalie New"
+
+# The path to the community member's photo.
+photo: "/assets/media/community/members/natalienew.jpg"
+
+# Used as the level 1 page header text.
+primary_title: 'Natalie New'
+
+# Used as the document title displayed in the browser title bar.
+title: 'OpenSearch Project Community Member: Natalie New'
+
+
+
+# Community member job title and company where they work.
+job_title_and_company: 'Sr. Content Project Manager at Protegrity'
+
+
+
+
+# URL for the community member profile.
+permalink: '/community/members/natalie-new.html'
+
+# Array of community member user personas.
+# At this time, only conference_speaker, and author are defined.
+personas:
+ - author
+
+# Array of conference IDs that the member is a speaker.
+#conference_id:
+# - "2023-north-america"
+
+
+# Optional GitHub username
+#github: githubusername
+
+# Optional LinkedIn username
+linkedin: natalie-new94
+
+# Optional Twitter username
+#twitter: twitterusername
+
+# Optional Mastodon server url, and username / handle.
+#mastodon:
+# url: https://mastodon.social/@mastodonusername
+# name: mastodonusername
+---
+Natalie New is the Sr. Content Project Manager at Protegrity and has worked
+in the data security space since 2021 and the content marketing industry
+since 2015. As the mounting requirements of data protection grow, Natalie is
+dedicated to providing the voice and perspective businesses need to
+understand their own data protection nuances and find the security their
+customers and patients have the right to. With proper data protection
+solutions, Natalie believes businesses and data security providers can work
+to create safer digital footprints for a better world.
\ No newline at end of file
diff --git a/_community_members/sonyailevasseur.md b/_community_members/sonyailevasseur.md
new file mode 100644
index 0000000000..32053cecee
--- /dev/null
+++ b/_community_members/sonyailevasseur.md
@@ -0,0 +1,72 @@
+---
+#
+# Sample data for community members.
+#
+
+# The short name is used to identify related pieces of content in the site. For example it is used in the "authors" array of blog posts, and it is used in the "presenters" array for OpenSearch Conference sessions to identify who is speaking.
+# The format for existing values is not normalized. In some cases it is "first-initial-of-first-name" + "last-name", or matching a GitHub username, or something all together random. What is important is that it is unique within the system.
+short_name: "sonyailevasseur"
+
+# The member's full name, or otherwise meaningful preferred name. It is used in the templates for presenting content authors as well as the name of conference speakers.
+name: "Sonya Itchkavich-Levasseur"
+
+# The path to the community member's photo.
+photo: "/assets/media/community/members/sonyailevasseur.jpg"
+
+# Used as the level 1 page header text.
+primary_title: 'Sonya Itchkavich-Levasseur'
+
+# Used as the document title displayed in the browser title bar.
+title: 'OpenSearch Project Community Member: Sonya Itchkavich-Levasseur'
+
+
+# Community member job title and company where they work.
+job_title_and_company: 'UI/UX Product Manager at Protegrity'
+
+# Array of conference IDs for which the community member is a keynote speaker, if any, or boolean false otherwise.
+# This value is only relevant for member's with the "conference_speaker" user persona.
+#keynote_speaker:
+# - '2023-north-america'
+# keynote_speaker: false
+
+# The conference topic track for the conference sessions that the user is a speaker. These are shaped as an array of value pairs mapping conference ID and name.
+# For example for the North American conference for the year 2023, and the "Community" track:
+#session_track:
+# - conference_id: "2023-north-america"
+# name: "Community"
+
+# URL for the community member profile.
+permalink: '/community/members/sonya-itchkavich-levasseur.html'
+
+# Array of community member user personas.
+# At this time, only conference_speaker, and author are defined.
+personas:
+# - conference_speaker
+ - author
+
+# Array of conference IDs that the member is a speaker.
+#conference_id:
+# - "2023-north-america"
+
+
+# Optional GitHub username
+github: sonya.il
+
+# Optional LinkedIn username
+linkedin: sonya-itchkavich-levasseur-9720277
+
+# Optional Twitter username
+#twitter: twitterusername
+
+# Optional Mastodon server url, and username / handle.
+#mastodon:
+# url: https://mastodon.social/@mastodonusername
+# name: mastodonusername
+---
+Sonya Itchkavich-Levasseur is a dedicated UI/UX Product Owner and
+Manager with over 13 years of experience in creating digital experiences
+that serve the customer first. She is passionate about working in data
+security, where customer safety is paramount. Sonya leads her team with
+both empathy and inclusivity, with a strong focus on building user-centered
+interfaces that are intuitive and accessible for all, with the overarching goal
+of bridging the gap between technology and the human experience.
\ No newline at end of file
diff --git a/_data/header_navmenu_datafile.json b/_data/header_navmenu_datafile.json
index ede32fb930..a096cc3cfe 100644
--- a/_data/header_navmenu_datafile.json
+++ b/_data/header_navmenu_datafile.json
@@ -413,7 +413,7 @@
{
"Title": "OpenSearch Project Roadmap",
"ClassValue": "drawer-content-subheader-link",
- "SubText": "Project development plan for 2024-2025 and beyond",
+ "SubText": "Read our blog on 2024-2025 project development plan and beyond!",
"URL": "https://github.com/orgs/opensearch-project/projects/206",
"Roadmap_HeroBanner": "/assets/img/roadmap-graphic.png",
"Roadmap_Link": "https://github.com/orgs/opensearch-project/projects/206"
diff --git a/_includes/icons_navbar.html b/_includes/icons_navbar.html
index 150732b32a..50c1714f2d 100644
--- a/_includes/icons_navbar.html
+++ b/_includes/icons_navbar.html
@@ -60,7 +60,8 @@
{% when 'OpenSearch-Search-DrawerIcon-condensedImage' %}
- {% when 'search-magnifying-glass-navbar' %}
+
+ {% when 'search-magnifying-glass-navbar' %}
+
+
+ {% when 'chevron-in-circle' %}
+
+
{% endcase %}
\ No newline at end of file
diff --git a/_includes/navbar.html b/_includes/navbar.html
index 277a8cc537..7b8ec32c64 100644
--- a/_includes/navbar.html
+++ b/_includes/navbar.html
@@ -119,16 +119,16 @@
diff --git a/_posts/2024-09-18-empowering-action-through-accessibility.md b/_posts/2024-09-18-empowering-action-through-accessibility.md
new file mode 100644
index 0000000000..b8aff73cb4
--- /dev/null
+++ b/_posts/2024-09-18-empowering-action-through-accessibility.md
@@ -0,0 +1,102 @@
+---
+layout: post
+title: Empowering Action Through Accessibility
+authors:
+ - natalienew
+ - alejandrasevilla
+ - sonyailevasseur
+ - pattijuric
+ - apasun
+
+date: 2024-10-11 12:30:00 -0600
+categories:
+ - releases
+meta_keywords: WCAG 2.1 compliance, web content accessibility, Protegrity, OpenSearch data visualization, inclusive design, UX, user experience
+meta_description: Explore how Protegrity uses OpenSearch and embraces WCAG 2.1 compliance to integrate web content accessibility guidelines and data visualizations that foster inclusivity, drive innovation, and utilize secure data.
+---
+Accessibility is no longer just a legal requirement — it's a cornerstone of inclusivity and innovation. At Protegrity, we understand the importance of making our technology accessible to all users, regardless of their abilities, experiences, or expertise levels. Empowering end users makes our customers more effective at data security and, by extension, keeps their customers’ data safe. By embracing accessibility standards such as the Web Content Accessibility Guidelines (WCAG) 2.1, Conformance Level AA Success Criteria, and leveraging data visualizations, we're meeting regulatory requirements and empowering users to take meaningful action.
+
+
+**OpenSearch accessibility**
+
+Our vision is laser-focused on expanding accessibility within our technology using OpenSearch data visualizations. These visualizations simplify complex data sets and empower a broader community within our businesses to interpret logs and take actionable steps. By reducing the need for security and data expertise, [OpenSearch data visualizations](https://opensearch.org/docs/latest/dashboards/visualize/viz-index/) enable users at all levels to protect our data effectively, make informed decisions, and drive meaningful action.
+
+**Empowering professionals using accessibility insights**
+
+Protegrity provides data security solutions, such as Insight and various data protection methods for managing access to sensitive data (e.g., PII and PHI). In order to strengthen their data security posture, enterprises need data protection solutions and an auditing mechanism to keep records of operations performed on sensitive data. Protegrity Insight is an auditing, monitoring, and analysis solution that helps security analysts keep track of security events and respond quickly and effectively.
+
+
+Security analysts can use Insight’s User Behavior Analytics (UBA) to analyze erratic actions of users/systems and identify potential risks. This helps identify irregular patterns, such as unauthorized access attempts, security threats, and data breaches. Insight is a central system for analysis, wherein Protegrity security operation logs are collected and analyzed for user activity across the IT environment. From there, Insight appropriately responds to security events that can impact an enterprise. Protegrity Insight utilizes various functionalities of OpenSearch to provide highly flexible, scalable, and robust data-processing enterprises need for their security solutions.
+
+
+Insight provides ease of analysis via its Visualization Layer based on OpenSearch Dashboards. It provides various functionalities, like full-text search, pattern matching, etc., enabling users to find audit log data easily and quickly without writing complex queries. The ability to create visualizations, alerts, monitor dashboards, and more makes it a powerful tool that can help security analysts and cloud administrators manage the security and function of an enterprise’s infrastructure.
+
+**Adhering to WCAG 2.1**
+
+Protegrity recognizes that democratizing data security empowers users to protect sensitive data, which remains a core part of our mission. We're committed to investing in accessibility initiatives across our products and websites, adhering to WCAG 2.1, Conformance Level AA Success Criteria. This criterion ensures that our technology is accessible to all users, regardless of their abilities or assistive technologies, reflected in user experience using the four principles of accessibility, POUR:
+
+
+
+* **Perceivable:** Users should be able to perceive all information in your content, including interface components.
+* **Operable:** Users should be able to navigate and operate your interface component easily and successfully.
+* **Understandable:** All information and interface elements should be easy to understand and operate.
+* **Robust:** Content should be robust and reliable so that various user agents and assistive technologies can interpret it.
+
+**Insight's visualizations promote action with precision**
+
+One core use case for Insights is identifying potential risks. These can be user-based systems, applications, and more. Using audit logs from various systems, administrators can create alerts, monitoring, and visualizations with combinations of user-generated events on a system and across date and time ranges. Visualizations can easily detect any outliers in security audit logs, allowing administrators to take appropriate action.
+Examples:
+
+* A security Analyst can utilize User Behavior Analytics (UBA)
+* A user accessed a data asset over the weekend — this is an uncommon behavior. Using visualizations for access logs, we can easily identify who accesses which system, and at what date and time
+* A visualization that maps authorized and unauthorized access for a data asset can be helpful to identify security gaps. From there, an admin or security analyst can devise an appropriate action plan
+* A visualization shows a user has accessed a database; however, the user is not entitled to have that access. This information can help to avoid unauthorized access to data or a potential data breach
+
+
+
+To better adhere to positive user experiences, we’ve updated our product UIs to make them easier to navigate and more user-friendly. These updates benefit users with disabilities and enhance the usability of our solutions for all users. Additionally, our website and customer portal updates focus on making information easily accessible and presenting it in a format that meets diverse user needs.
+
+
+By prioritizing accessibility in everything we do, we ensure that our technology is accessible to all users, regardless of their abilities or expertise.
+
+
+
+
+
+
+
+
+This shows the trend graph for logs that are ingested in OpenSearch for a given time frame.
+
+**How we’re improving the user experience**
+
+We have partnered with a third-party accessibility evaluation vendor to assess accessibility in the user experience for Enterprise Security Administrator, Data Security Gateway, the Protegrity website, documentation, and customer portal.
+
+
+The Protegrity website and customer portal now display icons as visual cues, indicating that our digital properties are accessible. They link back to our [_Protegrity Accessibility Statement page_](https://www.protegrity.com/accessibility-statement), which outlines our commitment to accessibility across all user interfaces.
+
+
+We have fixed over 90 accessibility issues in this process including:
+
+
+
+* Keyboard operability of controls, buttons, details, tabs, and dropdown menus
+* Guarantee proper color contrast for text and interactive elements
+* Solve focus order and keyboard navigation issues
+* Screen reader compatibility for data tables
+* Addressing other identified accessibility concerns identified by Level Access
+
+
+
+In conclusion, integrating accessibility standards and enhancing data visualizations isn't just a legal requirement — it is a fundamental aspect of creating an inclusive and innovative environment.
+
+
+At Protegrity, we're committed to empowering all users to take meaningful action by making our technology accessible to anyone, including those who require optimized interfaces. Now, all users can:
+
+* Maximize their keyword operability
+* Navigate color contrasts on-screen
+* Enjoy data table screen reader compatibility
+
+And more. Making these improvements allows those of the vision and mobility impaired to access data systems with their needs in mind, allowing disabled communities to not only improve their current working conditions in technical fields, but also experience new job opportunities to advance their careers.
+
+By embracing accessibility and using OpenSearch Dashboards we are meeting regulatory requirements, fostering inclusivity, and driving innovation for those who will safely utilize secure data to make our world a better place.
\ No newline at end of file
diff --git a/_sass/_navbar.scss b/_sass/_navbar.scss
index 25cf81b1b2..f1844f7853 100644
--- a/_sass/_navbar.scss
+++ b/_sass/_navbar.scss
@@ -88,25 +88,41 @@
.btn-primary-dark {
--bs-btn-padding-y: 15px;
- --bs-btn-padding-x: 25px;
+ --bs-btn-padding-x: 20px;
background-color: $primary-open-sky-s1;
border-radius: 0px;
color: $secondary-sanfrancisco-fog-t1;
- font-size: 18px;
+ font-size: 15px;
font-weight: 700;
line-height: 24px;
border-radius: 30px;
+ text-wrap: nowrap;
- --bs-btn-active-color: $secondary-golden-poppy;
- --bs-btn-active-bg:$primary-open-sky-s3;
-
+ // --bs-btn-active-color: $secondary-golden-poppy;
+ // --bs-btn-active-bg:$primary-open-sky-s3;
+ > .button-content-icon-svg {
+ fill: $secondary-sanfrancisco-fog-t1;
+ margin-bottom: 2px;
+ }
&:active {
- background-color: $primary-open-sky-s3;
- color: $secondary-golden-poppy;
+ background-color: $primary-open-sky-s3 !important;
}
&:hover {
background-color: $primary-open-sky-s3;
+ color: $secondary-sanfrancisco-fog-t1;
+ }
+ &:active > .button-content {
+
+ > .button-content-icon {
+ > .button-content-icon-svg{
+ fill: $secondary-golden-poppy;
+ }
+ }
+ > .button-content-text {
+ color: $secondary-golden-poppy;
+ }
+
}
&:visited {
color: $secondary-sanfrancisco-fog-t1;
@@ -115,8 +131,32 @@
+.button-content-icon-svg {
+ fill: $secondary-sanfrancisco-fog-t1;
+ margin-bottom: 2px;
+
+ // &:has( + input:active) {
+ // fill: $secondary-golden-poppy;
+ // }
+
+ // &:active {
+ // fill: $secondary-golden-poppy;
+ // }
+ // &:hover {
+ // fill: $secondary-sanfrancisco-fog-t1;
+ // }
+ &:visited {
+ fill: $secondary-sanfrancisco-fog-t1;
+ }
+}
+// .navbar-downloads-button {
+// &:hover {
+// border-color: #006D97;
+// color: #003551;
+// }
+// }
.button-dark {
// --bs-btn-color: $secondary-sanfrancisco-fog-t1;
@@ -200,17 +240,17 @@
}
.nav-drawer-triangle {
- z-index: 1;
+ z-index: 0;
}
.nav-search-icon {
- background-color: #B9D9EB;
+ background-color: $primary-open-sky-s1;
padding-top: 100px;
&:active,
&:focus,
&:hover {
- background-color: #006D97;
+ background-color: $primary-open-sky-s3;
box-shadow: none;
outline: none;
}
@@ -279,6 +319,7 @@
font-size: 30px;
font-weight: 700;
text-decoration: none;
+ z-index: 1;
}
.drawer-content-header-link {
color: $primary-open-sky-s3;
@@ -287,6 +328,7 @@
font-size: 30px;
font-weight: 700;
text-decoration: underline;
+ z-index: 1;
&:hover {
color: $primary-open-sky;
@@ -298,7 +340,8 @@
font-size: 21px;
font-weight: 700;
line-height: 36px;
- text-decoration: none;
+ text-decoration: none;
+ z-index: 1;
}
.drawer-content-subheader-link {
color: $primary-open-sky-s2;
@@ -306,6 +349,7 @@
font-weight: 700;
line-height: 36px;
text-decoration: underline;
+ z-index: 1;
&:hover {
color: $primary-open-sky;
text-decoration: underline;
@@ -318,6 +362,7 @@
line-height: 24px;
word-wrap: break-word;
text-decoration: none;
+ z-index: 1;
}
.drawer-content-text-link {
color: $primary-open-sky-s3;
@@ -326,6 +371,7 @@
line-height: 24px;
word-wrap: break-word;
text-decoration: none;
+ z-index: 1;
&:hover {
color: $primary-open-sky;
diff --git a/_sass/_opensearch.scss b/_sass/_opensearch.scss
index 283e647d8f..24436c8b90 100644
--- a/_sass/_opensearch.scss
+++ b/_sass/_opensearch.scss
@@ -102,13 +102,11 @@
.img-fluid {
max-width: 100%;
height: auto;
- border: 1px solid $line-lighter;
}
.img-centered {
max-width: 100%;
margin: 0 auto;
display: block;
- border: 1px solid $line-lighter;
}
.downloads-page {
.layout-2col {
@@ -506,7 +504,14 @@
}
.page--blog-post {
-
+ #content-main {
+ img {
+ padding: 10px;
+ border: 1px solid $line-lighter;
+ border-radius: 4px;
+ box-shadow: 0 1px 2px rgba(0, 0, 0, 0.12), 0 3px 10px rgba(0, 0, 0, 0.08);
+ }
+ }
.highlight pre, .highlight code {
border: none;
diff --git a/assets/media/blog-images/2024-09-18-empowering-action-through-accessibility/Figure-1.png b/assets/media/blog-images/2024-09-18-empowering-action-through-accessibility/Figure-1.png
new file mode 100644
index 0000000000..2807126215
Binary files /dev/null and b/assets/media/blog-images/2024-09-18-empowering-action-through-accessibility/Figure-1.png differ
diff --git a/assets/media/community/members/alejandrasevilla.jpg b/assets/media/community/members/alejandrasevilla.jpg
new file mode 100644
index 0000000000..8842a6ae24
Binary files /dev/null and b/assets/media/community/members/alejandrasevilla.jpg differ
diff --git a/assets/media/community/members/kevin-fallis.png b/assets/media/community/members/kevin-fallis.png
new file mode 100644
index 0000000000..a3888e9fa5
Binary files /dev/null and b/assets/media/community/members/kevin-fallis.png differ
diff --git a/assets/media/community/members/natalienew.jpg b/assets/media/community/members/natalienew.jpg
new file mode 100644
index 0000000000..2342d709ed
Binary files /dev/null and b/assets/media/community/members/natalienew.jpg differ
diff --git a/assets/media/community/members/sonyailevasseur.jpg b/assets/media/community/members/sonyailevasseur.jpg
new file mode 100644
index 0000000000..3d927d990b
Binary files /dev/null and b/assets/media/community/members/sonyailevasseur.jpg differ
{% when 'OpenSearch-Search-DrawerIcon-condensedImage' %}
- {% when 'search-magnifying-glass-navbar' %}
+
+ {% when 'search-magnifying-glass-navbar' %}
+
+
+ {% when 'chevron-in-circle' %}
+
+
{% endcase %}
\ No newline at end of file
diff --git a/_includes/navbar.html b/_includes/navbar.html
index 277a8cc537..7b8ec32c64 100644
--- a/_includes/navbar.html
+++ b/_includes/navbar.html
@@ -119,16 +119,16 @@