FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, Icinga

•Transferir como PPTX, PDF•

0 gostou•65 visualizações

Do you know what it feels like to navigate as someone who can’t distinguish between green and red - looking at those badges that tell you whether something is broken or a-okay? I’ll give you a quick look into what it feels like with some examples from the monitoring tool Icinga Web 2. We all tend to forget, that not everyone sees the world like we do. In this talk I’ll be walking you through different views in Icinga Web 2 with side-by-side comparisons for the default views and how different kinds of vision impairments affect those. The talks also features a few suggestions on how to improve colour schemes and making websites and webapps better to navigate with screen readers!

Tecnologia

Accessibility in Icinga
Flying Blind
by Feu Mourek

the quality or characteristic of something that makes it possible to approach, enter, or use it
/ɪkˈses·əˈbɪl·ɪ·t̬i/ noun
(Definition of accessibility from the Cambridge Business English Dictionary © Cambridge University Press)
Accessibility

Numbers!
(numbers from colourblindawareness.org)
285 Million globally … or 1 out of these here:

Colour Vision Deficiency
(made with Color Oracle and Sketch)

Common Variants
Deuteranopia Tritanopi
a
Protanopia

Colours in Icinga
(made with Color Oracle and Sketch)

Keep that in mind!
(numbers from https://www.ncwit.org )

See for yourself
(made with Color Oracle and Sketch)

Video time!
https://www.youtube.com/watch?v=q_ATY9gimOM

Structure
Content needs to be weighted
If it is not, there is no way of telling what is important, without looking at everything.
While styling can tell sighted people what to focus on, we need to look at the structure too.

Static content
A lot of websites use iframes and other widgets that they do not control directly.
To these cases you need to pay special attention, and maybe add an alternative description to
what they are supposed to show.
The alternative descriptions are also needed for images, which you need to describe in the alt
attribute.

Structure
( from developer.mozilla.org )

State changes
ARIA provides attributes for declaring the current state of a UI widget.
aria-checked: indicates the state of a checkbox or radio button
aria-disabled: indicates that an element is visible, but not editable or otherwise operable
aria-grabbed: indicates the 'grabbed' state of an object in a drag-and-drop operation
Use CSS attribute selectors to alter the visual appearance based on the state changes
HTML:
<li role="menuitemcheckbox" aria-checked="true">Sort by Last Modified</li>
CSS:
[aria-checked="true"] { font-weight: bold; }

Visibility changes
When content visibility is changed (i.e., an element is hidden or shown), developers should change
the aria-hidden property value.
Use this to declare CSS to visually hide an element using display:none.
Because if something isn’t visible, it doesn’t mean it isn’t there.
CSS:
div[aria-hidden="true"] {
display: none;
}

Read up on ARIA
( from developer.mozilla.org )

Design with Accessibility
in mind!
( from developer.mozilla.org )

Mais conteúdo relacionado

Semelhante a FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, Icinga

2007 Max Presentation - Creating Custom Flex Components

michael.labriola

Introduction to Honeycomb APIs - Android Developer Lab 2011 Q3

Paris Android User Group

We too often start building out a site looking at the specific content types, or pages, with too much detail. Missing the similarities of the different pieces of content. When we streamline multiple Content Types, Views, and Blocks, we can simplify the development and administrative experience. We can make this happen using tools such as Taxonomy based Panels and Views arguments, View Modes, and more. When you use these Reusable Components, you can give more power to your client, and make your site a lot easier to plan, develop, and theme. Why stop there? I will show you some basic Reusable Component concepts, and how they can help in estimation, design, planning, and keeping everyone happy. Not only will your site development be super awesome and efficient, but you will be able to plan and build components for all levels of the project that could be reused throughout the process.

Making you, and your Clients Happy, by Using Reusable Components to Build Dru...

bmx269

Accessibility within the Web Environment

Vision Australia

SDN Mentor Hands On - Exercise 2

dan_mcweeney

Advanced Topics in Continuous Deployment

Mike Brittain

Is accessibility the new black?

George Otoiu

Testing For Web Accessibility

Hagai Asaban

Web accessibility - WAI-ARIA a small introduction

Geoffroy Baylaender

ARIA and JavaScript Accessibility

Paul Bohman

3. C# Guide Advance - To Print

Chinthaka Fernando

90% of all Notes applications start life via File… Database… New Copy. After that most organizations lose track of the common code shared across the 100s or 1,000s of applications it has deployed. Eventually we even lose track of what applications are being used and which ones aren’t. In this session we take a close look at a range of options for managing our Notes applications and their components.

Modern Notes: Databases

Peter Presnell

Scala and Akka together - geek night jan 2017

Raj Saxena

WP7 HUB_Introducción a Silverlight

MICTT Palma

What I Learned At Drupal Con Dc 2009

Neil Giarratana

Easily enrich capella models with your own domain extensions

Obeo

Appcelerator Titanium Kinetic practices part 1

フ乇丂ひ丂

Cble assignment powerpoint activity for moodle 1

LK394

Project Cost Estimate Ppt Sample Download

SlideTeam

Power Pointing Off The Beaten Path

gmoore

Semelhante a FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, Icinga (20)

2007 Max Presentation - Creating Custom Flex Components

Introduction to Honeycomb APIs - Android Developer Lab 2011 Q3

Making you, and your Clients Happy, by Using Reusable Components to Build Dru...

Accessibility within the Web Environment

SDN Mentor Hands On - Exercise 2

Advanced Topics in Continuous Deployment

Is accessibility the new black?

Testing For Web Accessibility

Web accessibility - WAI-ARIA a small introduction

ARIA and JavaScript Accessibility

3. C# Guide Advance - To Print

Modern Notes: Databases

Scala and Akka together - geek night jan 2017

WP7 HUB_Introducción a Silverlight

What I Learned At Drupal Con Dc 2009

Easily enrich capella models with your own domain extensions

Appcelerator Titanium Kinetic practices part 1

Cble assignment powerpoint activity for moodle 1

Project Cost Estimate Ppt Sample Download

Power Pointing Off The Beaten Path

Mais de DevOpsDays Tel Aviv

From idea to execution, the challenges of publishing an open source project are very similar to initializing a startup when it comes to creating a successful product that people will love and use. Most open source projects are not “taking-off”, although they are really good! This is because developers (which are usually the creators of open source projects) think that writing the code is the hard part and “neglect” the other parts of publishing a good open source project. In this talk, I will use my experience as a contributor to open source and product head of a startup, to go beyond writing the code itself and cover the other central aspects of creating an open source project, like MVP, product/market fit, marketing and more.

YOUR OPEN SOURCE PROJECT IS LIKE A STARTUP, TREAT IT LIKE ONE, EYAR ZILBERMAN...

DevOpsDays Tel Aviv

If you have never used GraphQL before, you probably think that it is just another buzzword that will be forgotten in a few years. You might think: “Why do I need to learn a new way to write APIs when REST already answers all my needs?”. Or, you are excited to learn something new but don’t believe GraphQL is mature enough for production. In this talk, I will remind you of some of the pain points you have probably experienced when using REST. I will then explain what GraphQL is and demonstrate how it solves these pain points. Next, I will discuss the disadvantages of GraphQL. Finally, I will provide some guidelines for choosing between REST and GraphQL. By the end of this talk, you will understand what GraphQL is and when to use it.

GRAPHQL TO THE RES(T)CUE, ELLA SHARAKANSKI, Salto

DevOpsDays Tel Aviv

“The International Space Station has been orbiting the Earth for over 20 years. It was not launched fully formed, as a monolith in space. Instead, it is built out of dozens of individual modules, each with a dedicated role - life support, engineering, science, commercial applications and more. Each module (or container) functions as a microservice, adding additional capabilities to the whole. Not only do the modules need to function together, delivering both functional and non-functional capabilities, they were designed, developed and built by different countries on Earth and once launched into space (deployed in multiple different ways), had to work together - perfectly. Despite the many (minor) reliability issues which have occurred over the decades, the ISS remains a highly reliable platform for cutting edge scientific and engineering research. In this session I will describe the way the space station was developed and the lessons Site Reliability and DevOps Engineers can learn from it.

MICROSERVICES ABOVE THE CLOUD - DESIGNING THE INTERNATIONAL SPACE STATION FOR...

DevOpsDays Tel Aviv

Have you ever felt you took every wrong turn possible in the process of mitigating a production incident? Did you go through a 3-hour hell during incident response and felt the incident wasn’t complex enough to justify the horrors you’ve experienced? Did it cause you to question your engineering or problem-solving skills? Well, it’s only partially you. Our brain is wired to make decision-making simpler. In doing so, it exposes itself to biases, heuristics, and other quirks that may seem like “bad decisions” in hindsight. In this talk, through real-life outages, we’ll project those psychological principles onto the world of production monitor, and incident management. As a responder, you’ll learn why those behavioral patterns emerge during production incidents and what can be done to limit their effect, and as a manager, you’ll learn how to enable and encourage a healthy environment to better support those patterns.

THE (IR)RATIONAL INCIDENT RESPONSE: HOW PSYCHOLOGICAL BIASES AFFECT INCIDENT ...

DevOpsDays Tel Aviv

The word observable entered the English language roughly 400 years ago, but the concepts of what it means to see, comprehend, and understand something have been debated since time immemorial. Starting in the 19th century, a series of postulates and criteria coalesced into control theory, and it is from this body of knowledge that we gained the word “observability”. Today, with the advent of complex, interconnected computer systems, that word has taken on new meanings and connotations—some useful, some detrimental, and some just plain confusing. In this talk, we’ll mix a little history, a touch of philosophy, and a healthy dose of reality, to demystify what observability means to us as professional computer people. We’ll tear through the marketing material and unearth foundational principles that will help us to build better infrastructure, write better software, and promote healthier business practices. Finally, we’ll explore some potential new avenues for discussion and understanding.

PRINCIPLES OF OBSERVABILITY // DANIEL MAHER, DataDog

DevOpsDays Tel Aviv

Security people say users are the weakest link. But are they? When complying with security becomes too burdensome, users take shortcuts, find workarounds, and end up jeopardizing security. Blaming users is lazy and easy. Making security usable is time consuming and challenging. How does design research help us understand our customers? What patterns and principles drive secure behavior? How can we build empathy with customers and make the right thing to do the easiest thing to do? This session explores these questions, and provides examples of how design thinking and research can help us be more secure. We will walk through our creation of core user personas, design principles, and how these inform and direct our design choices and intent. Don’t blame your users anymore. Come learn how to be part of a future where usability leads security.

NUDGE AND SLUDGE: DRIVING SECURITY WITH DESIGN // J. WOLFGANG GOERLICH, Duo S...

DevOpsDays Tel Aviv

This is for you, you rockstar, ninja coffee drinking workaholic who doesn’t know what a vacation day looks like. Even though you love your job and are dedicated and are super important, you need a break too. We tend to think that working all the time is an effective practice while the truth is that finding the time for self care and recharging your batteries is beneficial for both you and your company. Additionally, if you’re a leader, you’re responsible for the wellbeing of your team. In this talk I’ll discuss the importance of taking time off of work and creating a positive culture surrounding vacation time.

(Ignite) TAKE A HIKE: PREVENTING BATTERY CORROSION - LEAH VOGEL, CHEGG

DevOpsDays Tel Aviv

This is a story about taking the cloud infrastructure of a successful company, that is still managed as infrastructure of a startup company, and rebuilding it to support the growing business requirements, especially around disaster recovery and business continuity. In the session I will share Next Insurance’s journey - where we started, where we are now and what we learned on the way so far. I will talk about how we managed to build our proven DR plans, and actually execute them in our DR drills. I will also talk about why we decided that the only way to prove your DR plan works is to continue running your business in the DR account and make it your production account, and go on to build your next DR account. If you are a part of a company that is about to embark on a similar journey, this session might equip you with some very useful insights on how to think about such a challenge, and some very useful and practical tips on how to execute it.

BUILDING A DR PLAN FOR YOUR CLOUD INFRASTRUCTURE FROM THE GROUND UP, MOSHE BE...

DevOpsDays Tel Aviv

CI/CD pipelines are quickly becoming the path of least resistance for would-be attackers into sensitive internal systems, gaining access to critical data, with minimal effort. In the InfoSec world when we talk about CI/CD security often times this focuses on specific aspects of securing your pipeline - scanning the code, protecting secrets, securely managing code deployments, or even authentication and authorization mechanisms, but we rarely talk about all of these together. After years of being in the trenches and realizing that the attack surface is growing and the threat landscape becoming more and more complex, it has become increasingly apparent that security teams need to adapt and modify strategies to keep up with the new reality of CI/CD protection, without compromising developer velocity. In this talk I would like to propose a new way of thinking about CI/CD security - that encompasses the three disciplines that comprise CI/CD security - security in the pipeline, of the pipeline, and around the pipeline. Partial coverage of any or all of these disciplines simply will not cut it with the continuously evolving risk landscape. Security engineers need to address each of these aspects in their entirety to provide the full scope of coverage that modern organizations need, and I will take a deep dive on the challenges each introduce, and the approaches and techniques for mitigating them based on adversarial sec research.

THE THREE DISCIPLINES OF CI/CD SECURITY, DANIEL KRIVELEVICH, Cider Security

DevOpsDays Tel Aviv

The last two decades have been all about SaaS, with advantages that cannot be overstated. Except SaaS isn’t always an option, nor is it always the right choice: businesses in tightly regulated industries, or where information security is paramount, for example, will not - often can not - consider any software that isn’t under their control. For many software enterprises, this leads to the dreaded inevitability of on-premise deployment. Fortunately, the situation today is dramatically different to a scant few years ago, let alone a decade or two: the same technologies that enable SaaS have also radically transformed on-prem deployment. Modern tools like Docker, Consul, ELK and Kubernetes - to name a few - can be leveraged to completely transform the experience for both customers and vendors. In this talk we’ll contrast the challenges and advantages of SaaS and on-prem, see how things have evolved in recent history, and see how modern on-prem deployment can be, if not pleasurable, at least relatively painless.

THE PLEASURES OF ON-PREM, TOMER GABEL

DevOpsDays Tel Aviv

Configuration Management is at the core of Ops. It’s the biggest enabler of any compute operation, small and big. In the past decade, we have switched from thinking about the machines we are configuring, to think about the software and services we are controlling. With that change of mindset, so did the tools we are using. Traditional tools like Puppet, chef, salt and Ansible are slowly declining while new tools such as Terraform, Pulumi, Helm and Kustomize are on the rise. In this talk I will try to describe the pain-points and the opportunities of this transformation as well as suggesting a future direction based on tools developed at the big-tech companies (Mainly facebook and google).

CONFIGURATION MANAGEMENT IN THE CLOUD NATIVE ERA, SHAHAR MINTZ, EggPack

DevOpsDays Tel Aviv

We all know how hard it is to find DevOps engineers, and creating a diverse team despite gender and ethnicity bias? Nearly impossible. At this talk we will show our tools and methods implemented in the Develeap hiring process that overcome this inherited bias. About 2 years ago we faced a crisis in our DevOps consulting company - the market demand was higher than we could supply. The traditional recruiting process depending on CV and artificial credentials was not working. So we came up with an alternative solution, and since then - we are growing exponentially and diversely. In this talk we will show the practical tools we deployed in order to increase our capacity, and we will show how these tools overcome the inherited bias in the process.

SOLVING THE DEVOPS CRISIS, ONE PERSON AT A TIME, CHRISTINA BABITSKI, Develeap

DevOpsDays Tel Aviv

Everyone wants observability into their system, but find themselves with too many vendors and tools, each with its own API, SDK, agent and collectors. With the increasing complexity of modern applications, continuous profiling methods and tools are gaining popularity among the Developer and Engineering communities. In this session, we cover what continuous profiling entails and why you should implement a profiler into your tech stack (if you haven’t done so already). We’ll then bring theory to practice and demonstrate a real-life scenario using gProfiler, a free open-source continuous profiling tool, covering Linux servers on multiple architectures (such as Graviton).

OPTIMIZING PERFORMANCE USING CONTINUOUS PRODUCTION PROFILING ,YONATAN GOLDSCH...

DevOpsDays Tel Aviv

“Being oncall sucks. But it doesn’t have to!” We all heard this one before. Why is it though, that oncall still remains the biggest scar for many? What can a modern Engineering org do to rein the oncall dragons, and actually help people grow as professionals as they go oncall? In this talk, I will present the main reasons why oncall is difficult in modern orgs, and describe ways to mitigate these hardships. The idea is that oncall is often the ‘backroom’ of an org, where all the technical and organizational debt take their toll. Be it unwieldy systems or broken processes between teams, oncall checks all the ‘weak boxes’. Therefore, the only way to win at oncall is to sort out your debts, starting with the organizational ones. I will dive into the detail of the oncall rotation at Snyk as the org scaled from 1 to 220 people, what worked well about it, and what was less than perfect. I will discuss the decisions made to turn oncall into a building block of the org, and show a path to rein oncall in your organization as well.

HOW TO SCALE YOUR ONCALL OPERATION, AND SURVIVE TO TELL, ANTON DRUKH

DevOpsDays Tel Aviv

Github Copilot and tools that help us code better are cool. But I’m lucky if I spend 90 minutes a day writing code. We really need to optimize the hours we spend reviewing code, updating tickets and tracing where our code is deployed. Learn how I save an hour a day streamlining non-coding tasks. This talk is unique because 99% of developer productivity tools and hacks are about coding faster, better, smarter. And yet the vast majority of our time is spent doing all of this other stuff. After I started focusing on optimizing the 10 hours I spend every day on non-coding tasks, I found I my productivity went up and my frustration at annoying stuff went way down. I cover how to save time by reducing cognitive load and by cutting menial, non-coding tasks that we have to perform 10-50 times every day. For example: Bug or hotfix comes through and you want to start working on it right away so you create a branch and start fixing. What you don’t do is create a Jira ticket but then later your boss/PM/CSM yells at your due to lack of visibility. I share how I automated ticket creation in Slack by correlating Github to Jira. You have 20 minutes until your next meeting and you open a pull request and start a review. But you get pulled away half way through and when you come back the next day you forgot everything and have to start over. Huge waste of time. I share an ML job I wrote that tells me how long the review will take so I can pick PRs that fit the amount of time I have. You build. You ship it. You own it. Great. But after I merge my code I never know where it actually is. Did the CI job fail? Is it release under feature flag? Did it just go GA to everyone? I share a bot I wrote that personally tells me where my code is in the pipeline after it leaves my hands so I can actually take full ownership without spending tons of time figuring out what code is in what release.

HOW TO OPTIMIZE NON-CODING TIME, ORI KEREN, LinearB

DevOpsDays Tel Aviv

Recent years have exposed startups to a major plague - cloud overspend. No vaccine appears to exist, plethora of tools and consultants fail to stop the bleeding. And yet, some companies manage to stay safe. What makes them different? Is it the tools? Is it the mindset? Is it developer training? In this session we will examine the cultural factors involved in sound and responsible financial management in the cloud. We will also look at relevant system design elements and product design elements which enable us to spend wisely while our business runs smoothly. Following this session, you should be better versed in cost-aware system design and some of the cultural and structural requirements to keeping your cloud bill low.

(Ignite) WHAT'S BURNING THROUGH YOUR CLOUD BILL - GIL BAHAT, CIDER SECURITY

DevOpsDays Tel Aviv

In every development process there is the question, do we invest enough on quality? Do we need to invest more? Every team knows about the dilemma of how many tests is the right amount of tests we should write. Is 80% test coverage is good enough? Maybe 90%? 100%? Should we invest more time in unit testing? Are we wasting too much time on unit-testing? Should we invest time on a faster rollback mechanism? WIIFM “Without data, you’re just another person with an opinion” - W. Edwards Deming SLO Driven Development is a framework that helps the developers focus on impact and balance of every aspect of the dev process. When working currently with SLI, SLA, SLO and error budget you can learn where to invest in the development process. Let’s talk about the importance of good SLOs and how they can help us improve our day2day

SLO DRIVEN DEVELOPMENT, ALON NATIV, Tomorrow.io

DevOpsDays Tel Aviv

In this talk, I will share do's and don'ts on how to onboard successfully in a remote or hybrid setup including moving to a leadership role, speaking from my own journey onboarding remotely in the midst of a global pandemic. I will share the tips that worked for me for successful onboarding, how I was able to be productive, impactful, and make a good impression on others. The key issues as an “onbordee” that I will talk about are how to create relationships, make yourself visible in the company, time management, and more. Since I started working in Augury over 100 new employees have joined the company. Each month I give a session that is part of their general onboarding process. This became a crucial step due to the fact that we are now a hybrid company and a lot of people are onboarding remotely or in a hybrid setup for the first time in their lives. I joined the company as a backend developer and a few months into my role, the squad leader position in my squad was up for grabs and I was fortunate enough to grab it :) This is my first official leadership role, which I also needed to onboard into in a hybrid setup. I will share the process that I built for myself on “How to lead”. Also, a word or two on the process we built as a squad on how we work in a hybrid setup, what are we optimizing for when we do meet and how to include new members of the team.

ONBOARDING IN LOCKDOWN, HILA FOX, Augury

DevOpsDays Tel Aviv

In your ever-changing Infrastructure, some changes are intentional while others are not. Drift is what happens whenever the real-world state of your infrastructure differs from the state defined in your configuration. This can happen for many reasons, sometimes it happens when adding or removing resources, other times when changing resource definitions upon resource termination or failure, and even when changes have been made manually or via other automation tools. While Terraform itself can detect drifts, in most cases, you will be informed about it too late: just before you are about to deploy new changes to your infrastructure. What’s interesting about Terraform though, is that you can apply changes in two separate and distinct steps of “Planning” and “Applying”. This means that you have full visibility of what Terraform is planning on doing beforehand, and if you are satisfied with the changes, you can choose to apply them. So how does this work? When something is changed intentionally, it will appear in the source code, and the Terraform plan will not do anything. However, if any part of the infrastructure has been changed manually, Terraform’s plan will identify this, and alert you to the change. In other words, if your IaC drifted from its expected state, then Terraform’s plan will, in fact, detect it. Applying this simple solution can empower DevOps and developer velocity, with the reassurance and context for unexpected changes in your IaC, in near real-time. This talk will showcase real-world examples, and practical ways to apply this in your production environments while doing so safely and at the pace of your engineering cycles.

DON'T PANIC: GETTING YOUR INFRASTRUCTURE DRIFT UNDER CONTROL, ERAN BIBI, Firefly

DevOpsDays Tel Aviv

KEYNOTE | WHAT'S COMING IN THE NEXT 10 YEARS OF DEVOPS? // ELLEN CHISA, bolds...

DevOpsDays Tel Aviv

Mais de DevOpsDays Tel Aviv (20)

YOUR OPEN SOURCE PROJECT IS LIKE A STARTUP, TREAT IT LIKE ONE, EYAR ZILBERMAN...

GRAPHQL TO THE RES(T)CUE, ELLA SHARAKANSKI, Salto

MICROSERVICES ABOVE THE CLOUD - DESIGNING THE INTERNATIONAL SPACE STATION FOR...

THE (IR)RATIONAL INCIDENT RESPONSE: HOW PSYCHOLOGICAL BIASES AFFECT INCIDENT ...

PRINCIPLES OF OBSERVABILITY // DANIEL MAHER, DataDog

NUDGE AND SLUDGE: DRIVING SECURITY WITH DESIGN // J. WOLFGANG GOERLICH, Duo S...

(Ignite) TAKE A HIKE: PREVENTING BATTERY CORROSION - LEAH VOGEL, CHEGG

BUILDING A DR PLAN FOR YOUR CLOUD INFRASTRUCTURE FROM THE GROUND UP, MOSHE BE...

THE THREE DISCIPLINES OF CI/CD SECURITY, DANIEL KRIVELEVICH, Cider Security

THE PLEASURES OF ON-PREM, TOMER GABEL

CONFIGURATION MANAGEMENT IN THE CLOUD NATIVE ERA, SHAHAR MINTZ, EggPack

SOLVING THE DEVOPS CRISIS, ONE PERSON AT A TIME, CHRISTINA BABITSKI, Develeap

OPTIMIZING PERFORMANCE USING CONTINUOUS PRODUCTION PROFILING ,YONATAN GOLDSCH...

HOW TO SCALE YOUR ONCALL OPERATION, AND SURVIVE TO TELL, ANTON DRUKH

HOW TO OPTIMIZE NON-CODING TIME, ORI KEREN, LinearB

(Ignite) WHAT'S BURNING THROUGH YOUR CLOUD BILL - GIL BAHAT, CIDER SECURITY

SLO DRIVEN DEVELOPMENT, ALON NATIV, Tomorrow.io

ONBOARDING IN LOCKDOWN, HILA FOX, Augury

DON'T PANIC: GETTING YOUR INFRASTRUCTURE DRIFT UNDER CONTROL, ERAN BIBI, Firefly

KEYNOTE | WHAT'S COMING IN THE NEXT 10 YEARS OF DEVOPS? // ELLEN CHISA, bolds...

Último

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Edi Saputra

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Martijn de Jong

Abhishek Deb(1), Mr Abdul Kalam(2) M. Des (UX) , School of Design, DIT University , Dehradun. This paper explores the future potential of AI-enabled smartphone processors, aiming to investigate the advancements, capabilities, and implications of integrating artificial intelligence (AI) into smartphone technology. The research study goals consist of evaluating the development of AI in mobile phone processors, analyzing the existing state as well as abilities of AI-enabled cpus determining future patterns as well as chances together with reviewing obstacles as well as factors to consider for more growth.

Exploring the Future Potential of AI-Enabled Smartphone Processors

debabhi2

As privacy and data protection regulations evolve rapidly, organizations operating in multiple jurisdictions face mounting challenges to ensure compliance and safeguard customer data. With state-specific privacy laws coming up in multiple states this year, it is essential to understand what their unique data protection regulations will require clearly. How will data privacy evolve in the US in 2024? How to stay compliant? Our panellists will guide you through the intricacies of these states' specific data privacy laws, clarifying complex legal frameworks and compliance requirements. This webinar will review: - The essential aspects of each state's privacy landscape and the latest updates - Common compliance challenges faced by organizations operating in multiple states and best practices to achieve regulatory adherence - Valuable insights into potential changes to existing regulations and prepare your organization for the evolving landscape

TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments

TrustArc

Real Time Object Detection Using Open CV

Khem

Axa Assurance Maroc - Insurer Innovation Award 2024

The Digital Insurer

Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows. We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases. This video focuses on the deployment of external web forms using Jotform for Bonterra Impact Management. This solution can be customized to your organization’s needs and deployed to support the common use cases below: - Intake and consent - Assessments - Surveys - Applications - Program registration Interested in deploying web form automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.

Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...

Jeffrey Haguewood

In the thrilling conclusion to 2023, ransomware groups had a banner year, really outdoing themselves in the "make everyone's life miserable" department. LockBit 3.0 took gold in the hacking olympics, followed by the plucky upstarts Clop and ALPHV/BlackCat. Apparently, 48% of organizations were feeling left out and decided to get in on the cyber attack action. Business services won the "most likely to get digitally mugged" award, with education and retail nipping at their heels. Hackers expanded their repertoire beyond boring old encryption to the much more exciting world of extortion. The US, UK and Canada took top honors in the "countries most likely to pay up" category. Bitcoins were the currency of choice for discerning hackers, because who doesn't love untraceable money?

Ransomware_Q4_2023. The report. [EN].pdf

Overkill Security

Manulife - Insurer Transformation Award 2024

The Digital Insurer

Automating Google Workspace (GWS) & more with Apps Script

wesley chun

Created by Mozilla Research in 2012 and now part of Linux Foundation Europe, the Servo project is an experimental rendering engine written in Rust. It combines memory safety and concurrency to create an independent, modular, and embeddable rendering engine that adheres to web standards. Stewardship of Servo moved from Mozilla Research to the Linux Foundation in 2020, where its mission remains unchanged. After some slow years, in 2023 there has been renewed activity on the project, with a roadmap now focused on improving the engine’s CSS 2 conformance, exploring Android support, and making Servo a practical embeddable rendering engine. In this presentation, Rakhi Sharma reviews the status of the project, our recent developments in 2023, our collaboration with Tauri to make Servo an easy-to-use embeddable rendering engine, and our plans for the future to make Servo an alternative web rendering engine for the embedded devices industry. (c) Embedded Open Source Summit 2024 April 16-18, 2024 Seattle, Washington (US) https://events.linuxfoundation.org/embedded-open-source-summit/ https://ossna2024.sched.com/event/1aBNF/a-year-of-servo-reboot-where-are-we-now-rakhi-sharma-igalia

A Year of the Servo Reboot: Where Are We Now?

Igalia

Accelerating FinTech Innovation: Unleashing API Economy and GenAI Vasa Krishnan, Chief Technology Officer - FinResults Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...

apidays

AWS Community Day CPH - Three problems of Terraform

Andrey Devyatkin

Scaling API-first – The story of a global engineering organization Ian Reasor, Senior Computer Scientist - Adobe Radu Cotescu, Senior Computer Scientist - Adobe Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

apidays

Data Cloud, More than a CDP by Matt Robison

Anna Loughnan Colquhoun

A Beginners Guide to Building a RAG App Using Open Source Milvus

Zilliz

FWD Group - Insurer Innovation Award 2024

The Digital Insurer

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Juan lago vázquez

Whatsapp Number Escorts Call girls 8617370543 Available 24x7 Navi Mumbai Call Girls Service Offer Genuine VIP Model Escorts Call Girls in Your Budget. Navi Mumbai Call Girls Service Provide Real Call Girls Number. Make Your Sexual Pleasure Memorable with Our Navi Mumbai Call Girls at Affordable Price. Top VIP Escorts Call Girls, High Profile Independent Escorts Call Girls, Housewife Women Escorts Call Girl, College Girls Escorts Call Girls, Russian Escorts Call girls Service in Your Budget.

Navi Mumbai Call Girls 🥰 8617370543 Service Offer VIP Hot Model

Deepika Singh

Strategies for Landing an Oracle DBA Job as a Fresher

Remote DBA Services

FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, Icinga

1. Accessibility in Icinga Flying Blind by Feu Mourek

3. the quality or characteristic of something that makes it possible to approach, enter, or use it /ɪkˈses·əˈbɪl·ɪ·t̬i/ noun (Definition of accessibility from the Cambridge Business English Dictionary © Cambridge University Press) Accessibility

4. Visual Impairment

5. Numbers! (numbers from colourblindawareness.org) 285 Million globally … or 1 out of these here:

6. Colour Vision Deficiency (made with Color Oracle and Sketch)

7. Colour Vision Deficiency (made with Color Oracle and Sketch)

8. Common Variants Deuteranopia Tritanopi a Protanopia

9. Colours in Icinga (made with Color Oracle and Sketch)

10. Colours in Icinga (made with Color Oracle and Sketch)

11. Colours in Icinga (made with Color Oracle and Sketch)

12. Keep that in mind! (numbers from https://www.ncwit.org )

13. Themes can help!

14. See for yourself (made with Color Oracle and Sketch)

15. See for yourself (made with Color Oracle and Sketch)

16. What if you can’t see?

17. Video time! https://www.youtube.com/watch?v=q_ATY9gimOM

18. Structure Content needs to be weighted If it is not, there is no way of telling what is important, without looking at everything. While styling can tell sighted people what to focus on, we need to look at the structure too.

19. Static content A lot of websites use iframes and other widgets that they do not control directly. To these cases you need to pay special attention, and maybe add an alternative description to what they are supposed to show. The alternative descriptions are also needed for images, which you need to describe in the alt attribute.

20. Structure ( from developer.mozilla.org )

21. State changes ARIA provides attributes for declaring the current state of a UI widget. aria-checked: indicates the state of a checkbox or radio button aria-disabled: indicates that an element is visible, but not editable or otherwise operable aria-grabbed: indicates the 'grabbed' state of an object in a drag-and-drop operation Use CSS attribute selectors to alter the visual appearance based on the state changes HTML: <li role="menuitemcheckbox" aria-checked="true">Sort by Last Modified</li> CSS: [aria-checked="true"] { font-weight: bold; }

22. Visibility changes When content visibility is changed (i.e., an element is hidden or shown), developers should change the aria-hidden property value. Use this to declare CSS to visually hide an element using display:none. Because if something isn’t visible, it doesn’t mean it isn’t there. CSS: div[aria-hidden="true"] { display: none; }

23. Read up on ARIA ( from developer.mozilla.org )

24. Design with Accessibility in mind! ( from developer.mozilla.org )

Notas do Editor

Hello everyone! Todays topic is “flying blind - accessibiilty in icinga”, where I want to walk you through the worlds of people with visual impairments! The internet has a lot of barriers for people with impairments. I’ll give you an overview on how to improve your websites and what to pay attention to when using the internet,so that those people can be included in our activities and make more valuable contribute to our discussions! be interactive more examples (video / code) give examples of companies that focus on accessibility more stories
But before we dive into that, my name is Feu Mourek and my pronouns are they / them. I started out as a developer at Icinga and nowadays my job title is “development advocate“. That means I am basically the “development community interface”. And I really like changing things up to see how they look!
The definition of accessibility, according to the Cambridge Business English Dictionary, is “the quality or characteristic of something that makes it possible to approach, enter, or use it“
The main focus today will be visual Impairment. This includes colour vision deficiency and complete inability to interact with visual elements. First we’ll have a look at the numbers:
There are roughly 285 million blind & vision impaired people out there. That is just a little less than the entire population of the States! Roughly 1 in 11 people! That’s a lot! And 98% of U.S.-based webpages are not accessible to the disability community from a legal perspective, according to the 2020 Web Accessibility Annual Report. Let’s try to get this number down!
Our eyes have three cones for colour vision: red, green and blue. Those allow us humans to see the spectrum we can, by mixing those three colours together. But, as all things in our bodies, those can malfunction.
In most cases, they won’t be completely unable to distinguish between certain colours. It’s just a little harder. But since we want to be inclusive to everyone I’ll just be looking at actual colour blindness from here on, where one of the cones doesn’t work at all.
The three cones correspond to the three variants: Deuteranopia and Protanopia, commonly referred to as Red-Green blindness And the rarer form of Tritanopia, sometimes called Yellow-Blue blindness
To give you a better picture of what this looks like in practise: The squares in the first row are the unaltered Icinga colours. Below, I have simulated what they look like with the three variants of colour blindness.
This is what the tactical overview looks like with the default theme. As you can see, especially if you look at the labels in the legend, the colours for the states are rather difficult to tell apart.
While you could still understand the information from the context in the donut, this is not possible in the service grid. In the second picture, which services are Critical? Or in the third, which are pending?
And this is why an accessible design is important. There are a lot of people affected and you usually don’t even know! And it’s crucial that we don’t withhold important information from them.
Icinga Web has a colour blind theme. It doesn’t just work with hues, but also with different stages of brightness to signal severity.
Here the pictures for comparison: Without the theme. - pause - And with it enabled.
The colours in the grid view are also distinguishable now. Every state has both a distinguishing colour and a brightness, that helps figure out which items are more important at that moment.
Designing for people who can not see at all is a little different, as you can imagine. The colours and shapes don’t matter at all in this case, so in order to design for blindness, you need to understand how they “see”
https://www.youtube.com/watch?v=q_ATY9gimOM
Weighted means that a document is split into different sections and does not have to be read through from top to bottom. Header, Navigation elements (search bar?), Main Content, Sign up form, Footer
Weighted means that a document is split into different sections and does not have to be read through from top to bottom. Header, Navigation elements (search bar?), Main Content, Sign up form, Footer
In order for a screen reader to know what to read out in which order, you need to separate structure from styling in the HTML. This means no <br> tags. Make those spaces your CSS!
Weighted means that a document is split into different sections and does not have to be read through from top to bottom. Header, Navigation elements (search bar?), Main Content, Sign up form, Footer
Weighted means that a document is split into different sections and does not have to be read through from top to bottom. Header, Navigation elements (search bar?), Main Content, Sign up form, Footer
ARIA means Accessible Rich Internet Application Aria is a set of attributes that define ways to make web more accessible. It supplements HTML so that interactions can be passed to assistive technologies more easily.
So if you want to build a webpage or -application, take the time to think about your audience!

FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, Icinga

Recomendados

Recomendados

Mais conteúdo relacionado

Semelhante a FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, Icinga

Semelhante a FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, Icinga (20)

Mais de DevOpsDays Tel Aviv

Mais de DevOpsDays Tel Aviv (20)

Último

Último (20)

FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, Icinga

Notas do Editor