Over the past two weeks I've generated rapid prototypes for all my app work in Figma Make. I can't see myself ever needing Design again outside of small asset/component creation. Unless of course, the "ai credits" for an enterprise account count for nothing. I guess time will tell. #figma
02.03.2026 20:27
π 1
π 0
π¬ 0
π 0
Success Criteria Lookup - Designing for Accessibility
Quick update: I added Level AA and AAA to my success criteria look up page. Hopefully its useful to someone. #accessibility
designingforaccessibility.com/criteria-loo...
17.02.2026 20:51
π 0
π 0
π¬ 0
π 0
Title II of the ADA requires state and local governments to ensure all digital content, including web-based documents (PDFs, Word, Excel, PowerPoint), conforms to
WCAG 2.1 Level AA standards by April 24, 2026. Your documents must be accessible!
27.01.2026 17:26
π 0
π 0
π¬ 0
π 0
Government Licensing Software - Designing for Accessibility
Alright, my Success Criteria look up is live. Its only Level A for now but if people like it I'll do AA, and AAA. Its just a nice and simple lookup to explain criteria in its simplest terms.
designingforaccessibility.com/criteria-loo... #accessibility
15.01.2026 23:41
π 1
π 0
π¬ 0
π 0
Spent a few weeks designing and coding a Level A Success Criteria lookup. Type in the number, 1.1.1 for example and you get the criteria description and a layman's term explanation with an example. I'll share it soon #accessibility #vpat
13.01.2026 22:55
π 1
π 0
π¬ 0
π 0
New UX article for December in my practical UX perspectives section - "Reassuring your UX team about AI" - designingforaccessibility.com/reassuring-u... #ux
22.12.2025 21:46
π 0
π 0
π¬ 0
π 0
www.forbes.com/councils/for... Why Accessibility Is The Next Competitive Advantage #accessibility
21.12.2025 18:03
π 1
π 0
π¬ 0
π 0
We once got dinged by a state for removing the instructions pages, I kid you not. Asked us to put it all back in. I actually produce a completed "full" and "abbreviated" version of the VPAT to avoid that in the future. Ridiculous I know.
21.11.2025 21:20
π 1
π 0
π¬ 0
π 0
Are you waiting to publish your VPAT until all your defects are fixed? Don't. A VPAT is a disclosure document. An old VPAT looks worse than a new one with an acknowledgement of gaps and a mitigation plan.
#vpat #accessibility
19.11.2025 18:11
π 1
π 0
π¬ 1
π 0
Designing for Accessibility - UX Perspectives
My second "UX Perspectives" article is live. Head over to theuxperspective.com to see the list. This time its, "Handling Conflict in UX: From Design Debate To Real Solutions"
12.11.2025 22:44
π 0
π 0
π¬ 0
π 0
I'm getting a lot of questions about who's responsibility it is to produce the VPAT. Well, it depends: In smaller orgs (no a11y team), it's often a collaboration between devs, UX, and QA, with one person owning the VPAT documentation (usually someone on product or compliance). #vpat #accessibility
12.11.2025 22:43
π 0
π 0
π¬ 0
π 0
Next UX article coming in a couple of days: Handling Conflict in UX: From Design Debate To Real Solutions. I also registered a specific domain for the UX perspectives. I'll share that soon too. (its just a redirect for now) #ux
11.11.2025 17:10
π 0
π 0
π¬ 0
π 0
Accessibility Guidelines - Designing for Accessibility
First #ux related article is live from my "UX Perspectives" category. Its entitled - The Hill Worth Dying On. Any feedback or opinion is appreciated. π designingforaccessibility.com/ux-perspecti...
04.11.2025 19:59
π 0
π 0
π¬ 0
π 0
Finally got some time to start work on my "Practical UX Perspectives" section of the website. First article is, "The Hill Worth Dying On". Knowing when to fight for a design decision and when to let it go. π
29.10.2025 14:25
π 0
π 0
π¬ 0
π 0
A VPAT shows how accessible a product is.
WCAG is the standard those reports are measured against.
The numbers (2.0, 2.1, 2.2) are just versions, with newer ones adding more coverage.
The levels (A, AA, AAA) show how complete the accessibility effort is, with AA being the most common requirement
08.09.2025 18:20
π 0
π 0
π¬ 0
π 0
Sharing options on the pages is now complete and accessible. I think that's it for the site upgrades for now, back to some article research
07.08.2025 13:56
π 0
π 0
π¬ 0
π 0
Search added to the homepage. Simple js file for now but it works well. Now I'm working on the ability to share the articles.
03.08.2025 19:29
π 0
π 0
π¬ 0
π 0
After hours of work, I've now updated the website to include a light and dark theme switcher. Phew.
Next up: Search!
02.08.2025 22:32
π 0
π 0
π¬ 0
π 0
Designing for Accessibility - Inclusive Design for UX/UI
Learn how to design accessible websites and apps for all users. Practical accessibility tips for UX and UI designers.
I spent some time reorganizing and redesigning the website to better suite consumers. I'm not quite done but its live you wanna check it out. I need to add a search and a "dark mode" switcher but that'll come in time. - designingforaccessibility.com
17.07.2025 16:44
π 0
π 0
π¬ 0
π 0
Understanding Success Criterion 1.4.11: Non-text Contrast | WAI | W3C
Quick reminder (because I needed it myself) - Disabled elements are exempt from color contrast. π #accessibility www.w3.org/WAI/WCAG21/U...
01.07.2025 14:38
π 0
π 0
π¬ 0
π 0
Designing for Accessibility - A guide to web accessibility
Put together another article today - Building Accessible Government Licensing Software: A Developer's Guide to Pre-Built Components. Very specific you might think, but this topic is the majority of my work life. Figured I would share - designingforaccessibility.com/pre-built-co...
15.06.2025 04:57
π 0
π 0
π¬ 0
π 0
Designing for Accessibility - A guide to web accessibility
Did some clean up today and moved some things around. I also published, Accessibility Is Everyone's Job: Defining Responsibilities Across the SDLC #accessibility π
11.06.2025 21:10
π 0
π 0
π¬ 0
π 0
An example of a good error message best practices:
- Say what happened
- Say why it happened
- Provide reassurance
- Give them a way out
- Help them fix it
11.06.2025 15:07
π 0
π 0
π¬ 0
π 0
When it comes to the development of software, Accessibility should be everybody's responsibility. That means, specifics should come from Product and BA. UX Libraries and guides should be compliant. Dev components should be tested at the source, and QA procedures in place.
27.05.2025 20:07
π 1
π 0
π¬ 0
π 0
Designing for Accessibility - A guide to web accessibility
My article, 'Make a Mitigation and Remediation Plan', is now live. Check it out. Feedback appreciated. - #accessibility designingforaccessibility.com/mitigation-r...
21.05.2025 17:04
π 0
π 0
π¬ 0
π 0
Spent the morning writing a document called Accessibility Mitigation and Remediation for VPATs. I've also added some specifics for UAT and Releases. I'll be updating the website soon. π
19.05.2025 19:30
π 0
π 0
π¬ 0
π 0
Virginia HB2541 | 2025 | Regular Session
Bill Text (2025-03-24) Information Technology Access Act; digital accessibility, definitions, procurement requirements. [Acts of Assembly Chapter text (CHAP0571)]
VA recently enacted an accessibility law, effective April 24, 2026 or April 2027 depending on population.
Section 2.2-3503 requires all bidders on public contracts to submit an ACR/VPAT evidencing accessibility conformance with WCAG 2.1 Level A/AA. π #accessibility
legiscan.com/VA/text/HB25...
09.04.2025 16:32
π 0
π 0
π¬ 0
π 0
A quick word on tooltips - Because the tooltip itself never receives focus and is not in the tabbing order, a tooltip can not contain interactive elements like links, inputs, or buttons. #accessible #accessibility
07.04.2025 21:54
π 0
π 0
π¬ 0
π 0