This is the first of several webinars under our series AI Strategically. Sign up to get updates about future events.

Don’t miss our other events! 

<h3>Build hyperpersonalized customer journeys with practical AI</h3>In the first two episodes of our AI Strategically Webinar series, we covered finding use cases and improving CX. In this hands-on session, we’ll build a working AI chatbot – live!AI Strategically is perfect for:<ul><li>Banking, Telco, Insurance and Finance industries</li><li>Product, Innovation and Customer Success leaders</li><li>Anyone who is looking for a simple way to implement AI in their company</li></ul>

What you’ll learn

Use simple techniques to personalize customer interactions without needing complex systems or extra team members. &nbsp;

Mastering AI prompts

Learn how to organize and automate processes that turn your internal data into actionable customer experiences. &nbsp;

Building effective workflows


Explore real business cases where AI transforms from a tool into a strategic product development partner.

AI as your product partner

Learn how easy it is to build a functional company chatbot from scratch using your own company data &nbsp;

Building a working AI Chatbot in minutes

Many companies aren’t sure what AI can realistically do for them. We’ll clear up common misconceptions and share practical use cases to help you see the full potential. &nbsp;

Unclear AI expectations

Knowing where to begin is often the hardest part. Get pointers on how to identify and prioritize the right AI projects for your needs.

Finding your starting point

Connect scattered customer insights across your legacy systems to finally see the complete customer journey. &nbsp;

Data silos

AI can feel complex, but small steps make a big difference. Watch us build a functional chatbot from zero during the session – and learn how you can then build your own using the same techniques.

Turning ideas into action

Anticipate customer needs before they become tickets and prevent churn before customers even consider leaving.

Breaking the reactive support cycle

Master prompting techniques, then learn how to connect your own company data through DataStax to create a real AI assistant – demonstrated live.

Translating company data to insights and digital products

AI Strategically gives you a clear map to navigate AI in your industry. 


Learn with us to avoid the usual challenges

Speaker:

AI_Webinar_Ondrej.png

Invitation to the webinar ‘AI Solutions that deliver 10× value?’ by GoodRequest. Scheduled for October 24, 2025 at 4:00 PM on LinkedIn Live. Speaker: Ondrej Sarnecký, AI Innovation Specialist.

Post1.png

Miroslav Gajan

Exclusive webinar series for Product, Innovation, Customer Success and CX leaders.

How to build AI solutions that deliver 10× more value for your business

Our work often goes unnoticed, yet we are there at both the beginning and the end of every feature. The role of an analyst, especially a technical one, is to connect the vision, user needs, and technical possibilities in a way that ensures smooth development and a meaningful final product.<h2>Technical analyst in practice</h2>As analysts in application development, we are present at the very birth of every feature, from gathering requirements and documenting them all the way to delivery in production. Our job is to understand what needs to be built, why it makes sense, and how it fits into the existing solution.<h3>Our work includes:</h3><ul><li>gathering and analyzing requirements,</li><li>asking the right questions and uncovering inconsistencies,</li><li>creating and maintaining technical specifications,</li><li>designing edge-case scenarios (e.g., server outages, empty lists, invalid inputs),</li><li>collaborating on design,</li><li>visualizing complex processes through diagrams,</li><li>providing ongoing support during development and testing,</li><li>facilitating communication and coordination between teams and stakeholders,</li><li>guiding the client on technical feasibility,</li><li>assisting the project manager with estimations and cost calculations.</li></ul>

<h2>What does a day in the life of an analyst look like?</h2>The day usually starts with checking emails and responding to questions from the team or the client. Then comes the standup, where we help provide clarity and make sure everything is moving in the right direction.The rest of the day is a mix of detailed work and coordination:<ul><li>fine-tuning bug reports,</li><li>writing and updating specifications,</li><li>preparing refinements,</li><li>creating tasks for developers, or discussing new features with the client.</li></ul>An analyst constantly balances between detail and the bigger picture – looking for logical connections as well as those unexpected edge cases that could otherwise cause problems.

Just as analyst connects team, technical specifications connect vision with successful development. Read more 👇

<h2>Core skills of an analyst</h2><h3>Hard skills</h3><ul><li>Fundamentals of technical thinking – understanding API documentation and integrations, as well as the basics of mobile and web application architecture.</li><li>Structure and precision – writing clear specifications that account for exceptions and different system states.</li><li>Tool proficiency – working with various tools (e.g., Notion, Jira, Confluence, Figma, Postman, …) that support us in our daily work.</li><li>Testing and QA collaboration – understanding bug reports.</li><li>Process modeling – creating diagrams.</li></ul><h3>Soft skills</h3><ul><li>Asking questions – lots of them. Not because we don’t understand, but because we want to capture every detail.</li><li>Clear communication – with both business and development. We often act as “translators” between worlds that speak different languages.</li><li>Attention to detail – even small inconsistencies can turn into big issues later. Our goal is to catch them before they become bugs.</li><li>Curiosity with humility – not being afraid to ask, verify, admit mistakes, and do things better.</li><li>Organization and systems thinking – connecting the dots across the system, keeping specifications tidy and up to date.</li><li>Contextual thinking – considering different scenarios (“what if...”).</li><li>Patience and perseverance – digging for answers when requirements aren’t immediately clear.</li><li>Empathy and collaboration – understanding the client’s needs while also respecting developers’ requirements and recommendations.</li><li>Time management – balancing specifications, consultations, daily operations, and meetings without letting things slip through the cracks.</li></ul><h2>We are a key part of the development process</h2>Designers shape how the product should look and feel for the user. Developers know how to build it so that it’s reliable. The client brings their vision and goals. As technical analysts, we connect these perspectives – we bring clarity, define the details, and help turn an idea into a functional solution without unnecessary misunderstandings. We look for balance between what the client wants, what makes sense for the user, and what is technically feasible.<ul><li>The client knows what they want to achieve, but not always how it should work.</li><li>Developers know how to build it, but need to know exactly what to build.</li><li>Designers know how it should look, but need a framework.</li><li>Analysts make sure we’re all pulling in the same direction.</li></ul>

The role of an analyst may be quiet, but it’s essential. We are the bridge between business and development – we understand context, think in connections, and ask the questions that move a project forward. Our work brings clarity to the team, helps prevent mistakes, and saves both time and resources. We are not just “document writers,” but the ones who turn ideas into actionable, workable solutions. That’s why every team should have a dedicated place for an analyst.

V softwarových týmech existují role, které si umí představit téměř každý. Většina lidí má zhruba představu, co dělají vývojáři, testeři nebo designéři. Ale co analytik? Co tato role vlastně obnáší? Odpověď nebývá vždy tak jasná.

Význam analytiků v úspěšných softwarových projektech

V softvérových tímoch sú roly, ktoré si vie predstaviť takmer každý. Každý zhruba vie, aká je náplň práce developerov, testerov či dizajnérov. Ale čo analytik? Čo sa za týmto pojmom vlastne skrýva? Odpoveď nebýva vždy jasná.

Význam analytikov v úspešných softvérových projektoch

Ilustrácia postavy s logom GoodRequest namiesto hlavy, ktorá stojí pred panelom so schémami, grafmi a ikonami. Panel je prepojený čiarami ako myšlienková mapa a nad postavou svieti žiarovka symbolizujúca nápad.

Odhalenie úlohy analytika Hero.png

Odhalenie úlohy analytika Thumb.png

Mária Brandoburová

In software teams, there are roles that almost anyone can picture. Most people have a rough idea of what developers, testers, or designers do. But what about an analyst? What does this role actually entail? The answer isn’t always so clear.

Importance of analysts in successful software projects

Visual accessibility refers to the ability of a website to communicate information to every user, regardless of their abilities or technical limitations. For developers, this means looking at colors, contrast, typography, and interactive elements not only from an aesthetic perspective, but also from a usability and readability perspective.

<h2>1. Text and page size</h2>The design has to be flexible and let users zoom in up to 200% without losing content or functionality. Content should adapt smoothly to the screen width to avoid horizontal scrolling (except for large tables, maps, or other two-dimensional layouts). We support a minimum display width of <code>320px</code>.

You can achieve this by specifying font sizes, container sizes, and element positions using relative units such as <code>rem</code>, <code>em</code>, <code>%</code>, <code>vw</code> or <code>vh</code>. Avoid using absolute units such as pixels (px), pri špecifikovaní štýlovania prvkov a rozloženia.when specifying element styling and layout. Users can also increase <code>letter-spacing</code>, <code>word-spacing</code>, <code>line-height</code> and paragraph spacing without cropping content or disrupting functionality.<pre><code class="language-css">// Bad examples ❌
font-size: 16px;
line-height: 8px;
@media (min-width: 800px) {}

// Good examples ✅

// If we set zoom to 200%, website will be rendered as on a mobile device (e.g., menu will be hidden).
@media (min-width: 50rem) {}
font-size: 1rem;
line-height: 1.5;</code></pre><h4>When to use px values?</h4><blockquote>For more information on the proper use of relative units and <code>px</code> see article: <a href="https://www.joshwcomeau.com/css/surprising-truth-about-pixels-and-accessibility/">The Surprising Truth About Pixels and Accessibility</a>.</blockquote><h4>When to use rem values?</h4>Using <code>rem</code> values &nbsp;is great when it comes to typography. However, when we use <code>rem </code>values for horizontal indentation, we reduce the amount of usable space, further limiting the number of words that fit on a line (see comparison):

Therefore, it does not make sense to use <code>rem</code> values for <code>border-width</code> either. When choosing between pixels and <code>rem</code>, &nbsp;you should ask yourself this question:🤔 Should this value increase when the user increases the default font size in the browser?

<h2>2. Text styling (AAA rule, but I recommend implementing it)</h2>For blocks of text, avoid centering or justified alignment, set the line height to at least 1.5, and do not exceed 80 characters per line. Users must be able to set the text and background color. People with dyslexia or other learning disabilities often benefit from shorter lines, larger line height, and simple text aligned to the left.

<h2>3. Sufficient color contrast</h2>Text on the web must have sufficient contrast against the background so that it can be read by all users, including those with visual impairments or color blindness, for whom low contrast can cause text to disappear completely into the background. Use the contrast checker tools in Figma or your browser's DevTools to verify that you meet the required ratios.<h3>Main rules for text contrast:</h3><ul><li>Regular text: Must have a contrast ratio of at least 4.5:1. For example, black text on a white background has high contrast, while light gray text on a white background has low contrast and is difficult to read.</li><li>Large text: Should have a contrast ratio of at least 3:1 if it is:<ul><li>larger than 24px</li><li>or bold and larger than 19px.</li></ul></li><li>All important visual elements that have informational value (such as icons, graphs, buttons, form fields, and other interactive components) must have a contrast ratio of at least 3:1 relative to their surroundings or neighboring elements.</li></ul>

<h2>4. Color distinction</h2>Do not use color as the only visual aid. Information, actions, calls to action, or visual distinctions must not be conveyed solely by color. The design should also include other visual indicators such as icons, underlining, bold font, or different shapes. For color-blind, visually impaired, or blind users who use a screen reader, there must be another way to convey the information.<ul><li>Text alternatives: For example, if you indicate incorrect fields in a form with a red border, also add a text warning about the error.</li><li>Links in text: Links in text should not be distinguished by color alone. Always underline them or change their font style, boldness, or add a border.</li></ul>

<ul><li>Graphics: On maps, graphs, or other visuals where color distinguishes elements, add symbols or icons for each category.</li></ul>

Accessibility isn't just about design. Check out this handy checklist that shows you how to write HTML and CSS to make your website readable, usable, and fair for everyone 👇

<h2>5. Size of interactive elements</h2>Buttons, links, and other interactive elements on the website should have a minimum size of 24 x 24 pixels (for important content, a minimum size of 48 x 48 pixels is recommended). If this is not possible, they must have sufficient empty space around them to prevent accidental clicks. Small and crowded elements are frustrating to click, especially on touch screens for people with:<ul><li>limited hand control (e.g., tremors, arthritis),</li><li>using smaller screens, or having larger fingers.</li></ul>

<h2>6. Consistent website navigation</h2>Users expect features such as menus, search, skip content buttons, or contact menus to remain in the same place when they visit different subpages of a website.Predictable website layout makes life easier for everyone. When users always know where to find key navigation elements, they do not waste time searching. Maintaining consistency is not just useful, it is essential.

<h3>Consistency of interactive elements</h3>Interactive elements such as buttons, links, and form controls are labeled consistently throughout the website. If something performs the same action on multiple pages, it should always be identified in the same way.Blind people rely on screen readers when interacting with websites. If a button on one page says "Add to cart" and on another "Buy now," they have to figure out if it performs the same function, which requires unnecessary effort.Interactive components that are commonly duplicated on websites include:<ul><li>Buttons: Submit, Add to Cart, Share on Socials, Play/Pause Media…</li><li>Icons: Print, Save, Download, Trash…</li><li>Pagination: Go to Page 3, Previous Page…</li><li>Call-to-Action links: Learn More, Sign Up, Get Started…</li></ul>

<h2>7. Non-text content</h2>Non-text content is anything on a website other than text, such as images, graphs, video, audio, and other visual and audio content. Text alternatives help make non-text content accessible to blind or deaf people.<blockquote>ℹ️ Search engines such as Google or AI (Gemini) understand the content of a page better thanks to alternative texts, so by filling in alternative texts correctly, you improve SEO.</blockquote>Rules for writing alternative texts for images:<ul><li>Conciseness and clarity: Text should accurately describe what is in the image, but without unnecessary details.</li><li>Context is key: Always think about why an image is on the page. What purpose does it serve? Alternative text should convey that purpose.</li><li>Do not start with phrases like "Image..." or "Photo...": screen reader already knows that it is an image (from the HTML tag <code>&lt;img&gt;</code>). Adding this to the <code>alt</code> text s unnecessary and distracting.</li><li>If the image is a link, describe the link destination: If a clickable image leads to another page, <code>alt</code> text should describe where the user will be taken (e.g., "Home page of company XY").</li><li>Decorative images must have an empty <code>alt</code> attribute: If an image is not used to convey information, but only for visual enhancement (e.g., various wavy lines, backgrounds), it must have <code>alt=""</code>. This signals the reader to ignore it. Do not omit the <code>alt</code> attribute entirely!</li></ul><pre><code class="language-html">// Good examples ✅
&lt;!-- It is concise, to the point, and accurately describes the main idea of the image. --&gt;
&lt;img alt="A golden retriever plays with a red ball in the park."&gt;

&lt;!-- If the data is simple and concise, you can insert it directly into the alt text. --&gt;
&lt;img alt="Bar chart of visits: April - 5,000, May - 8,000, June - 12,000 visits."&gt;

&lt;!-- It clearly communicates that clicking on the logo will return the user to the home page. It describes the function, not just what is in the image. --&gt;
&lt;img src="logo_GR.png" alt="GoodRequest - home page"&gt;

// Bad examples ❌
&lt;!-- Too general. Does not provide any useful information. --&gt;
&lt;img alt="a dog"&gt;

&lt;!-- Unnecessarily long and begins with the word "Photo." Details about the weather or the color of the grass are apparently not relevant to the context of the article. --&gt;
&lt;img alt="Photo of a golden retriever playing with a red ball on green grass in a park on a sunny day."&gt;

&lt;!-- Does not describe the function of the link. User does not know where clicking on it will take them. --&gt;
&lt;img alt="Logo"&gt;

&lt;!-- Better, but information about the link destination is still missing. --&gt;
&lt;img alt="WebTech company logo"&gt;

&lt;!-- Unnecessarily interrupts the user with information that has no value to them --&gt;
&lt;img alt="Blue wavy line"&gt; 

&lt;!-- User does not learn anything from the data displayed in the graph. It is the same as if there were no image there. --&gt;
&lt;img alt="Visitor graph"&gt;</code></pre>Rules for writing alternative texts for other types of content:<ul><li>Audio content (e.g. podcast): Complete transcript must be available. This transcript should include not only the spoken word, but also a description of important sounds (e.g., "[laughter]," "[audience applause]").</li><li>Video content: Synchronized captions must be provided. If possible, provide sign language interpretation for the deaf. If the video displays important visual information, you should provide an audio or text description that describes everything important that is happening in the video.</li><li>CAPTCHA (e.g., describing distorted text from an image): You must provide an alternative that does not require vision, such as an audio captcha.</li></ul>

<h2>8. Do not use text in images</h2>Static images with text content do not allow people to change the appearance of the text to improve its readability, e.g. color contrast, text size, etc. Text in images is blurred when zoomed in. Unlike real text on a page, text in an image does not adapt to different screen sizes or user settings.Screen readers cannot interpret text within images, so people who rely on these tools will not be able to access the content unless the image is properly labeled or contains alternative text.

<h2>9. Pausing automatically changing content</h2>Automatically moving or animated content that lasts longer than 5 seconds must be able to be paused or hidden. Elements that automatically update cause problems for screen reader users or people who are unable to process information quickly (cognitive disabilities).

<h3>Adjustable timing</h3>Time limits should be avoided unless they are necessary for the task at hand (e.g., exams, auctions). If time limits are used, it must be possible to disable them, adjust them to at least 10 times the default value, or extend them by at least 10 times.<h3>Flashing content more than three times per second</h3>Nothing on the page should flash more than three times per second. It does not matter how large or bright the content is. Some web content, such as videos, games, or animated graphics, may flash rapidly to attract attention. However, this type of flashing can cause seizures or other serious health problems in users who are sensitive to flashing content.

<h2>10. Additional rules</h2><ul><li>Device orientation: When you rotate the device from portrait to landscape mode, the content will be perfectly readable and usable.</li><li>Automatic audio playback (usually activated together with the video) lasting longer than 3 seconds can be muted or stopped.</li><li>Timeout settings: If a website has any timeout settings (e.g., automatic logout after 10 minutes of inactivity), the user must be able to disable, modify, or simply extend this timeout before it expires.<ul><li>Example: If an e-shop reserves goods in the shopping cart for 10 minutes, it may not remove them without warning after the time has elapsed. Instead, the system must notify the user in advance that the time is running out. At the same time, it must offer the user a simple option, such as a button, to easily and repeatedly extend the time limit <code>I need more time (extend by 10 minutes)</code>.</li></ul></li></ul>

Vizuální přístupnost je základem webu, který dokáže sloužit všem. Od čitelného textu přes dostatečný kontrast až po přehlednou navigaci má každý detail význam. Jasně stanovené principy pomáhají udržet konzistentnost a zaručit férovou uživatelskou zkušenost.

 Praktický průvodce vizuální přístupností

Vizuálna prístupnosť je základom webu, ktorý dokáže slúžiť všetkým. Od čitateľného textu cez dostatočný kontrast až po prehľadnú navigáciu, každý detail má význam. Jasne stanovené princípy pomáhajú udržať konzistentnosť a zaručiť férovú používateľskú skúsenosť.

Praktický sprievodca vizuálnou prístupnosťou

Vizuálna prístupnosť hero.png

Vizuálna prístupnosť thumb.png

Andrej Nemeček

Visual accessibility is the foundation of a website that can serve everyone. From readable text to sufficient contrast to clear navigation, every detail matters. Clearly defined principles help maintain consistency and ensure a fair user experience.

Practical guide to visual accessibility

We’re a trusted partner who can help your organisation discover and leverage new business opportunities, create outstanding digital products, and drive long-term growth for your brand.

Experts in

GoodRequest-2024.jpg

 GoodRequest

We’re a digital studio with over 11 years of experience creating sustainable products for growing businesses and industry leaders. Our work brings lasting value, a genuine competitive advantage, and is positioned for long-term growth.

Our projects

We help turn ideas into long-term success

Testimonials

What we do

We  define and validate your product idea

Product 

Successful and sustainable products are placed at the intersection of human and business needs. To create a successful product, we take the time to thoroughly understand your target audience and business objectives before we do any work.

Excellent outcomes through research and design

Design

Our certified UX/UI designers work closely with your users to understand their needs, behaviours, and preferences. They conduct user research and usability testing to gather real user experiences and honest opinions.&nbsp;

Full-scale mobile and web app development 

Development

Since 2013, we’ve deployed more than 200 successful mobile and web applications. Our testers and developers have received the prestigious Citadelo, ISTQB, and SOACP certifications. We invest to the professional development of our people so they can create high-quality digital products.

Growth

Launching a digital product is just the beginning; we don't stop there. We stay ahead of the curve by building our products on reliable and scalable platforms. This ensures that they continue to grow along with your business.

Experts in
software developmentdigital productsapp developmentproduct design

Our projects

We help turn ideas into long-term success

A digital guide for children in the world of finance TABI from Tatra banka

Modernization and streamlining of beauty salons with Notino Partner

Creating a state-of-the-art experience for Benu pharmacies

Creating a consistent digital experience for Fitshaker, the largest fitness community in Slovakia

Testimonials

What we do

We define and validate your product idea

Blog

Stay ahead of the curve.

How to build AI solutions that deliver 10× more value for your business

Importance of analysts in successful software projects

Practical guide to visual accessibility

Experts in software developmentdigital productsapp developmentproduct design

Our projects

We help turn ideas into long-term success

A digital guide for children in the world of finance TABI from Tatra banka

Modernization and streamlining of beauty salons with Notino Partner

Creating a state-of-the-art experience for Benu pharmacies

Creating a consistent digital experience for Fitshaker, the largest fitness community in Slovakia

Testimonials

What we do

We define and validate your product idea

Blog

Stay ahead of the curve.

How to build AI solutions that deliver 10× more value for your business

Importance of analysts in successful software projects

Practical guide to visual accessibility

Experts in
software developmentdigital productsapp developmentproduct design