pickpuck
Joined 12 years ago
Joined 12 years ago
There are a few ARIA "widgets" that have no HTML equivalent, such as Tabs or a spreadsheet-like Grid. Those are heavily documented so you can basically copy and paste whenever you need them.
Avoiding sprinkling ARIA on already-semantic HTML, because this can lead to confusing or inconsistent behaviors for the end user.
Remote: Yes
Willing to relocate: No
Technologies: TypeScript, React, React Native, Next.js, Node.js, TailwindCSS, AI/LLM integration, UI/UX, Figma, Design systems, WCAG accessibility, Lit.js, Web components
Résumé/CV: https://puckett.codes
Email: [email protected]
I'm a creative technologist with extensive experience building accessible, user-friendly digital products and tools. X-Apple. X-Google. 15+ years in tech.
Open to freelance work, employment, co-founder roles.
Just like here you could get a timeline of key events, a graph of connected entities, links to original documents.
Newsrooms might already do this internally idk.
This code might work as a foundation. I love that it's RDF.
Instead of a WASM backend, I used react-dom/server to generate the HTML.
https://github.com/michaelcpuckett/listleap?tab=readme-ov-fi...
You might consider the Accessibility Tree and its semantics. Plain divs are basically filtered out so you're left with interactive objects and some structural/layout cues.
https://www.goodreads.com/book/show/1616203.Word_Clues_Vocab...