Skip to main content

Navigating WCAG 2.1: A Step-by-Step Approach for Developers

 Get Familiar with WCAG 2.1: WCAG 2.1 is like the rulebook for web accessibility. It's split into four parts: Perceivable, Operable, Understandable, and Robust (POUR). For instance, "Perceivable" includes rules like giving all images a text description (alt text) for folks who can't see them.  Run an Accessibility Audit: Use tools like Google Lighthouse or WAVE to scan your site. They'll flag up stuff like missing alt text, low color contrast, or form fields without labels.  Manual Testing: Automated tools can't catch everything. You'll need up roll to your sleeves and do some manual testing. Try navigating your site using only your keyboard, or using a screen reader like NVDA or VoiceOver. You're checking that all content and functionality is accessible.   Write an Accessibility Statement: This is a page on your site where you talk about your commitment to accessibility. You could mention that you're aiming for WCAG 2.1 Level AA compliance, lis...

5 different and very useful React libraries

Here are a few Best React libraries that I found very useful to developers in 2021.

1. React Query
If you know how to work with promises or async/await, then you already know how to use React Query. There's no global state to manage, reducers, normalization systems, or heavy configurations to understand. Simply pass a function that resolves your data. It provides us with all of the data that we require without having to declare a state variable.

2. React Hook Form
It Reducing the amount of code you need to write, and removing unnecessary re-renders are some of the primary goals of React Hook Form. 

3. Rebass
A very simple and easy-to-implement UI components library capable of creating a very powerful set of theme-able UI elements. A whole set of customization and theme you can apply and play with.

4. Grommet
grommet is a react-based framework that provides accessibility, modularity, responsiveness, and themes in a tidy package

5. Fluent UI
Fluent UI's robust, up-to-date web controls are built with the React framework. Look through the control list to see the building blocks that are available using Fluent UI React.

Comments

Popular posts from this blog

Flexbox CSS Cheat Sheet by Learnpine

 

Debug Angular app in VS code editor

Simplest way to debug your Angular app by adding debugger for chrome extension in your MS Visular Studio. Add below configuration. You can add configuration by visiting debug panel. It will create .vscode directory for you and it will add default configuration for you. You can add/ modify configuration based on your requirement. For local development debugging you can use below configuration by enabling chrome debugging. launch.json { // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "chrome", "request": "launch", "name": "Launch Chrome against localhost", "url": "http://localhost:4200", "webRoot...

Navigating WCAG 2.1: A Step-by-Step Approach for Developers

 Get Familiar with WCAG 2.1: WCAG 2.1 is like the rulebook for web accessibility. It's split into four parts: Perceivable, Operable, Understandable, and Robust (POUR). For instance, "Perceivable" includes rules like giving all images a text description (alt text) for folks who can't see them.  Run an Accessibility Audit: Use tools like Google Lighthouse or WAVE to scan your site. They'll flag up stuff like missing alt text, low color contrast, or form fields without labels.  Manual Testing: Automated tools can't catch everything. You'll need up roll to your sleeves and do some manual testing. Try navigating your site using only your keyboard, or using a screen reader like NVDA or VoiceOver. You're checking that all content and functionality is accessible.   Write an Accessibility Statement: This is a page on your site where you talk about your commitment to accessibility. You could mention that you're aiming for WCAG 2.1 Level AA compliance, lis...