🆕 blog! “What about using rel="share-url" to expose sharing intents?”
Let's say that you've visited a website and want to share it with your friends. At the bottom of the article is a list of popular sharing destinations - Facebook, BlueSky, LinkedIn, Telegram, Reddit, HackerNews etc.
You click the relevant icon and get taken to the site with the…
I am not going to dive into the details of and . Go read Scott’s 2019 post How do you figure? for an overview. That said, since Scott’s post there has been movement on the AAPI mapping (partly by Scott).
I hate modern frontend with its #JavaScript frameworks zoo, with people not even wanting to learn semantic #HTML and making their disgusting design with two tags, <div> and <span>, like uneducated parrots knowing only two words. I totally understand why things like Turbo, Stimulus and HTMX exist, I wish they were more spread in the web though. Oh yeah, and I want a #backend job.
"I made the mistake in a recent article of using the placeholder attribute content to illustrate when a label is not correctly associated the text label does not provide an accessible name."
A: "Hey I just noticed that on your website, feature X doesn't work" B: "Oh really? Thanks for reporting we'll fix that"
a: "Hey I just noticed that on your website, feature X doesn't work for #screenreader users and hasn't for over a year" B: "It's very important to us and is on our roadmap, thanks for reporting baii"
If you work in, or need, #accessibility you'll be intimately familiar with this frankly embarrassing situation. If you're a #developer, let this be your trigger to educate yourself on the doubtless extensive docs your UI toolkit of choice (yes, that includes #react and #html) maintains on accessibility so you don't have to send that response and make a human being feel like they don't belong to society, because there's a non-zero chance that's EXACTLY how someone might read such a dismissal. I woke up to three such emails today and I think I'm done with advocacy today before even starting my day. Shit's depressing as all fuck. How's your day? :)
Always fun to read #hackerNews and their rather ... let's call it ... qualitatively exceedingly disappointing mentality towards #accessibility (stroopwafel to the dutchies who see what i did there). But some points do make me think to what degree, say, #screenReaders could be innovating more. One thing that stuck by me was a comment on an article regarding the use of "click here" that basically suggested some kind of heuristic for, say, reading the entire line of text when that's encountered, rather than the link text. Another one could be including the previous sibling's accessible name on unlabeled form fields which I ...think? JAWS might already be doing? Like obviously these should be toggleable to not screw up audits but I think after 30 years we can safely say people often can't be forked to learn #HTML basics and it might make some things smoother?
My employer, after 7 months of work, fired me overnight. Because I would be too "finicky" about code quality and security risks, which would better suit "a bank or cybersecurity company".
Sometimes you run into a main landmark where you don’t expect one. Like Main Street USA in Hong Kong Disney. So you grab a snack in a diner that serves no hot dogs.
🤔HTML semantics: <abbr> theory versus abbreviation reality
"The HTML <abbr> element is deceptively familiar and attractive, its been around forever (1999) and thus people assume that it does what it does and does it well. Nothing much changed over the iterations of the abbr element definition over the years."
I disagree with use cases that rely on CSS, generally at risk from network interruptions and caching, to trigger programmatic state changes in the HTML that references it (see pic). Cart / horse and all.
The CSS3 logo as a head atop a torso with its arms folded across its chest. I am a big proponent of the First Rule of ARIA (don’t use ARIA). But ARIA brings a lot to the table that HTML does not, such as complex widgets and state information that…
Wanna learn how to SCREAM or SING for free?Sign Up for our free four-part screaming or singing crash courses!Screaming ►►►http://bit.ly/Screaming101 Singin...
In my post Brief Note on Figure and Figcaption Support I demonstrate how, when encountering a figure with a screen reader, you won’t hear everything announced at once: No screen reader combo treats the caption as the accessible name nor accessible de…
Web developers don't know HTML; or at least they don't implement proper HTML (which is ridiculous; it's like a lawyer not knowing or applying the law). Just look at 4 of the top 5 web accessibility issues from the WebAIM Million. So frustrating, and for decades now...
Our core team is looking for a senior Front-end Developer to elevate the web UI/UX experience for our users.
Ideally:
1. You are highly skilled in accessible and semantic #HTML 2. Proficient in modern #CSS 3. Experienced with #Javascript, #Typescript and complex React/Redux applications
This remote full-time position requires a 4-hour overlap with the CET timezone.
I love to see coding tutorials like this make the coder code for accessibility by giving them examples and stating up front they do not treat accessibility as an afterthought write-on.org/html/ #CSS #WebDev #HTML #Accessibility #A11y
Even popular sites fail to implement the 11 best practices mentioned in this article, and thus have at least one mistake. Use this checklist on your next pull request review that deals with any form.
The four most popular ways to use RDF-based metadata on websites are RDFa-Core, RDFa-Lite, Microdata, and inline JSON-LD.
I can’t use RDFa-Lite because I need rel HTML attributes. rel silently upgrades RDFa-Lite to RDFa-Core, which parses differently. I doubt all parsers upgrade correctly; some will try to parse RDFa-Core as RDFa-Lite. Conformant RDFa parsers upgrade RDFa-Lite pages to RDFa-Core despite many authors only being familiar with RDFa-Lite. I suppose resources like Schema.org and Google’s documentation only documenting RDFa-Lite markup worsens the confusion. Update 2024-12-16: Sarven Capadisli has clarified on the Fediverse that this is the behavior of one faulty parser; rel only triggers an upgrade when used with an RDFa namespace. I may re-evaluate RDFa.
With RDFa split between two incompatible alternatives with a confusing upgrade mechanism, the alternatives are Microdata and JSON-LD. I use structured data extensively; JSON-LD would duplicate most of the page. Let’s use this relatively short article as an example. Exruct can convert the embedded Microdata into a massive JSON document featuring JSON-LD. Take a look at the JSON-LD and HTML side by side. Microdata attributes take a fraction of the footprint, encode the same information, and don’t require duplicating nearly the entire page.
Most JavaScript libraries offer a library of client-side widgets that mimic the behavior of familiar desktop interfaces. Sliders, menu bars, file list views, and more can be built with a combination of JavaScript, CSS, and HTML.
"My personal take on this is it sucks, as while the control is disabled for all, only for a subset of users (low vision) the text label for the disabled control is illegible."
I've told this story at conferences - but due to the general situation I thought I'd retell it here. A few years ago I was doing policy research in a housing benefits office in London. They are singularly unlovely places.
Semantic websites are awesome! Among other things, they let you write reusable CSS. Please send me your semantic websites, so I can analyze them for common patterns and write a composable CSS framework.
