Peter Goes

The Scaled Accessibility Model visualised. Mission and vision come through management. Practitioners are supported by a mandate and requirements from management, resources, goals and community and culture.

I am looking for a company that wants an accessibility at scale.

I do really really well with repeating booked days; weekly days focussed on specific companies. I don not have that right now, and that's not working well for my mental state. So:

I am looking for a company that wants accessibility f

Magistrale beelden van de Olympische Winterspelen. Timelapse meets double exposure www.gettyimages.nl/editorial-im... via @gettyimages.com

I switched to Proton for email, and Bunny CDN for my website hosting. Really happy so far

My top 5 out of 21 selected:

1. Invoker commands
2. Custom elements extend build ins via is attribute
3. HTML closeby on dialog
4. @container style()
5. Cross document view transitions

😇

Ow my... What is the direction of the Z axis? Am I looking down on a stack of devices (top = closest to my eyes) or am I at the bottom looking up?

#notAnUXExpert

(My pick would be the second most squared one)

I'm sorry, but I think you credited the wrong Peter Goes in your post. I am not an illustrator 🙂

How was your migration experience? Did you have dns through netlify?

Congrats dude!!

But yeah, I can see the business decision here as well

I understand. My initial assumption was, thus, not correct.

I still would prefer a dedicated dev version (closer to normal) over a beta / nightly 🙂

I am not sure what the difference is, but I assumed that the dev version is equal to the normal version but with better dev tools.

Beta or nightly have a different feature set. So I'd like to develop with the latest 'public' version to experience what users would experience.

It gives me a dedicated dev browser not being polluted by normal browsing habits / junk. A clear separation between dev extensions vs browsing extensions.

Would hate to see it discontinued if that is on the table

petergoes.nl

Closing thoughts: I think you are technically right, but that does not help me as a willing developer. It makes me less certain.

Maybe that is my main point. I find it so hard getting some guidance, that statements like "components can not be wcag ever" (paraphrasing here), feels like another hurtle where I thought I found some hand holds.

...standard, like the motor. But you are right that that usually is it's own standard.

(Thinking out loud here)

Since we don't have multiple standards, falling back to wcag feels like a proper way of doing things. It gives some form of direction. Which I find more helpful than nothing at all.

... What so ever, that component does not violate any SC's.

Except for the whole pages rule, it does not violate any other rule. Therefore it should be confirming to wcag.

About the washing machine, the argument was more for the manufacturing company. Individual components can confirm to a...

... Contains any media content, all SC's related to time based media do not apply, right?

So the concept of some SC's not applying to a webpage can be expanded to components.

Say I have a paragraph component with default styles giving it enough contrast and size, and no configuration...

Yes, I see your line of reasoning. And I am well aware of my little experience with the concept of standards as opposed to yours, so I don't want to come across as dismissive.

I would like to counter, though, that conformation with wcag is to not violate a SC, right? So if my site does not...

However, it does not mean that I, as the developer of the page/site, should not test my product as a whole, by only using wcag conforming components. I still have the ultimate responsibility of delivering an accessible product.

...that does not. And as a well-meaning developer, it's on me to read the manual and implement it right.

Which would be easier because a well-meaning component developer that is advertising wcag conformance, is likely to have proper documentation on how to implement it's component properly.

...not those of 1927. So the whole house does not confirm, but that reconstructed wall certainly does.

Allowing a component to conform to wcag (again, if properly implemented), will "Help well-meaning developers get it right".

I'd rather choose a component that advertised as conforming over one...

...it will break. That does not mean that the washing machine is not build according to some standard and have passed some tests.

The house I live in is almost 100 years old. When we bought it, we did some reconstruction on it. Those reconstructions were performed to the standards of 2016...

I think components should be able to claim that they, if implemented properly, conform to wcag.

IMHO the conformance requirement is outdated in respect to how modern front ends are constructed.

If I buy a washing machine, throw away the manual and load it beyond the specified weight...

Life hack: www.bol.com/nl/nl/p/lego... to get them in to it.

Mine is 8, the cool thing is, it is not dubbed in Dutch, so he has to read subtitles. Since the story telling is _much_ slower than current day productions, he can actually follow it.

Life goal achieved, watching #starwars A New Hope with my kid for the first time ☺️

Amit Sheen on CodePen

@syntax.fm you should challenge @amitsheen.bsky.social for a CSS Battle!

But check out his codepen before to make sure you are up for it.

He just blew us away here on #cssday

codepen.io/amit_sheen/

@ishadeed.com, do you think it is time to rebrand the term Responsive Design to Fluid Design? #cssday

Mixin test ...

@miriam.codes first thought about mixins after your talk at #cssday. A mixin to toggle a label with an icon based on a media query: codepen.io/petergoes/pe...

This could not have been done (without JS) when using a `.sr-only` class.

(might be with sass, but I prefer not to use a pre processer)