DEV Community: Niharika Pujari

Angular's New Template Control Flow (@if, @for, @switch) - A Cleaner Way to Write Angular Templates

Niharika Pujari — Mon, 09 Mar 2026 02:30:49 +0000

Introduction

Angular has evolved significantly over the last few releases. One of the most noticeable improvements in modern Angular is the new template control flow syntax.

If you've been working with Angular for a while, you're probably used to writing templates like this:

*ngIf
*ngFor
*ngSwitch

But newer Angular versions introduced a cleaner alternative:

@if
@for
@switch

These new block-based directives make templates easier to read, easier to maintain, and more aligned with modern Angular features like Signals.

Let’s walk through how they work and why they matter.

Why Angular Introduced New Control Flow

Traditional structural directives worked well, but they came with some drawbacks:

• Complex templates became harder to read
• Often required extra wrapper elements (ng-container)
• Less optimized for Angular’s newer rendering strategies

The new block-style control flow syntax improves readability and allows Angular’s compiler to better optimize template updates.

It also fits naturally with Angular’s signal-based reactivity model, which is becoming more common in modern Angular applications.

Conditional Rendering with @if

Old approach:

<div *ngIf="isLoggedIn">
  Welcome back!
</div>

New approach:

@if (isLoggedIn) {
  <div>Welcome back!</div>
}

You can also easily add an else block.

@if (isLoggedIn) {
  <div>Welcome back!</div>
} @else {
  <div>Please log in</div>
}

This reads much closer to regular programming logic, which makes templates easier to understand.

Looping with @for

Old approach:

<li *ngFor="let product of products">
  {{ product.name }}
</li>

New approach:

@for (product of products; track product.id) {
  <li>{{ product.name }}</li>
}

Benefits of the new syntax:

• Cleaner and more readable
• Built-in tracking support
• Better performance optimization opportunities

Switch Statements with @switch

Old approach:

<div [ngSwitch]="status">
  <p *ngSwitchCase="'loading'">Loading...</p>
  <p *ngSwitchCase="'success'">Success!</p>
  <p *ngSwitchDefault>Error</p>
</div>

New approach:

@switch (status) {
  @case ('loading') {
    <p>Loading...</p>
  }

  @case ('success') {
    <p>Success!</p>
  }

  @default {
    <p>Error</p>
  }
}

Again, the syntax now feels much closer to normal application logic.

A Simple Real-World Example:

Let’s imagine a product list page that loads data from an API and shows different UI states.

Component:

status = signal('loading');
products = signal([]);

Template:

@switch (status()) {

  @case ('loading') {
    <p>Loading products...</p>
  }

  @case ('success') {
    <ul>
      @for (product of products(); track product.id) {
        <li>{{ product.name }}</li>
      }
    </ul>
  }

  @default {
    <p>Something went wrong.</p>
  }

}

This example combines:

• Signals for state
• Modern Angular control flow
• Cleaner UI logic

Why This Matters for Angular Developers

The new template syntax improves several things:

• Better readability
• Templates feel more like normal code.
• Less boilerplate
• Fewer structural directives and wrapper elements.
• Performance improvements
• Angular can optimize block syntax more efficiently.
• Better integration with Signals
• Signals and block syntax together enable fine-grained UI updates.

Should You Start Using It?

If you are:

• Starting a new Angular project
• Upgrading to Angular 17+
• Using signals and standalone components

Then adopting this new syntax is highly recommended.

Existing applications can migrate gradually over time.

Conclusion

Angular’s modern direction is becoming clear:

• Signal-based reactivity
• Cleaner template syntax
• Better developer experience

The new @if, @for, and @switch syntax is a small change that can significantly improve template readability and maintainability.

If you haven't tried it yet, it’s definitely worth experimenting with in your next Angular project.

Angular 21: The Upgrade from v20, That's Actually Worth It!

Niharika Pujari — Mon, 02 Feb 2026 15:42:11 +0000

Angular continues evolving quickly, and Angular 21 brings some of the most exciting updates in recent releases. In this post, I will walk through why you should upgrade, when Angular 21 was released, and highlight a few key new features including one you should consider adopting immediately.

Introduction

Angular has solidified itself as a top framework for building scalable front-end applications. With every major version, the Angular team focuses on performance, developer productivity, and modern patterns that help make apps easier to build and maintain.

Angular 21 marks an important step forward, not just with incremental changes, but with real enhancements to reactivity, tooling, and the developer experience.

When Was Angular 21 Released?

Angular 21 was officially released on November 20, 2025.
This continues Angular's twice-a-year release cadence, where major versions typically launch in May and November each year.

Why Should You Upgrade to the Latest?

Upgrading to Angular 21 isn't just about having the newest version - it brings practical benefits:

Performance Improvements – Faster builds and smaller bundles.
Modern Tooling – New test runner and AI-powered dev tools.
Developer Experience Enhancements – Less boilerplate and cleaner patterns.
Future-Proofing - Staying aligned with the Angular ecosystem as it evolves (signals, zoneless reactivity).

Staying on older versions may mean missing out on productivity gains and tooling improvements that can boost team velocity and app performance.

Key New Features in Angular 21

Here is a curated look at a few standout Angular 21 features along with some mini examples.

Signal Forms (next-gen forms)

Angular 21 introduces a brand new way to build forms - Signal Forms. This approach shifts form management onto Signals, making form state easier to reason about and more predictable than classic reactive forms.

Example (simple login form):

import { form, required, email } from '@angular/forms/signals';

const loginForm = form({
  email: ['', [required(), email()]],
  password: ['', [required()]],
});

Signal Forms makes validation and state tracking more intuitive and aligns with Angular’s signals-first philosophy.
Note: While Signal Forms are one of the most exciting additions in Angular 21, they are still experimental and best introduced incrementally.

Zone-less Change Detection by Default

Angular has moved away from zone.js by default in this version, relying instead on Signals for change detection. This leads to fewer unnecessary change detection cycles and better performance.

This change makes apps more predictable and efficient, particularly in large apps with lots of dynamic UI.

Vitest as Default Test Runner

Switching to Vitest replaces older testing tools like Karma/Jasmine with a modern, faster test runner that's lighter, easier to configure, and built for modern web tooling.

Angular Aria and Accessibility Enhancements

Angular 21 also adds new ARIA-focused components and accessibility improvements, making it easier to build inclusive, accessible UI components.

One Feature You Should Adopt Now — HttpClient by Default

One practical change that many developers will immediately appreciate is that HttpClient is now included by default - you no longer need to import HttpClientModule manually:

import { Component, inject } from '@angular/core';
import { HttpClient } from '@angular/common/http';

@Component({
  selector: 'app-users',
  template: `<ul>@for (user of users(); track user.id)<li>{{ user.name }}</li></ul>`,
})
export class UsersComponent {
  private http = inject(HttpClient);
  users = this.http.get<{ id: number; name: string }[]>('/api/users');
}

This change eliminates common boilerplate and lets you start fetching data faster especially useful in smaller apps or micro-services components.

Conclusion

Angular 21 delivers a blend of strategic evolution and practical upgrades. From the reimagined Signal Forms to better tooling and improved performance, it’s a release worth upgrading to especially for teams looking to stay current and take advantage of modern Angular patterns.

Before upgrading:

Make sure your dependencies and third-party libraries are compatible.
Review zone-less implications if you use legacy patterns.
Try Signal Forms incrementally to smooth the transition.

If you are on Angular 20 or earlier, moving to Angular 21 could be one of the most productive upgrades you make this year.

Accessibility: Building Inclusive Experiences | A Lens on Basic A11y Testing

Niharika Pujari — Fri, 02 Jan 2026 19:40:29 +0000

Introduction

Accessibility testing can feel intimidating at first. Between WCAG guidelines, assistive technologies, and tooling, it’s easy to think you need to be an expert before you can meaningfully contribute. After watching and reading Basic Accessibility Testing by Glen Walker (via Equalize Digital), one thing became very clear: you don’t need to know everything to start making a real impact.

Takeaways

How to think about accessibility testing in day-to-day frontend work:

Start Small — Basic Testing Goes a Long Way

One of the most reassuring messages from my learning is that basic accessibility testing catches a large percentage of real user issues. Even though WCAG 2.1 AA includes many success criteria, you can uncover meaningful problems by focusing on a few core areas:

Keyboard navigation
Page structure and semantics
Color contrast
Images and alternative text

This reframing helps remove the “all or nothing” mindset. Accessibility progress is incremental — and that’s okay.

Keyboard Testing Is a Powerful First Step

Using just the Tab key, you can immediately spot accessibility issues:

Can every interactive element be reached?
Is the focus order logical and predictable?
Are there keyboard traps or mouse-only interactions?

This is especially important for users who rely entirely on keyboard navigation, including screen reader users and people with motor disabilities. Keyboard testing is simple, fast, and incredibly high-value.

Screen Readers Reveal What Visual Testing Can’t

Listening to a page using a screen reader changes how you understand your UI. Glen demonstrates how tools like NVDA, JAWS, or VoiceOver expose issues such as:

Missing or incorrect labels
Poorly structured headings
Controls that look fine visually but make no sense audibly

Even basic familiarity with a screen reader can dramatically improve how accessible your interfaces are.

Make Focus Visible (Really Visible)

A practical tip I loved: add a strong, custom focus outline during testing.

This helps uncover:

Missing focus states
Hidden or unintended focusable elements
Interactive components that don’t clearly communicate state or purpose

It’s a small change that makes keyboard issues impossible to ignore.

Semantic Structure Matters More Than Styling

Headings, lists, and tables should communicate structure — not just appearance. Styling text to look like a heading without using semantic HTML breaks screen reader navigation and page comprehension.

This reinforced an important reminder: accessibility is deeply tied to frontend architecture, not just visual design.

Color Contrast Is Foundational, Not Optional

Low contrast affects far more users than we often realize, including people with low vision or temporary impairments. While automated tools help, Glen highlights that:

CSS inspection is sometimes necessary
Responsive states and hover/focus styles can introduce new contrast issues
Contrast needs to be checked intentionally, not assumed.

Responsive Design Can Introduce New Accessibility Issues

Accessibility testing shouldn’t stop at desktop. Responsive layouts often change:

Navigation behavior
Focus order
Touch target size and spacing

Testing across breakpoints is essential to ensure accessibility doesn’t regress on mobile or tablet views.

Automated Tools Are Helpful — but Incomplete

Tools like axe or WAVE are useful for catching obvious issues, but they only surface a fraction of real accessibility problems.

Manual testing — especially with keyboard and screen readers — is where the majority of meaningful issues are found. Automation should support human testing, not replace it.

ARIA Should Be Used Carefully

One key caution: ARIA can do more harm than good when misused. Incorrect roles or attributes often make experiences worse, not better.

This reinforced the principle:
Use native HTML first. Add ARIA only when necessary — and only when you fully understand the impact.

Progress Over Perfection

Perhaps the most important takeaway: don’t wait for perfect accessibility knowledge to start testing.

Every improvement — better focus order, clearer labels, stronger contrast — makes a product more inclusive. Accessibility is a journey, and meaningful progress matters far more than completeness.

How I cleared my AWS Certified Solutions Architect Associate exam in 30 Days?

Niharika Pujari — Tue, 30 Dec 2025 19:44:10 +0000

A little about myself 🐥

I am a Lead Software Engineer, working for about 8 years now. I decided to give my self some challenge for my professional development so I chose to level up my knowledge about AWS. I had previously got from AWS Cloud practitioner certification in 2021 but if you are new to cloud, then the foundational certification is the way to go!

The first thing I would suggest is to set a date for your exam:

The best motivation to start preparing for the AWS certified exam is to Schedule the exam.

How to schedule the exam?

Follow this link to Schedule Exam. Since I was planning to give the exam from my home office, I opted for the Pearson Vue option.

Once you register for the exam, the confirmation mail will have the necessary details needed for the exam. Video Reference

What resources I used:

Udemy:
A udemy course by Stephane Maarek set a foundation for what to expect on the exam, I found the chapter summary and exam tips to be very helpful.
Udemy practice exams:
After preparing for about 2 weeks (2 hours everyday), I started giving some practice tests on Udemy. I found these exams useful since they gave me a taste on what kind of questions I should expect in my exam. Udemy practice tests
White papers:
I did not get a chance to go over all the white papers, but I did take a glance on the glossary and read through the topics which I was not comfortable with. I would recommend reading the white papers when you are close to the exam.
AWS Free training:
This course helped me tremendously to understand cloud concepts with real life exams. Huge shout out to the content creators!! AWS free training

On exam day:

I just read through the notes I prepared for the exam during the Udemy course and the practice questions that I answered incorrectly. Try to keep calm and take a walk! 😌

Conclusion:

I hope these resources, links and my experience helps you in passing your AWS Solutions Architect Exam, and if you have any questions or need help, please don’t hesitate to reach out to me or leaving a comment below! All the best! 👍🍀

Accessibility: Building Inclusive Experiences | A Lens on How UX, UI, and Accessibility Work Together

Niharika Pujari — Tue, 30 Dec 2025 19:31:25 +0000

Introduction

Accessibility is often treated as a set of standards to be checked off, but in practice it’s an emergent property of good UX and UI. UX defines the flow and logic of interactions, UI implements visual and interactive cues, and accessibility ensures those cues work across abilities and contexts. When these elements are aligned from the start, the result is a more robust and inclusive experience.

Design Holistically, Not in Silos

One of the most practical lessons from analyzing a real site audit is that UX, UI, and accessibility must be treated as interconnected concerns. UX identifies frustrations and gaps in how people use a product; UI focuses on presentation and interaction; accessibility ensures that those interactions are inclusive for all users. Treating these disciplines as isolated tasks increases the risk of leaving usability or accessibility problems undetected.

User Patterns Matter - Respect Conventions

Usability conventions - like placing navigation menus or logos where users expect them - aren’t arbitrary. They reflect learned behavior that helps users scan and interact more intuitively. Breaking these conventions without reason can interrupt user flow and cause confusion, which impacts both ease of use and accessibility.

Clarity in Content Structure Helps Everyone

Semantic elements such as headings are more than SEO tools — they are critical for screen readers and users who scan content quickly. Skipped or incorrect heading levels not only disrupt assistive navigation but also diminish the hierarchical flow of a page.

Contrast and Legibility Are Core UX Decisions

Low contrast between text and background isn’t just an accessibility violation - it’s a UX flaw. Even users without impairments struggle with poor visual contrast, especially in bright glare or low-light environments. Tools to measure contrast should be part of routine design checks.

Consistency Is More Than Aesthetic

Consistency in typography, button styles, and text casing isn’t a cosmetic preference - it reduces cognitive load and creates reliable interaction patterns. Too many fonts or mixed casing patterns force users to “re-learn” how to read or interact on each page.

Keyboard Navigation Is a Basic Accessibility Test

Before reaching for advanced tools, a simple keyboard navigation check reveals whether interactive elements are focusable and predictable. If users cannot reliably tab through interactive controls, that’s a strong indicator of deeper accessibility and UX issues.

Data Should Drive Design Decisions

Analytics aren’t just numbers - they’re signals. High bounce rates, low engagement on key pages, or rapid exits on forms can point to underlying UX or accessibility issues. Developers and designers should leverage real usage data early to prioritize fixes that matter most to users’ behavior.

UX Extends Beyond Websites

UX principles are not limited to digital screens. They apply to any interaction - whether it’s physical exhibits, interactive installations, or ways users navigate information contextually. Thinking about UX as a mindset rather than a job title broadens its impact.

Accessibility: Building Inclusive Experiences | A Lens on Branding and Design

Niharika Pujari — Tue, 30 Dec 2025 19:08:53 +0000

Introduction

In a world where digital experiences shape how we work, play, shop, learn, and communicate, accessibility isn’t a passing trend - it’s a core requirement of good engineering and thoughtful design. Accessibility ensures that digital products and services can be used by everyone, regardless of ability, device, or context.

Despite its impact, accessibility is still too often treated as an after-thought addressed late in the process or reduced to a compliance checkbox. In this post, we’ll take a more holistic view, exploring accessibility through four key lenses: branding and design, the intersection of UX and UI, foundational testing practices, and practical workflows that scale. These insights come from practitioners actively building accessibility into real-world design and development processes, offering lessons developers can apply today.

Accessibility as a Core Part of Brand and System Design

Accessibility Enhances Brand Reach and Impact

Accessibility isn’t just a moral or legal concern — it expands who can actually use and understand your product or service. Considering accessibility early increases your potential audience instead of limiting it.

Common Misconceptions About Accessibility

Many designers (and stakeholders) assume accessible design must be ugly, use only dark colors, or restrict creative choices. In reality, no color is inherently inaccessible — what matters is how colors work together in the final design. Thoughtful use of contrast and pairings lets you maintain visual richness without excluding users.

Color Choices Matter — But Not in the Way People Think

Accessibility is not about preferring darker colors. Good contrast and readable combinations are what make a design inclusive — even bright palettes can be accessible if chosen carefully.
Designers should consider conditions like low vision, cataracts, glaucoma, and color blindness, which affect how users perceive color combinations and readability. Planning for contrast consistency helps ensure content remains legible for everyone.

Strategic Accessibility Saves Time and Money

If accessibility is only added at the end of a project, designers often face expensive remediations and redesigns that can shift the entire brand’s look. Making accessibility part of the process avoids costly iterations later.

Improving Accessibility Can Preserve Brand Integrity

When accessibility is an afterthought, fixes often involve changing or darkening brand colors — which can distort original design intent and weaken consistency across a brand’s assets.

Accessibility Strengthens Communication

At its core, design is about communicating ideas. Accessible designs make that communication clearer for everyone, including users with invisible challenges such as cognitive, neurological, or learning disabilities.

Positive Business Outcomes

Studies show a large percentage of users with accessibility barriers will leave a site they can’t read or interact with comfortably. Prioritizing accessibility keeps users engaged and reduces lost traffic or revenue.

Accessibility Builds Professional Credibility

For developers and designers alike, proactively addressing accessibility signals expertise, nurtures client trust, and differentiates you from competitors who still treat accessibility as optional.

Fun activity alert: Typing test

Niharika Pujari — Thu, 16 Dec 2021 15:30:59 +0000

I took the typing test today using https://www.typingtest.com/ website (Check your typing skills in 60 seconds).

I got a net speed of 47 WPM. What is yours?

Observables... why?

Niharika Pujari — Fri, 03 Dec 2021 16:36:31 +0000

Many times in the front end realm, while using angular framework we come across "Let's use an observable". OH! Well ok, but why?

Observables are used to fetch data Asynchronously and we can use their return values in a continuous sequence (multiple times) when executed.

By default, they are lazy as it emits values when time progresses.
They offer a lot of operators which simplifies the coding effort.
Can be cancelled using unsubscribe method anytime.
RXJS operators: You have many pipe operators majorly map, filter, switchMap, combineLatest, etc. to transform observable data before subscribing.
Subscribe method allows us to have a centralized and predictable error handling.
One operator retry can be used to retry whenever needed, also if we need to retry the observable based on some conditions retryWhen can be used.

Reference:
RXJS: https://rxjs.dev/guide/overview
List of operators along with their interactive diagrams: https://rxmarbles.com/

AWS Certified Developer - Associate Resources

Niharika Pujari — Tue, 10 Aug 2021 17:21:43 +0000

Hello Again! I started researching on how I can achieve my next milestone.. Yes, the AWS Certified Developer certification. Here is what I got:

Exam Details

Registration: Schedule an exam

Format: 65 questions; either multiple choice or multiple response

Time: 130 mins to complete the exam

Cost: 150 USD (Practice exam: 20 USD)

Exam guide: https://d1.awsstatic.com/training-and-certification/docs-dev-associate/AWS-Certified-Developer-Associate_Exam-Guide.pdf

Resources:

ACloudGuru
AWS Certified Developer Associate (FIRST 6 HOURS) by Ranga Karanam
freeCodeCamp
AWS Certification Prep
Exam Readiness

Recommeneded whitepapers:

AWS Well-Architected Framework
Practicing Continuous Integration and Continuous Delivery on AWS Accelerating Software Delivery with DevOps
Microservices on AWS
Serverless Architectures with AWS Lambda
Optimizing Enterprise Economics with Serverless
Architectures Running Containerized Microservices on AWS Blue/Green Deployments on AWS

Conclusion:

Hope this resources help you to get started; help you to complete your AWS Certified Developer certification study and prepare you for the exam.

P.S:
I will update this post as and when I come across some interesting content. Stay Tuned!!

If you are looking to complete the AWS Cloud Practitioner certification, please refer my previous posts to help you getting started.

That's all folks! 😎

How I cleared my AWS cloud practitioner exam in 3 weeks?

Niharika Pujari — Mon, 02 Aug 2021 18:53:19 +0000

A little about myself 🐥

I am a software engineer, working for about 3 years now. I decided to give my self some challenge for my professional development so I chose to learn about AWS. I had no prior experience with cloud concepts, so if you are new to cloud, then the foundational certification is the way to go!

The first thing I would suggest is to set a date for your exam:

The best motivation to start preparing for the AWS certified exam is to Schedule the exam.

How to schedule the exam?

Follow this link to Schedule Exam. Since I was planning to give the exam from my home office, I opted for the Pearson Vue option.

Once you register for the exam, the confirmation mail will have the necessary details needed for the exam. Video Reference

What resources I used:

A Cloud Guru:
A cloud guru course set a foundation for what to expect on the exam, I found the chapter summary and exam tips to be very helpful.
Udemy practice exams:
After preparing for about 2 weeks (2 hours everyday), I started giving some practice tests on Udemy. I found these exams useful since they gave me a taste on what kind of questions I should expect in my exam. Udemy practice tests
White papers:
I did not get a chance to go over all the white papers, but I did take a glance on the glossary and read through the topics which I was not comfortable with. I would recommend reading the white papers when you are close to the exam.
AWS Free training:
This course helped me tremendously to understand cloud concepts with real life exams. Huge shout out to the content creators!! AWS free training

On exam day:

I just read through the notes I prepared for the exam during the cloud guru course I took and the Udemy practice questions that I answered incorrectly. Try to keep calm and take a walk! 😌

Conclusion:

I hope these resources, links and my experience helps you in passing your AWS Cloud Practitioner Exam, and if you have any questions or need help, please don’t hesitate to reach out to me or leaving a comment below!

GOOD LUCK!! 👍🍀

AWS Cloud Practitioner Certification Resources

Niharika Pujari — Tue, 30 Mar 2021 19:56:11 +0000

The AWS Certified Cloud Practitioner examination is intended for individuals who have the knowledge and skills necessary to effectively demonstrate an overall understanding of the AWS Cloud, independent of specific technical roles addressed by other AWS Certifications. The exam can be taken at a testing center or from the comfort and convenience of a home or office location as an online proctored exam.

Exam Details :

65 MCQ questions

90 minutes to complete the exam

Testing center or online proctored exam

100 USD (Practice Exam: 20 USD)

Resources:

LinkedIn Learning:

Prepare for AWS certified cloud practitioner exam

White papers:

Practice tests

Udemy AWS certified cloud practitioner Practice exams

Cherry pick commits in Github

Niharika Pujari — Fri, 26 Mar 2021 00:42:29 +0000

What does cherry picking mean?

Cherry picking in Git means to choose a commit from one branch and apply it onto another.

Ok, what should I do?

Switch to the branch you want to apply the commit.

git checkout <target-branch>

Then...?

Copy the commit SHA of the commit you would like to apply, you can use git log to view your commits.

git cherry-pick <commit-hash>

Am I done?

Yes, commit and push to target branch.

Cheers!

DEV Community: Niharika Pujari

Angular's New Template Control Flow (@if, @for, @switch) - A Cleaner Way to Write Angular Templates

Introduction

Why Angular Introduced New Control Flow

Why This Matters for Angular Developers

Should You Start Using It?

Conclusion

Angular 21: The Upgrade from v20, That's Actually Worth It!

Introduction

When Was Angular 21 Released?

Why Should You Upgrade to the Latest?

Key New Features in Angular 21

One Feature You Should Adopt Now — HttpClient by Default

Conclusion

Accessibility: Building Inclusive Experiences | A Lens on Basic A11y Testing

Introduction

Takeaways

Start Small — Basic Testing Goes a Long Way

Keyboard Testing Is a Powerful First Step

Screen Readers Reveal What Visual Testing Can’t

Make Focus Visible (Really Visible)

Semantic Structure Matters More Than Styling

Color Contrast Is Foundational, Not Optional

Responsive Design Can Introduce New Accessibility Issues

Automated Tools Are Helpful — but Incomplete

ARIA Should Be Used Carefully

Progress Over Perfection

Further Reading & Inspiration:

How I cleared my AWS Certified Solutions Architect Associate exam in 30 Days?

A little about myself 🐥

How to schedule the exam?

What resources I used:

On exam day:

Conclusion:

Accessibility: Building Inclusive Experiences | A Lens on How UX, UI, and Accessibility Work Together

Introduction

Design Holistically, Not in Silos

User Patterns Matter - Respect Conventions

Clarity in Content Structure Helps Everyone

Contrast and Legibility Are Core UX Decisions

Consistency Is More Than Aesthetic

Keyboard Navigation Is a Basic Accessibility Test

Data Should Drive Design Decisions

UX Extends Beyond Websites

Further Reading & Inspiration:

Accessibility: Building Inclusive Experiences | A Lens on Branding and Design

Introduction

Accessibility as a Core Part of Brand and System Design

Accessibility Enhances Brand Reach and Impact

Common Misconceptions About Accessibility

Color Choices Matter — But Not in the Way People Think

Strategic Accessibility Saves Time and Money

Improving Accessibility Can Preserve Brand Integrity

Accessibility Strengthens Communication

Positive Business Outcomes

Accessibility Builds Professional Credibility

Further Reading & Inspiration:

Fun activity alert: Typing test

Observables... why?

AWS Certified Developer - Associate Resources

Exam Details

Resources:

Recommeneded whitepapers:

Conclusion:

How I cleared my AWS cloud practitioner exam in 3 weeks?

A little about myself 🐥

How to schedule the exam?

What resources I used:

On exam day:

Conclusion:

AWS Cloud Practitioner Certification Resources

Resources:

LinkedIn Learning:

White papers:

Practice tests

Cherry pick commits in Github