Skip to content

Blog

User Experience Accessibility

WCAG Accessibility 7: Improving Alt Text and Image Accessibility on a WordPress Website

WCAG Accessibility 7: Images, Alt Text & Media Accessibility In the previous post, we focused on improving screen reader accessibility using semantic HTML and ARIA. In this post, we look at images and media, and how proper use of alt text improves accessibility for screen reader users. Read WCAG Accessibility 6: ARIA & Semantic HTML In this seventh post in our WCAG accessibility series, we focus on images and media — and how they can either support or block accessibility depending on how they are implemented. Images play an important role in communicating content, but without proper alternative text (alt
User Experience Accessibility

WCAG Accessibility 6: Improving Screen Reader Accessibility with ARIA and Semantic HTML

WCAG Accessibility 6: ARIA Roles & Semantic HTML In the previous post, we focused on keyboard navigation and improving focus visibility across the site. In this post, we look at how semantic HTML and ARIA help improve the experience for screen reader users. Read WCAG Accessibility 5: Improving Keyboard Navigation In this sixth post in our WCAG accessibility series, we focus on improving the experience for screen reader users by using semantic HTML and ARIA (Accessible Rich Internet Applications) attributes. While visual improvements such as colour contrast and layout are important, accessibility also depends heavily on how content is structured
User Experience Accessibility

WCAG Accessibility 5: Improving Keyboard Navigation on a WordPress Website

WCAG Accessibility 5: Keyboard Navigation & Focus Management  In this fifth post in our WCAG accessibility series, we focus on keyboard accessibility — a critical requirement for users who cannot use a mouse. In the previous post, we focused on improving colour contrast to enhance readability and visual accessibility. In this post, we look at keyboard navigation and how ensuring full keyboard access improves usability for all users. Read WCAG Accessibility 4: Fixing Colour Contrast Issues   Ensuring that a website is fully usable via keyboard is a core part of WCAG 2.2 Level AA compliance. It benefits users who
User Experience Accessibility

WCAG Accessibility 4: Fixing Colour Contrast Issues on a WordPress Website

WCAG Accessibility 4: Fixing Colour Contrast & Visual Accessibility Issues  In the previous post, we focused on improving form accessibility, addressing issues such as missing labels and placeholder misuse. In this post, we turn our attention to colour contrast and how it impacts readability and usability across the Rainbows Ireland website. Read WCAG Accessibility 3: Fixing Form Accessibility Issues   In this fourth post in our WCAG accessibility series, we focus on one of the most common — and most overlooked — accessibility issues: colour contrast. While colour choices are often driven by branding and design preferences, insufficient contrast can
User Experience Accessibility

WCAG Accessibility 3: Fixing Form Accessibility Issues in WordPress

WCAG Accessibility 3: Fixing Form Accessibility Issues in WordPress   In our previous post, we reviewed the accessibility issues identified during our audit of the Rainbows Ireland website. In this post, we focus on resolving one of the most common problem areas — form accessibility. Read WCAG Accessibility 2: Reviewing Accessibility Issues As part of the accessibility work carried out on the Rainbows Ireland website, one of the most important areas to address was form accessibility. Forms are often where accessibility problems become most serious, because they directly affect a user’s ability to log in, make contact, submit information, or
User Experience Accessibility

WCAG Accessibility 2: Reviewing Accessibility Issues Found on a WordPress Website

WCAG Accessibility 2: Fixing WordPress Accessibility Issues (Elementor & Jupiter X)   In our previous post, we conducted a comprehensive accessibility audit of the Rainbows Ireland website using WAVE and manual testing. In this post, we take a closer look at the specific accessibility issues identified during that audit and how they impact usability. Read WCAG Accessibility 1: Auditing a WordPress Website Following the initial WordPress accessibility audit of the Rainbows Ireland website, the next step was to work through the issues highlighted by WAVE and Google Lighthouse and determine which problems were real, which were theme-related, and which were
User Experience Accessibility

WCAG Accessibility 1: Auditing a WordPress Website (Rainbows Ireland Case Study)

WCAG Accessibility 1: WordPress Accessibility Audit (Rainbows Ireland Case Study) This is the first post in our WCAG Accessibility series, where we document a step-by-step approach to auditing and improving accessibility on a live WordPress website. View the full WCAG Accessibility Series As part of an ongoing accessibility review, we recently carried out a WordPress accessibility audit of the Rainbows Ireland website. The goal at this stage was simple: identify the key accessibility issues before making any changes. Rather than jumping straight into fixes, we focused on understanding: where users may experience difficulties how the site performs against WCAG 2.1
Computer pc and laptop with programming code on screen

Codeigniter 22: Exploring the Future of REST APIs and Alternatives in Modern Development

Codeigniter 22: Exploring the Future of REST APIs and Alternatives in Modern Development REST APIs have long been the cornerstone of modern web and application development. However, as the technological landscape evolves, so do the methodologies for designing and consuming APIs. This blog explores the evolution of REST APIs, emerging alternatives like GraphQL, and how CodeIgniter remains relevant in the changing API ecosystem. The Evolution of REST APIs The Rise of REST: Representational State Transfer (REST) emerged as a simpler, more scalable alternative to SOAP. Key principles such as statelessness, resource-based URLs, and standard HTTP methods (GET, POST, PUT, DELETE)
Computer pc and laptop with programming code on screen

Codeigniter 21: REST API Development in CodeIgniter: Lessons Learned from Real-World Projects

Codeigniter Series 21: REST API Development in CodeIgniter: Lessons Learned from Real-World Projects Developing REST APIs with CodeIgniter is both a rewarding and challenging experience. Over time, real-world projects reveal insights and lessons that can shape best practices for future development. In this blog, we share the challenges faced, solutions implemented, and lessons learned while building REST APIs using CodeIgniter. Common Challenges in REST API Development with CodeIgniter Managing Large Codebases: As projects grow, managing controllers, models, and routes becomes increasingly complex. Maintaining Consistency: Ensuring consistent response formats and error handling across multiple endpoints. Handling Scalability: Scaling APIs to handle
Computer pc and laptop with programming code on screen

Codeigniter 20: Tips for Securing Sensitive Data in CodeIgniter REST APIs

Codeigniter 20: Tips for Securing Sensitive Data in CodeIgniter REST APIs Securing sensitive data is one of the most critical aspects of building a REST API. With data breaches becoming more frequent, it’s essential to adopt advanced security practices to protect sensitive user information. In this blog, we’ll discuss techniques such as encryption, secure data transmission, and best practices for data storage to secure your CodeIgniter REST API. Why Secure Sensitive Data? Prevent Data Breaches: Protect user information from unauthorized access. Ensure Compliance: Meet regulatory standards like GDPR, HIPAA, or PCI-DSS. Maintain Trust: Secure APIs foster trust among users and
Computer pc and laptop with programming code on screen

Codeigniter 19: How to Write Unit Tests for Your CodeIgniter REST APIs

Codeigniter 19: How to Write Unit Tests for Your CodeIgniter REST APIs Unit testing is an essential practice in modern software development, ensuring that individual components of your application work as expected. This guide will walk you through writing unit tests for your CodeIgniter REST API endpoints, helping you maintain a reliable and bug-free application. Why Unit Testing Matters Identify Bugs Early: Catch issues during development before they reach production. Enhance Code Quality: Ensure every component works as intended. Facilitate Refactoring: Modify code confidently, knowing tests will catch regressions. Improve Collaboration: Clear, automated tests help teams work effectively together. Setting
Computer pc and laptop with programming code on screen

Codeigniter 18: Best Practices for Structuring REST API Code in CodeIgniter

Codeigniter 18: Best Practices for Structuring REST API Code in CodeIgniter A well-structured codebase is crucial for building maintainable and scalable REST APIs. CodeIgniter’s flexibility allows developers to organize their application in a way that supports clean architecture and easy debugging. This guide explores best practices for structuring REST API code in CodeIgniter. Why Structure Matters Maintainability: A clean structure makes it easier to debug and enhance code. Scalability: Supports growth by simplifying the addition of new features. Collaboration: Helps teams work efficiently with a standardized codebase. Core Principles of Structuring a REST API Separation of Concerns: Keep responsibilities separated