I'm so proud of the https://w3c.github.io/hr-time/#sec-concepts section. Every time I see someone using a duration or "moment" in another spec, I imagine the "a number of milliseconds" it would have been before that new section, and smile. #bragging #WebStandards
Obvious that #AI has no experience of either #WebStandards or #depression
👀 🆕 in #HTML
<search> = #ARIA role=search
“The search element represents a part of a document or application that contains a set of form controls or other content related to performing a search or filtering operation. This could be a search of the web site or application; a way of searching or filtering search results on the current web page; or a global or Internet-wide search function.”
Drop focus appearance SC from #WCAG 2.2 = move to Recommendation in April 2023
Move focus appearance to AAA = re-enter CR and expected move to Rec. in June 2023
#accessibility @w3c #WebStandards
"Based on the survey and the call today, we agreed to move Focus Appearance to AAA."
#WCAG #a11y #WebStandards
You know I typically only take the piss out of @jaffathecake but I honestly really respect the work he and his team are doing on #viewTransitions
I don't even know if I care about the feature, but his dedication to the #webStandards process and immaculate communication of it is fucking admirable! #careerGoals
Do slippymaps next Jake!
>SPA view transitions land in Chrome 111 https://developer.chrome.com/blog/spa-view-transitions-land/
It's such a huge failure of the #webStandards bodies that slippy maps are STILL not a standardized part of the #webPlatform.
If #Google actually wanted to advance the #openWeb they'd standardize #googleMaps, but I'm certain they don't want to give up that #monopoly.
@brianleroux that's more of an "untraining" isn't it?
Do you think there is a market for web standards focused training?
Not necessarily counter to React/modern JS but rather as a path to building more performant, accessible and resilient applications. Maybe even starting w those tools and teaching how to migrate out.
we need more web focused conferences in north america.
any would be nice, in fact.
not react conferences. *web* conferences.
😍 Looks like aria-haspopup values will be supported in upcoming NVDA screen reader release 🎉
#accessibility #WebStandards #ARIA #UX #WebDev
Because our work w https://enhance.dev is based on a dynamic runtime process you can do things like talk to a database without spinners or API calls.
Inspired by Rails scaffold check out a modern approach to CRUDL with basic #webstandards like #html, #css and #js --in that order.
there is nothing quite like working through the admin portal of an insurance company
like a cold shower … the web we want and the one we get is quite a wide chasm to cross still today
I’m so excited about Chrome’s intent to ship `text-wrap: balance`!! 😱️
I have started contributing PR's to improve the @w3c #HTML Validator/Checker, you should too!
The @w3c launches a new beta website:
To mention one (important) reason why #Webkit, #Blink/#Chromium must implement Tabular model for #Ruby: Search and Copy.
Interleaved copy-paste: 韓 (한) (Han) 國 (국) (guk)
Tabular: 韓國 (한국) (Hanguk)
Testing #HTML & #CSS #Ruby annotation support in #Mozilla #Firefox, #Microsoft #Edge, and #Naver #Whale browsers. (The last two are #Chromium-based browsers.)
Ruby model used: Interleaved.
The preferred model is Tabular, which only Firefox currently supports.
Woke up at 2am (again) for a piss and read 2 rigorous reminders that I am in the audience of greatness:
#HTML #WebStandards #accessibility #browsers
📌 How Shadow DOM and accessibility are in conflict, by @sundress
📌 Safari 16.4 Is An Admission, by @slightlyoff
One advantage of having only one browser engine on iOS is that #webDevelopment is constrained only by the #webStandards support in a single engine.
One disadvantage of having only one browser engine on iOS is that #webDevelopment is constrained by the #WebStandards support of that single engine
The good folks at Logrocket let me on their podcast to talk about Enhance.
#webdev #webstandards #html #css #js
the LAST place I want to see a singe page app shudder into existence with a skeleton screen and jittering spinners is a BANK
nice take one Enhance herein:
New t-shirt design by @patrick_h_lauke
#browser #love #war #WebStandards
wrt to the inevitable difficult to swallow discourse around #react these days
"In offering one’s opinion, one must first ascertain whether or not the recipient is in the right frame of mind to receive counsel. … Remember though, how can you expect a man to become a better person just through humiliating him?" - Yamamoto Tsunetomo
💫 “aria-owns is surprisingly strong magic
aria-owns allows developers to restructure the parent-child relationships in the accessibility tree. This means that screen reader users may experience a different semantic structure and meaning to other users when they navigate and interact with content using their screen readers virtual/browse mode.”
#webDev #a11y #HTML #WebStandards
It's kind of sad to find out that some leaders of the #webstandards movement are also arrogant assholes.
General distribution I guess.
feels extra right starting with pure standards based html.
not markdown that compiles into html.
On W3C re-launch
"W3C has a long tradition of working to provide a web that supports participation by disabled people. This extends to participation by disabled people within W3C to develop the specifications and guidelines which improve accessibility. TPGi have been actively engaged for the past 15 years as Specification Editors, Working Group participants and Chairs, and we are committed and excited to actively participate in the W3C of the future."
trying to stay positive that team react is coming around to backend rendering aka 'ssr' after years of downplaying, gaslighting and outright hostility towards the proven practice
its tough, and I genuinely am unsure what the high road looks like here. good for them? cause it sure feels more like 🙄
@besenwagen 👋 Eric, #WebStandards work should come with a health warning. Anything I can do to provide support give me a yell!
If GitHub is to be believed there are 100M devs now. Up from 20M a decade ago.
I bet most are frontend devs. Or aspiring anyhow.
We need to start centering real web standards more now than ever. Not transpiling. Not dialects that compile. Or things will only get worse.
“WCAG SC 1.3.1:Info and Relationships is often cited as a reason why strong and em must be used and Technique H49:Using semantic markup to mark emphasized or special text provides examples of “Using the em and strong elements to emphasize text” In practice their use does nothing for screen reader users at least, nothing that the i and b elements don’t provide (with their default styles).”
#accessibility #WebDev #WebStandards #WCAG