Link List

Acces­si­bil­i­ty arti­cle for devel­op­ers to bet­ter under­stand text-to-speech and screen read­ers.

Beau­ti­ful­ly designed com­po­nents that you can copy and paste into your apps. Acces­si­ble. Cus­tomiz­able. Open Source.

In this post Matt dis­cuss­es 16 acces­si­bil­i­ty issues and solu­tions we’ve encoun­tered while build­ing a bi-lin­gual web­site appli­ca­tion for a pub­lic sec­tor…

A col­lec­tion of bad prac­tices in HTML, copied from real web­sites.

It is dif­fi­cult for a user to under­stand a date when they are not aware of the con­ven­tion. The most obvi­ous exam­ple is, for instance, 05/04/2021 —the US cit­i­zen will read it as the 4^th of May, but for cit­i­zens of oth­er coun­tries, it means the 5^th of April (when I was a child in my coun­try, the same date would be writ­ten as 5IV2021).

As LGBTQIA+ Pride Month comes to a close, here are some core prin­ci­ples to con­sid­er as you build for every­one.

A for­ward-think­ing library of web com­po­nents.

Head­less UI for build­ing pow­er­ful tables & data­grids with TS/JS, React, Sol­id, Svelte and Vue

Unstyled, ful­ly acces­si­ble UI com­po­nents

Joel Strohmeier, Acces­si­bil­i­ty Con­sul­tant, looks at a much-used fea­ture of web­site inter­faces: the ​‘card’ com­po­nent.

W3C launch their redesigned web­site today — 20^th June 2023. It’s a proud moment for Stu­dio 24 as we cel­e­brate our part­ner­ship.

Dig­i­tal Acces­si­bil­i­ty Cen­tre (DAC) is a non-prof­it social enter­prise and one of the lead­ing providers of web acces­si­bil­i­ty ser­vices.

UK-based soft­ware test­ing & qual­i­ty assur­ance (QA) com­pa­ny. Real feed­back, from real peo­ple on real devices. Largest UK mobile & desk­top device lab.

Meet your hosts for the next 24 hours. We’ll be hav­ing a gen­er­al chat about acces­si­bil­i­ty, inclu­sive design, and talk­ing about the ses­sions we are most loo­ki…

For years, devel­op­ers have passed around a set of styles like a mag­ic incan­ta­tion. It’s time we made it a web stan­dard.

Adri­an Rosel­li shares an exam­ple of a respon­sive, acces­si­ble table along with a dis­cus­sion of the code and the deci­sions behind the code.

This spec­i­fi­ca­tion defines the author­ing rules for using Acces­si­ble Rich Inter­net Appli­ca­tions (WAI-ARIA) 1.2 and Dig­i­tal Pub­lish­ing WAI-ARIA Mod­ule 1.0 attrib­ut­es on HTML ele­ments.

A quick cus­tomiz­able ref­er­ence to Web Con­tent Acces­si­bil­i­ty Guide­lines (WCAG) 2 require­ments (suc­cess cri­te­ria) and tech­niques.

This check­list uses The Web Con­tent Acces­si­bil­i­ty Guide­lines (WCAG) as a ref­er­ence point.

Under­stand­ing how peo­ple with dis­abil­i­ties browse the web using assis­tive tech­nolo­gies (AT) is core to mak­ing acces­si­ble a good user expe­ri­ence. This brows­ing with assis­tive tech­nol­o­gy video series intro­duces com­mon­ly used soft­ware, how it works, and ways peo­ple nav­i­gate con­tent.